Skip to content

SegmentMetadataQuery: Fix default interval handling.#5489

Merged
gianm merged 2 commits intoapache:masterfrom
gianm:fix-smq-filter-segments
Mar 15, 2018
Merged

SegmentMetadataQuery: Fix default interval handling.#5489
gianm merged 2 commits intoapache:masterfrom
gianm:fix-smq-filter-segments

Conversation

@gianm
Copy link
Copy Markdown
Contributor

@gianm gianm commented Mar 14, 2018

PR #4131 introduced a new copy builder for segmentMetadata that did
not retain the value of usingDefaultInterval. This led to it being
dropped and the default-interval handling not working as expected.
Instead of using the default 1 week history when intervals are not
provided, the segmentMetadata query would query all segments,
incurring an unexpected performance hit.

This patch fixes the bug and adds a test for the copy builder.

@gianm gianm added the Bug label Mar 14, 2018
@gianm gianm force-pushed the fix-smq-filter-segments branch 2 times, most recently from d18b526 to f5d09a7 Compare March 14, 2018 21:57
PR apache#4131 introduced a new copy builder for segmentMetadata that did
not retain the value of usingDefaultInterval. This led to it being
dropped and the default-interval handling not working as expected.
Instead of using the default 1 week history when intervals are not
provided, the segmentMetadata query would query _all_ segments,
incurring an unexpected performance hit.

This patch fixes the bug and adds a test for the copy builder.
Copy link
Copy Markdown
Contributor

@jihoonson jihoonson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 after CI.

@gianm gianm force-pushed the fix-smq-filter-segments branch from f5d09a7 to 6d50118 Compare March 14, 2018 23:09
@gianm gianm merged commit 16b81fc into apache:master Mar 15, 2018
@gianm gianm deleted the fix-smq-filter-segments branch March 15, 2018 17:06
gianm added a commit to implydata/druid-public that referenced this pull request Mar 15, 2018
* SegmentMetadataQuery: Fix default interval handling.

PR apache#4131 introduced a new copy builder for segmentMetadata that did
not retain the value of usingDefaultInterval. This led to it being
dropped and the default-interval handling not working as expected.
Instead of using the default 1 week history when intervals are not
provided, the segmentMetadata query would query _all_ segments,
incurring an unexpected performance hit.

This patch fixes the bug and adds a test for the copy builder.

* Intervals
gianm added a commit to implydata/druid-public that referenced this pull request Mar 15, 2018
* SegmentMetadataQuery: Fix default interval handling.

PR apache#4131 introduced a new copy builder for segmentMetadata that did
not retain the value of usingDefaultInterval. This led to it being
dropped and the default-interval handling not working as expected.
Instead of using the default 1 week history when intervals are not
provided, the segmentMetadata query would query _all_ segments,
incurring an unexpected performance hit.

This patch fixes the bug and adds a test for the copy builder.

* Intervals
@gianm gianm added this to the 0.12.1 milestone Apr 9, 2018
gianm added a commit to gianm/druid that referenced this pull request Apr 9, 2018
* SegmentMetadataQuery: Fix default interval handling.

PR apache#4131 introduced a new copy builder for segmentMetadata that did
not retain the value of usingDefaultInterval. This led to it being
dropped and the default-interval handling not working as expected.
Instead of using the default 1 week history when intervals are not
provided, the segmentMetadata query would query _all_ segments,
incurring an unexpected performance hit.

This patch fixes the bug and adds a test for the copy builder.

* Intervals
fjy pushed a commit that referenced this pull request Apr 10, 2018
* SegmentMetadataQuery: Fix default interval handling.

PR #4131 introduced a new copy builder for segmentMetadata that did
not retain the value of usingDefaultInterval. This led to it being
dropped and the default-interval handling not working as expected.
Instead of using the default 1 week history when intervals are not
provided, the segmentMetadata query would query _all_ segments,
incurring an unexpected performance hit.

This patch fixes the bug and adds a test for the copy builder.

* Intervals
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants