[
https://issues.apache.org/jira/browse/CALCITE-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16236679#comment-16236679
]
JD Zheng commented on CALCITE-1436:
-----------------------------------
I'd love to contribute. Given the nature of this bug (a member of a class is
accessed before it is initialized), it seems that the bindable code path is
very immature. I am not sure if I should fix the exact bug or rather make the
druid adapter use the enumerable convention. It'll be very helpful if someone
can explain me the difference between bindable convention and enumerable
convention and why we have both.
> AggregateNode NPE for aggregators other than SUM/COUNT
> ------------------------------------------------------
>
> Key: CALCITE-1436
> URL: https://issues.apache.org/jira/browse/CALCITE-1436
> Project: Calcite
> Issue Type: Bug
> Components: core
> Reporter: Gian Merlino
> Assignee: Julian Hyde
> Priority: Major
>
> AggregateNode.getAccumulator does this for any aggregation other than COUNT
> or SUM:
> final AggImpState agg = new AggImpState(0, call, false);
> int stateSize = agg.state.size();
> This NPEs because "state" is null on freshly created AggImpState instances.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
