-
Notifications
You must be signed in to change notification settings - Fork 15
[Transactions3/ABR] Need to abort at the put timestamp or higher #5847
Conversation
Generate changelog in
|
@@ -123,7 +124,6 @@ public Statement bindAbortStatement(PreparedStatement preparedAbortStatement, Tr | |||
BoundStatement bound = preparedAbortStatement.bind(rowKeyBb, columnNameBb, valueBb); | |||
return bound.setConsistencyLevel(ConsistencyLevel.QUORUM) | |||
.setSerialConsistencyLevel(ConsistencyLevel.SERIAL) | |||
.setDefaultTimestamp(CellValuePutter.SET_TIMESTAMP + 1) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From javadoc of Statement#setDefaultTimestamp(long)
:
* <p>Note that unlike other configuration, when this statement is prepared {@link
* BoundStatement}s created off of {@link PreparedStatement} do not inherit this configuration.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It doesn't seem like this should apply, given that we set it on the bound statement already
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I certainly hope this fixes it
also need to handle STAGING (can be separate pr) |
It already works with STAGING? |
Goals (and why):
Implementation Description (bullets):
Testing (What was existing testing like? What have you done to improve it?):
Concerns (what feedback would you like?):
to investigate: this looks like it's set lower down, why doesn't it work already?
Where should we start reviewing?: small
Priority (whenever / two weeks / yesterday): this week please, blocks transactions3 and ABR rollouts!