[
https://issues.apache.org/jira/browse/DRILL-6310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16528209#comment-16528209
]
ASF GitHub Bot commented on DRILL-6310:
---------------------------------------
Ben-Zvi commented on a change in pull request #1324: DRILL-6310: limit batch
size for hash aggregate
URL: https://github.com/apache/drill/pull/1324#discussion_r199274859
##########
File path:
exec/java-exec/src/main/java/org/apache/drill/exec/physical/impl/common/HashTableTemplate.java
##########
@@ -684,7 +694,7 @@ public PutStatus put(int incomingRowIdx, IndexPointer
htIdxHolder, int hashCode,
}
htIdxHolder.value = currentIdx;
return addedBatch ? PutStatus.NEW_BATCH_ADDED :
- (freeIndex + 1 > (batchHolders.size() * BATCH_SIZE)) ?
+ (freeIndex + 1 > totalIndexSize) ?
Review comment:
Problem: The original code "overflew" the (64K - 1) by adding one, hence
this check returned KEY_ADDED_LAST, which signaled to the caller that a batch
just got filled -- a good opportunity to check if need to spill (since a new
batch would surely be allocated soon).
By going below 64K, this would not work, hence the code misses on some of
the checks of "is spill needed now".
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> limit batch size for hash aggregate
> -----------------------------------
>
> Key: DRILL-6310
> URL: https://issues.apache.org/jira/browse/DRILL-6310
> Project: Apache Drill
> Issue Type: Improvement
> Components: Execution - Flow
> Affects Versions: 1.13.0
> Reporter: Padma Penumarthy
> Assignee: Padma Penumarthy
> Priority: Major
> Fix For: 1.14.0
>
>
> limit batch size for hash aggregate based on memory.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
