-
Notifications
You must be signed in to change notification settings - Fork 3.4k
HBASE-28328 Add an option to count different types of Delete Markers in RowCounter #6435
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
Merged
Merged
Changes from all commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
8b9787c
Added feature to count delete markers in RowCounter.
fa10771
Put all new features under the flag for correct working.
0cb98d8
Added UT.
972d3b7
Fixed style.
db72e7c
Fixed style by applying spotless plugin.
f2e9886
Removed banned dependency and used shaded one.
f3db2d5
Removed annotation.
1240594
Fixed test.
5754e53
Changed filter behaviour for the scan in case of --countDeleteMarkers…
0e69048
Applied spotless plugin.
7f1d9ba
Altered postion of setting conf property.
1904ed6
Added more test coverage for all types of delete markers.
478ead4
Removed pom change.
3b103ef
Added UT for range row case.
9476622
Added annotation.
f4a1b12
Merge branch 'apache:master' into HBASE-28328
shubham-roy File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
this doesnot look necessary, we have been validating counters with following logic for existing tests. Please update tests to take a similar approach:
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.
@NihalJain, the method
runCreateSubmittableJobWithArgsinternally callsRowCounter.createSubmittableJob(TEST_UTIL.getConfiguration(), args). However, the methodcreateSubmittableJobis marked for deprecation - code link. So ideally, I believe (please correct me if I am wrong), we should not be making a change to that method. To use that method, we have to change the scan behaviour based on the flag.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.
Hey @shubham-roy I mean we could rewriten a helper in tests similar to above example method
runCreateSubmittableJobWithArgsand make assertions. IMO we should try to get rid of deprecated API as another task than mixing implementations and doing same thing in different ways at different places.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.
@NihalJain , don't you think that the access to the job object via a getter method (which I exposed) could be a good starting point to getting rid of the deprecated method
createSubmittableJob. I already used it in a way that could be easily extended to other use cases as well. LMK what do you think.Uh oh!
There was an error while loading. Please reload this page.
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.
Sure but I would prefer to do that as another cleanup task for separation of concerns
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.
@NihalJain , I agree and I am also not touching any of the other tests. I just used whatever is needed for my testing in an extensible way. Fixing of remaining tests can be taken up as a separate cleanup task.
Uh oh!
There was an error while loading. Please reload this page.
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.
will leave this upto others as i am still not convinced. +0 from me.
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.
@virajjasani , can you please have a look at this thread and let us know of your thoughts on the same?