Free Developer Tool · Apache Ossie / Dosi

Omni to Apache Ossie Converter

Import Omni views, relationships and topics into Apache Ossie. Try the four-file sales example, keep relative paths and review the converted model.

No signup · Sample models included · Offline conversion checks

Conversion Workbench

Source Files4Example

Omni · Sales (4 files)

views/orders.view.yaml

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

Import an Omni model into Apache Ossie as a related set of definitions. The four-file sales fixture includes views, relationships and a topic, so you can inspect the boundaries between them before converting.

Source Format

Supported Omni project files with relative paths intact. Include the views and relationships needed by the topic you intend to convert.

Generated Output

An Apache Ossie model and diagnostics that you can review before adopting the definition in another semantic workflow.

Conversion Steps

Inspect the four-file Omni sales example or upload the relevant project bundle.
Choose a view or topic if those source-specific fields are exposed by the catalog.
Convert and inspect the generated dataset relationships, field exposure and metric definitions.
Download the Ossie files and compare the intended analysis queries in your destination environment.

Review Before Using the Output

The importer does not authenticate to an Omni account or fetch a live project.

Check topic scope and SQL expressions; moving definitions does not automatically reproduce the original analysis environment.

Continue Exploring

FAQ

Frequently asked questions

Which Omni files should I include?

Supply the related supported views, relationships and topics required by the model. The included example has four files; folder uploads preserve relative paths, subject to the public input limits.

Can I choose a particular Omni view or topic?

Source-specific configuration fields come from the deployed catalog. When view or topic options are available, use them to select the definition you intend to convert.

Why does an Omni export contain multiple files?

The target can separate views, relationships and topics into multiple definitions. A ZIP download preserves those relative paths and includes your current edits.