disable group by config applyLimitPushDownToSegment by default (#9711)

* disable group by config applyLimitPushDownToSegment by default

* document
This commit is contained in:
Clint Wylie 2020-04-16 03:03:35 -07:00 committed by GitHub
parent 42590ae64b
commit b89ad49396
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 6 additions and 4 deletions

View File

@ -414,7 +414,7 @@ Supported runtime properties:
|`druid.query.groupBy.forceHashAggregation`|Force to use hash-based aggregation.|false|
|`druid.query.groupBy.intermediateCombineDegree`|Number of intermediate nodes combined together in the combining tree. Higher degrees will need less threads which might be helpful to improve the query performance by reducing the overhead of too many threads if the server has sufficiently powerful cpu cores.|8|
|`druid.query.groupBy.numParallelCombineThreads`|Hint for the number of parallel combining threads. This should be larger than 1 to turn on the parallel combining feature. The actual number of threads used for parallel combining is min(`druid.query.groupBy.numParallelCombineThreads`, `druid.processing.numThreads`).|1 (disabled)|
|`druid.query.groupBy.applyLimitPushDownToSegment`|If Broker pushes limit down to queryable nodes (historicals, peons) then limit results during segment scan.|true (enabled)|
|`druid.query.groupBy.applyLimitPushDownToSegment`|If Broker pushes limit down to queryable data server (historicals, peons) then limit results during segment scan. If typically there are a large number of segments taking part in a query on a data server, this setting may counterintuitively reduce performance if enabled.|false (disabled)|
Supported query contexts:

View File

@ -80,7 +80,7 @@ public class GroupByQueryConfig
private boolean forcePushDownLimit = false;
@JsonProperty
private boolean applyLimitPushDownToSegment = true;
private boolean applyLimitPushDownToSegment = false;
@JsonProperty
private boolean forcePushDownNestedQuery = false;

View File

@ -56,6 +56,7 @@ public class GroupByQueryConfigTest
Assert.assertEquals(4, config.getMaxOnDiskStorage());
Assert.assertEquals(5, config.getMaxMergingDictionarySize());
Assert.assertEquals(6.0, config.getBufferGrouperMaxLoadFactor(), 0.0);
Assert.assertFalse(config.isApplyLimitPushDownToSegment());
}
@Test
@ -78,6 +79,7 @@ public class GroupByQueryConfigTest
Assert.assertEquals(4, config2.getMaxOnDiskStorage());
Assert.assertEquals(5, config2.getMaxMergingDictionarySize());
Assert.assertEquals(6.0, config2.getBufferGrouperMaxLoadFactor(), 0.0);
Assert.assertFalse(config2.isApplyLimitPushDownToSegment());
}
@Test
@ -95,7 +97,7 @@ public class GroupByQueryConfigTest
"maxOnDiskStorage", 0,
"maxResults", 2,
"maxMergingDictionarySize", 3,
"applyLimitPushDownToSegment", false
"applyLimitPushDownToSegment", true
)
)
.build()
@ -109,6 +111,6 @@ public class GroupByQueryConfigTest
Assert.assertEquals(0, config2.getMaxOnDiskStorage());
Assert.assertEquals(3, config2.getMaxMergingDictionarySize());
Assert.assertEquals(6.0, config2.getBufferGrouperMaxLoadFactor(), 0.0);
Assert.assertFalse(config2.isApplyLimitPushDownToSegment());
Assert.assertTrue(config2.isApplyLimitPushDownToSegment());
}
}