Fix DeserializeStage
to ensure output messages correctly contain the correct rows for each batch
#2015
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.
Description
DeserializeStage
now performs a copy of the rows needed for each batch, ensuring each outputControlMessage
now has a uniqueMessageMeta
and underlyingDataFrame
SlicedMessageMeta::get_mutable_info().checkout_obj()
returns the entireDataFrame
DeserializeStage
will require the GIL.make_output_message
methodSlicedMessageMeta
(unrelated but I was in this part of the code).Closes #2002
Closes #2011
By Submitting this PR I confirm: