Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
| Dev | vasudevpathak(*) |
| QA |
|
| Priority | Low |
| Complexity | Unknown |
| Component | MongoJS |
| Version | 18.0 |
|
|
87 KB
|
|
80 KB
Hi Jenny,
readConcern is introduced in MongoDB 3.2. According to MonogDB docs readConcern query option is for replicaset and replicaset shards.
I think we should not use this query option with standalone connection. Please check.
When we execute readConcern with standalone in MongoDB 3.2.1 CLI, It returns an error for first time execution. ADS also returns the same error message.
When execute the same command second time it shows result. screen-shot.
Thanks!
Based upon @vasudev's findings, I'm marking this issue as invalid. QA pls confirm Vasudev's findings.
Based upon @vasudev's findings, I'm marking this issue as invalid. QA pls confirm Vasudev's findings.
Closing this issue as invalid
Closing this issue as invalid
Issue #14308 |
| Closed |
| Invalid |
| Resolved |
Completion |
| No due date |
| No fixed build |
| No time estimate |
Hi Jenny,
readConcern is introduced in MongoDB 3.2. According to MonogDB docs readConcern query option is for replicaset and replicaset shards.
I think we should not use this query option with standalone connection. Please check.
When we execute readConcern with standalone in MongoDB 3.2.1 CLI, It returns an error for first time execution. ADS also returns the same error message.
When execute the same command second time it shows result. screen-shot.
Thanks!