Repository navigation
feat: Compute Engine Initial Implementation #5223
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
21 commits
Select commit
Hold shift + click to select a range
1183a9a
add compute engine
haoxu0 2825ee4
fix linting
haoxu0 4210f68
fix linting
haoxu0 a398075
fix linting
haoxu0 68c48dc
fix linting
haoxu0 1c9ae31
add doc
haoxu0 25af94e
add test
haoxu0 ed0cdf4
add integration test
haoxu0 6b57e94
update API
haoxu0 227f8f4
update API
haoxu0 e9362de
update API
haoxu0 68cf242
update API
haoxu0 3a5cf92
update API
haoxu0 c1ba3d6
fix linting
haoxu0 95f757d
update doc
haoxu0 e5445a2
update doc
haoxu0 263024b
Merge branch 'master' into compute-engine
haoxu0 2433064
update test
haoxu0 87e51c7
update doc
haoxu0 c698b64
Merge branch 'master' into compute-engine
haoxu0 0877c03
Merge branch 'master' into compute-engine
haoxu0 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
update API
Signed-off-by: HaoXuAI <sduxuhao@gmail.com>
- Loading branch information
commit e9362de5623ca333e6db8cbc61003853be50dcc4
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I'm to be honest, I don't love putting the transformation in the FeatureView.
I think it'd be more intuitive to put Aggregation under Transformation and make the FeatureViews purely represent schemas available for online or offline.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree. This is only to be consistent with the current
StreamFeatureViewandAggregationclass. It makes sense to haveAggregationone type ofTransformation(as well as for Filter), but that will need some work to refactor.For Tecton, they put
Aggregateinfeature(what Feast calledschema) asIn some way that also make sense but for Feast it will needs much more work to refactor the
schemaAPI.For Chrono they put it into a GroupBy API, which is similar to our FeatureView:
I can look into how to merge
AggregationwithTransformationtogether in the next PR, and added it to a TODO for now.