You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hive.apache.org by "Jakob Homan (JIRA)" <ji...@apache.org> on 2012/05/03 01:15:52 UTC

[jira] [Updated] (HIVE-895) Add SerDe for Avro serialized data

     [ https://issues.apache.org/jira/browse/HIVE-895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jakob Homan updated HIVE-895:
-----------------------------

    Attachment: HIVE-895-draft.patch

Here's a first draft of the port to ASF.  It corresponds to the mergeHive8ToMaster branch on github, which has all the latest fixes and is compatible with Hive 8.  Need to re-format to Hive style and run full unit tests.  

One thing of concern is that the avroserde relies on the ql package, which required a change to the build script to build serde afterwards.  Is there a defined dependency for Hive's modules, and if so does this break that?  If so, the other option would be to move this to the contrib package, but to me contrib is a dirty word and I'd like to avoid that.  

Also, this bundles the avro serde into the serde jar.  It'd be nice for those not using Avro to not require it, but Avro is already a build-time dependency so it's not a new problem.  Eventually it'd be nice to have a separate jar with just the serde in it to make the code more modular.

I'll finish the port in the next couple of days, but take a glance and comment if you'd like.
                
> Add SerDe for Avro serialized data
> ----------------------------------
>
>                 Key: HIVE-895
>                 URL: https://issues.apache.org/jira/browse/HIVE-895
>             Project: Hive
>          Issue Type: New Feature
>          Components: Serializers/Deserializers
>            Reporter: Jeff Hammerbacher
>            Assignee: Jakob Homan
>         Attachments: HIVE-895-draft.patch
>
>
> As Avro continues to mature, having a SerDe to allow HiveQL queries over Avro data seems like a solid win.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira