You could also remove the autoWatermarkInterval, if you are satisfied with ProcessingTime.
Although keep in mind that processingTime assigns timestamps to elements based on the order that they arrive to the operator. This means that replaying the same stream can give different results. If you care about time handling and reproducibility of your results you could use event or ingestion time (the latter means that each element will have its timestamp based on when it was first ingested by you Flink job). For more information on “time” you can look here https://ci.apache.org/projects/flink/flink-docs-release-1.3/dev/event_time.html <https://ci.apache.org/projects/flink/flink-docs-release-1.3/dev/event_time.html> Cheers, Kostas > On May 31, 2017, at 2:29 PM, Biplob Biswas <revolutioni...@gmail.com> wrote: > > Hi Kostas, > > My application didn't have any timestamp extractor nor my events had any > timestamp. Still I was using event time for processing it, probably that's > why it was blocked. > > Now I removed the part where I mention timechracteristics as Event time and > it works now. > > For example: > > Previously: > > StreamExecutionEnvironment env = > StreamExecutionEnvironment.getExecutionEnvironment(); > env.setStreamTimeCharacteristic(TimeCharacteristic.EventTime); > env.getConfig().setAutoWatermarkInterval(1000); > > And MyEvent was (No field for timestamp): > > public class BAMEvent { > private String id; > private String eventName; > private String eventId; > private List<String> correlationID; > > //Getters > > //Setters > } > > > Now: > > StreamExecutionEnvironment env = > StreamExecutionEnvironment.getExecutionEnvironment(); > /* env.setStreamTimeCharacteristic(TimeCharacteristic.EventTime); */ > env.getConfig().setAutoWatermarkInterval(1000); > > > > -- > View this message in context: > http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/No-Alerts-with-FinkCEP-tp13333p13405.html > Sent from the Apache Flink User Mailing List archive. mailing list archive at > Nabble.com.
