Free Developer Tool · Apache Ossie / Dosi

dbt to Apache Ossie Converter

Import a compiled dbt semantic_manifest.json into Apache Ossie. Try an editable manifest fixture, review conversion diagnostics and download Ossie YAML.

No signup · Sample models included · Offline conversion checks

Conversion Workbench

Source Files1Example

dbt · Compiled Semantic Manifest

target/semantic_manifest.json

{
  "semantic_models": [
    {
      "name": "orders",
      "description": "One row per order",
      "node_relation": {
        "alias": "ORDERS",
        "schema_name": "PUBLIC",
        "database": "ANALYTICS",
        "relation_name": "ANALYTICS.PUBLIC.ORDERS"
      },
      "entities": [
        {
          "name": "id",
          "type": "primary"
        },
        {
          "name": "customer_id",
          "type": "foreign"
        }
      ],
      "measures": [],
      "dimensions": [
        {
          "name": "ordered_at",
          "type": "time",
          "is_partition": false,
          "type_params": {
            "time_granularity": "day"
          }
        },
        {
          "name": "amount",
          "type": "categorical",
          "is_partition": false
        }
      ]
    },
    {
      "name": "customers",
      "description": "Customer attributes",
      "node_relation": {
        "alias": "CUSTOMERS",
        "schema_name": "PUBLIC",
        "database": "ANALYTICS",
        "relation_name": "ANALYTICS.PUBLIC.CUSTOMERS"
      },
      "entities": [
        {
          "name": "id",
          "type": "primary"
        }
      ],
      "measures": [],
      "dimensions": [
        {
          "name": "name",
          "type": "categorical",
          "is_partition": false
        },
        {
          "name": "segment",
          "type": "categorical",
          "is_partition": false
        }
      ]
    }
  ],
  "metrics": [
    {
      "name": "revenue",
      "description": "Total order revenue",
      "type": "simple",
      "type_params": {
        "expr": "amount",
        "input_measures": [],
        "metric_aggregation_params": {
          "semantic_model": "orders",
          "agg": "sum"
        },
        "join_to_timespine": false,
        "is_private": false
      }
    },
    {
      "name": "order_count",
      "type": "simple",
      "type_params": {
        "expr": "id",
        "input_measures": [],
        "metric_aggregation_params": {
          "semantic_model": "orders",
          "agg": "count_distinct"
        },
        "join_to_timespine": false,
        "is_private": false
      }
    }
  ],
  "project_configuration": {
    "time_spine_table_configurations": [],
    "dsi_package_version": {
      "major_version": "0",
      "minor_version": "213",
      "patch_version": "0"
    },
    "time_spines": []
  },
  "saved_queries": []
}

Source files stay in memory. Upload all referenced files together.

ResultsApache Ossie

Choose a source platform and convert to preview Ossie YAML.

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

What This Converter Does

Convert compiled dbt semantic definitions into Apache Ossie YAML. This importer reads semantic_manifest.json rather than compiling the source files of a dbt project.

Source Format

A compiled semantic_manifest.json. The prefilled JSON fixture shows the expected modeling surface; raw dbt YAML, SQL models and a general project folder are not interchangeable with this manifest.

Generated Output

An editable Apache Ossie definition and diagnostics about the supported semantic mapping. Use the result with an Ossie-compatible workflow after checking its model features.

Conversion Steps

Compile the semantic manifest through your existing dbt workflow, or inspect the provided test JSON.
Load semantic_manifest.json with dbt selected as the import source.
Convert and review the mapping of entities, dimensions, metrics and semantic models.
Download the Ossie result and validate representative metrics in your chosen runtime.

Review Before Using the Output

Retain the original dbt source project for future compilation and maintenance.

The converter does not run dbt or MetricFlow, execute SQL or establish that a manifest is compatible with every runtime version.

Continue Exploring

FAQ

Frequently asked questions

Can I upload raw dbt YAML?

The dbt importer expects a compiled semantic_manifest.json. Compile through your dbt workflow first; raw project YAML is not accepted as the equivalent semantic input.

Does Ossie export create a complete dbt project?

No. The dbt target exports a MetricFlow semantic_manifest.json. Retain or separately author the project YAML, model SQL, connection configuration and other files needed to run a dbt project.

Does a successful conversion validate my dbt metrics?

Success reports the offline checks available to the converter. Execute and compare the intended metrics in your own environment before relying on the generated definition.