0.9.2 groupBy v2 Strategy problem

[Zhenyuan Gao]

Hi, I update to 0.9.2 version.

1. set broker 

druid.query.groupBy.defaultStrategy=v2

druid.query.groupBy.maxMergingDictionarySize=100000000

druid.query.groupBy.maxOnDiskStorage=2000000000

druid.processing.numMergeBuffers=1

2. set historical

druid.query.groupBy.defaultStrategy=v2

druid.query.groupBy.maxMergingDictionarySize=100000000

druid.query.groupBy.maxOnDiskStorage=2000000000

druid.processing.numMergeBuffers=1

3. set query context 

"context": {

      "groupByStrategy" : "v2"

 }

But the result version is still v1, is this right? how can I verify the version of groupBy Strategy. Another question is server config, should I config both broker and  historical？

[Gian Merlino]

The result format is identical in groupBy v1 and v2, to make migration easier. The "version": "v1" in the returned results is actually _not_ referring to the strategy but it's referring to the result format, which hasn't changed. Usually you can tell the difference between the engines by running the same query repeatedly with "v1" and "v2" strategies (by changing the query context) and measuring the response times. On most setups you should see a measurable difference between the strategies.

Actually, there's no need to set druid.query.groupBy.defaultStrategy on the historical; the config on the broker controls what gets used. And they all get overridden by the query context.

Gian

--
You received this message because you are subscribed to the Google Groups "Druid User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to druid-user+unsubscribe@googlegroups.com.
To post to this group, send email to druid...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-user/51cf1b74-374d-4622-8c2f-6dc34d85baa8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Zhenyuan Gao]

Thanks

在 2016年12月9日星期五 UTC+8上午12:14:52，Gian Merlino写道：

The result format is identical in groupBy v1 and v2, to make migration easier. The "version": "v1" in the returned results is actually _not_ referring to the strategy but it's referring to the result format, which hasn't changed. Usually you can tell the difference between the engines by running the same query repeatedly with "v1" and "v2" strategies (by changing the query context) and measuring the response times. On most setups you should see a measurable difference between the strategies.

Actually, there's no need to set druid.query.groupBy.defaultStrategy on the historical; the config on the broker controls what gets used. And they all get overridden by the query context.

Gian

On Thu, Dec 8, 2016 at 1:41 AM, Zhenyuan Gao <cn.er...@gmail.com> wrote:

Hi, I update to 0.9.2 version.

1. set broker 

druid.query.groupBy.defaultStrategy=v2

druid.query.groupBy.maxMergingDictionarySize=100000000

druid.query.groupBy.maxOnDiskStorage=2000000000

druid.processing.numMergeBuffers=1

2. set historical

druid.query.groupBy.defaultStrategy=v2

druid.query.groupBy.maxMergingDictionarySize=100000000

druid.query.groupBy.maxOnDiskStorage=2000000000

druid.processing.numMergeBuffers=1

3. set query context 

"context": {

      "groupByStrategy" : "v2"

 }

But the result version is still v1, is this right? how can I verify the version of groupBy Strategy. Another question is server config, should I config both broker and  historical？

--
You received this message because you are subscribed to the Google Groups "Druid User" group.

To unsubscribe from this group and stop receiving emails from it, send an email to druid-user+...@googlegroups.com.