Task Summary
Remove the obsolete bin/bootstrap-lakekeeper.sh script, which has been superseded by bin/local-dev.sh.
bin/bootstrap-lakekeeper.sh runs Lakekeeper natively on the host. It was added because, at the time, running Lakekeeper in Docker did not work for local development: the warehouse's S3 endpoint was registered as a Docker-internal hostname (texera-minio:9000) that the host-native Texera could not resolve, while switching it to localhost broke the Lakekeeper-container → MinIO connection. So the REST catalog required Lakekeeper to run on the host.
bin/local-dev.sh (#5961) now starts Lakekeeper in Docker and sets the S3 endpoint to the host's LAN IP, which is reachable from both the host-native Texera and the Lakekeeper container. I verified the REST-catalog path end-to-end with local-dev.sh: workflow results are written to the texera-iceberg MinIO bucket through Lakekeeper.
Since Docker Lakekeeper now works, bin/bootstrap-lakekeeper.sh is redundant and can be removed.
Task Type
Task Summary
Remove the obsolete
bin/bootstrap-lakekeeper.shscript, which has been superseded bybin/local-dev.sh.bin/bootstrap-lakekeeper.shruns Lakekeeper natively on the host. It was added because, at the time, running Lakekeeper in Docker did not work for local development: the warehouse's S3 endpoint was registered as a Docker-internal hostname (texera-minio:9000) that the host-native Texera could not resolve, while switching it tolocalhostbroke the Lakekeeper-container → MinIO connection. So the REST catalog required Lakekeeper to run on the host.bin/local-dev.sh(#5961) now starts Lakekeeper in Docker and sets the S3 endpoint to the host's LAN IP, which is reachable from both the host-native Texera and the Lakekeeper container. I verified the REST-catalog path end-to-end withlocal-dev.sh: workflow results are written to thetexera-icebergMinIO bucket through Lakekeeper.Since Docker Lakekeeper now works,
bin/bootstrap-lakekeeper.shis redundant and can be removed.Task Type