[COMPASS-2982] Aggregation Pipeline on Database Scope Created: 06/Jul/18 Updated: 27/Sep/19 Resolved: 27/Sep/19 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | UI / UX |
| Affects Version/s: | 1.14.0 |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Minor - P4 |
| Reporter: | Jack Alder | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
User would like to run aggregation pipeline commands against a database. Specifically, user will want to build a pipeline where a step includes executing $currentOp on the admin database to gather running and dormant processes. The Compass application does not present the aggregation pipeline builder UI until after a collection is selected in scope. This leads to the stage not executing on the admin database and instead presenting an error message: |
| Comments |
| Comment by Massimiliano Marcon [ 27/Sep/19 ] |
|
Closing this issue in JIRA. It's been moved to the new, unified feedback engine at https://feedback.mongodb.com/forums/924283-compass. We are looking for input to decide how to prioritize it, so go there, look for the suggestion, vote and leave comments. If you don't find it, feel free to create a new one. |