[
https://issues.apache.org/jira/browse/FLINK-2309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17329856#comment-17329856
]
Flink Jira Bot commented on FLINK-2309:
---------------------------------------
This issue has been labeled "stale-minor" for 7 days. It is closed now. If you
are still affected by this or would like to raise the priority of this ticket
please re-open, removing the label "auto-closed" and raise the ticket priority
accordingly.
> Use static code analysis to replace selector functions with field accesses.
> ---------------------------------------------------------------------------
>
> Key: FLINK-2309
> URL: https://issues.apache.org/jira/browse/FLINK-2309
> Project: Flink
> Issue Type: Improvement
> Components: API / Scala
> Affects Versions: 0.9
> Reporter: Stephan Ewen
> Priority: Minor
> Labels: stale-minor
>
> In the Scala API, it is nice and safe to specify the fields that are used for
> joining or grouping as selector functions, like this:
> {code}
> val a: DataSet[MyType] = ...
> val b: DataSet[(String, Int)] = ...
> a join b where { _.name } equalTo { _._1 }
> {code}
> We could save the MapFunctions that run the key selectors if we run the
> static code analysis on the key selectors and determine that they have only
> some read fields that they forward, and no modifications. In this case the
> SCA could adjust the program to
> {code}
> val a: DataSet[MyType] = ...
> val b: DataSet[(String, Int)] = ...
> a.join(b).where("name").equalTo(1)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
