You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ossie.apache.org by "fanruan-tuco (via GitHub)" <gi...@apache.org> on 2026/08/12 12:55:37 UTC

Re: [I] dbt converter loses derived metric time-context semantics in MetricFlow to Ossie conversion [ossie]

fanruan-tuco commented on issue #317:
URL: https://github.com/apache/ossie/issues/317#issuecomment-5267091154

   One possible follow-up is to preserve these semantics in custom_extensions, instead of only warning and dropping them.
   
   [Datus](https://github.com/Datus-ai) already does something similar in its OSI adapter. It stores fields like window, grain_to_date, and offset_window under vendor_name: DATUS, then converts them to MetricFlow at execution time. A representative implementation is https://github.com/Datus-ai/datus-semantic-adapter/pull/32
   
   Maybe the dbt converter could store the original MetricFlow definition under a DBT or METRICFLOW extension. Consumers that understand it could restore the full semantics, while other Ossie consumers could safely ignore it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@ossie.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org