← All workshopsRead The New Sensor Sends a Different Document

NoSQL

Read the two sensor formats through a declared adapter

BOTIE

Connect documents to Read each supported document shape. Inspect each decoded value and unit before attaching the Celsius conversion.
Ready to test
0 passed · 0 failed · 2 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

Connect documents to Read each supported document shape. Inspect each decoded value and unit before attaching the Celsius conversion.

The collection contains both old Celsius fields and new nested measurements.

Inspect the component calculation
Read each supported document shape(
  Versioned reading documents: Versioned sensor documents
)
Examples and results
Versioned sensor documents
[
  {
    "id": "R1",
    "schema": 1,
    "temp_c": 20
  },
  {
    "id": "R2",
    "schema": 2,
    "temperature": {
      "value": 77,
      "unit": "F"
    }
  }
]
Required result
[
  {
    "id": "R1",
    "value": 20,
    "unit": "C"
  },
  {
    "id": "R2",
    "value": 77,
    "unit": "F"
  }
]
Versioned sensor documents
[
  {
    "id": "R4",
    "schema": 2,
    "temperature": {
      "value": -5,
      "unit": "C"
    }
  }
]
Required result
[
  {
    "id": "R4",
    "value": -5,
    "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 local adapter returns a limited read view and does not migrate persistent documents or replace server validation. 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.

Old and new shapes describe subzero readings

This check uses the pieces from “Adapt each supported sensor shape”.

BOTIE

R8 is version one with temp_c minus five. R9 is version two with value fourteen and unit F. Predict the canonical Celsius documents while preserving their input order.
Versioned sensor documents
[
  {
    "id": "R8",
    "schema": 1,
    "temp_c": -5
  },
  {
    "id": "R9",
    "schema": 2,
    "temperature": {
      "value": 14,
      "unit": "F"
    }
  }
]

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.

Why is a projection containing only the declared measurement fields insufficient as a complete persistent migration?

A migration must also preserve required metadata, coordinate writers and update query/index paths.

The local adapter returns a limited read view and does not migrate persistent documents or replace server validation.

Work through the Python challenges →
Continue the courseThe Bad Update Reached Every Replica. What Can We Restore? →
← Why Does the Dashboard Still Count a Job That Was Closed?