-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Add ability to skip loadSpec,dimensions, metrics from DataSegment Announcements #2784
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -37,6 +37,18 @@ public class BatchDataSegmentAnnouncerConfig | |
| @Min(1024) | ||
| private long maxBytesPerNode = 512 * 1024; | ||
|
|
||
| // Skip LoadSpec from segment announcements | ||
| @JsonProperty | ||
| private boolean skipLoadSpec = false; | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. does removing loadspec have any impact on the information that the coordinator exposes via endpoints?
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. coordinator has end point for getting info for a particular segmentId which includes loadSpec too. |
||
|
|
||
| // Skip dimension list from segment announcements | ||
| @JsonProperty | ||
| private boolean skipDimensions = false; | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. do we need separate configs for dimensions and metrics? Is there any use in having one but not the other?
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. added separate config in case someone has any tools built on top which needs metrics list and not dimensions list or vice versa.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. does it actually make sense to have one but not the other?
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. created #2821 for follow up. |
||
|
|
||
| // Skip metrics list from segment announcements | ||
| @JsonProperty | ||
| private boolean skipMetrics = false; | ||
|
|
||
| public int getSegmentsPerNode() | ||
| { | ||
| return segmentsPerNode; | ||
|
|
@@ -46,4 +58,19 @@ public long getMaxBytesPerNode() | |
| { | ||
| return maxBytesPerNode; | ||
| } | ||
|
|
||
| public boolean isSkipLoadSpec() | ||
| { | ||
| return skipLoadSpec; | ||
| } | ||
|
|
||
| public boolean isSkipDimensions() | ||
| { | ||
| return skipDimensions; | ||
| } | ||
|
|
||
| public boolean isSkipMetrics() | ||
| { | ||
| return skipMetrics; | ||
| } | ||
| } | ||
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.
these wil need to be documented
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 docs