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.
Requesting historical features from Snowflake uses multiple intermediate results to do the point-in-time correct join. Recently, a new Snowflake feature was released which does exactly what we would expect from the join: ASOF JOIN (https://www.snowflake.com/en/blog/time-series-analytics-asof-join-generally-available/). The reported improvements in efficiency are very substantial.
Is your feature request related to a problem? Please describe.
Requesting historical features from Snowflake uses multiple intermediate results to do the point-in-time correct join. Recently, a new Snowflake feature was released which does exactly what we would expect from the join: ASOF JOIN (https://www.snowflake.com/en/blog/time-series-analytics-asof-join-generally-available/). The reported improvements in efficiency are very substantial.
Describe the solution you'd like
Could we use the ASOF JOIN in https://github.com/feast-dev/feast/blame/d1d80c0d208e25b92047fe5f162c67c00c69bb43/sdk/python/feast/infra/offline_stores/snowflake.py#L717 to improve efficiency of the query? From a superficial view it seems to be possible, only the ttl feature might be difficult with ASOF JOINs.
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: