[DRIVERS-806] $meta:"sortKey" expressions can generate BSON with duplicate field names which are not correctly handled by Document/Value class Created: 13/Dec/19 Updated: 28/Feb/23 Resolved: 28/Feb/23 |
|
| Status: | Closed |
| Project: | Drivers |
| Component/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Server Compat: | 4.3 | ||||||||
| Upstream Changes Summary: | This change affects how clients will see the results of a {$meta: "sortKey"} projection or a {$meta: "sortKey"} aggregation expression. From a quick search, I didn't find any documentation for this feature, but if there are examples in the documentation, they should be upgraded to show the new format. A release note about the change might be warranted as well. Previously, the result of {$meta: "sortKey"} would look like: {"": "first component", "second component", ..., "": "last component"}With this change in place the same sort key will look like this: I don't think any drivers are relying on the format of the sort key, but if they are, they will likely need minor compatibility fixes. Message me or the server-query Slack channel, and we can work out the details. Thanks! |
||||||||
| Description |
| Comments |
| Comment by Jessica Sigafoos [ 28/Feb/23 ] |
|
No driver changes needed. |
| Comment by Rachelle Palmer [ 21/Feb/23 ] |
|
Bumping to Needs Triage - if nothing is truly needed, lets close |
| Comment by Jeffrey Yemin [ 18/May/20 ] |
|
Nothing needed, Matt. |
| Comment by Matt Broadstone [ 18/May/20 ] |
|
jeff.yemin ping |
| Comment by Esha Bhargava [ 27/Jan/20 ] |
|
jeff.yemin Can you check if this is needed for any of your teams? |