UX-CAT-003 — Remove the artificial Warehouse hierarchy
| Field | Value |
|---|---|
| Status | Open finding; source-verified and product-reviewed |
| Severity | Low |
| Affected surface | Catalog and SQL Editor top-level navigation |
| Implementation issue | oqullus #542 |
| Code-change repository | sparqd/oqullus |
Where the problem appears
Inspect the Warehouse group and verify whether it has a backend identifier, authorization state, or query behavior.
Concrete observed case
Warehouse is a hard-coded collapsible presentation group. It is not a Trino catalog, connection, compute cluster, metastore, storage location, or policy boundary. Lakehouse would also be too format-specific for future heterogeneous sources.
Expected condition
List catalogs directly on the Catalog page. If SQL Editor needs a section heading, use Data sources while retaining Catalog as the technical selector and object type.
Cause and evidence
- Expanding the group triggers no warehouse discovery.
- All top-level entries are placed beneath it regardless of connector semantics.
- It has no canonical identity or security boundary.
Why it matters
The extra level misrepresents the architecture and creates terminology that will not scale to JDBC, streaming, or synthetic sources.
Existing controls and workarounds
Treat Warehouse only as a visual container; do not infer compute or storage semantics from it.
Alternatives considered
- Recommended: remove it in Catalog and use Data sources only where grouping helps.
- Group by connector capabilities when multiple source classes exist.
- Rename to Lakehouse — rejected because it excludes future non-lakehouse sources.
Component involvement
- Oqullus and product own navigation terminology.
- Catalog identity remains supplied by the query platform.
- Future grouping derives from capabilities, not a hard-coded product metaphor.
Reproduction and verification
Follow CAT-S012. Record the visible state, request outcome, effective identity, and recovery behavior relevant to this finding.
Resolution conditions
Close when no false architecture level is shown and user-facing terminology remains valid for the supported source model.
Validation and blockers
Oqullus, product, and design owners must validate.