NoSQL
Give the lookup its complete identity
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
Encode the requested parts and inspect the resulting text before connecting the store.
Two sites both use asset ID P1.
Inspect the component calculation
Encode all key parts( Ordered key parts: Requested site and asset )
Examples and results
- Requested site and asset
- 0north
- 1P1
- Required result
["north","P1"]
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.
Punctuation appears inside a site name
This check uses the pieces from “Build the complete lookup key”.
BOTIE
- Requested site and asset
- 0a
- 1b:c
- Stored status values
{ "[\"a:b\",\"c\"]": 4, "[\"a\",\"b:c\"]": 9 }- Missing status message
unavailable
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 should distinguish a failed connection from a successful lookup that reports no key?
Preserve identity, presence and transport failure as separate facts.
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 →