[
https://issues.apache.org/jira/browse/FLINK-2627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734101#comment-14734101
]
ASF GitHub Bot commented on FLINK-2627:
---------------------------------------
Github user sachingoel0101 commented on the pull request:
https://github.com/apache/flink/pull/1099#issuecomment-138401226
@StephanEwen , I have created a separate function to create type
information for 2-tuple.
One question though. Why is there a need to generate type information
explicitly here? The `TypeInformationGen` class does have a case analysis for
`Product` types. I may be very wrong, but `createTypeInformation` macro cannot
be used anywhere inside the module itself but only after the module's been
compiled. This is perhaps why `createTypeInformation` works in, say,
`flink-ml`.
> 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)
