-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Fix SQL planner bug when resolving columns with same name as a relation #3003
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3003 +/- ##
==========================================
+ Coverage 85.81% 85.84% +0.02%
==========================================
Files 282 283 +1
Lines 51531 51626 +95
==========================================
+ Hits 44219 44316 +97
+ Misses 7312 7310 -2
Help us with your feedback. Take ten seconds to tell us how you rate us. |
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, fixed the issues I was having.
i added a simple test case here andygrove#64 |
add a simple test case
Thank you @waitingkuo! |
Benchmark runs are scheduled for baseline = 55a1286 and contender = e23925c. e23925c is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
…on (apache#3003) * repro unit test * improve test * fix * make logic more robust * add a simple test case Co-authored-by: Wei-Ting Kuo <[email protected]>
Which issue does this PR close?
Closes #3002
Rationale for this change
This bug was preventing valid queries from running.
Master
This PR
What changes are included in this PR?
Improve logic for determining if a compound identifier is referencing a column or an indexed field
Are there any user-facing changes?
No