Skip to content

Add an opt-in Iron Head Spark SQL panel adapter - #1

Draft
boltonidze wants to merge 7 commits into
codex/joom-0.12.1from
codex/zeppelin-spark-ai-prototype
Draft

boltonidze wants to merge 7 commits into
codex/joom-0.12.1from
codex/zeppelin-spark-ai-prototype

Conversation

@boltonidze

@boltonidze boltonidze commented Oct 29, 2026 •

Copy link
Copy Markdown

Adds an optional Spark SQL assistant beside the existing notebook editor. The iframe uses the independent Iron Head /embed/sql panel and a versioned, origin/window/context-checked message bridge. SQL is inserted as a new paragraph through the normal notebook API and its ACL checks; existing text is never sent to the panel or replaced, and no paragraph is executed.

Runtime configuration defaults to disabled. Insertion requires a unique bound Spark SQL interpreter, or an explicit notebook default that unambiguously selects one. Offline/read-only/ambiguous cases retain copying; duplicate insertion requests and stale notebook contexts are rejected. An iframe stays hidden until the expected handshake, so an incompatible stage release cannot display the ordinary executing chat in the panel.

Validation: 10 host boundary tests pass. Angular production compilation passes. The final local asset-copy step hit ENOSPC; the pilot WAR combines the two newly compiled bundles with byte-verified unchanged bundles/assets from the prior successful production build. ZIP and index/runtime references were verified. Server/interpreter JARs are unchanged. The image is pinned in the separate datasci configuration PR. Full browser insertion and ACL results are recorded in the prototype evaluation report.

This PR is based on the 0.12.1 migration branch and contains only the AI adapter, its tests and UI-only build helper. It does not modify the migration branch itself.

Related prototype PRs: Iron Head API/panel, Zeppelin adapter, balloon Helm wiring.

RAT now passes locally after adding the missing Apache header to inherited joom/PORTS.md (the only initial license-check failure). Full upstream interpreter/build workflows are still separate from the targeted prototype checks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant