[python] Accept lookup config keys - #4543
Merged
Merged
Conversation
Member
Author
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
2 participants
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.
closes #4542
Python lookup waits up to 100 ms for other lookups to join its batch, so a caller that awaits each lookup before the next one pays about 100 ms per key. Java, Rust and C++ let callers lower that window, but the Python
Configrejects everylookup.*key.This change makes
Configacceptlookup.queue-size,lookup.max-batch-size,lookup.batch-timeout-ms,lookup.max-inflight-requestsandlookup.max-retries. It passes them to the Rust client's config and rejects a value that doesn't parse. Each setting also gets a property with a getter and a setter, the stub file declares them, and both Python API references list them with their defaults.