hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zoltan Haindrich (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HIVE-18359) Extend grouping set limits from int to long
Date Tue, 09 Jan 2018 11:30:00 GMT

    [ https://issues.apache.org/jira/browse/HIVE-18359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16318209#comment-16318209
] 

Zoltan Haindrich edited comment on HIVE-18359 at 1/9/18 11:29 AM:
------------------------------------------------------------------

[~prasanth_j] that NPE seems to be a leftover bug after HIVE-17617; I've fixed it, but the
fix caused {{groupby_rollup_empty.q}} to break - I will most probably open a new ticket for
it...HIVE-18413


was (Author: kgyrtkirk):
[~prasanth_j] that NPE seems to be a leftover bug after HIVE-17617; I've fixed it, but the
fix caused {{groupby_rollup_empty.q}} to break - I will most probably open a new ticket for
it...

> 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
>
>
> 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)

Mime
View raw message