You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Mark Wagner (JIRA)" <ji...@apache.org> on 2013/03/29 01:09:16 UTC

[jira] [Updated] (HIVE-4251) Indices can't be built on tables who's schema info comes from SerDe

     [ https://issues.apache.org/jira/browse/HIVE-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Wagner updated HIVE-4251:
------------------------------

    Attachment: HIVE-4251.1.patch

The attached patch fixes this for both 0.10 branch and trunk.
                
> Indices can't be built on tables who's 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.11.0, 0.10.1
>            Reporter: Mark Wagner
>            Assignee: Mark Wagner
>         Attachments: HIVE-4251.1.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