[prev in list] [next in list] [prev in thread] [next in thread] 

List:       avro-dev
Subject:    [jira] [Updated] (AVRO-2143) ReflectData should determine inner class names in a different way.
From:       "Doug Cutting (JIRA)" <jira () apache ! org>
Date:       2018-02-22 0:53:00
Message-ID: JIRA.13137896.1518451961000.247865.1519260780230 () Atlassian ! JIRA
[Download RAW message or body]


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

Doug Cutting updated AVRO-2143:
-------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

> ReflectData should determine inner class names in a different way.
> ------------------------------------------------------------------
> 
> Key: AVRO-2143
> URL: https://issues.apache.org/jira/browse/AVRO-2143
> Project: Avro
> Issue Type: Improvement
> Affects Versions: 1.7.7
> Reporter: Miguel
> Assignee: Doug Cutting
> Priority: Major
> Fix For: 1.9.0
> 
> 
> I used ReflectData to generate schemas containing inner classes. These classes were \
> named automatically by ReflectData with dollar ('$'), with, for example \
> com.company.avro.House$Type. Nevertheless @AvroAlias does not support aliases \
> containing '$' in names. In particulr, it fails in validateName in Schema core \
> class. The failure is correct given that AVRO name specs does notinclude the '$' \
> symbol.  I suppose that ReflectData should, for example, generate inner class names \
> in a different way, such as replacing '$' by dots ('.'), or it should fail. And a \
> detail: Although I cannot add aliases with '$', I can still encode and decode such \
> objects and inner classes using that schema.  I think that it newer versions it is \
> also happening. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[prev in list] [next in list] [prev in thread] [next in thread]