You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2021/05/15 17:58:02 UTC

[jira] [Updated] (BEAM-10564) Support more Avro field name formats when mapping to Java fields

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

Kenneth Knowles updated BEAM-10564:
-----------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Resolved)

Hello! Due to a bug in our Jira configuration, this issue had status:Resolved but resolution:Unresolved.

I am bulk editing these issues to have resolution:Fixed

If a different resolution is appropriate, please change it. To do this, click the "Resolve" button (you can do this even for closed issues) and set the Resolution field to the right value.

> Support more Avro field name formats when mapping to Java fields
> ----------------------------------------------------------------
>
>                 Key: BEAM-10564
>                 URL: https://issues.apache.org/jira/browse/BEAM-10564
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-core
>            Reporter: Ryan Worley
>            Assignee: Ryan Worley
>            Priority: P2
>              Labels: Clarified, Done
>          Time Spent: 3h 10m
>  Remaining Estimate: 0h
>
> When mapping Avro schema field names to the related generated Java class fields, Beam currently supports Avro field names like field_name and fieldName.  This improvement will add support for Avro field names like FieldName and FIELD_NAME.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)