NoSQL
Repair the maintenance dashboard from current job images
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
Connect stored and incoming images to Keep the latest full image of each job. Inspect the retained versions before attaching the count.
The job stream includes closures, reassignments and repeated images.
Inspect the component calculation
Keep the latest full image of each job( Stored job images: Stored job images Incoming job images: Incoming full images )
Examples and results
- Stored job images
[ { "id": "J1", "asset": "P7", "version": 1, "status": "open" } ]- Incoming full images
[ { "id": "J1", "asset": "P7", "version": 2, "status": "done" }, { "id": "J2", "asset": "P8", "version": 1, "status": "open" } ]- Required result
[ { "id": "J1", "asset": "P7", "version": 2, "status": "done" }, { "id": "J2", "asset": "P8", "version": 1, "status": "open" } ]
- Stored job images
[ { "id": "J2", "asset": "P8", "version": 3, "status": "deleted" } ]- Incoming full images
[ { "id": "J2", "asset": "P8", "version": 2, "status": "open" } ]- Required result
[ { "id": "J2", "asset": "P8", "version": 3, "status": "deleted" } ]
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 small projection rebuild retains full images and has no persisted network cursor. Real sinks need checkpoint and retention handling. 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.
A closure and repeated reassignment arrive together
This check uses the pieces from “Rebuild counts from current job images”.
BOTIE
- Stored job images
[ { "id": "J7", "asset": "P4", "version": 2, "status": "open" }, { "id": "J8", "asset": "P4", "version": 1, "status": "open" } ]- Incoming full images
[ { "id": "J8", "asset": "P5", "version": 2, "status": "open" }, { "id": "J7", "asset": "P4", "version": 3, "status": "done" }, { "id": "J8", "asset": "P5", "version": 2, "status": "open" } ]
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 information would an incremental counter need to retract a moved job without rebuilding the full view?
Retain the previous contribution or an appropriate before-image, and commit projection progress under a documented replay policy.
The small projection rebuild retains full images and has no persisted network cursor. Real sinks need checkpoint and retention handling.
Work through the Python challenges →