[
https://issues.apache.org/jira/browse/DRILL-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16014752#comment-16014752
]
ASF GitHub Bot commented on DRILL-5457:
---------------------------------------
Github user paul-rogers commented on a diff in the pull request:
https://github.com/apache/drill/pull/822#discussion_r117102340
--- Diff:
exec/java-exec/src/main/java/org/apache/drill/exec/ExecConstants.java ---
@@ -86,6 +92,19 @@
BooleanValidator EXTERNAL_SORT_DISABLE_MANAGED_OPTION = new
BooleanValidator("exec.sort.disable_managed", false);
+ // Hash Aggregate Options
+
+ String HASHAGG_NUM_PARTITIONS_KEY = "drill.exec.hashagg.num_partitions";
--- End diff --
For config options, the path is usually "drill.exec.something". But, for
system/session options, there is no need for the top "drill." namespace, so
they usually are of the form "exec.something" or even shorter. Check out some
of the other names and you'll see the pattern.
Or, am I confused? Normally, the option name appears as "key", then a
validator, using that name, appears below. But, in the validator, we have a
different name (one that does, in fact, follow the usual option rules.) So, we
we have both a config and a system/session option?
> Support Spill to Disk for the Hash Aggregate Operator
> -----------------------------------------------------
>
> Key: DRILL-5457
> URL: https://issues.apache.org/jira/browse/DRILL-5457
> Project: Apache Drill
> Issue Type: Improvement
> Components: Execution - Relational Operators
> Affects Versions: 1.10.0
> Reporter: Boaz Ben-Zvi
> Assignee: Boaz Ben-Zvi
> Fix For: 1.11.0
>
>
> Support gradual spilling memory to disk as the available memory gets too
> small to allow in memory work for the Hash Aggregate Operator.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
