You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Szehon Ho (JIRA)" <ji...@apache.org> on 2015/04/04 01:07:53 UTC
[jira] [Updated] (HIVE-7868) AvroSerDe error handling could be
improved
[ https://issues.apache.org/jira/browse/HIVE-7868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Szehon Ho updated HIVE-7868:
----------------------------
Release Note: (was: Thank you Ferdinand! I have committed this to trunk!)
Removing the thank you note from the release note :)
> AvroSerDe error handling could be improved
> ------------------------------------------
>
> Key: HIVE-7868
> URL: https://issues.apache.org/jira/browse/HIVE-7868
> Project: Hive
> Issue Type: Improvement
> Reporter: Brock Noland
> Assignee: Ferdinand Xu
> Fix For: 1.1.0
>
> Attachments: HIVE-7868.1.patch, HIVE-7868.2.patch
>
>
> When an Avro schema is invalid, AvroSerDe returns an error message instead of throwing an exception. This is described in {{AvroSerdeUtils.determineSchemaOrReturnErrorSchema}}:
> {noformat}
> /**
> * Attempt to determine the schema via the usual means, but do not throw
> * an exception if we fail. Instead, signal failure via a special
> * schema. This is used because Hive calls init on the serde during
> * any call, including calls to update the serde properties, meaning
> * if the serde is in a bad state, there is no way to update that state.
> */
> {noformat}
> I believe we should find a way to provide a better experience to our users.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)