[
https://issues.apache.org/jira/browse/FLINK-7614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-7614:
----------------------------------
Labels: auto-deprioritized-major stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Add a code snippet example of a valid POJO to "Data Types" documentation
> ------------------------------------------------------------------------
>
> Key: FLINK-7614
> URL: https://issues.apache.org/jira/browse/FLINK-7614
> Project: Flink
> Issue Type: Improvement
> Components: API / Type Serialization System, Documentation
> Reporter: Tzu-Li (Gordon) Tai
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> A user was struggling with working with POJO types, as reported in
> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Exception-when-using-keyby-operator-td15435.html
> We seem to have similar "accidentally not valid POJO" problems every now and
> then from users. We can probably improve this by having a solid code snippet
> of a valid POJO under [1] that demonstrates the POJO rules, instead of just a
> text description of the rules. A guideline to check if your type is actually
> recognized as a POJO by Flink should also be included.
> [1]
> https://ci.apache.org/projects/flink/flink-docs-release-1.3/dev/types_serialization.html#rules-for-pojo-types
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
