The GitHub Actions job "Required Checks" on 
texera.git/backport/6197-refresh-lakekeeper-warehouse-s3-endpoint-v1.2 has 
succeeded.
Run started by GitHub user Yicong-Huang (triggered by Yicong-Huang).

Head commit for run:
af8de6779c6b30deddd78a4bf9fda29044165623 / Jiadong Bai 
<[email protected]>
fix(local-dev): refresh Lakekeeper warehouse S3 endpoint when it already exists 
(#6197)

### What changes were proposed in this PR?

Makes `lakekeeper-init` (in `bin/single-node/docker-compose.yml`) keep
the Iceberg warehouse's S3 endpoint in sync with the current
`STORAGE_S3_ENDPOINT`. The warehouse persists its endpoint in
Lakekeeper's own DB; `local-dev` sets `STORAGE_S3_ENDPOINT` to the host
**LAN IP** (not `localhost`) so both the containerized Lakekeeper and
the host JVMs — which reach MinIO directly via Iceberg remote-signing —
use the same address. But that IP changes across networks / DHCP leases,
and the init was idempotent: it **skipped** the warehouse when it
already existed, so the stale endpoint was never refreshed. Workflow
execution then failed with an opaque
`org.apache.iceberg.exceptions.RESTException: Unable to process` at
`createTable`.

Instead of skipping, the existing-warehouse branch now `POST`s the
current endpoint + credentials to
`/management/v1/warehouse/{id}/storage` on every run. This is
non-destructive and preserves existing Iceberg tables (their metadata
stores `s3://bucket/...` paths, not the endpoint).

### Any related issues, documentation, discussions?

Closes #6195

### How was this PR tested?

- Verified the same `POST /management/v1/warehouse/{id}/storage` call
heals a live stack whose warehouse had a stale IP: it returned HTTP 200
and the vended endpoint updated to the current host IP, after which
workflow execution succeeded.
- `docker compose -f bin/single-node/docker-compose.yml config -q`
validates the file.
- Extracted the rendered `lakekeeper-init` command and confirmed `bash
-n` passes (after applying compose's runtime `$$`→`$` unescaping), so
the added heredoc/shell is syntactically sound.

### Was this PR authored or co-authored using generative AI tooling?

(backported from commit aaed0857c8a73a4b13fd174417cd9a823f1bab25)

Generated-by: Claude Opus 4.8 (1M context)

Report URL: https://github.com/apache/texera/actions/runs/30431357979

With regards,
GitHub Actions via GitBox

Reply via email to