Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
Imagine the following streams application:
stream1.join(stream2...)..join(stream2)
Each join will result in stream2 being materialized into a separate store. Arguably such multi-joins that involves the same stream multiple times is rare, but it worth considering if we can optimize such cases.
One thing to note, though, is that in our DSL parser today we do "put into store first, and then query the other store second", which means if we share the same store it would result in duplicates as the matching would already see the newly put records in the second join.
Attachments
Issue Links
- mentioned in
-
Page Loading...