[
https://issues.apache.org/jira/browse/HIVE-18359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16322261#comment-16322261
]
Zoltan Haindrich commented on HIVE-18359:
-----------------------------------------
I was unable to create a test for this - ( {{hasOutput}} has nothing to do with
the probably already sent summary row to reducer 2); while reducer1 ends up
with 0 records; so I think we probably have an issue here ...
To implement {{mapperIsAbsent}} I think the best would be to check for the
{{eventCounter}} being {{0}} of {{RuntimeTask}} but that's not accessible
because {{tezContext.getTezProcessorContext().runtimeTask}} is not accessible
(without reflection) ; runTimeTask would have great method:
{{getEventCounter()}}...
> Extend grouping set limits from int to long
> -------------------------------------------
>
> Key: HIVE-18359
> URL: https://issues.apache.org/jira/browse/HIVE-18359
> Project: Hive
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Prasanth Jayachandran
> Assignee: Prasanth Jayachandran
> Attachments: HIVE-18359.1.patch, HIVE-18359.2.patch,
> HIVE-18359.3.patch, HIVE-18359.4.patch, HIVE-18359.5.patch
>
>
> Grouping sets is broken for >32 columns because of usage of Int for bitmap
> (also GROUPING__ID virtual column). This assumption breaks grouping
> sets/rollups/cube when number of participating aggregation columns is >32.
> The easier fix would be extend it to Long for now. The correct fix would be
> to use BitSets everywhere but that would require GROUPING__ID column type to
> binary which will make predicates on GROUPING__ID difficult to deal with.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
