[
https://issues.apache.org/jira/browse/AVRO-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niels Basjes updated AVRO-1814:
-------------------------------
Attachment: AVRO-1814-20160410.patch
Turns out that this problem in essence is a limitation of the way Java does
resolution when there are name clashes between packages, classes, etc.
This patch at least mitigates the probability of this occurring in user
applications.
> 1.8 IDL generator broken when containing a field called 'org'
> -------------------------------------------------------------
>
> Key: AVRO-1814
> URL: https://issues.apache.org/jira/browse/AVRO-1814
> Project: Avro
> Issue Type: Bug
> Components: java
> Affects Versions: 1.8.0
> Reporter: Dustin Spicuzza
> Assignee: Niels Basjes
> Attachments: AVRO-1814-20160410.patch
>
>
> The problem is in the generated 'readExternal' and 'writeExternal' functions,
> because they do something like:
> WRITER$.write(this, org.apache.avro.specific.SpecificData.getEncoder(out));
> When a member variable called 'org' exists, then the compile fails because
> the compiler thinks that 'org' is a member variable and that 'apache cannot
> be resolved or is not a field'.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
