[SERVER-72688] $meta aggregate expression should be marked as unstable for API Version 1 Created: 10/Jan/23 Updated: 29/Oct/23 Resolved: 30/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Arun Banala | Assignee: | Naama Bareket |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | auto-reverted, neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Query Execution
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Sprint: | QE 2023-02-06 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 165 | ||||||||||||
| Description |
|
$meta mostly exposes internal server implementation details and the behavior should not be considered stable. |
| Comments |
| Comment by Githook User [ 26/Jan/23 ] |
|
Author: {'name': 'Naama Bareket', 'email': 'naama.bareket@mongodb.com', 'username': 'naama-bareket'}Message: |
| Comment by xgen-buildbaron-user [ 26/Jan/23 ] |
|
Ticket re-opened due to revert. jsCore_auth began a consistent failure of jstests/core/query/find/find_projection_meta_errors.js |
| Comment by Githook User [ 26/Jan/23 ] |
|
Author: {'name': 'auto-revert-processor', 'email': 'dev-prod-dag@mongodb.com', 'username': ''}Message: Revert " This reverts commit 2264da942fe2e4cbd0ee10742ce14758bd8303ef. |
| Comment by Githook User [ 25/Jan/23 ] |
|
Author: {'name': 'Naama Bareket', 'email': 'naama.bareket@mongodb.com', 'username': 'naama-bareket'}Message: |
| Comment by David Storch [ 13/Jan/23 ] |
|
arun.banala@mongodb.com, oh, I didn't realize that $text and $search are excluded from API version 1! In that case, agreed that we can just remove $meta entirely from API version 1. If we introduce a new user-facing meta-projection, we can decide at that point whether it should be explicitly included in API v1. |
| Comment by David Storch [ 13/Jan/23 ] |
|
arun.banala@mongodb.com if I understand this ticket correctly, then I think it should be closed as "Won't Do". There are various $meta projections that are absolutely user-facing, and therefore seem to belong in API Version 1:
I suppose we could also try to change things so that the $meta-projections that are intended to be internal (e.g. "randVal" or "recordId") are excluded from API Version 1 whereas the user-facing $meta-projections I listed above are included in API Version 1. |