[SPARK-51949][CONNECT] Bump up the default value of CONNECT_GRPC_MARSHALLER_RECURSION_LIMIT
#50756
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 changes were proposed in this pull request?
Bump the default value of
CONNECT_GRPC_MARSHALLER_RECURSION_LIMITfrom1024to4096.Why are the changes needed?
To aid plugin development. We have seen in our prod environment that
1024can be insufficient when processing complex queries.Does this PR introduce any user-facing change?
Yes. Nested gRPC messages deeper than
1024depth and up to4096depth can now be processed without explicitly/manually tuning the config.How was this patch tested?
Was this patch authored or co-authored using generative AI tooling?