免费开发工具 · Apache Ossie / Dosi

Apache Ossie 转 Omni 语义模型转换器

将 Apache Ossie YAML 导出为 Omni 视图、关联和主题。试用 Omni Sales 样例，检查多文件结果并下载可编辑 ZIP。

无需注册 · 内置测试样例 · 离线转换检查

转换工作台

源文件1样例

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

源文件仅保留在内存中，请一并上传所有被引用的文件。查看原始样例

结果

选择目标平台并转换，在此预览临时文件。

点击转换时，当前源文件将发送至 Datus 服务器；不会连接数据仓库或执行 SQL。

此转换器的用途

由 Apache Ossie 模型生成 Omni 视图、关联和主题。此页加载 Omni Sales Ossie 样例，并在导出方向预选 Omni。

来源格式

Apache Ossie YAML。转换前检查来源数据集与关联，替换现有 Omni 模型时尤其需要逐项比较。

生成产物

一组 Omni 模型文件。可通过结果文件树逐个检查定义，再下载保留目录结构的 ZIP。

转换步骤

检查 Omni Sales 来源模型，或上传其他兼容的 Ossie 定义。
保留 Omni 目标，检查模型和 SQL 表达式相关配置。
转换后查看各个视图、关联和主题，并阅读诊断。
下载当前文件，通过自己的 Omni 流程应用，并测试代表性查询。

使用产物前需要检查的事项

导出文件不会发布项目或配置 Omni 连接。

请针对自己的数仓验证主题字段集合与所选原生 SQL 表达式。

继续探索

常见问题

Ossie 转 Omni 的结果包含什么？

目标可以生成独立的视图、关联和主题文件。内置 Omni Sales 来源是 Apache Ossie 模型，请查看生成文件树与诊断，了解当前模型的输出结构。

导出 Omni 模型会发布到我的账号吗？

不会。工具生成可下载的模型文件，不登录 Omni，也不发布项目。请通过自己的目标流程应用文件并验证结果。

如何检查 Omni 导出中的 SQL？

检查来源已有的表达式，并在提供方言选项时选择所需表达式。转换不进行数仓 SQL 翻译，请在自己的数仓验证生成定义与代表性查询。