[
https://issues.apache.org/jira/browse/FLINK-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14035672#comment-14035672 ]
Aljoscha Krettek commented on FLINK-947:
----------------------------------------
Yes yes, again, the interface can be changed in a few minutes. That's not the hard part. (Both for the named v. as and the join interface. It's just easier to implement things without the many nested JoinWithPredicates etc. classes.)
Switching back to typesafe datasets is there but I'm not yet checking the types. In the example code it's called toDataSet(), adding checks here can be done.
> 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)
Locked
