You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gora.apache.org by "yasin tamer (JIRA)" <ji...@apache.org> on 2013/08/15 09:43:49 UTC

[jira] [Commented] (GORA-97) Write Gora GrammerGenerator to replace FakeResolvingDecoder

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

yasin tamer commented on GORA-97:
---------------------------------

Hi Lewis, we want to write GORA's ResolvingGrammerGenerator with [~ser2], but we need to know what gora write extra and where gora write extra data, which classes we must read and understand before implementation..
                
> Write Gora GrammerGenerator to replace FakeResolvingDecoder
> -----------------------------------------------------------
>
>                 Key: GORA-97
>                 URL: https://issues.apache.org/jira/browse/GORA-97
>             Project: Apache Gora
>          Issue Type: New Feature
>    Affects Versions: 0.2
>            Reporter: Lewis John McGibbney
>            Priority: Minor
>             Fix For: 0.4
>
>
> As mentioned in o.a.g.mapreduce.FakeResolvingDecoder
> Avro uses a ResolvingDecoder which resolves two schemas and converts records written by one to the other, and validates the input. However, Gora needs to write extra information along with the data, so the validation is not consistent with the grammer generated by Avro. So we need to fake the ResolvingDecoder (which is sadly hard coded into GenericDatumReader) until we can write our own GrammerGenerator extending ResolvingGrammerGenerator of Avro. As Avro has matured slightly, this issue should aspire to address exactly that.

--
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