[SERVER-24122] Make mongos sorted merge respect the collation Created: 10/May/16 Updated: 06/Jun/16 Resolved: 31/May/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.8 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | David Storch | Assignee: | David Storch |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Query 15 (06/03/16) |
| Participants: |
| Description |
|
There are two possible strategies:
|
| Comments |
| Comment by Githook User [ 31/May/16 ] |
|
Author: {u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}Message: This means that mongos merge sorting, which is done via $sortKey meta |
| Comment by Tess Avitabile (Inactive) [ 20/May/16 ] |
|
Okay, I'm fine with that. |
| Comment by David Storch [ 20/May/16 ] |
|
I'm fine with the sort order being wrong for nested docs when there is a non-simple collator until we implement |
| Comment by Tess Avitabile (Inactive) [ 20/May/16 ] |
|
Yes, |
| Comment by David Storch [ 20/May/16 ] |
|
Yup, but we can do it before we implement |
| Comment by Tess Avitabile (Inactive) [ 20/May/16 ] |
|
#2 also depends on |
| Comment by David Storch [ 20/May/16 ] |
|
After a bit of investigation, I believe that the correct implementation strategy is #2 (changing SORT_KEY_GENERATOR to convert strings to their collation keys). Halting progress for the time being, since a clean implementation of #2 depends on some of tess.avitabile's in-flight changes. |