Re: flink local & interactive development

[Fabian Hueske <fh...@gmail.com>]

Hi Georg,

I have no experience with SBT's console mode, so I cannot comment on that,
but Flink provides a Scala REPL that might be useful [1].

Best, Fabian

[1]
https://ci.apache.org/projects/flink/flink-docs-release-1.3/dev/scala_shell.html

2017-11-30 23:09 GMT+01:00 Georg Heiler <ge...@gmail.com>:

> Is interactive development possible with fink like with spark in a REPL?
>
> When trying to use the console mode of SBT I get the following error:
>
> java.lang.Exception: Deserializing the OutputFormat
> (org.apache.flink.api.java.Utils$CollectHelper@210d5aa7) failed: Could
> not read the user code wrapper
>
> for the word count example - even though a sbt run works just fine.
>
> Here the code: https://github.com/geoHeil/flinkGraphs maybe it is a class
> path problem with sbt provided scopes?
>
> Best, Georg
>

Re: flink local & interactive development

[Georg Heiler <ge...@gmail.com>]

That is basically the same thing, only that sbt will start a default scala
shell but put my personal code directly on the class path and requiring to
manually start flink.

However, this doesn't fully seem to work.
Fabian Hueske <fh...@gmail.com> schrieb am Fr. 1. Dez. 2017 um 10:11:

> Hi Georg,
>
> I have no experience with SBT's console mode, so I cannot comment on that,
> but Flink provides a Scala REPL that might be useful [1].
>
> Best, Fabian
>
> [1]
> https://ci.apache.org/projects/flink/flink-docs-release-1.3/dev/scala_shell.html
>
> 2017-11-30 23:09 GMT+01:00 Georg Heiler <ge...@gmail.com>:
>
>> Is interactive development possible with fink like with spark in a REPL?
>>
>> When trying to use the console mode of SBT I get the following error:
>>
>> java.lang.Exception: Deserializing the OutputFormat
>> (org.apache.flink.api.java.Utils$CollectHelper@210d5aa7) failed: Could
>> not read the user code wrapper
>>
>> for the word count example - even though a sbt run works just fine.
>>
>> Here the code: https://github.com/geoHeil/flinkGraphs maybe it is a
>> class path problem with sbt provided scopes?
>>
>> Best, Georg
>>
>
>