We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Are there any plans (or work done) to support the new (since mongo 3.6) OP_MSG opcode? https://docs.mongodb.com/manual/reference/mongodb-wire-protocol/#op-msg
When connecting to a mongodb that only supports the new format you will currently, with mongodb-erlang, simply get a
#{<<"code">> => 303, <<"errmsg">> => <<"Legacy opcodes are not supported">>, <<"ok">> => 0.0}
, for any operation that you perform (connecting seems to work though).
This happens for instance if you use this library against DocumentDB in Amazon AWS, which seems to only implement the new API.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Are there any plans (or work done) to support the new (since mongo 3.6) OP_MSG opcode?
https://docs.mongodb.com/manual/reference/mongodb-wire-protocol/#op-msg
When connecting to a mongodb that only supports the new format you will currently, with mongodb-erlang, simply get a
, for any operation that you perform (connecting seems to work though).
This happens for instance if you use this library against DocumentDB in Amazon AWS, which seems to only implement the new API.
The text was updated successfully, but these errors were encountered: