You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Users commonly want to leverage their existing tables created by dbt models within Feast. Right now, this requires manual creation
When materializing features to the online store, often, it's desirable to have dbt run first to create the upstream table prior to materializing an interval. This requires manual work today.
Describe the solution you'd like
A mechanism to import dbt models (e.g. feast dbt-import) that lets users import from a directory of models, or configure a directory and enable individual models
The above mechanism should generate a data source + feature view with pre-populated tags to track the origin dbt model. Something like
driver_stats_source=BigQuerySource(
name="driver_hourly_stats_source",
table="AUTO-IMPORTED-NAME",
tags={
"feast.dev/dbt-model-path": "INSERT MODEL PATH""feast.dev/dbt-model-serialized": "<serialized dbt model to be shown in UI>"
}
)
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This is a really cool feature request. I was wondering the exact same thing.
@adchia Do you suppose a workaround for this is to:
1- Create a custom DbtSource and logic of it would be to parse the dbt model .yaml file of a particular model
2- And then register that DbtSource
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Activity
stale commentedon Mar 18, 2023
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Zoltrix commentedon Jun 21, 2023
This is a really cool feature request. I was wondering the exact same thing.
@adchia Do you suppose a workaround for this is to:
1- Create a custom
DbtSourceand logic of it would be to parse the dbt model .yaml file of a particular model2- And then register that
DbtSourceIdo-Levi commentedon Sep 4, 2023
Hey, any news on this?
franciscojavierarceo commentedon Aug 6, 2024
We should open this back up @HaoXuAI.
bquocminh commentedon Jan 23, 2025
Hi guys, any updates on this request? Thanks.
franciscojavierarceo commentedon Jan 23, 2025
Hey, this isn't the top priority at the moment but it's something we certainly want to do!
stale commentedon Jun 27, 2025
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
1 remaining item
feat: Add dbt integration for importing models as FeatureViews (feast…
feat: Add dbt integration for importing models as FeatureViews (feast…
feat: Add dbt integration for importing models as FeatureViews (feast…
feat: Add dbt integration for importing models as FeatureViews (feast…
feat: Add dbt integration for importing models as FeatureViews (feast…
chore(release): release 0.59.0
feat: Add dbt integration for importing models as FeatureViews (feast…
chore(release): release 0.59.0
feat: Add dbt integration for importing models as FeatureViews (feast…
chore(release): release 0.59.0
chore(release): release 0.59.0
feat: Add dbt integration for importing models as FeatureViews (feast…
chore(release): release 0.59.0