-
Notifications
You must be signed in to change notification settings - Fork 1.3k
feat: Updating protos to separate transformation #4018
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
18 commits
Select commit
Hold shift + click to select a range
8f97cf1
feat: updating protos to separate transformation
franciscojavierarceo bc981c7
fixed stuff...i think
franciscojavierarceo 326ca4a
updated tests and registry diff function
franciscojavierarceo 0ea16a3
updated base registry
franciscojavierarceo 5121d8d
updated react component
franciscojavierarceo cbbfcf8
formatted
franciscojavierarceo 01b82c8
updated stream feature view proto
franciscojavierarceo 8712b2e
making the proto changes backwards compatable
franciscojavierarceo f1e3764
trying to make this backwards compatible
franciscojavierarceo 21c1c35
caught a bug and fixed the linter
franciscojavierarceo ff57b45
actually linted
franciscojavierarceo 6de6fcc
updated ui component
franciscojavierarceo 1212c12
accidentally commented out fixtures
franciscojavierarceo 2883d1b
Updated
franciscojavierarceo ea5e559
incrementing protos
franciscojavierarceo ef0795b
updated tests
franciscojavierarceo 529acac
fixed linting issue and made backwards compatible
franciscojavierarceo 6748fe7
added more tests
franciscojavierarceo 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
incrementing protos
- Loading branch information
commit ea5e559703f499acf68e86e917126894749f11d1
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
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.
I think it's a good time to rethink the naming here. My first suggestion was to rename the field (not message type) to
on_demand_pandas_transformationinstead ofuser_defined_function. But on second thought, since we are also aiming to reuse this inStreamFeatureViews, I think protos should no longer be calledOnDemand... What do you think? I'm thinking of something like this: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 was planning on doing that in a follow up PR to not add too much complexity here.