scala IT

[Nicos Maris]

Hi all,

the integration test in scala documented at the testing section fails:

https://travis-ci.org/nicosmaris/HelloDockerScalaSbt/builds/410075764

In previous commits of my demo repo, I tried typextractor , basictypeinfo and resultTypeQuerable with no success. I am new to flink and to Scala and I would like to have both, not flink with Java.

Am I doing something that is fundamentally wrong?

thanks,

Nicos Maris

[Hequn Cheng]

Hi Nicos,

It is weird. Have you updated your code? I check your code and the function has implemented ResultTypeQueryable. The code should works well. 

Best, Hequn

On Tue, Jul 31, 2018 at 6:30 AM, Nicos Maris <[hidden email]> wrote:

Hi all,

the integration test in scala documented at the testing section fails:

https://travis-ci.org/nicosmaris/HelloDockerScalaSbt/builds/410075764

In previous commits of my demo repo, I tried typextractor , basictypeinfo and resultTypeQuerable with no success. I am new to flink and to Scala and I would like to have both, not flink with Java.

Am I doing something that is fundamentally wrong?

thanks,

Nicos Maris

[vino yang]

Hi Nicos,

The thrown exception has given you a clear solution hint:

The return type of function 'apply(Mu

   ltiplyByTwoTest.scala:43)' could not be determined automatically, due to type erasure. You can giv

   e type information hints by using the returns(...) method on the result of the transformation call

   , or by letting your function implement the 'ResultTypeQueryable' interface.

You can consider the second option. More information on the Flink type system can be found in the official documentation[1].

[1]: https://ci.apache.org/projects/flink/flink-docs-release-1.5/dev/types_serialization.html#type-information-in-the-scala-api

Thanks, vino.

2018-07-31 6:30 GMT+08:00 Nicos Maris <[hidden email]>:

Hi all,

the integration test in scala documented at the testing section fails:

https://travis-ci.org/nicosmaris/HelloDockerScalaSbt/builds/410075764

In previous commits of my demo repo, I tried typextractor , basictypeinfo and resultTypeQuerable with no success. I am new to flink and to Scala and I would like to have both, not flink with Java.

Am I doing something that is fundamentally wrong?

thanks,

Nicos Maris

[Nicos Maris]

Isn't the returns functions deprecated?

On Tue, Jul 31, 2018, 5:32 AM vino yang <[hidden email]> wrote:

Hi Nicos,

The thrown exception has given you a clear solution hint:

The return type of function 'apply(Mu

   ltiplyByTwoTest.scala:43)' could not be determined automatically, due to type erasure. You can giv

   e type information hints by using the returns(...) method on the result of the transformation call

   , or by letting your function implement the 'ResultTypeQueryable' interface.

You can consider the second option. More information on the Flink type system can be found in the official documentation[1].

[1]: https://ci.apache.org/projects/flink/flink-docs-release-1.5/dev/types_serialization.html#type-information-in-the-scala-api

Thanks, vino.

2018-07-31 6:30 GMT+08:00 Nicos Maris <[hidden email]>:

Hi all,

the integration test in scala documented at the testing section fails:

https://travis-ci.org/nicosmaris/HelloDockerScalaSbt/builds/410075764

In previous commits of my demo repo, I tried typextractor , basictypeinfo and resultTypeQuerable with no success. I am new to flink and to Scala and I would like to have both, not flink with Java.

Am I doing something that is fundamentally wrong?

thanks,

Nicos Maris

[vino yang]

Hi Nicos,

The returns API is not deprecated, just because it is part of the DataStream Java API.

Thanks, vino.

2018-07-31 15:15 GMT+08:00 Nicos Maris <[hidden email]>:

Isn't the returns functions deprecated?

On Tue, Jul 31, 2018, 5:32 AM vino yang <[hidden email]> wrote:

Hi Nicos,

The thrown exception has given you a clear solution hint:

The return type of function 'apply(Mu

   ltiplyByTwoTest.scala:43)' could not be determined automatically, due to type erasure. You can giv

   e type information hints by using the returns(...) method on the result of the transformation call

   , or by letting your function implement the 'ResultTypeQueryable' interface.

You can consider the second option. More information on the Flink type system can be found in the official documentation[1].

[1]: https://ci.apache.org/projects/flink/flink-docs-release-1.5/dev/types_serialization.html#type-information-in-the-scala-api

Thanks, vino.

2018-07-31 6:30 GMT+08:00 Nicos Maris <[hidden email]>:

Hi all,

the integration test in scala documented at the testing section fails:

https://travis-ci.org/nicosmaris/HelloDockerScalaSbt/builds/410075764

In previous commits of my demo repo, I tried typextractor , basictypeinfo and resultTypeQuerable with no success. I am new to flink and to Scala and I would like to have both, not flink with Java.

Am I doing something that is fundamentally wrong?

thanks,

Nicos Maris