[
https://issues.apache.org/jira/browse/FLINK-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321726#comment-17321726
]
Flink Jira Bot commented on FLINK-3966:
---------------------------------------
This issue and all of its Sub-Tasks have not been updated for 180 days. So, it
has been labeled "stale-minor". If you are still affected by this bug or are
still interested in this issue, please give an update and remove the label. In
7 days the issue will be closed automatically.
> AvroTypeInfo does not work with readonly avro specific records
> --------------------------------------------------------------
>
> Key: FLINK-3966
> URL: https://issues.apache.org/jira/browse/FLINK-3966
> Project: Flink
> Issue Type: Bug
> Components: Formats (JSON, Avro, Parquet, ORC, SequenceFile)
> Affects Versions: 1.0.2, 1.0.3
> Reporter: Matthew Burghoffer
> Priority: Minor
> Labels: stale-minor
>
> When generating avro code, users will often supply createSetters=false and
> fieldVisibility=private for Avro specific records (for effectively immutable
> records). This means that, according to TypeExtractor.isValidPojoField, the
> object is not a valid pojo (though is completely a valid avro object) and the
> TypeInformation factory will fail.
> Specific records are usually created using builders, so perhaps using this
> mechanism for when creating a new record / mutating an existing record is
> required.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
