Package org.zalando.sprocwrapper
Annotation Type SProcCall
-
@Retention(RUNTIME) @Target(METHOD) @Inherited public @interface SProcCall
- Author:
- jmussler
-
-
Optional Element Summary
Optional Elements Modifier and Type Optional Element Description longadivsoryLockIdStringadivsoryLockNameStringnamebooleanparallelrun sproc on multiple shards in parallel?booleanreadOnlyflag this stored procedure call as read only: read only sprocs may run in cases were writing calls would not be allowed (maintenance, migration, ..)Class<?>resultMapperbooleanrunOnAllShardswhether the stored procedure should be called on all shards --- results are concatenated together.booleansearchShardswhether the stored procedure should be called on all shards --- return the first result found.SProcCall.WriteTransactionshardedWriteTransactionDefines how sharded writes will be handled.Class<?>shardStrategyStringsqllongtimeoutInMilliSecondsSProcCall.Validatevalidate
-
-
-
Element Detail
-
name
String name
- Default:
- ""
-
-
-
sql
String sql
- Default:
- ""
-
-
-
shardStrategy
Class<?> shardStrategy
- Default:
- java.lang.Void.class
-
-
-
shardedWriteTransaction
SProcCall.WriteTransaction shardedWriteTransaction
Defines how sharded writes will be handled. If set toSProcCall.WriteTransaction.NONE, no transaction context will be created. If set toSProcCall.WriteTransaction.ONE_PHASE, all errors during the sproc call will be rolled back. If set toSProcCall.WriteTransaction.TWO_PHASE, all errors during sproc call and "prepare transaction" are rolled back. In the last case, the Postgres instance must be configured to manage 2-phase-commits (XA).- Default:
- org.zalando.sprocwrapper.SProcCall.WriteTransaction.USE_FROM_SERVICE
-
-
-
resultMapper
Class<?> resultMapper
- Default:
- java.lang.Void.class
-
-
-
adivsoryLockName
String adivsoryLockName
- Default:
- "NO_LOCK"
-
-
-
validate
SProcCall.Validate validate
- Default:
- org.zalando.sprocwrapper.SProcCall.Validate.AS_DEFINED_IN_SERVICE
-
-