[
https://issues.apache.org/jira/browse/FLINK-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fabian Hueske closed FLINK-2668.
--------------------------------
Resolution: Fixed
Assignee: Chesnay Schepler
Fix Version/s: 0.10
Fixed on master with 32b0dfd102c4264a26ad9b5f6bb5779f8a8d33da
Fixed for 0.10 with 5c3eb8b8f8ff39fafc9d93e42d9f6a924e3d8576
> ProjectOperator method to close projection
> ------------------------------------------
>
> Key: FLINK-2668
> URL: https://issues.apache.org/jira/browse/FLINK-2668
> Project: Flink
> Issue Type: Improvement
> Components: Java API
> Affects Versions: 0.10
> Reporter: Greg Hogan
> Assignee: Chesnay Schepler
> Priority: Minor
> Fix For: 0.10
>
>
> I have come across an issue in my code where I called project(...) on a
> {{DataSet}} which was already a {{ProjectOperator}}. Instead of reducing the
> number of fields from 2 to 1 this instead increased the number of fields from
> 2 to 3 resulting in
> {{org.apache.flink.api.common.functions.InvalidTypesException: Input
> mismatch: Tuple arity '3' expected but was '1'.}} when processing the next
> operator.
> This can be resolved by adding an optional explicit call to conclude the
> projection, perhaps {{ProjectOperator.closeProjection()}}. Can this be done
> without creating a new no-op operator?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
