Skip to content

Add post: Lumen now speaks SQL on N-dimensional scientific data#100

Open
ghostiee-11 wants to merge 8 commits into
mainfrom
add-lumen-xarray-source-post
Open

Add post: Lumen now speaks SQL on N-dimensional scientific data#100
ghostiee-11 wants to merge 8 commits into
mainfrom
add-lumen-xarray-source-post

Conversation

@ghostiee-11

Copy link
Copy Markdown
Collaborator

New post: "Lumen now speaks SQL on N-dimensional scientific data". A writeup of the recently-landed XArraySQLSource (lumen#1741).

The post explains the new capability for an xarray / Zarr / Pangeo audience and walks through the architecture, a real query end-to-end on ARCO-ERA5, the metadata that survives the SQL round-trip, and the design decisions behind per-variable table registration and the xarray-sql plus DataFusion stack.

Assets

  • 4 architecture/explanatory diagrams in the editorial cream/vermillion palette
  • 3 cell screenshots rendered from the validation notebook (Gist)
  • 1 result map (D3 + topojson, plausible temperature field on the NCEP/NCAR grid extent, marked as representative not literal)

ghostiee-11 and others added 2 commits June 5, 2026 02:18
Writeup of the new XArraySQLSource for the xarray / Zarr / Pangeo
audience. Covers the architecture, a real ARCO-ERA5 query end to
end, where coordinate metadata actually lives today (source schema,
not the result DataFrame), and the design decisions behind
per-variable table registration and the xarray-sql + DataFusion
stack.

Adds 9 files under posts/2026-06-05-lumen-xarray-source/ (index.qmd
+ 8 PNGs in images/). No project-level config or CSS changes.
@ahuang11

ahuang11 commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

Did you see my other comments in my previous PR?

@ahuang11 ahuang11 marked this pull request as ready for review June 4, 2026 21:01
@ghostiee-11

Copy link
Copy Markdown
Collaborator Author

Yupp, i did and going to do that only

@ahuang11

ahuang11 commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

For reference you can view the dev version of blog here:
https://holoviz-dev.github.io/blog-dev/

@ghostiee-11

Copy link
Copy Markdown
Collaborator Author

Yup.. Thanks!!

@ghostiee-11

Copy link
Copy Markdown
Collaborator Author

#99 (comment)

@ahuang11, By the way, I was planning to lead Post 2 (the AI wiring post on #1791) with the Lumen AI chat angle. Keeping this one focused on the Source layer, so Post 2 has the machinery to plug into. Your views on this?

@ahuang11

ahuang11 commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

Sure. I think we should still advertise Lumen from Lumen AI lens though if that makes sense (e.g. users probably don't need to know about Pipeline maybe)

@ghostiee-11

Copy link
Copy Markdown
Collaborator Author

Yeah okay.. Makes sense

@ahuang11

ahuang11 commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

Basically I imagine this description is outdated since Lumen has pivoted to AI (90% of docs advertise the AI features) but the rest of the blog can elaborate how the XArrat SQL engine works.

declarative data application framework in the HoloViz stack. You describe a Source (where data comes from), a Pipeline (how to filter and transform it), and a View (how to render it). Lumen wires the three together into a deployable Panel app, an embeddable component, or, since the Lumen AI 1.0 release earlier this year, a chat-driven exploration surface.

@ghostiee-11

Copy link
Copy Markdown
Collaborator Author

Okay sure!! Will do this
On second thought, going to merge both source and wiring into one post. Leading with the Lumen AI chat demo, SQL engine details tuck underneath as the "how it works". Rewriting now, will tag you when the draft is up.

ghostiee-11 and others added 3 commits June 7, 2026 16:04
- Reframe recap from the Lumen AI lens (chat -> agents).
- New section "From a dropped file to a SQL agent" covers PR #1791
  wiring with the actual upload-handler snippet.
- Replace mocked notebook stills with eight real Lumen AI captures.
- Rework diagram-3 (Lumen AI architecture). Add diagram-5 (upload
  flow).
- Embed hero video from YouTube.
- Pair PR #1741 (source) and PR #1791 (wiring) in Get started and
  Credits.
@ahuang11

ahuang11 commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

Is this ready for review?

@ghostiee-11

Copy link
Copy Markdown
Collaborator Author

Yupp... It is @ahuang11

@ghostiee-11

Copy link
Copy Markdown
Collaborator Author

Hey @ahuang11, for now I have removed the example images you flagged. I am investigating that from my end!!

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.

2 participants