mengw15 opened a new pull request, #8550:
URL: https://github.com/apache/texera/pull/8550

   ### What changes were proposed in this PR?
   
   Backport of #8542 to `release/v1.3`: a clean cherry-pick of its squash 
commit, no adaptations — every added and removed line is identical to #8542's. 
See #8542 for the change itself (MinIO → RustFS in the compose files, the Helm 
chart, CI, tests and docs).
   
   Why a `feat` goes to a release branch: MinIO removed its Docker Hub images 
on 2026-09-11 (`minio/minio:RELEASE.2025-02-28T09-55-16Z` and `minio/mc` now 
return 404), so a v1.3 built from this branch can neither be deployed with its 
default object store nor pass its integration CI. It also un-breaks the 
pre-merge backport check for every amber change: `Backport Checks` runs 
`main`'s `build.yml`, which since #8542 provisions RustFS with `texera_rustfs`, 
against this branch's tree, whose `storage.conf` still said `texera_minio`, so 
`aws s3api create-bucket` fails with `InvalidAccessKeyId` (e.g. #8432).
   
   v1.3 has not been released, so #8542's migration note (object-store on-disk 
format and volume names change, no in-place upgrade) affects no deployed 
release.
   
   Source: 12aeeab5816b12880c5f58970460adf87b548d89
   
   ### Any related issues, documentation, discussions?
   
   Backport of #8542.
   
   ### How was this PR tested?
   
   The branch is verified to be exactly #8542's squash commit cherry-picked 
onto `release/v1.3` (48 files, no conflicts; the added/removed lines diff empty 
against #8542). Seven of those files were also changed on `main` after the v1.3 
cut (#7930, #8307, #7664, #8032, #6866, #8073); #8542's hunks in them are 
self-contained MinIO→RustFS renames and reference none of those later 
additions. Locally on this tree: `helm dependency build` and `helm template` 
with the default and `values-development.yaml` values render cleanly with no 
remaining `minio` reference, and `helm lint` passes; `sbt 
WorkflowCore/Test/compile FileService/Test/compile` succeed (the two amber 
Scala changes are comment-only); `ruff check` and `ruff format --check` at CI's 
pinned 0.14.7 pass on the changed `amber/` Python files. Release-branch CI on 
this PR runs the full matrix, with the integration jobs now provisioning RustFS.
   
   ### Was this PR authored or co-authored using generative AI tooling?
   
   Yes. Generated-by: Claude Code (claude-fable-5-1)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to