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
Assuming that fieldOrders vector should contain invariant about order of rows corresponding to that field, LJoinNode initiates it incorrectly: it assumes that all non-joined columns remain sorted in the same way as they were. However, it's clearly not the case, e.g. if we join these two tables on column A:
| A | B |
| 1 | 1 |
| 2 | 2 |
| 3 | 3 |
| A | C |
| 3 | 1 |
| 1 | 2 |
| 3 | 3 |
After join, column C will become unsorted.
The text was updated successfully, but these errors were encountered:
yeputons
added a commit
to yeputons/au-db-fall-2017
that referenced
this issue
Oct 23, 2017
Assuming that
fieldOrders
vector should contain invariant about order of rows corresponding to that field,LJoinNode
initiates it incorrectly: it assumes that all non-joined columns remain sorted in the same way as they were. However, it's clearly not the case, e.g. if we join these two tables on columnA
:| A | B |
| 1 | 1 |
| 2 | 2 |
| 3 | 3 |
| A | C |
| 3 | 1 |
| 1 | 2 |
| 3 | 3 |
After join, column
C
will become unsorted.The text was updated successfully, but these errors were encountered: