Free Developer Tool · Apache Ossie / Dosi

Apache Ossie to Omni Converter

Export Apache Ossie YAML as Omni views, relationships and topics. Try the Omni Sales fixture, inspect multi-file output and download an editable ZIP.

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

Create Omni views, relationships and topics from an Apache Ossie model. This page starts with the Omni Sales Ossie fixture and opens the export direction with Omni selected.

Source Format

Apache Ossie YAML. Review the source datasets and relationships before converting, particularly when you are replacing an existing Omni model.

Generated Output

A set of Omni model files. Use the output tree to review each generated definition and download a ZIP to preserve the directory structure.

Conversion Steps

Review the Omni Sales source model or upload another compatible Ossie definition.
Keep Omni as the target and inspect any model or SQL-expression options.
Convert, examine each generated view, relationship and topic, and read diagnostics.
Download the current files, apply them through your Omni workflow and test representative queries.

Review Before Using the Output

Exporting files does not publish a project or configure an Omni connection.

Validate the topic field set and the chosen native SQL expressions against your own warehouse.

Continue Exploring

FAQ

Frequently asked questions

What does an Ossie-to-Omni export contain?

The target can produce separate view, relationship and topic files. The included Omni Sales source is an Apache Ossie model; inspect the generated file tree and diagnostics to see the output contract for your model.

Does exporting an Omni model publish it to my account?

No. The tool generates downloadable model files without authenticating to Omni or publishing a project. Apply the files through your own destination workflow and verify the resulting model.

How should I review SQL in an Omni export?

Inspect the expressions available in the source model and select a preferred existing dialect where offered. Conversion does not translate warehouse SQL, so verify the generated definitions and representative queries against your warehouse.