[jira] [Commented] (FLINK-1126) Add suggestion for using large TupleX types

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14573203#comment-14573203 ] 

ASF GitHub Bot commented on FLINK-1126:
---------------------------------------

GitHub user rmetzger opened a pull request:

    https://github.com/apache/flink/pull/786

    [FLINK-1126][docs] Best practice: named TupleX types

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/rmetzger/flink flink1126

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/786.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 #786
    
----
commit ce49d9c137d7542a7f5b214df85ff3093a3519f9
Author: Robert Metzger <rm...@apache.org>
Date:   2015-06-04T17:32:17Z

    [FLINK-1126][docs] Best practice: named TupleX types

----


> 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
>
> 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)