[pinot-spark-connector] Bump spark connector max inbound message size #9475
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.
Updating the GRPC client configuration used by the Pinot Spark Connector to use
Int.MaxValue
for message size which effectively bumps the max message size from 4MB to ~2GBs.Spark-Connector is intended for potentially large reads, so 4MB can be a bottleneck for certain use cases (very wide tables).
Testing:
I've tested this locally with chunk sizes exceeding 4MB. I'm not adding an explicit test case not to unnecessarily burden the test runner.
bugfix
performance