gora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Akber Choudhry (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GORA-244) Upgrade to Avro 1.7.X in gora-accumulo
Date Mon, 17 Mar 2014 13:20:43 GMT

    [ https://issues.apache.org/jira/browse/GORA-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13937780#comment-13937780

Akber Choudhry commented on GORA-244:

OK. Will do.  Can you please merge with GORA-292, if possible.

I am looking for architecture guidance/feedback on one of the four possible approaches on
UNIONs, as the underlying problem was default values presenting themselves as UNIONs and thus
UNIONs also occurring in the values of Map types.

- Only support UNONs with null and another type and store the branch index in Avro-encoding
-- I have this working and tests passing.
- Only support UNIONs with null and another type (this is OK for Nutch schema and Gora test
suites) and pick the non-null branch when decoding.  In this way, the Avro-encoded UNION index
marker would not need to be saved along with the native value.
- Support all UNIONs with Avro-encoding of the UNION index and save in Avro-encoding.
- Support all UNIONs with String encoding of the UNION type and index as part of the value
being saved.

Any guidance would be appreciated.  I am also looking into he Cassandra and other implementations
for guidance.

> Upgrade to Avro 1.7.X in gora-accumulo
> --------------------------------------
>                 Key: GORA-244
>                 URL: https://issues.apache.org/jira/browse/GORA-244
>             Project: Apache Gora
>          Issue Type: Sub-task
>          Components: gora-accumulo, gora-core
>    Affects Versions: 0.4
>            Reporter: Lewis John McGibbney
>             Fix For: 0.4
>         Attachments: GORA-244.patch, GORA-244v2.patch

This message was sent by Atlassian JIRA

View raw message