NoSQL
Inspect the field inside the sensor
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
Read sensor and inspect its fields before probing latest.
An older writer omitted latest; a newer writer explicitly stores null for a failed measurement.
Inspect the component calculation
Read a document path( Document: Pump document Field path: sensor )
Examples and results
- Pump document
{ "asset_id": "P1", "sensor": { "latest": 0, "unit": "C" } }- Required result
{ "latest": 0, "unit": "C" }
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 sensor explicitly reports null
This check uses the pieces from “Enter the sensor object before inspecting its field”.
BOTIE
- Pump document
{ "asset_id": "P9", "sensor": { "latest": null, "unit": "C" } }- Sensor field to inspect
latest
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.
Would a reader using get with a default None retain the distinction between omission and an explicit null?
Document flexibility needs an agreed contract for missing fields and values.
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 →