leventov commented on issue #7571: Optimize coordinator API to retrieve
segments with overshadowed status
URL:
https://github.com/apache/incubator-druid/issues/7571#issuecomment-497019287
> I think the cleanest way to deal with this concern is to keep
SegmentWithOvershadowedStatus as a
leventov commented on issue #7571: Optimize coordinator API to retrieve
segments with overshadowed status
URL:
https://github.com/apache/incubator-druid/issues/7571#issuecomment-497018916
There can be a separate method `allDataAndOvershadowedStatusEquals()` in
leventov commented on issue #7571: Optimize coordinator API to retrieve
segments with overshadowed status
URL:
https://github.com/apache/incubator-druid/issues/7571#issuecomment-497018429
> should it consider a DataSegment instance and a
SegmentWithOvershadowedStatus instance as equal or
leventov commented on issue #7571: Optimize coordinator API to retrieve
segments with overshadowed status
URL:
https://github.com/apache/incubator-druid/issues/7571#issuecomment-496595306
Another problem with wrapper `SegmentWithOvershadowedStatus` is network
overhead: even in compressed
leventov commented on issue #7571: Optimize coordinator API to retrieve
segments with overshadowed status
URL:
https://github.com/apache/incubator-druid/issues/7571#issuecomment-496594002
> The wrapper object approach allows `DataSegment` objects to always be
shared
I realized
leventov commented on issue #7571: Optimize coordinator API to retrieve
segments with overshadowed status
URL:
https://github.com/apache/incubator-druid/issues/7571#issuecomment-496264473
Regarding interning - we have to get rid of them anyway: #7395 explains,
how. If a segment first
leventov commented on issue #7571: Optimize coordinator API to retrieve
segments with overshadowed status
URL:
https://github.com/apache/incubator-druid/issues/7571#issuecomment-495738096
@jihoonson the concurrency discussion started here:
leventov commented on issue #7571: Optimize coordinator API to retrieve
segments with overshadowed status
URL:
https://github.com/apache/incubator-druid/issues/7571#issuecomment-495288920
@jihoonson
> This sounds like going back to feature-based release instead of time-based
one.
leventov commented on issue #7571: Optimize coordinator API to retrieve
segments with overshadowed status
URL:
https://github.com/apache/incubator-druid/issues/7571#issuecomment-494443286
Added to 0.15 milestone because If `SegmentWithOvershadowedStatus` will leak
into Druid 0.15 API, it
leventov commented on issue #7571: Optimize coordinator API to retrieve
segments with overshadowed status
URL:
https://github.com/apache/incubator-druid/issues/7571#issuecomment-488332781
Probably all fields of `DataSegment` (except `overshadowed`) should remain
final to avoid
leventov commented on issue #7571: Optimize coordinator API to retrieve
segments with overshadowed status
URL:
https://github.com/apache/incubator-druid/issues/7571#issuecomment-488330261
@surekhasaharan
> So are we saying make DataSegment mutable and add a setter for
11 matches
Mail list logo