You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note the 2 additional rows at the bottom. The expected output should only be the 2 first rows.
Interestingly, changing the limit 10 to limit 4 doesn't change the query's output - but changing to limit 3 and limit 2 shaves off 1 resp. 2 of the wrong rows.
Here's are the optimizer diffs (not sure if they help):
This was likely due to the bug that caused left-hand side data to be read from BOTH indexes. If the two indexes had no fields in common, no errors are produced and instead null values appear on the left (as many extra null rows as there were rows on the right). This should be fixed by #117843
Reproducer:
Note the 2 additional rows at the bottom. The expected output should only be the 2 first rows.
Interestingly, changing the
limit 10
tolimit 4
doesn't change the query's output - but changing tolimit 3
andlimit 2
shaves off 1 resp. 2 of the wrong rows.Here's are the optimizer diffs (not sure if they help):
The text was updated successfully, but these errors were encountered: