Sorry, something went wrong.
Sorry, something went wrong.
|
Let's re-run tests? Random issue, but no changes to dependency management :/ |
Sorry, something went wrong.
Sorry, something went wrong.
|
seems like aws creds have expired @franciscojavierarceo |
Sorry, something went wrong.
|
@ntkathole @jeremyary can you investigate? |
Sorry, something went wrong.
There was a problem hiding this comment.
I think it might be better to add the config to the fs.materialize API? So that you can customize the materialize process that materialize the FeatureView if you need pushdown filter, and some other process you don't need.
Sorry, something went wrong.
|
I think it might be better to add the config to the fs.materialize API? So that you can customize the materialize process that materialize the FeatureView if you need pushdown filter, and some other process you don't need. Why not indeed. I'll check it out and tag you back. |
Sorry, something went wrong.
What this PR does / why we need it:
Adds an option to materialize only the latest values (essentially pushes down deduplication to offline store), to reduce client memory consumption and reduce e2e duration. Especially noticeable for large-scale materialization - think hundreds of thousands of rows with ~150 feature views, with latency-critical materializations - as we observed in our ML project at cast.ai.
Which issue(s) this PR fixes:
#5707 (comment)
Misc
This will be configured via feature store (repo) config file: