[DRIVERS-2402] Clarify the behavior of `comment` on database helpers on <4.4 servers Created: 28/Jul/22 Updated: 28/Oct/23 Resolved: 26/Sep/22 |
|
| Status: | Closed |
| Project: | Drivers |
| Component/s: | None |
| Fix Version/s: | None |
| Type: | Spec Change | Priority: | Minor - P4 |
| Reporter: | Bailey Pearson | Assignee: | Bailey Pearson |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Driver Changes: | Not Needed |
| Description |
Summary
MotivationWho is the affected end user?Users specifying a comment on listIndexes, listDatabase, listCollections on servers <4.4. How does this affect the end user?Users might expect a comment to be attached to their commands, but if other drivers interpreted the spec as Node did, a user might be confused as to why their comment isn't present in server logs. How likely is it that this problem or use case will occur?Unlikely. It's a small set of commands on a small set of old server versions. If the problem does occur, what are the consequences and how severe are they?Consequences are not severe - users might be confused as to why their comment isn't present in server logs. Is this issue urgent?No. Is this ticket required by a downstream team?No. Is this ticket only for tests? No. |
| Comments |
| Comment by Jeffrey Yemin [ 26/Sep/22 ] |
|
Spec change is merged. |
| Comment by Githook User [ 15/Sep/22 ] |
|
Author: {'name': 'Bailey Pearson', 'email': 'bailey.pearson@mongodb.com', 'username': 'baileympearson'}Message: |