Deprecate instanceId Config For Broker/Minion Specific Configs#9308
Deprecate instanceId Config For Broker/Minion Specific Configs#9308Jackie-Jiang merged 4 commits intoapache:masterfrom
Conversation
Codecov Report
@@ Coverage Diff @@
## master #9308 +/- ##
============================================
+ Coverage 63.64% 69.70% +6.05%
- Complexity 4984 5060 +76
============================================
Files 1809 1882 +73
Lines 96993 100177 +3184
Branches 14832 15232 +400
============================================
+ Hits 61735 69831 +8096
+ Misses 30707 25397 -5310
- Partials 4551 4949 +398
Flags with carried forward coverage won't be shown. Click here to find out more.
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Jackie-Jiang
left a comment
There was a problem hiding this comment.
We can deprecate instanceId
Currently controller and server is using pinot.<type>.instance.id as the key, I'd suggest making broker and minion following the same pattern to be consistent
pinot-broker/src/main/java/org/apache/pinot/broker/broker/helix/BaseBrokerStarter.java
Outdated
Show resolved
Hide resolved
pinot-minion/src/main/java/org/apache/pinot/minion/MinionConf.java
Outdated
Show resolved
Hide resolved
@Jackie-Jiang : We might need to deprecate pinot.broker.id as well in that case. Is that okay? |
@ankitsultana Per the current logic, I think we can directly modify the |
|
The field is read in But you are right, I took a look and both of these classes get the value from the one set by |
|
@Jackie-Jiang : Updated. One of the integration tests is failing with a "ServerSegmentMissing" error. Not sure if it is related. |
Jackie-Jiang
left a comment
There was a problem hiding this comment.
LGTM. Let me re-run the failed test
fixes #9290
I felt it might be best to mark instanceId as deprecated and create a new config for Minion ID. Lmk your thoughts.
cc: @Jackie-Jiang