Skip to content
Saiku Cloud

Schemas

Schemas is the catalog of saved Mondrian schemas in your tenant. Each schema is one or more cubes; each cube is what people and agents actually query. The page shows the schema name, the cubes inside, the connection it points at, and the last time it was updated.

Most of the time you’ll just glance at this page to confirm what’s saved. The two cases when you’ll actually do something here:

Editing a cube’s XML. Click a schema to open the detail view. The XML appears in an editor; Edit flips it to writable and Save persists the change. The engine refreshes its cache on the next query, so changes are live within seconds.

Cleaning up. Trash icon on the row, confirm, gone. There’s no undo — the schema XML is purged and any workbook pointing at its cubes returns a schema not found error until you re-save. Worth keeping a local backup before deletes if there’s any chance you’ll want it back.

What schema XML looks like

You shouldn’t usually need to read this — the Schema designer writes it for you — but a minimal cube reads:

<Schema name="sales">
  <Cube name="Sales">
    <Table name="fact_sales"/>
    <Dimension name="Date" foreignKey="date_id">
      <Hierarchy hasAll="true" primaryKey="date_id">
        <Table name="dim_date"/>
        <Level name="Year"    column="year"    type="Numeric"/>
        <Level name="Quarter" column="quarter" type="Numeric"/>
        <Level name="Month"   column="month"   type="Numeric"/>
      </Hierarchy>
    </Dimension>
    <Measure name="Revenue" column="revenue"  aggregator="sum"/>
    <Measure name="Orders"  column="order_id" aggregator="count"/>
  </Cube>
</Schema>

The editor accepts whatever Mondrian 4 accepts. If you save invalid XML we surface the parser error inline rather than silently keeping broken state.