[
https://issues.apache.org/jira/browse/FLINK-2627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734467#comment-14734467
]
ASF GitHub Bot commented on FLINK-2627:
---------------------------------------
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/1099#issuecomment-138488251
I think this looks good.
I personally like explicit arguments, even if it means sometimes explicitly
summoning an implicit bound. It just makes it clearer where the type infos
flow, which is not that easy to figure out ;-)
This is subject to debate, though. @tillrohrmann and @aljoscha may be of
different opinion here...
> Make Scala Data Set utils easier to access
> ------------------------------------------
>
> Key: FLINK-2627
> URL: https://issues.apache.org/jira/browse/FLINK-2627
> Project: Flink
> Issue Type: Improvement
> Components: Scala API
> Reporter: Sachin Goel
> Assignee: Sachin Goel
> Priority: Trivial
>
> Currently, to use the Scala Data Set utility functions, one needs to import
> {{import org.apache.flink.api.scala.DataSetUtils.utilsToDataSet}}
> This is counter-intuitive, extra complicated and should be more in sync with
> how Java utils are imported. I propose a package object which can allow
> importing utils like
> {{import org.apache.flink.api.scala.utils._}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
