-
Notifications
You must be signed in to change notification settings - Fork 419
fix: prom ql logical plan use column index not name #7109
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
Conversation
It looks like there’s a lot of duplicated code and structs. Can we refactor them? |
d4c5b50
to
1129482
Compare
refactor some method, but the "unfix" struct seems necessary, as refactor to either enum or use macro does seems even more messy, this is due to datafusion provided extension deserializer didn't provide input logical plan hence cause this issue |
1129482
to
9612706
Compare
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.
LGTM
Signed-off-by: discord9 <[email protected]>
Signed-off-by: discord9 <[email protected]>
Signed-off-by: discord9 <[email protected]>
Signed-off-by: discord9 <[email protected]>
Signed-off-by: discord9 <[email protected]>
Signed-off-by: discord9 <[email protected]>
Signed-off-by: discord9 <[email protected]>
3fa2468
to
6a1271e
Compare
I hereby agree to the terms of the GreptimeDB CLA.
Refer to a related PR or issue link (optional)
#7102
GreptimeTeam/greptime-proto#285 need merge first
What's changed and what's your intention?
to avoid substrait decode error, use index not name, which will prevent substrait from confuse column names since it will decoded to a slightly different plan(but project node's input schema should still in the same order)
This pull request contains AI slop
PR Checklist
Please convert it to a draft if some of the following conditions are not met.