Hi Harshvardhan, There are a number of factors to consider. 1. the consecutive Kafka messages must exist in a same topic of kafka. 2. the data should not been rebalanced. For example, operators should be chained in order to avoid rebalancing. 3. if you perform keyBy(), you should keyBy on a field the consecutive two messages share the same value.
Best, Hequn On Sat, Jul 28, 2018 at 12:11 AM, Harshvardhan Agrawal < harshvardhan.ag...@gmail.com> wrote: > Hi, > > > We are currently using Flink to process financial data. We are getting > position data from Kafka and we enrich the positions with account and > product information. We are using Ingestion time while processing events. > The question I have is: say I key the position datasream by account number. > If I have two consecutive Kafka messages with the same account and product > info where the second one is an updated position of the first one, does > Flink guarantee that the messages will be processed on the same slot in the > same worker? We want to ensure that we don’t process them out of order. > > Thank you! > -- > Regards, > Harshvardhan >
