flink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Ewen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-947) Add support for "Named Datasets"
Date Wed, 18 Jun 2014 13:04:05 GMT

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

Stephan Ewen commented on FLINK-947:
------------------------------------

Looks very good so far.

Two comments:
  - Switching from "typesafe" to "named" API should be consistently done, either through "named",
or through "as". I would vote for "as", it resembles common practice from SQL.
  - Is there a way of switching back from named to typesafe? Something like {{typed(Long.class,
String.class)}} or {{typed(MyBean.class)}}?
  - We should keep the syntax of the named and typesafe methods in sync, meaning going for
{{set.join(other).where(String...).equalTo(String...)}}. That also solves Robert's comment
at the same time.

> Add support for "Named Datasets"
> --------------------------------
>
>                 Key: FLINK-947
>                 URL: https://issues.apache.org/jira/browse/FLINK-947
>             Project: Flink
>          Issue Type: New Feature
>          Components: Java API
>            Reporter: Aljoscha Krettek
>            Assignee: Aljoscha Krettek
>            Priority: Minor
>
> This would create an API that is a mix between SQL like declarativity and the power of
user defined functions. Example user code could look like this:
> {code:Java}
> NamedDataSet one = ...
> NamedDataSet two = ...
> NamedDataSet result = one.join(two).where("key").equalTo("otherKey")
>   .project("a", "b", "c")
>   .map( (UserTypeIn in) -> return new UserTypeOut(...) )
>   .print();
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message