Skip to content

Conversation

@sushanb
Copy link
Contributor

@sushanb sushanb commented Feb 24, 2022

Add incompatible mutation/dropped mutations for deletes at future timestamp

@sushanb sushanb requested a review from vermas2012 February 24, 2022 20:00
@sushanb sushanb requested a review from a team as a code owner February 24, 2022 20:00
@product-auto-label product-auto-label bot added the api: bigtable Issues related to the googleapis/java-bigtable-hbase API. label Feb 24, 2022
@sushanb sushanb changed the title add future delete handling feat: add future delete handling Feb 24, 2022
long currTime = EnvironmentEdgeManager.currentTime();

// test if delete is in future timestamp
if (CellUtil.isDelete(cell) && cell.getTimestamp() > currTime) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This does not sound right, we should check with WalWriteTime. In case of large replication delay, currentTime and WAL write time will differ, we want to make sure that delete was issued in future.

+ cell.getTimestamp()
+ "current time: "
+ currTime);
throw new UnsupportedOperationException("Unsupported future delete: " + cell);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not right, We do support future deletes. The issue with future deletes is around behavior of DeleteRow. We should not try to "fix" anything here. but just flag the potential change of behavior.

@vermas2012 vermas2012 deleted the branch googleapis:replication February 28, 2022 19:27
@vermas2012 vermas2012 closed this Feb 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api: bigtable Issues related to the googleapis/java-bigtable-hbase API.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants