Engineering & roadmap

Implementation review: PB-118, PR 1053

Development documentation. This guide follows a reviewed snapshot of main and may describe capabilities not yet in Stable. Check Preview labels and release notes. Some executable names and paths remain unchanged for compatibility. Legacy names explained ↗
Field Value
Backlog item PB-118: Databricks notebook conversion says what it could not carry over (issue #854)
Pull request #1053 and #1146, merged, with #1242 and #1289; main at 063b84ed
Package none
Reviewer Product management thread
Date 2026-11-01
Environment Linux container, engine from source, no Databricks workspace

Outcome#

Accepted (recommended).

Recommended by: Product management thread. Decided by (product owner): Chris, 'Accept all six' on the decision card on 2026-11-01 (project message cmsg_018T4o2pQdpbLBNhHpgVNNGpHEi2797KQ2xEh3mRcFsM8K).

Acceptance criteria#

# Criterion (copied from the backlog item) Result Evidence
1 Each dropped or changed construct is listed with its cell Met test_a_databricks_import_lists_each_dropped_or_changed_construct_with_its_cell and test_an_import_names_the_databricks_gotchas_with_their_cell (sidecar/tests/test_notebook_formats.py)
2 Round-trip tests cover widgets, %sh, %fs and dbutils Met test_widgets_sh_fs_and_dbutils_survive_a_round_trip_through_databricks_source. #1242 adds round trips through Databricks, Fabric and Jupyter for every cell
3 Docs list what converts and what doesn't Met docs/notebook-import-export.md, "What a Databricks conversion doesn't carry over"

Tests: test_notebook_formats.py and test_fabric_spark.py, 99 passed.

Need a hand?

Find a fix in troubleshooting, or share a reproducible issue with the community.

Get support ↗Improve this guide on GitHub ↗

Search documentation

Start typing to search all 178 guides.

Search runs in your browser esc to close