ESQL: Refactor value reading so it can split Pages (#130573) #130781
+1,312
−884
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.
This refactors our
ValuesSourceReaderOperator
so it can split pages when it reads large values. It does not actually split the pages as that's a bit tricky. But it sets the stage for the next PR that will do so.ValuesSourceReaderOperator
to it's own packageAbstractPageMappingToIteratorOperator
instead ofAbstractPageMappingToOperator
Page
per inputPage
Page
per inputPage
ReleasableIterator
subclasses to satisfyAbstractPageMappingToIteratorOperator
status
of loading fields frompages_processed
topages_received
andpages_emitted
AbstractPageMappingToOperator
which can leak circuit breaker allocation if we fail to duringreceive
. This isn't possible in the existing implementations but is possible inValuesSourceReaderOperator
.Closes #130727
Also includes "Claim backported profile versions (#130187)"