You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Joseph Adler (JIRA)" <ji...@apache.org> on 2013/06/19 23:58:20 UTC
[jira] [Assigned] (AVRO-803) Java generated Avro classes make using
Avro painful and surprising
[ https://issues.apache.org/jira/browse/AVRO-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joseph Adler reassigned AVRO-803:
---------------------------------
Assignee: Joseph Adler (was: Doug Cutting)
> Java generated Avro classes make using Avro painful and surprising
> ------------------------------------------------------------------
>
> Key: AVRO-803
> URL: https://issues.apache.org/jira/browse/AVRO-803
> Project: Avro
> Issue Type: Improvement
> Components: java
> Affects Versions: 1.5.0
> Environment: Any
> Reporter: Sam Pullara
> Assignee: Joseph Adler
> Fix For: 1.6.0
>
> Attachments: AVRO-803.patch, AVRO-803.patch, Foo.java
>
>
> Currently the Avro generated Java classes expose CharSequence in their API. However, you cannot use any old CharSequence when interacting with them. In fact, you have to use the Utf8 class if you want to get consistent results. I think that Avro should work with any CharSequence if that is the API. Here is an example where this happens:
> https://github.com/spullara/avro-generated-code/blob/master/src/test/java/AnnoyingTest.java
> That prints out 'false' three times unexpectedly. If you can't get it to print 'true' three times then you should probably change it back to Utf8.
--
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