[SERVER-54597] Allow users to specify non-default collation when querying on time-series collections Created: 17/Feb/21 Updated: 29/Oct/23 Resolved: 30/Sep/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Katherine Wu (Inactive) | Assignee: | Maddie Zechar |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Sprint: | QO 2021-09-20, QO 2021-10-04 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
A query on a time-series collection is rewritten with the $_internalUnpackBucket stage and treated as a view on the underlying collection. Any operation on a view that attempts to change or override the default collation of the view will return an OptionNotSupportedOnView error. We should add functionality to allow users to be able to specify a collation different from the collection's default when querying on time-series collections. |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 28/Sep/21 ] |
|
Author: {'name': 'Maddie Zechar', 'email': 'mez2113@columbia.edu', 'username': 'madelinezec'}Message: |
| Comment by David Percy [ 11/Jun/21 ] |
|
This makes sense if $_internalUnpackBucket's behavior doesn't depend on a collation. (Edit: never mind, now I see that its behavior does depend on a collation, and we did SERVER-25954 (allow per-stage collation) would be another way to solve this. |