[
https://issues.apache.org/jira/browse/FLINK-40215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18101075#comment-18101075
]
Bettle commented on FLINK-40215:
--------------------------------
Hi, I'd like to work on this issue.
My proposed approach is:
1. Add a regression test using an Avro-generated class whose field name is a
Java reserved keyword.
2. Reproduce the mismatch between the generated field and getter names.
3. Adjust the Avro-specific POJO field/getter matching logic without changing
the generic POJO rules.
4. Verify normal Avro-generated classes and existing POJO extraction behavior
remain unchanged.
Could a committer please confirm the approach and assign this issue to me?
Thanks!
> AvroSerializer is not adhering to pojo rules of avro generation
> ---------------------------------------------------------------
>
> Key: FLINK-40215
> URL: https://issues.apache.org/jira/browse/FLINK-40215
> Project: Flink
> Issue Type: Bug
> Components: API / Type Serialization System
> Affects Versions: 2.2.1
> Reporter: Taranpreet Kaur
> Priority: Major
>
> For reserved keywords avro generate fields and methods with $.
> For Example: For word "interface" it will generate field "interface$" and
> method "getInterface$".
> But if we capitalize the reserved keyword then field will be generated
> without $ but method will be generated with $
> For Example: For word "Interface" it will generate field "Interface" and
> method will be "getInterface$".
>
> This fails the pojo analysis as field name and method name do not follow the
> same name structure. Need to make changes so that for Avro Serializer, it
> should follow avro generation rules for pojo analysis.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
