[AVRO-1316] IDL code-generation generates too-long literals for very large schemas

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.7.5
• Component/s: java
• Labels: patch
• Release Note: Correct java compilation error when schema is too large to be stored in a single String constant
• Tags: IDL
• Assignee: Jeremy Kahn
• Reporter: Jeremy Kahn
• Created: 01/May/13 23:31
• Updated: 19/May/14 21:54
• Resolved: 09/May/13 22:15

Description

When I work from a very large IDL schema, the Java code generated includes a schema JSON literal that exceeds the length of the maximum allowed literal string (65535 characters).

This creates weird Maven errors like: [ERROR] ...FooProtocol.java:[13,89] constant string too long.

It might seem a little crazy, but a 64-kilobyte JSON protocol isn't outrageous at all for some of the more involved data structures, especially if we're including documentation strings etc.

I believe the fix should be a bit more sensitivity to the length of the JSON literal (and a willingness to split it into more than one literal, joined by +), but I haven't figured out where that change needs to go. Has anyone else encountered this problem?

Issue Links

• relates to: AVRO-1274 Add a schema builder API