← All workshopsRead Which Records Does the Technician Need Together?

NoSQL

Keep every inspection for a pump

BOTIE

Build the collection under asset_id and inspect each bucket before adding the lookup.
Ready to test
0 passed · 0 failed · 1 not run

An empty floor. Start with the information your machine needs.

Received result

Your answer will arrive here.

Examples, experiments and workspace controls
Live values

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.

Start at an output arrow, then click or drag to an input. Drag empty space to pan. Delete removes a selection. Ctrl/Cmd+Z undoes a change.
Context for this challenge

Build the collection under asset_id and inspect each bucket before adding the lookup.

The pump screen asks for all visits belonging to its selected asset.

Inspect the component calculation
Collect records under a key(
  Records: Inspection records
  Field path: asset_id
)
Examples and results
Inspection records
[
  {
    "asset_id": "P1",
    "visit": "V1"
  },
  {
    "asset_id": "P2",
    "visit": "V2"
  }
]
Required result
{
  "P1": [
    {
      "asset_id": "P1",
      "visit": "V1"
    }
  ],
  "P2": [
    {
      "asset_id": "P2",
      "visit": "V2"
    }
  ]
}
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.

An asset with no recorded visit

This check uses the pieces from “Give each pump a list of its visits”.

BOTIE

The records contain only P8 visits while the screen asks for P9. Predict the returned history without borrowing another pump’s list.
Inspection records
[
  {
    "asset_id": "P8",
    "visit": "V8"
  },
  {
    "asset_id": "P8",
    "visit": "V9"
  }
]
Requested asset ID
P9
Empty history
[]

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.

If the source gains another visit after this grouped view is built, what must keep the view current?

Describe the read and the update process together. A convenient copy still needs a source of truth.

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 →
Continue the courseWhich P1 Did the Lookup Mean? →
← Pick Up New Changes Without Losing Late Readings