hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn Weeks (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-17713) disallow adding/modifying columns in metastore for Avro/CSV/etc. SerDes
Date Tue, 09 Oct 2018 23:00:00 GMT

    [ https://issues.apache.org/jira/browse/HIVE-17713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16644206#comment-16644206
] 

Shawn Weeks commented on HIVE-17713:
------------------------------------

While I understand why you wouldn't want this for files that embed or reference an external
schema, whats the reason for file formats backed by things like the OpenCSVSerde, MultiDelimiterSerde
and RegexSerde. Their schema isn't being derived external and they're generally just specialized
replacements for the default LazySimpleSerde.

> 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
>            Priority: Major
>
> 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
(v7.6.3#76005)

Mime
View raw message