[docs] Add HTTP Gateway lakehouse quickstart - #4231
Conversation
|
Could someone please review this PR when you get a chance? It adds the HTTP Gateway lakehouse quickstart for #4221. Thanks!! |
pbanakar
left a comment
There was a problem hiding this comment.
Hi @pranavshuklaa, thanks for the PR! left some comments
| @@ -0,0 +1,490 @@ | |||
| --- | |||
| title: Real-Time Lakehouse via the HTTP Gateway | |||
| sidebar_position: 3 | |||
There was a problem hiding this comment.
check if this conflicts with an existing quickstart. Our page_user_profile.md is at 4 and lakehouse.md and security.md both using sidebar_position 2 could you correct it? currently no file at 3?
| (however, Compose v1 might work with a few adaptions). | ||
| ::: | ||
|
|
||
| ### Build the Gateway image |
There was a problem hiding this comment.
every other quickstart uses a pre-built Docker Hub image. This one requires the user to have the Fluss source repo checked out locally and run docker/fluss-gateway/build.sh. That's not a quickstart experience that's a dev setup. The guide should either wait for a published Gateway image or clearly state this is a developer preview requiring a source build upfront, and this feature is for 1.0v that is not released yet
| ### Quitting SQL Client | ||
|
|
||
| ```sql title="Flink SQL" | ||
| quit; |
There was a problem hiding this comment.
all other Fluss quickstarts use exit;
Purpose
Linked issue: close #4221
Add an end-to-end quickstart showing how to build a real-time lakehouse using the Fluss HTTP Gateway, Fluss, Flink, Paimon, and RustFS.
Brief change log
$lakeand$lake$snapshots.Tests
API and Format
No API or storage format changes.
Documentation
Adds a new HTTP Gateway quickstart for a real-time lakehouse and documents the existing Gateway REST API, Fluss datalake integration, Flink Union Read, and Paimon tiering workflow.