-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: 6.0.5
-
Component/s: None
-
None
-
Query Integration
-
ALL
-
-
QI 2023-07-10, QI 2023-07-24, QI 2023-08-07, QI 2023-08-21, QI 2023-09-04, QI 2023-09-18, QI 2023-10-02, QI 2023-10-16, QI 2023-10-30, QI 2023-11-13, QI 2023-11-27, QI 2023-12-11, QI 2023-12-25, QI 2024-01-08, QI 2024-01-22, QI 2024-02-05, QI 2024-02-19, QI 2024-03-04, QI 2024-03-18, QI 2024-04-01, QI 2024-04-15, QI 2024-04-29, QI 2024-05-13, QI 2024-05-27, QI 2024-06-10, QI 2024-06-24, QI 2024-07-08, QI 2024-07-22, QI 2024-08-05, QI 2024-08-19, QI 2024-09-02, QI 2024-09-16, QI 2024-09-30, QI 2024-10-14
When running an aggregation pipeline that includes a $unionWith or $lookup stage to a timeseries collection, specifying a collation that is different than the timeseries collection's collation causes an error to be thrown:
MongoServerError: Cannot override a view's default collation
If the collation of the timeseries collection and the specified collation of the aggregation are the same, then the aggregation succeeds.
There was a similar issue where performing an aggregation on a timeseries collection and specifying a non-default collation caused the same error to be thrown, but that was fixed: https://jira.mongodb.org/browse/SERVER-54597. The issue of specifying a non-default collation when a unionWith/lookup stage to a timeseries collection is involved still remains.
- is related to
-
SERVER-54597 Allow users to specify non-default collation when querying on time-series collections
- Closed