[
https://issues.apache.org/jira/browse/FLINK-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377907#comment-14377907
]
Fabian Hueske commented on FLINK-1776:
--------------------------------------
The fix is straight-forward.
We get the numbers of fields of the extracted grouping and sorting keys and add
that offset to all indexes of input record fields.
I am working on a fix for all affected operators.
> APIs provide invalid Semantic Properties for Operators with SelectorFunction
> keys
> ---------------------------------------------------------------------------------
>
> Key: FLINK-1776
> URL: https://issues.apache.org/jira/browse/FLINK-1776
> Project: Flink
> Issue Type: Bug
> Components: Java API, Scala API
> Affects Versions: 0.9
> Reporter: Fabian Hueske
> Assignee: Fabian Hueske
> Priority: Critical
> Fix For: 0.9
>
>
> Semantic properties are defined by users and evaluated by the optimizer.
> When semantic properties such as forwarded or read fields are bound to the
> input type of a function.
> In case of operators with selector function keys, a user function is wrapped
> by a wrapping function that has a different input types than the original
> user function. However, the user-defined semantic properties are verbatim
> forwarded to the optimizer.
> Since the properties refer to a specific type which is changed by the
> wrapping function and the semantic properties are not adapted, the optimizer
> uses wrong properties and might produce invalid plans
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
