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
{{ message }}
Repository navigation
Commit 0e49f1c
Browse filesBrowse the repository at this point in the historyBrowse files
fix: scope a TakeOrderedAndProject's sort keys and projection apart, as Spark evaluates them
3090d85 gave CometTakeOrderedAndProjectExec's sort keys and projection one shared set. Spark's
ordering evaluates each sort key on its own, without subexpression elimination, and its projection
runs separately over the rows the sort keeps. So a cast in two sort keys, or in a sort key and the
projection, raised in Comet where Spark returns the rows. The top-K plans now use an empty set, and
the projection its projection list.
0 commit comments