[
https://issues.apache.org/jira/browse/HIVE-9397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14302848#comment-14302848
]
Navis commented on HIVE-9397:
-----------------------------
Now OIs are acquired directly from row schema of final GBY operator. And also
I've fixed double to float type casting, making identical result between
stat-optimized and not.
It would be possible to extend StatsOptimizer to accept queries like "select
min(x)+max(x) from tbl" but seemed better to be done in following issue.
> SELECT max(bar) FROM foo is broken after ANALYZE ... FOR COLUMNS
> ----------------------------------------------------------------
>
> Key: HIVE-9397
> URL: https://issues.apache.org/jira/browse/HIVE-9397
> Project: Hive
> Issue Type: Bug
> Components: Beeline
> Affects Versions: 0.14.0, 0.15.0
> Reporter: Damien Carol
> Assignee: Navis
> Attachments: HIVE-9397.1.patch.txt, HIVE-9397.2.patch.txt
>
>
> These queries produce an error :
> {code:sql}
> DROP TABLE IF EXISTS foo;
> CREATE TABLE foo (id int) STORED AS ORC;
> INSERT INTO TABLE foo VALUES (1);
> INSERT INTO TABLE foo VALUES (2);
> INSERT INTO TABLE foo VALUES (3);
> INSERT INTO TABLE foo VALUES (4);
> INSERT INTO TABLE foo VALUES (5);
> SELECT max(id) FROM foo;
> ANALYZE TABLE foo COMPUTE STATISTICS FOR COLUMNS id;
> SELECT max(id) FROM foo;
> {code}
> The last query throws {{org.apache.hive.service.cli.HiveSQLException}}
> {noformat}
> 0: jdbc:hive2://nc-h04:10000/casino> SELECT max(id) FROM foo;
> +-------------+--+
> | _c0 |
> +-------------+--+
> org.apache.hive.service.cli.HiveSQLException: java.lang.ClassCastException
> 0: jdbc:hive2://nc-h04:10000/casino>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
