You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Ashish Thusoo (JIRA)" <ji...@apache.org> on 2009/03/11 01:26:50 UTC
[jira] Updated: (HIVE-238) complex columns are not handled properly
in cluster by, distributed by, sort by clauses and in some select clauses
[ https://issues.apache.org/jira/browse/HIVE-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ashish Thusoo updated HIVE-238:
-------------------------------
Priority: Blocker (was: Major)
Affects Version/s: 0.3.0
Marking as a blocker for 0.3 as there is no good workaround.
> complex columns are not handled properly in cluster by, distributed by, sort by clauses and in some select clauses
> ------------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-238
> URL: https://issues.apache.org/jira/browse/HIVE-238
> Project: Hadoop Hive
> Issue Type: Bug
> Components: Query Processor
> Affects Versions: 0.3.0
> Reporter: Prasad Chakka
> Priority: Blocker
>
> if a column is complex then the sub fields can't be referenced in cluster by, distributed by, sort by clauses
> for example if column c1 is an object with attributes a and b then the following query returns an error
> select * from t1 cluster by t1.c1.a (or similar queries)
> also the following query will return an error because current code doesn't distinguish between a complex column or a table alias.
> select c1.a from t1
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.