SegmentMetadataQuery support for returning aggregators.#2295
SegmentMetadataQuery support for returning aggregators.#2295fjy merged 1 commit intoapache:masterfrom
Conversation
There was a problem hiding this comment.
is it never possible to have any overlap here?
There was a problem hiding this comment.
Different rows in different segments count as two rows, so there can't be overlap
There was a problem hiding this comment.
nvm, this is just copied from deleted code
|
👍 |
c9bc98d to
776981f
Compare
|
hmm, one thing I did in this patch is make null + something = something, rather than null. The idea was that for users that have Metadata.merge on the other hand treats null + something = null. maybe that difference is confusing and I should change it. Or maybe it should be an option. any thoughts anyone? |
|
OK I changed it |
|
actually I'm gonna add a flag to make both modes possible. will reopen. |
c8309fb to
b09848f
Compare
|
reopened with |
b09848f to
8f2bcb9
Compare
There was a problem hiding this comment.
why not just make this an empty list? easier to read the following code
There was a problem hiding this comment.
oh, you might rely on newIntervals to be a null for a check later on I guess
|
Still 👍 |
There was a problem hiding this comment.
not all aggregators might implement equals() correctly, we should probably put a comment here saying this is best-effort only.
|
👍 besides #2295 (comment) lenient merging is ok for the UI usecase (also its configurable so doesn't really matter for other use cases) |
8f2bcb9 to
f2c7cdb
Compare
f2c7cdb to
d416279
Compare
|
rebased against master |
…data SegmentMetadataQuery support for returning aggregators.
No description provided.