Allowing custom transformers to be passed to SegmentProcessingFramework #11887
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.
Problem:
We need the ability to pass in custom RecordTransformers that can be used during map transformation (segment generation). Without this, users have to introduce custom RecordReaders where custom transformations have to be done. With customer RecordReaders, we no longer have control over allocations/deallocations of RecordReaders (eg: users can pass in long list of pre-allocated Parquet recordReaders which can result in holding up large heap allocations during segment generation and even result in OOM). Moreover we also have a well defined RecordTransformer interface just to do this transformation.
This PR allows users to pass custom RecordTransformers to SegmentProcessorFramework.