-
Notifications
You must be signed in to change notification settings - Fork 533
RUBY-1559 Implement uri option spec tests #1170
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
e4b4585
to
dadb6e5
Compare
dadb6e5
to
7910476
Compare
7438857
to
ffc3704
Compare
This PR should also have a ticket reference, API documentation for added options and tutorial documentation for added options. |
My mistake, there is a ticket. I've updated the description. |
We currently don't have any API documentation for URI options; we have it for client options, but no new client options have been added, only additional mappings to them from URI options. If you want me to, I can open a separate ticket for us to add API documentation for URI options. |
* - authMechanism=String | ||
- ``:auth_mech => Symbol`` | ||
|
||
* - authMechanismProperties=Strings |
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.
How would a user determine what to put in Strings
for this option?
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.
This already existed in the old code; I just alphabetized the list for easier reading. If you just look at the diff for e396935, you'll see the options that are new.
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've added extra documentation to this option and the others below where the type being forwarded is different from the type specified in the URI. Let me know if you think any of the other options need extra documentation as well.
131beed
to
2fefd93
Compare
889ddd5
to
039f10b
Compare
039f10b
to
80fcbe7
Compare
I believe I've addressed all of the outstanding comments on this, so it's ready for review again |
|
||
* - compressors=Strings | ||
- ``:compressors => Array<String>`` | ||
Specified as a comma-separated list, e.g. "zlib,snappy" |
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.
This is a weird default to specify in the Ruby driver because snappy isn't supported by Ruby. Will this warn?
Perhaps a better language is something along the lines of:
Specified as a comma-separated list. Note that the Ruby driver only supports zlib compression, however other drivers may support snappy. For maximum compatibility with drivers specify "snappy,zlib", if compatibility with other drivers is not a concern specify "zlib". Compression is not enabled by default and when using MongoDB 4.0 and earlier, zlib compression must be manually enabled on the server in order for the Ruby driver to compress wire protocol data.
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 didn't intend this to be interpreted as a default, but rather just to demonstrate how specifying more than one would work. I'm happy to make the suggested change, though.
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.
Okay that makes sense, let's put this language in given user confusion over compression.
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.
Just pushed
Spec test pull request: mongodb/specifications#414
https://jira.mongodb.org/browse/RUBY-1559