-
Notifications
You must be signed in to change notification settings - Fork 1.1k
PYTHON-4206 - QE Range Protocol V2 #1670
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
pymongo/asynchronous/encryption.py
Outdated
@@ -836,7 +831,7 @@ async def encrypt( | |||
when the algorithm is :attr:`Algorithm.INDEXED`. An integer value | |||
*must* be given when the :attr:`Algorithm.INDEXED` algorithm is | |||
used. | |||
:param range_opts: Experimental only, not intended for public use. | |||
:param range_opts: Index options for `range` queries. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need notes in the docstrings for the new public parameter being added.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For trimFactor
? Or for all of the rangeOpts
themselves?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
rangeOpts
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
|
||
def __init__( | ||
self, | ||
sparsity: int, | ||
trim_factor: int, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Making this a required argument is a breaking change. Is that intended? Are users expected to always specifiy trim_factor?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, as per the spec, trim_factor
is a required argument.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure that is the case. Adrian says:
My understanding is that [trimFactor is] a knob for our tech support to debug performance issues and that average users should not touch it.
No description provided.