@Retention(value=RUNTIME) @Target(value=METHOD) @Inherited public @interface SProcCall
| Modifier and Type | Optional Element and Description |
|---|---|
long |
adivsoryLockId |
String |
adivsoryLockName |
String |
name |
boolean |
parallel
run sproc on multiple shards in parallel?
|
boolean |
readOnly
flag this stored procedure call as read only: read only sprocs may run in cases were writing calls would not be
allowed (maintenance, migration, ..)
|
Class<?> |
resultMapper |
boolean |
runOnAllShards
whether the stored procedure should be called on all shards --- results are concatenated together.
|
boolean |
searchShards
whether the stored procedure should be called on all shards --- return the first result found.
|
SProcCall.WriteTransaction |
shardedWriteTransaction
Defines how sharded writes will be handled.
|
Class<?> |
shardStrategy |
String |
sql |
long |
timeoutInMilliSeconds |
SProcCall.Validate |
validate |
public abstract String name
public abstract String sql
public abstract Class<?> shardStrategy
public abstract boolean runOnAllShards
public abstract boolean searchShards
public abstract boolean parallel
public abstract boolean readOnly
public abstract SProcCall.WriteTransaction shardedWriteTransaction
SProcCall.WriteTransaction.NONE, no transaction context will
be created. If set to SProcCall.WriteTransaction.ONE_PHASE, all errors during the sproc call will be rolled back.
If set to SProcCall.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).public abstract Class<?> resultMapper
public abstract String adivsoryLockName
public abstract SProcCall.Validate validate
Copyright © 2012–2022 Zalando SE. All rights reserved.