[
https://issues.apache.org/jira/browse/FLINK-5888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-5888:
----------------------------------
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.
> ForwardedFields annotation is not generating optimised execution plan in
> example KMeans job
> -------------------------------------------------------------------------------------------
>
> Key: FLINK-5888
> URL: https://issues.apache.org/jira/browse/FLINK-5888
> Project: Flink
> Issue Type: Bug
> Components: API / DataSet, Examples
> Affects Versions: 1.1.3
> Reporter: Ziyad Muhammed Mohiyudheen
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> Flink KMeans java example [1] shows the usage of ForwardedFields function
> annotation. How ever, the example job was taking more time than expected on
> medium sized data itself. By merely removing the function annotation from the
> example code (with out any other change), a better execution plan and run
> time was obtained. The execution plan shows that no combiner is used and the
> two Map tasks are not chained when ForwardedFields is enabled. The experiment
> is documented in [2]
> [1]
> https://github.com/apache/flink/blob/master/flink-examples/flink-examples-batch/src/main/java/org/apache/flink/examples/java/clustering/KMeans.java
> [2] https://drive.google.com/open?id=0B0IlZv0uHBuvVEZ5ZmNpN19jVVU
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
