Re: 1.1.4 IntelliJ Problem

es. This might mean that > flink-test-utils library on your classpath has version 1.1.3 whereas > flink-runtime has 1.1.4. > > You might want to thoroughly inspect your classpath to ensure that every > Flink-related dependency has version 1.1.4. > > Regards,

Re: 1.1.4 IntelliJ Problem

onfiguration in the IDE. > > It often helps to do "Maven->Reimport" or use "restart and clear caches". > > > On Tue, Jan 3, 2017 at 9:48 AM, Stephan Epping <mailto:stephan.epp...@zweitag.de>> wrote: > Hey, > > thanks for the reply. I didn

Re: 1.1.4 IntelliJ Problem

"Maven->Reimport" or use "restart and clear caches". > > > On Tue, Jan 3, 2017 at 9:48 AM, Stephan Epping <mailto:stephan.epp...@zweitag.de>> wrote: > Hey, > > thanks for the reply. I didn’t change the scala version, as it worked before. >

Re: 1.1.4 IntelliJ Problem

ung wrote: > > Seems like you didn't setup the correct scala SDK > > best, > Kurt > > On Mon, Jan 2, 2017 at 10:41 PM, Stephan Epping <mailto:stephan.epp...@zweitag.de>> wrote: > Hi, > > I am getting this error running my tests with 1.1.4 inside

1.1.4 IntelliJ Problem

Hi, I am getting this error running my tests with 1.1.4 inside intellij ide. java.lang.NoSuchMethodError: org.apache.flink.runtime.jobmanager.JobManager$.startJobManagerActors(Lorg/apache/flink/configuration/Configuration;Lakka/actor/ActorSystem;Lscala/Option;Lscala/Option;Ljava/lang/Class;Ljava

Re: Problem with JodaTime

ve to implement a custom serializer > for the field that is causing the issues. > > On Thu, Dec 22, 2016 at 3:44 PM, Stephan Epping <mailto:stephan.epp...@zweitag.de>> wrote: > Hi, > > I noticed the following Problem with a POJO I use to encapsulate Values. > > j

Problem with JodaTime

Hi, I noticed the following Problem with a POJO I use to encapsulate Values. java.lang.NullPointerException at org.joda.time.tz.CachedDateTimeZone.getInfo(CachedDateTimeZone.java:143) at org.joda.time.tz.CachedDateTimeZone.getOffset(CachedDateTimeZone.java:103) at org.j

Re: What is the best way to load/add patterns dynamically (at runtime) with Flink?

I also found this really interesting post http://stackoverflow.com/questions/40018199/flink-and-dynamic-templates-recognition

Re: Cassandra Connector

a case classes) but we >> did not want the user to be aware of it. This has the neat property that we >> can change the underlying classes >> any way we want (like modifying the constructor) without breaking anything. >> >> Regards, >> Chesnay >>

Re: Maintaining watermarks per key, instead of per operator instance

y(new ReadingAggregate(), new AggregateReadings(), new > AggregateReadings()); > > > Feedback is very welcome. > > best, Stephan > > > > >> On 11 Nov 2016, at 00:29, Fabian Hueske-2 [via Apache Flink User Mailing >> List archive.] <[hidden email]

Cassandra Connector

Hello, I wondered why the cassandra connector has such an unusual interface: CassandraSink csink = CassandraSink.addSink(readings) while all other sinks seem to look like RMQSink sink = new RMQSink(cfg, "readings_persist_out", new JSONReadingSchema()); readings.addSink(sink); best, Stephan

Docker

Hi, It would be really nice to have an official docker image (e.g. https://github.com/apache/flink/tree/master/flink-contrib/docker-flink ). Or a least to have a regular image/build on docker hub best, Stephan

Re: Maintaining watermarks per key, instead of per operator instance

ault-tolerance. >> >> To me, the stateful FlatMapOperator looks like the best approach. There is >> an upcoming feature for registering timers in user-functions, i.e., a >> function is called after the timer exceeds. This could be helpful to >> overcome the prob

apply with fold- and window function

Hello, I wondered if there is a particular reason for the window function to have explicitly the same input/output type? public SingleOutputStreamOperator apply(R initialValue, FoldFunction foldFunction, WindowFunction function) for example (the following does not work): DataStream aggregate

Re: Maintaining watermarks per key, instead of per operator instance

an > > 2016-11-10 11:01 GMT+01:00 Stephan Epping <mailto:stephan.epp...@zweitag.de>>: > Hello, > > I found this question in the Nabble archive > (http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Maintaining-watermarks-per-key-instead-of-per-operator

Re: Maintaining watermarks per key, instead of per operator instance

Hello, I found this question in the Nabble archive (http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Maintaining-watermarks-per-key-instead-of-per-operator-instance-tp7288.html