tanishqgandhi1908 opened a new pull request, #6974:
URL: https://github.com/apache/texera/pull/6974
### What changes were proposed in this PR?
The model REST API from #6869 and #6872 covers create / list / access /
version upload. This PR extends and add more endpoints so the management UI can
be built as frontend-only work.
**New endpoints on `ModelResource`**
| Endpoint | Purpose |
| --- | --- |
| `GET /model/presign-download` (+ `-s3`, `public-`, `public--s3`) |
short-lived signed URL for one file โ file preview, and how a worker reads a
model |
| `GET /model/{mid}/diff` | staged (uncommitted) changes, so the upload page
can list pending files |
| `PUT /model/{mid}/diff?filePath=` | discard one staged change |
| `POST /model/{mid}/existing-upload-files` | which of these files does the
repo already hold at the same size โ lets the client skip re-uploading large
weights |
| `GET /model/{mid}/versionZip?mvid=\|latest=true` | download a whole
version |
| `GET /model/user-model-owners` | owner facet for the list page |
**Validation.** `framework` and `format` are now checked against
`SUPPORTED_FRAMEWORKS` (`pytorch`, `tensorflow`, `onnx`, `sklearn`) and
`SUPPORTED_FORMATS` (`torchscript`, `state-dict`, `safetensors`, `onnx`,
`savedmodel`, `joblib`, `pickle`), rejecting anything else with 400, so the
loader in can dispatch on a known value.
### Any related issues, documentation, discussions?
- Closes #6498
- Part of #6494
- Stacked on #6872. Base is `main`, so the diff shows the parent PRs'
commits until they merge;
### How was this PR tested?
```
sbt scalafixAll && sbt scalafmtAll
sbt "FileService/test"
```
`Suites: completed 16, aborted 0` ยท `Tests: succeeded 346, failed 0` โ the
whole file-service suite, not only the touched specs.
### Was this PR authored or co-authored using generative AI tooling?
Generated-by: Claude Code (Claude Opus 5)
--
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]
