[AVRO-803] Java generated Avro classes make using Avro painful and surprising

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5.0
• Fix Version/s: 1.6.0
• Component/s: java

Environment

Any

• Assignee: Joseph Adler
• Reporter: Sam Pullara
• Created: 13/Apr/11 19:54
• Updated: 15/May/20 17:09
• Resolved: 11/Oct/11 23:27

Description

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.

Issue Links

• is duplicated by: AVRO-897 Map lookup behavior is ill-defined in Java
• is related to: AVRO-2838 Schema in generated Java class is different than the original one
• is superceded by: AVRO-911 remove object reuse from Java APIs