[COMPASS-3176] Cannot use "$cond" in aggregate pipeline in an "$expr" Created: 04/Oct/18 Updated: 29/Oct/23 Resolved: 09/Apr/19 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | Compass |
| Affects Version/s: | 1.16.0-beta.7, 1.15.4 |
| Fix Version/s: | 1.19.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Nishant Bhardwaj | Assignee: | Durran Jordan |
| Resolution: | Fixed | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Sprint: | Iteration Antelope, Iteration Bison |
| Description |
|
Tested in compass 1.15.4 and 1.16.0-beta.7, the aggregation pipeline builder gives error:
However, same query with "$cond" runs fine in mongo shell. Please see the screenshots attached. |
| Comments |
| Comment by Githook User [ 09/Apr/19 ] |
|
Author: {'name': 'Durran Jordan', 'username': 'durran', 'email': 'durran@gmail.com'}Message: Fixes $cond and $text validation errors in $match stages. |
| Comment by Githook User [ 09/Apr/19 ] |
|
Author: {'email': 'durran@gmail.com', 'name': 'Durran Jordan', 'username': 'durran'}Message: Fixes $cond and $text validation errors in $match stages. |
| Comment by Pierre Bazoge [ 24/Jan/19 ] |
|
Got same issue +1 |