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

Jakob Homan commented on HIVE-3447:
-----------------------------------

This is a bad idea for two reasons: (a) schema.url and schema.literal are too 
generic to be used for this case, which is why they were changed and (b) as 
part of the Apacheification of Haivvreo, these parameters are no longer serde 
properties, but are table properties (in order to avoid a circular dependency 
on the ql and serde packages).  So even if this backwards compatible patch went 
in, it would have a very complicated use pattern.  

Since the necessary change is just a metadata change, and since users already 
have to change the packaging, there's no reason to add this extra complication.
                
> 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

Reply via email to