[
https://issues.apache.org/jira/browse/HIVE-10324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14493628#comment-14493628
]
Szehon Ho commented on HIVE-10324:
----------------------------------
Basically, after you run the query, run describe extended on the table. The
table should still have the old avro.schema.url (hdfs://namenode:8080).
> Hive metatool should take table_param_key to allow for changes to avro
> serde's schema url key
> ---------------------------------------------------------------------------------------------
>
> Key: HIVE-10324
> URL: https://issues.apache.org/jira/browse/HIVE-10324
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Affects Versions: 1.1.0
> Reporter: Szehon Ho
> Assignee: Ferdinand Xu
>
> HIVE-3443 added support to change the serdeParams from 'metatool
> updateLocation' command.
> However, in avro it is possible to specify the schema via the tableParams:
> {noformat}
> CREATE TABLE `testavro`(
> `test` string COMMENT 'from deserializer')
> ROW FORMAT SERDE
> 'org.apache.hadoop.hive.serde2.avro.AvroSerDe'
> STORED AS INPUTFORMAT
> 'org.apache.hadoop.hive.ql.io.avro.AvroContainerInputFormat'
> OUTPUTFORMAT
> 'org.apache.hadoop.hive.ql.io.avro.AvroContainerOutputFormat'
> TBLPROPERTIES (
> 'avro.schema.url'='hdfs://namenode:8020/tmp/test.avsc',
> 'kite.compression.type'='snappy',
> 'transient_lastDdlTime'='1427996456')
> {noformat}
> Hence for those tables the 'metatool updateLocation' will not help.
> This is necessary in case like upgrade the namenode to HA where the absolute
> paths have changed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
