Hi Kurt,
Thanks for the reply.
Does this mean that if my job has 3 operators (not chained), it will use at
least 3 slots? I thought parallelism was task based. You can define it at
an operator level, but that only means that the tasks for that operator are
distributed across that many slots.
When I start my flink application with a -p parallelism value of 24, 29
slots are used for the application. Is that expected behavior in some
scenarios?
My application reads in an event stream from Kafka. It does some filtering
and does a keyBy on the stream. Then it processes the same stream
We're currently investigating Flink, and one of the features that we'd like
to have is a TTL feature to time out older values in state. I saw this
thread and it sounds like the functionality was being considered. Is there
any update?
--
View this message in context:
http://apache-flink-use
