NoSQL
Total the urgent visits, not every visit on their pumps
BOTIE
Examples, experiments and workspace controls
Connect a tool's inputs to see what it produces. You can try a branch before connecting it to Result.
Try your own inputs
Use a copy of the example to try your own data. Keep the problem's assumptions in mind, and predict the effect of a change before checking the output. You can also add another branch to compare two ways of doing the calculation.
Context for this challenge
Filter the parent site and expand visits. Inspect routine and urgent rows before adding the member filter.
The site report reads pump documents containing visit arrays.
Inspect the component calculation
Make one row per array member(
Documents: Keep matching document values(
Documents: Pumps with recent visits
Compared value: Requested site
Field path: site
Comparison: =
)
Array field: visits
)Examples and results
- Pumps with recent visits
[ { "asset_id": "P1", "site": "north", "visits": [ { "kind": "urgent", "minutes": 12 } ] }, { "asset_id": "P2", "site": "north", "visits": [ { "kind": "urgent", "minutes": 8 } ] } ]- Requested site
north
- Required result
[ { "asset_id": "P1", "site": "north", "visits": { "kind": "urgent", "minutes": 12 } }, { "asset_id": "P2", "site": "north", "visits": { "kind": "urgent", "minutes": 8 } } ]
Try a fresh construction
This clears this draft, including its undo history. Earlier successful attempts stay recorded. Build again without opening hints to record an independent attempt.
Stuck? Inspect a worked construction
The tools below form one possible solution. You can assemble it, follow its signals, and undo that change to return to your own construction.
Assumptions and test precision
The browser runs an explicit model of the mechanism. It does not connect to MongoDB or Redis, simulate their query planners, or establish their concurrency guarantees. Numerical tests allow a difference of 0.001. Lists and structures must also have the right shape.
Your last tested pieces can start the full construction. An existing draft there keeps its own pieces.
The site has visits but none are urgent
This check uses the pieces from “Reduce only the urgent visits at the selected site”.
BOTIE
- Pumps with recent visits
[ { "asset_id": "P8", "site": "north", "visits": [ { "kind": "routine", "minutes": 70 } ] }, { "asset_id": "P9", "site": "north", "visits": [] } ]- Requested site
north
- Visit kind to count
urgent
Use a number, text, or an array matching the requested result. For a matrix, put each row in brackets. Saving your prediction runs your current construction on these inputs and checks the earlier examples too.
Build a construction in the workspace above first. This case will test those pieces.
What would summing a pump’s annual budget after unwinding every visit count?
Name the grain after every stage and aggregate only values that belong to it.
The browser runs an explicit model of the mechanism. It does not connect to MongoDB or Redis, simulate their query planners, or establish their concurrency guarantees.
Work through the Python challenges →