[SERVER-81811] [CQF] Shard key with dotted path incorrectly populated in optimizer metadata Created: 03/Oct/23  Updated: 29/Oct/23  Resolved: 04/Oct/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.2.0-rc0

Type: Bug Priority: Major - P3
Reporter: Ben Shteinfeld Assignee: Ben Shteinfeld
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-79900 Create sharded passthrough suite with... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: QO 2023-10-16
Participants:

 Description   

The function which translates a string representing a path into an ABT iterates the string from left to right, when it should go right to left. This causes incorrect plans to be generated.



 Comments   
Comment by Githook User [ 04/Oct/23 ]

Author:

{'name': 'Ben Shteinfeld', 'email': 'ben.shteinfeld@mongodb.com', 'username': 'bshteinfeld'}

Message: SERVER-81811 [CQF] Fix population of dotted shard key in optimizer metadata.

We were incorrectly translating the shard key into an ABT by iterating
over the string from left to right, rather than right to left. This is
because we build ABTs bottom up and must start with the last component
of a path.
Branch: master
https://github.com/mongodb/mongo/commit/22cd6188278b491831209c01e15a70015880e95d

Generated at Thu Feb 08 06:47:29 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.