[
https://issues.apache.org/jira/browse/HIVE-13780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15933756#comment-15933756
]
Lefty Leverenz commented on HIVE-13780:
---------------------------------------
Should this be documented in the wiki? A new configuration parameter created
in patch 0 is gone in the final patch, but perhaps some instructions should be
added to the AVRO wikidoc:
* [Avro SerDe | https://cwiki.apache.org/confluence/display/Hive/AvroSerDe]
> Allow user to update AVRO table schema via command even if table's definition
> was defined through schema file
> -------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-13780
> URL: https://issues.apache.org/jira/browse/HIVE-13780
> Project: Hive
> Issue Type: Improvement
> Components: CLI
> Affects Versions: 2.0.0
> Reporter: Eric Lin
> Assignee: Adam Szita
> Priority: Minor
> Fix For: 2.2.0
>
> Attachments: HIVE-13780.0.patch, HIVE-13780.1.patch,
> HIVE-13780.3.patch
>
>
> If a table is defined as below:
> {code}
> CREATE TABLE test
> STORED AS AVRO
> TBLPROPERTIES ('avro.schema.url'='/tmp/schema.json');
> {code}
> if user tries to run command:
> {code}
> ALTER TABLE test CHANGE COLUMN col1 col1 STRING COMMENT 'test comment';
> {code}
> The query will return without any warning, but has no affect to the table.
> It would be good if we can allow user to ALTER table (add/change column,
> update comment etc) even though the schema is defined through schema file.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
