avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jinal Shah (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AVRO-1316) IDL code-generation generates too-long literals for very large schemas
Date Mon, 19 May 2014 21:55:39 GMT

    [ https://issues.apache.org/jira/browse/AVRO-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14002465#comment-14002465
] 

Jinal Shah commented on AVRO-1316:
----------------------------------

I'm using 1.7.5 but still getting the error. So is there something else that needs to be added
for this to work?

> 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
>            Assignee: Jeremy Kahn
>            Priority: Minor
>              Labels: patch
>             Fix For: 1.7.5
>
>         Attachments: AVRO-1316.patch, AVRO-1316.patch, AVRO-1316.patch, AVRO-1316.patch,
AVRO-1316.patch, AVRO-1316.patch, AVRO-1316.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message