[
https://issues.apache.org/jira/browse/HIVE-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13452322#comment-13452322
]
Jakob Homan commented on HIVE-3447:
-----------------------------------
bq. @Shreepadma: The AvroSerDe was added in HIVE-895. This patch has not yet
appeared in a release. The Haivvreo SerDe (which was never part of Hive)
supported the schema.url property. The AvroSerDe (added in HIVE-895) has always
supported avro.schema.url.
Correct.
I'm of the position that Apache projects have no responsibility to support
external solutions, such as Haivvreo, even if they eventually get merged into
Apache. Users already using Haivvreo are welcome to continue to do so as part
of Hive 10 with no changes. Those who wish to switch will only need to update
the serde class, in/outputformats (to accomodate the new packaging regime) and
replace their schema.url or schema.literal serdeproperty with a corresponding
avro.schema.url or avro.schema.literal table property.
> Provide backward compatibility for AvroSerDe properties
> -------------------------------------------------------
>
> Key: HIVE-3447
> URL: https://issues.apache.org/jira/browse/HIVE-3447
> Project: Hive
> Issue Type: Improvement
> Components: Serializers/Deserializers
> Affects Versions: 0.10.0
> Reporter: Zhenxiao Luo
> Assignee: Zhenxiao Luo
> Fix For: 0.10.0
>
> Attachments: HIVE-3447.1.patch.txt
>
>
> haivvreo has been merged into Hive as AvroSerDe.
> It has been so popular that many hive users/customers are using it now.
> There are a number of hive users/customers using haivvreo before its merge,
> their old application/script is not working due to some of the property
> changes(eg. schema.url -> avro.schema.url, schema.literal ->
> avro.schema.literal).
> It could be a good idea that, we provide backward compatibility for AvroSerDe
> properties, say, if "avro.schema.url" is not provided, take "schema.url", so
> that hive users/customers haivvreo application/script could be working
> smoothly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
