[
https://issues.apache.org/jira/browse/HIVE-17713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Shelukhin updated HIVE-17713:
------------------------------------
Description:
This is kind of a followup from HIVE-11985
When a SerDe uses an external schema (either embedded, or via a file link),
it's not using the information stored in metastore for the columns. So, if the
users modify table schema via add column and other such commands it won't have
effect on the serde, since it's using the external schema to figure out what
the columns are; leading to confusion and bugs. We should not allow such a
modification for SerDes not in hive.serdes.using.metastore.for.schema
was:
This is kind of a followup from HIVE-11985
When a SerDe uses an external schema (either embedded, or via a file link),
it's not using the information stored in metastore for the columns. So, if the
users modify table schema via add column and other such commands it won't have
effect on serde, since it's using the external schema; leading to confusion and
bugs. We should not allow such a modification for SerDes not in
hive.serdes.using.metastore.for.schema
> disallow adding/modifying columns in metastore for Avro/CSV/etc. SerDes
> -----------------------------------------------------------------------
>
> Key: HIVE-17713
> URL: https://issues.apache.org/jira/browse/HIVE-17713
> Project: Hive
> Issue Type: Bug
> Reporter: Sergey Shelukhin
>
> This is kind of a followup from HIVE-11985
> When a SerDe uses an external schema (either embedded, or via a file link),
> it's not using the information stored in metastore for the columns. So, if
> the users modify table schema via add column and other such commands it won't
> have effect on the serde, since it's using the external schema to figure out
> what the columns are; leading to confusion and bugs. We should not allow such
> a modification for SerDes not in hive.serdes.using.metastore.for.schema
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
