You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Doug Cutting (JIRA)" <ji...@apache.org> on 2009/11/12 00:54:39 UTC

[jira] Resolved: (AVRO-164) Generate paranamer metadata for interfaces as part of SpecificCompiler

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

Doug Cutting resolved AVRO-164.
-------------------------------

       Resolution: Duplicate
    Fix Version/s: 1.3.0
         Assignee: Doug Cutting

The fix for this was included in AVRO-185.

> Generate paranamer metadata for interfaces as part of SpecificCompiler
> ----------------------------------------------------------------------
>
>                 Key: AVRO-164
>                 URL: https://issues.apache.org/jira/browse/AVRO-164
>             Project: Avro
>          Issue Type: Improvement
>          Components: java
>            Reporter: Philip Zeyliger
>            Assignee: Doug Cutting
>             Fix For: 1.3.0
>
>
> As discussed a bit in AVRO-146, we shouldn't need to run paranamer in a separate build step if we have all the schema information already.  We could keep the code paths the same across the reflected and specific use cases by simply generating the necessary paranamer variable in SpecificCompiler.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.