Mailing-List: contact dev-help@avro.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@avro.apache.org
Date: Sat, 5 Sep 2015 20:01:45 +0000 (UTC)
From: "Prateek Rungta (JIRA)" <jira@apache.org>
To: dev@avro.apache.org
Message-ID: <JIRA.12777270.1424806953000.265102.1441483305888@Atlassian.JIRA>
In-Reply-To: <JIRA.12777270.1424806953000@Atlassian.JIRA>
References: <JIRA.12777270.1424806953000@Atlassian.JIRA>
 <JIRA.12777270.1424806953954@arcas>
Subject: [jira] [Updated] (AVRO-1642) JVM Spec Violation 255 Parameter Limit
 Exceeded
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/AVRO-1642?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:all-tabpanel ]

Prateek Rungta updated AVRO-1642:
---------------------------------
    Attachment: AVRO-1642-1.patch

Attaching new patch with the implicit control over generation of the All-Ar=
gs Constructor. Ryan, Sean - what do you guys think?

> JVM Spec Violation 255 Parameter Limit Exceeded=20
> ------------------------------------------------
>
>                 Key: AVRO-1642
>                 URL: https://issues.apache.org/jira/browse/AVRO-1642
>             Project: Avro
>          Issue Type: Bug
>          Components: java
>    Affects Versions: 1.7.7
>         Environment: Windows/Linux all Java
>            Reporter: Bryce Alcock
>            Assignee: Prateek Rungta
>            Priority: Critical
>              Labels: build, maven, specific
>         Attachments: AVRO-1642-0.patch, AVRO-1642-1.patch, avro-1642-fail=
.tar
>
>
> The JVM Spec indicates that:
> {quote}The number of method parameters is limited to 255 by the definitio=
n of a method descriptor (=C2=A74.3.3), where the limit includes one unit f=
or this in the case of instance or interface method invocations. Note that =
a method descriptor is defined in terms of a notion of method parameter len=
gth in which a parameter of type long or double contributes two units to th=
e length, so parameters of these types further reduce the limit. {quote}
> Avro Generated Java code with say more than 255 fields will create a cons=
tructor that is not valid and won't compile.
> Simple test is to create a 256 field avro schema, use the avro-maven auto=
 code gen plugin, and try to compile the resulting class.
> DON'T use linux when doing this use windows, my suspicion is that Linux J=
avaC generates invalid byte code but does not complain.
> Windows will correctly complain indicating that you are a violator of the=
 JVM specification.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)