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

Toggle data stores using flags in feature specifications #38

Closed
woop opened this issue Jan 4, 2019 · 4 comments
Closed

Toggle data stores using flags in feature specifications #38

woop opened this issue Jan 4, 2019 · 4 comments
Assignees
@tims
Labels
good first issue Good for newcomers

Comments

@woop
Copy link
Member

woop commented Jan 4, 2019 •
edited
Loading

I'm considering whether it is cleaner to have options within feature specifications like useFeatureWarehouse: false to enable or disable a specific type of storage option (serving, warehouse).

Thoughts?

Related to: #5
@woop woop assigned tims Jan 4, 2019
@woop woop mentioned this issue Jan 4, 2019
Merged
@tims
Copy link
Contributor

tims commented Jan 6, 2019

This would help override and disable default stores. So I think this is nice.

@woop woop added the good first issue Good for newcomers label Jan 7, 2019
@woop
Copy link
Member Author

woop commented Jan 7, 2019

This would help override and disable default stores. So I think this is nice.

Great. This is a classic good first issue, haha.

PR #39

How is this PR related?

@tims
Copy link
Contributor

tims commented Jan 11, 2019

Ah oops.. it's not. I removed my comment.. but it's still linked. ah well.

@thirteen37 thirteen37 mentioned this issue Apr 10, 2019
Merged
@tims
Copy link
Contributor

tims commented Apr 12, 2019

closing, wont fix, as we believe it would make more sense to configure stores with which features belong to them (in a future where we can deploy multiple serving stores with overlapping feature sets), than to configure the features.

@tims tims closed this as completed Apr 12, 2019
Yanson pushed a commit to Yanson/feast that referenced this issue Jul 29, 2020
@algattik
Spark checkpoint (feast-dev#38)
3c00ead 
Closes KE-695, KE-866

Use Spark structured streaming checkpoint to track Kafka offsets and continue stream progressing after a restart.
dmartinol added a commit to dmartinol/feast that referenced this issue Jul 10, 2024
@dmartinol
Merge pull request feast-dev#38 from dmartinol/feast-rbac-auth
c3e279b 
fixed broken IT
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tims tims

Labels
good first issue Good for newcomers
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tims @woop