UX-CAT-001 — Do not present local rename as a durable mutation
| Field | Value |
|---|---|
| Status | Open finding; source-verified, live reproduction pending |
| Severity | High |
| Affected surface | Catalog tree Rename interaction |
| Implementation issue | oqullus #530 |
| Code-change repository | sparqd/oqullus |
Where the problem appears
Double-click a disposable tree label, rename it, then reload and compare Trino, HMS, Superset, and DataHub.
Concrete observed case
Rename changes only browser memory. The label appears changed during the session but refresh restores the original backend-derived name.
Expected condition
Remove Rename until a durable, authorized, audited, conflict-aware rename exists. If retained as a display alias, label it explicitly and store it through an authoritative alias service.
Cause and evidence
- The current action mutates local tree state only.
- No backend identity changes.
- Refresh restores the source name.
Why it matters
Users can reference a name that never existed, lose work silently, or believe downstream identities and queries were updated.
Existing controls and workarounds
Do not use tree Rename. Use the authoritative object-management path and refresh Catalog.
Alternatives considered
- Recommended: remove the action.
- Implement durable engine/metastore rename with governance migration and rollback.
- Support a display alias — only if clearly distinct from the queryable object name.
Component involvement
- Oqullus removes or accurately labels the action.
- Platform/BFF owns any durable rename orchestration.
- DataHub and lineage owners handle identity migration if rename becomes supported.
Reproduction and verification
Follow CAT-S003. Record the visible state, request outcome, effective identity, and recovery behavior relevant to this finding.
Resolution conditions
Close when the false action is removed or an approved rename survives reload and updates query identity, metadata, lineage, audit, conflict, and recovery consistently.
Validation and blockers
Oqullus and product are primary; durable rename would require cross-platform ownership.