You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Jeremy Kahn (JIRA)" <ji...@apache.org> on 2013/05/02 01:32:17 UTC
[jira] [Created] (AVRO-1316) IDL code-generation generates too-long
literals for very large schemas
Jeremy Kahn created AVRO-1316:
---------------------------------
Summary: IDL code-generation generates too-long literals for very large schemas
Key: AVRO-1316
URL: https://issues.apache.org/jira/browse/AVRO-1316
Project: Avro
Issue Type: Bug
Components: java
Reporter: Jeremy Kahn
Priority: Minor
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|http://stackoverflow.com/questions/8323082/size-of-initialisation-string-in-java]).
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?
--
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