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
Bug #30220791: INCORRECT RESULT WHEN THE ITERATOR EXECUTOR IS USED
Handle first match "split jumps" correctly in the iterator executor,
by way of our usual fallback strategy of rewriting them to weedout.
These are set up whenever the join optimizer inserts otherwise irrelevant
tables in the middle of a first match segment. Not handling them leads
to potentially wrong result in such queries (depending on row order in
the input tables), removing rows that should have been there.
Change-Id: I44e600d40bed62af520ca1f80d153784d3281412
0 commit comments