[SERVER-429] btree change (Sorting and other) master case Created: 19/Nov/09  Updated: 12/Jul/16  Resolved: 06/Jul/11

Status: Closed
Project: Core Server
Component/s: Index Maintenance
Affects Version/s: None
Fix Version/s: 1.9.1

Type: Task Priority: Major - P3
Reporter: Eliot Horowitz (Inactive) Assignee: Dwight Merriman
Resolution: Done Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-993 btree BucketSize is wrong. Closed
Related
related to SERVER-405 dates before epoch sorting Closed
related to SERVER-1300 use memcmp, not strcmp for comparing ... Closed
related to SERVER-393 $exists queries should use index Closed
is related to SERVER-480 figure out what to do with sorting by... Closed
Participants:

 Description   

this is a holder for all cases that require sorting changes so we do them all at once

search keywords: index sort order



 Comments   
Comment by Dwight Merriman [ 01/Jul/11 ]

leaving open until sharding work verified done and also a mongod test added

Comment by Eliot Horowitz (Inactive) [ 07/Jul/10 ]

@mathias - yes. can you make that change?

Comment by Mathias Stearn [ 07/Jul/10 ]

should 1.6.0 sharding prevent people from inserting data with shardkeys that would be effected by these changes?

Comment by Eliot Horowitz (Inactive) [ 21/Dec/09 ]

Going to try and keep 1.3.x short

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