Free Developer Tool · Apache Ossie / Dosi

Apache Ossie to dbt MetricFlow Converter

Export Apache Ossie YAML as a dbt MetricFlow semantic_manifest.json. Try the NVIDIA Sales fixture and inspect the generated manifest before using it.

No signup · Sample models included · Offline conversion checks

Conversion Workbench

Source Files1Example

NVIDIA Sales · ANSI_SQL / SNOWFLAKE

nvidia_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.

version: 0.2.0.dev0
name: sales
description: Sales model
ai_context:
  instructions: Use approved metrics
datasets:
- name: orders
  source: analytics.public.orders
  primary_key:
  - order_id
  description: Orders
  ai_context:
    synonyms:
    - purchases
  fields:
  - name: order_id
    expression:
      dialects:
      - dialect: ANSI_SQL
        expression: order_id
    dimension:
      is_time: false
  - name: customer_id
    expression:
      dialects:
      - dialect: ANSI_SQL
        expression: customer_id
    dimension:
      is_time: false
  - name: order_date
    expression:
      dialects:
      - dialect: ANSI_SQL
        expression: order_date
    dimension:
      is_time: true
  - name: net_total
    expression:
      dialects:
      - dialect: ANSI_SQL
        expression: subtotal - discount
    dimension:
      is_time: false
- name: customers
  source: analytics.public.customers
  primary_key:
  - customer_id
  fields:
  - name: customer_id
    expression:
      dialects:
      - dialect: ANSI_SQL
        expression: customer_id
    dimension:
      is_time: false
  - name: customer_name
    expression:
      dialects:
      - dialect: ANSI_SQL
        expression: name
    dimension:
      is_time: false
relationships:
- name: orders_to_customers
  from: orders
  to: customers
  from_columns:
  - customer_id
  to_columns:
  - customer_id
metrics:
- name: revenue_per_customer
  description: Revenue per customer
  expression:
    dialects:
    - dialect: ANSI_SQL
      expression: SUM(orders.subtotal) / COUNT(DISTINCT customers.customer_id)
    - dialect: SNOWFLAKE
      expression: SUM(orders.subtotal)::NUMBER / COUNT(DISTINCT customers.customer_id)

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

Export an Apache Ossie semantic model as a dbt MetricFlow manifest. The included NVIDIA Sales fixture contains ANSI_SQL and Snowflake expressions and a ratio metric, giving you a concrete export input to review.

Source Format

Apache Ossie YAML with model definitions supported by the deployed engine. For a source containing multiple semantic models, select the intended model when the workbench requests it.

Generated Output

semantic_manifest.json for the dbt MetricFlow Manifest target. This is compiled semantic metadata, not the source YAML and SQL of a runnable dbt project.

Conversion Steps

Load the NVIDIA Sales fixture or upload your Apache Ossie YAML.
Keep the dbt MetricFlow Manifest destination and complete required model or dataset selections.
Convert and inspect the generated JSON, metric expressions and compatibility diagnostics.
Download the manifest, validate it against your intended MetricFlow workflow and retain the original project configuration separately.

Review Before Using the Output

A generated manifest does not replace dbt project YAML, SQL models or connection profiles.

SQL dialect preferences select existing source expressions; they do not translate expressions or run MetricFlow queries.

Continue Exploring

FAQ

Frequently asked questions

Which file does the Ossie-to-dbt target generate?

The dbt MetricFlow Manifest target produces semantic_manifest.json. It does not generate the original YAML files, SQL models or connection configuration of a runnable dbt project.

Can the NVIDIA Sales example be exported to a dbt manifest?

The workbench provides it as an Apache Ossie export fixture with ANSI_SQL and Snowflake expressions and a ratio metric. Convert the current snapshot, then inspect the target diagnostics and generated JSON.

Will exporting a manifest run MetricFlow?

No. Conversion performs the available offline checks without starting dbt or MetricFlow or querying a warehouse. Validate the manifest against the versions and metric workflows in your own environment.