Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FR] Consider utilizing time travel feature in Delta when users materialize features to avoid multiple cutoff time. #891

Open
2 of 4 tasks
xiaoyongzhu opened this issue Nov 30, 2022 · 0 comments
Labels
feature New feature or request

Comments

@xiaoyongzhu
Copy link
Member

Willingness to contribute

No. I cannot contribute a bug fix at this time.

Feature Request Proposal

Currently a lot users are using delta format. Maybe an optimization to save some space when materializing features is to use the time travel feature in delta to avoid multiple cutoff time.

Motivation

What is the use case for this feature?

Currently a lot users are using delta format. Maybe an optimization to save some space when materializing features is to use the time travel feature in delta to avoid multiple cutoff time.

Details

No response

What component(s) does this feature request affect?

  • Python Client: This is the client users use to interact with most of our API. Mostly written in Python.
  • Computation Engine: The computation engine that execute the actual feature join and generation work. Mostly in Scala and Spark.
  • Feature Registry API: The frontend API layer supports SQL, Purview(Atlas) as storage. The API layer is in Python(FAST API)
  • Feature Registry Web UI: The Web UI for feature registry. Written in React
@xiaoyongzhu xiaoyongzhu added the feature New feature or request label Nov 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant