mengw15 opened a new issue, #8588: URL: https://github.com/apache/texera/issues/8588
The computing-unit picker badges the selected unit's status; the warehouse picker shows none, because `DashboardWarehouse` carries no status field — not because warehouses have none. Lakekeeper's management API returns `status` (`active`/`inactive`) and `protected` per warehouse, and neither reaches the frontend. Surfacing `active`/`inactive` alone would be close to worthless: Texera only creates and deletes warehouses and never deactivates one, so the badge would be permanently green. The signal that would actually help is **reachability** — whether the warehouse can be read from and written to right now. A warehouse whose storage profile has gone stale (see #8569) still lists and still looks healthy, while every read and write against it fails; a badge reflecting that would turn a confusing failure into an obvious one. Lakekeeper has no health endpoint for this, so it would mean a probe on the Texera side (the write probe its storage-profile update performs is the shape of the check), plus a status field on `DashboardWarehouse` and a badge on the picker and the dashboard row. Part of #6870. -- 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]
