[
https://issues.apache.org/jira/browse/FLINK-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14378851#comment-14378851
]
ASF GitHub Bot commented on FLINK-1776:
---------------------------------------
GitHub user fhueske opened a pull request:
https://github.com/apache/flink/pull/532
[FLINK-1776] Add offsets to field indexes of semantic properties for
operators with key selectors
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/fhueske/flink fixSelectionKeySemProps
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/532.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #532
----
commit 72dcf2b2e1d62f22a5d684cdc09eaba3d4d78358
Author: Fabian Hueske <[email protected]>
Date: 2015-03-24T14:18:21Z
[FLINK-1776] Add offsets to field indexes of semantic properties for
operators with key selectors
----
> 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)
