Serve every kind's reads through the unified resource endpoints
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 35/100
Direzione di ricerca
Start by reading the generated interfaces from #9485 and the shared resource code under common/resource, then trace the agent service client calls and access check from #9488. The task spans several services, generated endpoints, paging, search, and compatibility with existing reads. It is done when all six kinds serve the specified reads through generated interfaces with one access check and the agent service can list a user's datasets.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Task Summary
Reading a resource takes a different endpoint for each kind, and two kinds cannot be read one at a time at all: there are GET /workflow/{wid}, GET /dataset/{did}, GET /model/{mid} and GET /computing-unit/{cuid}, but nothing for environments and warehouses. Lists differ in the same way, from GET /workflow/list to GET /pve/db and GET /warehouse/status. So a feature that works across kinds, such as letting the agent list the datasets a user can read (#9377) or a list page in the React frontend (#9387), needs a client for every kind.
This task serves the reads of every kind through the endpoints of #9395, from the shared code, before any write moves:
| Operation | Endpoint | Kinds |
|---|---|---|
| List | GET /{kind} |
all six |
| Read | GET /{kind}/{rid} |
all six |
| List versions | GET /{kind}/{rid}/versions |
workflows, datasets, models |
| Read a version | GET /{kind}/{rid}/versions/{vno} |
workflows, datasets, models |
Because these endpoints only read through the views of #9487, they cannot break anything that works today, and the old read endpoints stay until #9492.
Before
flowchart LR
c["Client"]
ds["Dashboard Service"]
fs["File Service"]
cs["Computing Unit<br/>Managing Service"]
ew["Environments,<br/>warehouses"]
c -- "GET /workflow/{wid}" --> ds
c -- "GET /dataset/{did}<br/>GET /model/{mid}" --> fs
c -- "GET /computing-unit/{cuid}" --> cs
c -. "no read endpoint" .-> ew
After
flowchart LR
c["Generated client"]
ifc["Generated interface<br/>in each kind's service"]
sh["Shared read code<br/>common/resource"]
chk["One access check"]
v[("resource,<br/>resource_version<br/>views")]
c -- "GET /{kind}<br/>GET /{kind}/{rid}<br/>and their versions" --> ifc
ifc --> sh
sh --> chk
sh --> v
Scope
- The reads above. Served from the generated interfaces of #9485, with paging and a text query, and filtered by the check of #9488.
- One shape. A read returns the common fields of
resource, and the kind's own fields asspec. What only one kind has, such as the files of a dataset version, stays an operation of that kind. - The agent service first. The agent service calls these reads through the client of #9485. When the frontend moves is a question for #9492.
This task changes no write, which is #9490.
Discussion Points
- Where the reads run. Each kind's service serves its own kind, so the gateway would route
/api/datasetsto file-service and/api/computing-unitsto the Computing Unit Managing Service. Workflows and warehouses are served by the Dashboard Service and environments by the computing unit, both on Dropwizard 1.3, so they need a Dropwizard 4 host first, as discussion point 3 of the parent issue says. - Search. The dashboard search maps the columns of each kind by hand into one schema of 28 columns. It can become a text query on these lists, with its full-text indexes on
resource, or stay a separate endpoint over the same views.
Done when every kind answers the reads above through generated interfaces and one access check, and the agent service lists a user's datasets with the generated client.
Task Type
- Refactor / Cleanup
- DevOps / Deployment / CI
- Testing / QA
- Documentation
- Performance
- Other
- Lingua principale
- Scala
- Stelle
- 333
- Fork
- 202
- Merge medio
- 3g 11h
- PR unite (30g)
- 185
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di apache/texera
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
I maintainer di solito rispondono entro 1 giorno
-
addOperator returns an error but still adds the operatorForse già presa @sunny-kavixo l’ha presa 5 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
apache/texera#9121 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Failed tool calls are marked as succeeded (isError is always false)Forse già presa @oliarmak-web l’ha presa 14 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 80/100
apache/texera#9120 · 8 commenti · 1 assegnatario ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
apache/texera#8682 · 5 commenti ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di apache/texera
Issue simili
-
? - Needs Triage bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
NVIDIA/cudf-spark#16937 ·
I maintainer di solito rispondono entro 1 giorno
-
LFST not-issued-store count truncation can incorrectly clear strictShouldWaitForse già presa @weidingliu l’ha presa oggi. Apertamodule: memory type: bug/reported
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
OpenXiangShan/XiangShan#6974 · 1 commento · 1 assegnatario ·
I maintainer di solito rispondono entro 3 giorni
-
bug indigo
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
PurpleKingdomGames/indigoengine#300 · 1 commento ·
-
JavaReservoirSampleOperator returns the whole input when the dataset size is unknownForse già presa @sasmith-14 l’ha presa 2 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
apache/wayang#884 · 3 commenti ·
I maintainer di solito rispondono entro 2 giorni
-
AI Generated CI/CD ⚒️ Flaky-tests 🐦 python 🐍
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
valkey-io/valkey-glide#7722 ·
I maintainer di solito rispondono entro 1 giorno