[SERVER-38759] Add a type to describe a richer path Created: 21/Dec/18 Updated: 06/Dec/22 Resolved: 29/Jan/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query
|
| Participants: |
| Description |
|
Such a type will be used to disambiguate "paths" like "a.b" and "a.0.b". For example, you could imagine translating "a.b" into a path "start at root, go through a subdocument 'a' to find field named 'b'" or "start at root, go through each element of the array a and look at the field 'b' within each of those documents". "a.b" might mean either in MongoDB. |
| Comments |
| Comment by David Storch [ 29/Jan/19 ] |
|
While a richer internal path representation is desirable, the latest proposed design for mongocryptd will not need this new "rich path" type. This ticket was intended to track work on the path representation only as needed for mongocryptd. Therefore, I'm closing it as Won't Fix. |