forked from feast-dev/feast
-
Notifications
You must be signed in to change notification settings - Fork 3
fix: ts range filter bug #220
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
Open
omirandadev
wants to merge
2
commits into
master
Choose a base branch
from
ts-range-filter-bug
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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
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
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.
This would convert normal Int64 values to timestamps as well. Why not just do this data conversion in typeconversion.go?
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 we would need to know the expected type of the sortkey to know what to convert it to. We pass that into the request. For example,
"sort_key_filters": [ { "sort_key_name": "feature_5", "range": { "range_end": { "double_val": "60" }, "end_inclusive": true } } ]However, we don't pass this to the onlinereadrange method. My proposed solution would be to add a ValueType field to the SortKeyFilter struct, so that we can know the expected type of it upon a request. Then I'd add a method in the type conversion package that translates the request type to the data type cassandra expects (based on the Valuetype of the SortKeyFilter).
I want to get your input on this before implementation in case there is a more simple solution I'm not considering.
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.
We already validate that the sort key filter values are the correct type. Since both the proto and go are strictly typed there shouldn't be any need to explicitly pass the type information.
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.
But how can the OnlineReadRange method know what the correct type is? I think it needs to know that prior to constructing the cql statement, otherwise it won't be able to know if an int64 should be converted to an int64 or to unix timestamp.