-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add aggregate method to MongoDB #8117
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #8117 +/- ##
========================================
Coverage 67.08% 67.08%
========================================
Files 122 122
Lines 4123 4123
Branches 658 658
========================================
Hits 2766 2766
Misses 950 950
Partials 407 407 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Nice work mel, this is definitely a more low-code solution. I was wondering about the new I was thinking the term Flow might be a bit of an overloaded, and possibly something that might make more sense is to display |
Changed 'flow' to 'pipeline' and renamed "Action Type" to "Query Type" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Great work Mel
Co-authored-by: Martin McKeaveney <martin@budibase.com>
Description
You can now use aggregations in the MongoDB connector.
There are two modes:
In the JSON mode, you simply provide an array of objects that represent each stage, as per the API docs: https://www.mongodb.com/docs/manual/aggregation/#aggregation-pipeline-example
In the Pipeline mode, you are presented with stages that can be added with the UI. This might be more suitable for "low-code users".
Currently the json and pipeline modes store data separately, but it could be changed to allow mapping between the two.
Addresses:
Screenshots
JSON mode
Dropdown stages with templates:
Swap stages