Fix eager execution due to flatMap #5430
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is the goal of this PR?
We currently have a use of
flatMap()
on the stream of answers that is produced from Janus via our various transformations to produce Concepts and Answers. TheflatMap()
at the end of this sequence of stream manipulations is not necessarily lazy.See:
https://bugs.openjdk.java.net/browse/JDK-8075939
To fix this we introduced
Vavr
which is able to properly handle lazy streams andflatMap
operations. We introduce a minimal change using this library as required here, converting to a Vavr stream and back once the flatMap is added to the stream.What are the changes implemented in this PR?
io.vavr.vavr
that has no transitive dependencies beyond one of its own further packagesflatMap
inQueryExecutor.match
with a few steps to utilisevavr
's stream implementation that actually lazy