You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Greg Hogan (JIRA)" <ji...@apache.org> on 2015/09/14 20:43:45 UTC
[jira] [Updated] (FLINK-2668) ProjectOperator method to close
projection
[ https://issues.apache.org/jira/browse/FLINK-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Greg Hogan updated FLINK-2668:
------------------------------
Description:
I have come across an issue in my code where I called {monospace}project(...){noformat} on a DataSet which was already a {noformat}ProjectOperator{noformat}. Instead of reducing the number of fields from 2 to 1 this instead increased the number of fields from 2 to 3 resulting in {noformat}org.apache.flink.api.common.functions.InvalidTypesException: Input mismatch: Tuple arity '3' expected but was '1'.{noformat} when processing the next operator.
This can be resolved by adding an optional explicit call to conclude the projection, perhaps {noformat}ProjectOperator.closeProjection(){noformat}. Can this be done without creating a new no-op operator?
was:
I have come across an issue in my code where I called {noformat}project(...){noformat} on a DataSet which was already a {noformat}ProjectOperator{noformat}. Instead of reducing the number of fields from 2 to 1 this instead increased the number of fields from 2 to 3 resulting in {noformat}org.apache.flink.api.common.functions.InvalidTypesException: Input mismatch: Tuple arity '3' expected but was '1'.{noformat} when processing the next operator.
This can be resolved by adding an optional explicit call to conclude the projection, perhaps {noformat}ProjectOperator.closeProjection(){noformat}. Can this be done without creating a new no-op operator?
> 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: master
> Reporter: Greg Hogan
> Priority: Minor
>
> I have come across an issue in my code where I called {monospace}project(...){noformat} on a DataSet which was already a {noformat}ProjectOperator{noformat}. Instead of reducing the number of fields from 2 to 1 this instead increased the number of fields from 2 to 3 resulting in {noformat}org.apache.flink.api.common.functions.InvalidTypesException: Input mismatch: Tuple arity '3' expected but was '1'.{noformat} when processing the next operator.
> This can be resolved by adding an optional explicit call to conclude the projection, perhaps {noformat}ProjectOperator.closeProjection(){noformat}. Can this be done without creating a new no-op operator?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)