You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Robert Metzger (JIRA)" <ji...@apache.org> on 2015/06/05 19:17:00 UTC
[jira] [Resolved] (FLINK-1126) Add suggestion for using large
TupleX types
[ https://issues.apache.org/jira/browse/FLINK-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Metzger resolved FLINK-1126.
-----------------------------------
Resolution: Fixed
Fix Version/s: 0.9
Resolved in http://git-wip-us.apache.org/repos/asf/flink/commit/86e84258
> Add suggestion for using large TupleX types
> -------------------------------------------
>
> Key: FLINK-1126
> URL: https://issues.apache.org/jira/browse/FLINK-1126
> Project: Flink
> Issue Type: Improvement
> Components: Documentation
> Reporter: Ufuk Celebi
> Assignee: Robert Metzger
> Priority: Minor
> Fix For: 0.9
>
>
> Instead of
> {code}
> Tuple11<String, String, ..., String> var = new ...;
> {code}
> I would like to add a hint to use custom types like:
> {code}
> CustomType var = new ...;
> public static class CustomType extends Tuple11<String, String, ..., String> {
> // constructor matching super
> }
> {code}
> I saw a couple of users sticking to the large TupleX types instead of doing this, which leads to a very clumsy user code.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)