You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Benjamin Zikarsky (JIRA)" <ji...@apache.org> on 2019/04/09 10:30:00 UTC

[jira] [Updated] (AVRO-2372) Compiler can generate breaking code when there are cross-namespace type references

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

Benjamin Zikarsky updated AVRO-2372:
------------------------------------
    Summary: Compiler can generate breaking code when there are cross-namespace type references  (was: Compiler can gerade breaking code when there are cross-namespace type references)

> Compiler can generate breaking code when there are cross-namespace type references
> ----------------------------------------------------------------------------------
>
>                 Key: AVRO-2372
>                 URL: https://issues.apache.org/jira/browse/AVRO-2372
>             Project: Apache Avro
>          Issue Type: Bug
>          Components: java
>    Affects Versions: 1.9.0
>            Reporter: Benjamin Zikarsky
>            Priority: Major
>
> *Problem*
> With the current version of 1.9.0-SNAPSHOT (as of 9th of April 2019) the java compiler generates broken code under 2 circumstances:
> # Type A (e.g. {{foo.A}}) references Type B from a different namespace (e.g. {{bar.B}})
> # Both types fulfill the criteria of {{SpecificCompiler.isCustomCodable(..)}}
> This generates code where {{foo.A}} is generated with a {{protected customCode(...)}} which calls out to {{bar.B}}'s {{protected customCode(...)}}. This breaks as {{A}} cannot access {{B}}'s protected methods.
>  *Possible solutions*
> # Change the {{isCustomCodeable}} criteria in such a way that it fails for namespace-crossing type-references
> # Open up access to customCode/customDecode. This may expose internals though.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)