Free Developer Tool · Apache Ossie / Dosi

Apache Ossie to Cube Converter

Export Apache Ossie YAML as Cube model definitions. Inspect joins, dimensions and measures, edit generated files and download a model bundle for review.

No signup · Sample models included · Offline conversion checks

Conversion Workbench

Source Files1Example

Omni Sales · ANSI_SQL

omni_sales.yml

# Licensed to the Apache Software Foundation (ASF) under one
# or more contributor license agreements.  See the NOTICE file
# distributed with this work for additional information
# regarding copyright ownership.  The ASF licenses this file
# to you under the Apache License, Version 2.0 (the
# "License"); you may not use this file except in compliance
# with the License.  You may obtain a copy of the License at
#
#   http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing,
# software distributed under the License is distributed on an
# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
# KIND, either express or implied.  See the License for the
# specific language governing permissions and limitations
# under the License.

# yaml-language-server: $schema=../../../../core-spec/ossie-schema.json
#
# Fixture A -- all-native round-trip (Ossie -> Omni -> Ossie).
# Star schema; every construct maps to a native Omni slot. Documented
# normalizations on the Ossie -> Omni -> Ossie trip: relationship names are
# regenerated (`<from>_to_<to>`), and unique_keys that merely restate the
# primary key are absorbed by it.

version: "0.2.0.dev0"

name: sales
description: Sales orders with customer attributes
ai_context:
  instructions: "Use this model for order analysis."
datasets:
  - name: orders            # fact: no incoming relationship -> topic base_view
    source: samples.tpch.orders
    primary_key: [o_orderkey]
    description: One row per order
    fields:
      - name: o_orderkey
        expression:
          dialects:
            - dialect: ANSI_SQL
              expression: o_orderkey
        description: Order identifier
      - name: o_custkey
        expression:
          dialects:
            - dialect: ANSI_SQL
              expression: o_custkey
      - name: o_orderdate
        expression:
          dialects:
            - dialect: ANSI_SQL
              expression: o_orderdate
        label: Order Date
        dimension:
          is_time: true
        ai_context:
          synonyms: [order date, date]
      - name: o_totalprice
        expression:
          dialects:
            - dialect: ANSI_SQL
              expression: o_totalprice
  - name: customer
    source: samples.tpch.customer
    primary_key: [c_custkey]
    fields:
      - name: c_custkey
        expression:
          dialects:
            - dialect: ANSI_SQL
              expression: c_custkey
      - name: c_name
        expression:
          dialects:
            - dialect: ANSI_SQL
              expression: c_name
        description: Customer name
relationships:
  - name: orders_to_customer
    from: orders
    to: customer
    from_columns: [o_custkey]
    to_columns: [c_custkey]
metrics:
  - name: total_revenue
    expression:
      dialects:
        - dialect: ANSI_SQL
          expression: SUM(orders.o_totalprice)
    description: Total order revenue
    ai_context:
      synonyms: [revenue, sales]
  - name: order_count
    expression:
      dialects:
        - dialect: ANSI_SQL
          expression: COUNT(*)
    description: Number of orders

Source files stay in memory. Upload all referenced files together.View Original Example

Results

Choose a target and convert to preview temporary files.

Clicking Convert sends the current source files to Datus servers. No warehouse connection or SQL execution is performed.

What This Converter Does

Generate Cube model definitions from Apache Ossie YAML. The workbench opens the export direction with the Cube destination selected and an editable sales model as its source.

Source Format

Apache Ossie YAML, including the supported Dosi extensions understood by the deployed converter. Use the included sales fixture to inspect the structure before uploading your model.

Generated Output

Cube model files for review and import into your own project. Multiple generated files download as a ZIP with their relative paths and your current edits.

Conversion Steps

Inspect the Ossie sales model or upload a supported YAML source.
Check the Cube target and fill in any required options shown by the converter catalog.
Convert the snapshot and inspect the generated Cube file tree, dimensions, measures and joins.
Download the definitions, integrate them into your Cube project and compare representative query results.

Review Before Using the Output

The output does not configure Cube API serving, caching, warehouse credentials or deployment.

Keep the original Ossie model and review the target diagnostics before replacing existing Cube definitions.

Continue Exploring

FAQ

Frequently asked questions

What source does the Ossie-to-Cube converter accept?

Start with an Apache Ossie YAML model, including supported Dosi extensions. The prefilled sales fixture lets you inspect the source before uploading your own definition. The deployed target catalog determines available output options.

Does a Cube export include serving and caching configuration?

The tool converts supported semantic definitions. It does not configure Cube serving, caching, connection credentials or deployment. Review the output, add the environment configuration your Cube project requires and verify representative queries.

How do I download multiple generated Cube files?

Use Download Locally for a ZIP that preserves relative paths and includes your current edits. Review the diagnostics and the destination model before replacing existing Cube definitions.