-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
In SegmentPurger, use table config to generate the segment #5325
In SegmentPurger, use table config to generate the segment #5325
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.
LGTM. Thank you for working on this!
@@ -39,7 +41,7 @@ public static MinionContext getInstance() { | |||
|
|||
private File _dataDir; | |||
private MinionMetrics _minionMetrics; | |||
private String _minionVersion; | |||
private ZkHelixPropertyStore<ZNRecord> _helixPropertyStore; |
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 for this!
I thought of fetching table config calling controller API. This approach is much simpler :)
|
All the indexing and partition info are stored in the table config. Without the table config, purged segment will lose the indexing and partition info, which could cause performance issue. In the following pr, we will enforce all segment creation to provide table config and schema to guarantee the consistent behavior.
df1f03f
to
4db2ecd
Compare
Yeah, need to modify the test to plug in the property store |
Codecov Report
@@ Coverage Diff @@
## master #5325 +/- ##
==========================================
- Coverage 66.07% 56.85% -9.23%
==========================================
Files 1072 1072
Lines 54562 54552 -10
Branches 8139 8137 -2
==========================================
- Hits 36052 31015 -5037
- Misses 15865 21105 +5240
+ Partials 2645 2432 -213
Continue to review full report at Codecov.
|
All the indexing and partition info are stored in the table config.
Without the table config, purged segment will lose the indexing and partition info, which could cause performance issue.
In the following pr, we will enforce all segment creation to provide table config and schema to guarantee the consistent behavior.