Details
Description
Additional use cases for collation would be enabled if it could be specified at a more granular level than per-operation. Some examples:
- A compound index or sort criteria with different collations for each key
- A query filter with different collations per operator
- An aggregation pipeline with different collations per stage (e.g. a case-insensitive collation for a $match and a case-sensitive one for a subsequent $sort)
- A read-only view with different collations for the view itself, a view that it depends on, and an operation on the view (this would be enabled by allowing a collation per aggregation stage)
Attachments
Issue Links
- is duplicated by
-
SERVER-49046 Provide the ability to perform a collation aware search only on the fields on which the index is defined
-
- Closed
-
- is related to
-
SERVER-55653 Queries on time-series views do not accept collations on indexes
-
- Closed
-
- related to
-
SERVER-53637 Allow collation to be specified for a $lookup sub-pipeline
-
- In Code Review
-