-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Add Tuples and InOp implementation to EvalEngine #9281
Merged
Merged
Conversation
This file contains 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
Signed-off-by: Manan Gupta <manan@planetscale.com>
Signed-off-by: Manan Gupta <manan@planetscale.com>
Signed-off-by: Manan Gupta <manan@planetscale.com>
Signed-off-by: Manan Gupta <manan@planetscale.com>
Signed-off-by: Manan Gupta <manan@planetscale.com>
Signed-off-by: Manan Gupta <manan@planetscale.com>
GuptaManan100
added
Type: Enhancement
Logical improvement (somewhere between a bug and feature)
Component: Query Serving
release notes
labels
Nov 23, 2021
GuptaManan100
requested review from
vmg,
systay,
harshit-gangal and
frouioui
November 23, 2021 10:20
systay
reviewed
Nov 23, 2021
Signed-off-by: Manan Gupta <manan@planetscale.com>
frouioui
reviewed
Nov 23, 2021
frouioui
reviewed
Nov 23, 2021
Signed-off-by: Manan Gupta <manan@planetscale.com>
frouioui
approved these changes
Nov 23, 2021
vmg
approved these changes
Nov 23, 2021
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.
Looking good! I'm confused about collations propagation for comparisons where the right side is a tuple, but that's something I gotta figure out myself in my branch. 👌
harshit-gangal
approved these changes
Nov 23, 2021
Signed-off-by: Manan Gupta <manan@planetscale.com>
harshit-gangal
approved these changes
Nov 24, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Component: Query Serving
Type: Enhancement
Logical improvement (somewhere between a bug and feature)
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.
Description
As a long term goal, we want to replace the usage of
PlanValue
everywhere. To accomplish this change, we need to add an implementation toevalengine.Expr
which can store tuples and evaluate them. This PR accomplishes that change. It introduces a new implementation ofevalengine.Expr
which stores multiple values and also changes theEvalResult
struct to be able to store multiple results for intermediate steps.Related Issue(s)
Checklist
Deployment Notes