[
https://issues.apache.org/jira/browse/HIVE-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648665#comment-13648665
]
Mark Wagner commented on HIVE-4251:
-----------------------------------
Hi Steven,
Indexing on the field of a record/struct isn't supported yet. That's also the
case for other metadata like cluster, sort, and skew columns. I've been taking
a look at that recently, and will open up a JIRA to discuss/track. I tried your
second case and got the same issue as you. It seems to be an unrelated issue
that is preventing group by using a struct as a key. These are both issues that
affect all storage formats though, so we should discuss them in their own JIRAs.
Can you confirm that you're able to create indices on top level primitive
columns of Avro tables with this patch?
Thanks,
Mark
> Indices can't be built on tables whose schema info comes from SerDe
> -------------------------------------------------------------------
>
> Key: HIVE-4251
> URL: https://issues.apache.org/jira/browse/HIVE-4251
> Project: Hive
> Issue Type: Bug
> Affects Versions: 0.10.0, 0.11.0, 0.10.1
> Reporter: Mark Wagner
> Assignee: Mark Wagner
> Fix For: 0.11.0, 0.10.1
>
> Attachments: HIVE-4251.1.patch, HIVE-4251.2.patch
>
>
> Building indices on tables who get the schema information from the
> deserializer (e.g. Avro backed tables) doesn't work because when the column
> is checked to exist, the correct API isn't used.
> {code}
> hive> describe doctors;
>
> OK
> # col_name data_type comment
>
> number int from deserializer
> first_name string from deserializer
> last_name string from deserializer
> Time taken: 0.215 seconds, Fetched: 5 row(s)
> hive> create index doctors_index on table doctors(number) as 'compact' with
> deferred rebuild;
> FAILED: Error in metadata: java.lang.RuntimeException: Check the index
> columns, they should appear in the table being indexed.
> FAILED: Execution Error, return code 1 from
> org.apache.hadoop.hive.ql.exec.DDLTask
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
