Free Developer Tool · Apache Ossie / Dosi

Semantic Model Converter

Convert Cube, dbt, Omni and other supported platform models to Apache Ossie, or export Ossie / Dosi YAML to another format. Try prefilled examples, inspect diagnostics, edit files and download results.

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.

Import to Ossie or Export to Your Platform

A semantic model describes datasets, fields, relationships and metrics. Choose Import to Ossie for supported vendor YAML, JSON or BIM bundles, or Export from Ossie for Apache Ossie YAML and supported Dosi extensions. The tool sends a snapshot to Datus for conversion using Apache Ossie converters with compatibility and quality checks. The generated files are a starting point for import into your target platform.

How to Convert a Semantic Model

Choose a Direction and Load an Example
Select Import to Ossie or Export from Ossie. Each direction opens with a prefilled example. Upload your source files or folder, paste a new definition, or choose a sample bundle. Source files stay editable.
Choose the Source or Target Platform
For import, choose the original platform; the target is Apache Ossie. For export, choose the destination format. Fill in fields marked with an asterisk. Database is optional where offered. A preferred SQL dialect selects an existing expression; it does not translate SQL.
Convert and Review
Click Convert to submit the current input and settings. Success passes the available offline checks. Needs Review includes diagnostics; Blocked results cannot be exported.
Edit and Download
Inspect the generated files in the workbench. Download a single file directly or a multi-file ZIP with relative directories preserved. Downloads include your edits.

Supported Imports to Apache Ossie

Import support is separate from export support. The live source catalog controls availability. Snowflake Cortex Analyst and Hex are export-only in this tool; there is no general reverse importer for them here.

Cube
Omni
dbt MetricFlow (compiled manifest)
Microsoft Power BI / Fabric (BIM)
Sigma
WisdomAI
Holistics (compiled AML JSON)
Honeydew
ThoughtSpot (Model + TML)
GoodData LDM
NVIDIA Auto Ontology
OrionBelt OBML

Supported Export Formats

The workbench loads its available targets and required options from the conversion service. Exports cover these formats; available targets depend on the deployed engine version.

Snowflake Cortex Analyst
dbt MetricFlow Manifest
Cube
Omni
Microsoft Power BI / Fabric
Sigma
WisdomAI
Hex
Holistics AML
Honeydew
ThoughtSpot TML
GoodData LDM
NVIDIA Auto Ontology
OrionBelt OBML

Try Real Apache Ossie Examples

Import examples are authored test bundles for Cube, Omni, dbt and Power BI. Export examples are unchanged Apache-2.0 fixtures pinned to an upstream revision. Choose a sample in the workbench to prefill the complete input; no signup is needed.

Cube → Ossie

Three YAML files: orders, customers and a commerce view. Demonstrates relationships and a complete multi-file import.

Omni → Ossie

Views, relationships and a sales topic in a four-file bundle, ready to convert.

dbt → Ossie

A compiled semantic_manifest.json test fixture. Raw dbt project YAML is not accepted by this importer.

Power BI → Ossie

An offline model.bim file. Native expressions intentionally demonstrate the Needs Review diagnostic flow.

Omni Sales

ANSI_SQL sales model. Suggested target: Omni, producing multiple YAML files for views, relationships and topics.

NVIDIA Sales

ANSI_SQL and Snowflake expressions, including a ratio metric. Suggested target: dbt MetricFlow Manifest, producing a JSON file.

TPC-DS Retail

A larger ANSI_SQL retail model. Suggested target: Snowflake Cortex Analyst. Expected metadata warnings demonstrate the Needs Review flow.

What Conversion Does—and What Still Needs Checking

Conversion does not connect to a warehouse, run SQL or DAX, or deploy files to the target platform. Verify import and execution in that platform.

Some source constructs cannot be represented in every target. Read target-specific notes and diagnostics; do not assume every model converts losslessly.

The dbt target exports semantic_manifest.json, not the source YAML files of a runnable dbt project. Microsoft Power BI / Fabric exports offline BIM JSON.

The public tool accepts up to 1 MiB of UTF-8 input (including paths for imports) and up to 50 source files per import, with server-side request limits. Source files is sent to Datus servers when you click Convert. Inputs and generated files are not persisted by the tool; keep downloads before leaving the page.

Continue Exploring

FAQ

Frequently asked questions

What input does the semantic model converter accept?

Choose Import to Ossie for supported vendor models, including Cube YAML bundles, Omni project files, compiled dbt semantic_manifest.json and offline Power BI model.bim JSON. Choose Export from Ossie for Apache Ossie YAML and supported Dosi extensions. Imports accept up to 50 files and 1 MiB total UTF-8 content including paths. Each direction includes prefilled examples; the deployed catalog determines available formats.

Is this a YAML-to-YAML formatter?

No. Conversion maps semantic datasets, fields, relationships and metrics into a target platform’s model format. Output can be YAML, JSON, BIM, AML or TML, depending on the target. Unsupported constructs and possible loss of metadata are reported as diagnostics rather than treated as a formatting change.

Does Success mean the output will run in the target platform?

Success means the available offline conversion and quality checks passed. The tool does not connect to your warehouse, execute SQL or DAX, or deploy to the destination. Import the files into the target platform, configure any required connections, and verify metric results before using the model in production.

Are my YAML files processed in the browser?

The browser holds your editable input and output, but conversion runs on Datus servers. Clicking Convert submits a snapshot of all current source files and settings. No account is required. The tool does not persist source models or results; refresh or close the page to clear them, and download files you want to keep.

Why do some results show Needs Review or Blocked?

Needs Review means files were generated with warnings, such as metadata that the target cannot preserve. Read the diagnostics before downloading or importing them. Blocked means a conversion or quality problem prevents export. Correct the source or required settings and convert again; selecting a different target can change which constructs are supported.