-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Enhance revertReplaceSegments api #8166
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
Conversation
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.
Can you put a fail after line 761 then please?
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.
+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.
@jtao15 Can we add fail() for all the places where we try{} catch{} ?
I think that we have a lot of tests like this and I remember that I didn't add fail().
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.
Added
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.
the currentLineageEntry here seems unnecessary?
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.
+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.
Removed.
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.
+1
snleee
left a comment
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.
LGTM otherwise
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.
+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.
@jtao15 Can we add fail() for all the places where we try{} catch{} ?
I think that we have a lot of tests like this and I remember that I didn't add fail().
...ntroller/src/main/java/org/apache/pinot/controller/helix/core/PinotHelixResourceManager.java
Outdated
Show resolved
Hide resolved
ba79980 to
c6f5acd
Compare
Codecov Report
@@ Coverage Diff @@
## master #8166 +/- ##
============================================
+ Coverage 71.36% 71.40% +0.04%
+ Complexity 4308 4307 -1
============================================
Files 1623 1623
Lines 84356 84365 +9
Branches 12654 12657 +3
============================================
+ Hits 60197 60245 +48
+ Misses 20023 19993 -30
+ Partials 4136 4127 -9
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
jackjlli
left a comment
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.
LGTM. Thanks for making the change!
...ntroller/src/main/java/org/apache/pinot/controller/helix/core/PinotHelixResourceManager.java
Outdated
Show resolved
Hide resolved
4e9ca3e to
61261e7
Compare
…g example is not allowed:
entry1: {Seg_0 -> Seg1, COMPLETED}
entry2: {Seg_1 -> Seg2, COMPLETED/IN_PROGRESS}
61261e7 to
2ce2f88
Compare
Enhance
revertReplaceSegmentsapi so reverting entry1 in the following example is not allowed:entry1:
{Seg_0 -> Seg1, COMPLETED}entry2:
{Seg_1 -> Seg2, COMPLETED/IN_PROGRESS}