You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 11, 2024. It is now read-only.
Is there a way to define strict order for messages?
Currently they can arrive to MyRichCoFlatMapFunction as "message1,message2" or "message2,message1" triggering flatMap1 or flatMap2 in arbitrary order, which is not good for unit testing
The text was updated successfully, but these errors were encountered:
This is an interesting case. The philosophy of flinkspector was always to simulate an environment as close to the actual cluster. Which is why for example tests run at default at a parallelism of 2. This approach is of course debatable, but the idea is to provide almost lightweight integration tests. Based on our experience this allows you to find certain errors, which would otherwise not be discovered until running your program on an actual cluster.
In your case you have two streams. And you would like to be able to define a order of messages across these two streams. And this order should be preserved until they arrive at a certain operator. With the current design of the framework, which just runs a local cluster and injects messages, I don't have enough control to achieve this in a satisfying way.
Hi,
I have a RichCoFlatMapFunction with flatMap1 and flatMap2 functions for each kind of messages.
When I'm specifying order of original messages in a stream, the order they come to RichCoFlatMapFunction is arbitrary
I'm creating stream like that:
DataStream<Message> stream = createTestStreamWith(message1).emit(message2).close();
Doing assertion:
assertStream(job.processStream(stream), matcher);
processStream looks like:
Is there a way to define strict order for messages?
Currently they can arrive to MyRichCoFlatMapFunction as "message1,message2" or "message2,message1" triggering flatMap1 or flatMap2 in arbitrary order, which is not good for unit testing
The text was updated successfully, but these errors were encountered: