[
https://issues.apache.org/jira/browse/HIVE-21897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16868092#comment-16868092
]
Mithun Radhakrishnan commented on HIVE-21897:
---------------------------------------------
At the risk of muddying the waters, I'd consider {{AvroSerDe}} which relies on
the table/serde settings for {{"avro.schema.url"}} and
{{"avro.schema.literal"}}.
When an Avro table's schema changes, old partitions might link to an older
schema-literal SerDe-parameter value than newer partitions.
I could be wrong, but we might want to reevaluate the assumption that SerDe
settings should apply uniformly across all partitions in a table.
> Setting serde / serde properties for partitions
> -----------------------------------------------
>
> Key: HIVE-21897
> URL: https://issues.apache.org/jira/browse/HIVE-21897
> Project: Hive
> Issue Type: Bug
> Components: Hive
> Affects Versions: 3.1.1
> Reporter: Miklos Gergely
> Assignee: Ashutosh Chauhan
> Priority: Major
> Fix For: 4.0.0
>
>
> According to
> [https://cwiki.apache.org/confluence/display/Hive/LanguageManual+DDL#LanguageManualDDL-AddSerDeProperties]
> the SerDe and the SerDe properties can be set for a partition too, so
>
> {code:java}
> ALTERT TABLE table PARTITION (partition_col='partition_value') SET SERDE
> 'serde.class.name';{code}
> Is a valid statement. In fact it is not rejected, but it is not doing
> anything at all. The execution is successful, everything remains the same.
> The same is true for setting the serde properties:
> {code:java}
> ALTER TABLE table PARTITION (partition_col='partition_value') SET
> SERDEPROPERTIES ('property_name'='property_value');{code}
> is also a valid statement, and not doing anything.
> I suggest to modify the parser, and reject these statements. SerDe is for a
> table, and not for a partition.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)