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
It looks like after #2557, there's now a possibility that we get problems with the plan ordering key for an in-union plan containing FanOut key expressions. This can happen in a scenario like:
If there's an index on field("repeated", FanType.FanOut).nest("foo"), then this index can be selected, with two legs being unioned together. We previously were rejecting that plan because of an "unordered distinct" meaning that we wouldn't have enough information to select the ordering key, but with #2557, we started selecting this index with a plan ordering key that still contained the repeated field (though perhaps it doesn't need to). This results in a runtime exception with the message "Should evaluate to single key only" coming from a call to evaulateSingleton in the union execution logic.
The text was updated successfully, but these errors were encountered:
* Revert "Resolves#2556: FailedInJoinAsUnion support for unordered distinct (#2557)"
This reverts commit e411e1f.
* Revert #2557: FailedInJoinAsUnion support for unordered distinct
This reverts #2557 because of the issue alluded to in #2563.
It looks like after #2557, there's now a possibility that we get problems with the plan ordering key for an in-union plan containing
FanOut
key expressions. This can happen in a scenario like:If there's an index on
field("repeated", FanType.FanOut).nest("foo")
, then this index can be selected, with two legs being unioned together. We previously were rejecting that plan because of an "unordered distinct" meaning that we wouldn't have enough information to select the ordering key, but with #2557, we started selecting this index with a plan ordering key that still contained the repeated field (though perhaps it doesn't need to). This results in a runtime exception with the message "Should evaluate to single key only" coming from a call toevaulateSingleton
in the union execution logic.The text was updated successfully, but these errors were encountered: