You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@flink.apache.org by Nicos Maris <ni...@gmail.com> on 2018/07/30 22:30:18 UTC

scala IT

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

Re: scala IT

Posted by vino yang <ya...@gmail.com>.

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 <ni...@gmail.com>:

> Isn't the returns functions deprecated?
>
> On Tue, Jul 31, 2018, 5:32 AM vino yang <ya...@gmail.com> 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 <ni...@gmail.com>:
>>
>>> 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
>>>
>>
>>

Re: scala IT

Posted by Nicos Maris <ni...@gmail.com>.

Isn't the returns functions deprecated?

On Tue, Jul 31, 2018, 5:32 AM vino yang <ya...@gmail.com> 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 <ni...@gmail.com>:
>
>> 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
>>
>
>

Re: scala IT

Posted by vino yang <ya...@gmail.com>.

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 <ni...@gmail.com>:

> 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
>

Re: scala IT

Posted by Hequn Cheng <ch...@gmail.com>.

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 <ni...@gmail.com> 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
>