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.

Sign up for GitHub

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

Jump to bottom

created_timestamp and last_updated_timestamp are never set #2267

Closed
judahrand opened this issue Feb 2, 2022 · 1 comment · Fixed by #2266
Closed

created_timestamp and last_updated_timestamp are never set #2267

judahrand opened this issue Feb 2, 2022 · 1 comment · Fixed by #2266
Assignees
@achals
Labels
kind/bug priority/p2

Comments

@judahrand
Copy link
Member

judahrand commented Feb 2, 2022 •
edited
Loading

Expected Behavior

created_timestamp and last_updated_timestamp should be set when things are updated in the Registry.

Current Behavior

For:

  • FeatureViews
  • SavedDatasets
  • Entites
  • FeatureServices

this field is not currently set.

For OnDemandFeatureViews the last_updated_timestamp field does not even exist and the created_timestamp is not set.

Steps to reproduce

Specifications

  • Version:
  • Platform:
  • Subsystem:

Possible Solution

Set the fields 😉
@judahrand judahrand mentioned this issue Feb 2, 2022
Merged
@woop
Copy link
Member

woop commented Feb 2, 2022

Nice catch @judahrand.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@achals achals

Labels
kind/bug priority/p2
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Set created_timestamp and last_updated_timestamp fields judahrand/feast
3 participants
@achals @woop @judahrand