Uh oh!
There was an error while loading. Please reload this page.
PHOENIX-6408 LIMIT on local index query with uncovered columns in the WHERE returns wrong result. - #1161
Conversation
stoty
commented
Mar 10, 2021
💔 -1 overall
This message was automatically generated. |
| return next; | ||
| } | ||
| } | ||
| if (extraLimit >= 0 && --extraLimit == 0) { |
There was a problem hiding this comment.
Should not this check be at the end of this method just before it returns?
There was a problem hiding this comment.
It does not matter as long as this is after the local index extra where filtering (and there are no other exit points after this). I wanted to isolate that to local indexing only, to not affect the other code paths.
There was a problem hiding this comment.
Oh. You are right. We're not building the right tuple in this case if we have a tuple projector.
In fact this caused PointInTimeScanQueryIT to fail.
lhofhansl
commented
Mar 10, 2021
I'm looking into the PointInTimeLimitedIT failures. They look pertinent. |
lhofhansl
commented
Mar 10, 2021
Updated as per @kadirozde's suggestion, which also fixes the test failures. |
… WHERE returns wrong result.
lhofhansl
commented
Mar 10, 2021
Thanks! I'll await the next test run and then merge. |
stoty
commented
Mar 10, 2021
💔 -1 overall
This message was automatically generated. |
See description in the jira.
The fix is relatively straight forward, if not particularly pretty:
I added extra tests for this.