[SERVER-79427] [CQF] ScanDefinition should contain a structured NamespaceStringOrUUID Created: 27/Jul/23 Updated: 29/Oct/23 Resolved: 05/Sep/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc10 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | David Percy | Assignee: | Daniel Segel |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Optimization
|
| Backwards Compatibility: | Minor Change |
| Sprint: | QO 2023-09-04, QO 2023-09-18 |
| Participants: |
| Description |
|
I had a brief discussion with mathis.bessa@mongodb.com on serverless about the parseFromScanDef function in abt_lowering. This function extracts a NamespaceStringOrUUID from a ScanDefinition, which sounds more like a getter than a parser. I think we already construct a NamespaceStringOrUUID much earlier in the request, so we should store that on ScanDefinition directly, instead of converting to a string and back. Classes like NamespaceStringOrUUID and DatabaseName track the tenantId separately from the user-visible database name, which helps avoid ambiguity between a database's internal name and its user-visible name. |
| Comments |
| Comment by Githook User [ 05/Sep/23 ] |
|
Author: {'name': 'Daniel Segel', 'email': 'daniel.segel@mongodb.com', 'username': ''}Message: |