Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IGNITE-17968 Fix write-intents being filtered out in case if it's a tombstone #1252

Merged
merged 3 commits into from
Oct 26, 2022

Conversation

SammyVimes
Copy link
Contributor

Copy link
Contributor

@rpuch rpuch left a comment

Choose a reason for hiding this comment

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

  1. Let's add clarifications to #scan() javadocs: when exactly tombstones might be returned by a scan
  2. Does read() have same properties (like 'interpreting only not-yet-committed tombstones')? Do we have tests about this property? If read() behaves differently from scan() in this regard, we probably need to note this in javadocs on both methods.

@SammyVimes SammyVimes merged commit c65c306 into main Oct 26, 2022
ivgag pushed a commit to unisonteam/ignite-3 that referenced this pull request Nov 4, 2022
lowka pushed a commit to gridgain/apache-ignite-3 that referenced this pull request Mar 18, 2023
lowka pushed a commit to gridgain/apache-ignite-3 that referenced this pull request Apr 19, 2023
@SammyVimes SammyVimes deleted the ignite-17968 branch June 28, 2023 07:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants