[SERVER-66097] Investigate seek() behavior for column indexes Created: 29/Apr/22  Updated: 29/Oct/23  Resolved: 13/Dec/22

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

Type: Task Priority: Major - P3
Reporter: Ian Boros Assignee: Dianna Hohensee (Inactive)
Resolution: Fixed Votes: 0
Labels: pm2646-m4
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Participants:

 Description   

In regular b-tree indexes, there is some behavior in cursor seeking here that's necessary because WT::Cursor::search_near() is not guaranteed to return the maximum key that compares lower than the search key. We should determine whether we need equivalent logic for the column index. See here



 Comments   
Comment by Githook User [ 13/Dec/22 ]

Author:

{'name': 'Dianna Hohensee', 'email': 'dianna.hohensee@mongodb.com', 'username': 'DiannaHohensee'}

Message: SERVER-66097 Add concurrency with committed prepared transactions handling to the column store
Branch: master
https://github.com/mongodb/mongo/commit/a060f0be81078701b28f2b27a84da1326c8af730

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