aicam opened a new pull request, #6896:
URL: https://github.com/apache/texera/pull/6896
### What changes were proposed in this PR?
Add **per-computing-unit dataset mounting** on top of the mount
infrastructure (#6866) — the platform step of the dataset-mounting feature
(#6606).
A user can mount / list / unmount a dataset version on a running computing
unit. The platform asks that CU's node mounter to perform the mount and reports
the in-pod path back; nothing consumes the mount yet — that is the follow-up
Python-UDF PR.
- **Per-computing-unit mount API** — `GET/POST/DELETE
/computing-unit/{cuid}/mounts` (`ComputingUnitManagingResource`), backed by a
**credential-free** `MounterClient` that talks to the CU's node mounter over
HTTP. Authorization stays in file-service via the pod's JWT — no credential
enters the platform path.
- **`FileResolver`** — resolve a dataset path to `(repo, versionHash)` and
back, so a mount is shown to the user as `/owner/dataset/version`.
- **"Mount datasets into computing unit" UI** — a per-CU modal, opened from
the computing-unit selector, to mount / list / unmount datasets.
### Any related issues, documentation, discussions?
Closes #6863 · part of #6606 · builds on #6866.
### How was this PR tested?
- `sbt ComputingUnitManagingService/Test/compile` green (main + test).
- `MounterClientSpec` exercises mount / list / unmount against a stub
node-mounter HTTP server, asserting the request shape and non-2xx error
handling.
- Validated end-to-end on a single-node minikube: mounting a dataset version
onto a CU via the modal, listing it, and unmounting it.
### Was this PR authored or co-authored using generative AI tooling?
Generated-by: Claude Opus 4.8
--
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]
