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 c362d0f
Browse filesBrowse the repository at this point in the historyBrowse files
fix: check query stages in the UDF benchmark and reframe when to write a vectorized UDF
- The benchmark's native-plan check stripped only the top-level adaptive node,
so it reported a ShuffleQueryStage as a Spark operator. Check the plan
inside each query stage, as CometTestBase.checkCometOperatorsInFinalPlan
does.
- For simple functions, most of the gap to the codegen dispatcher is its
overhead around the call rather than the call itself. Reframe the user
guide around what a function of one row cannot express, and say so in
the benchmark's scaladoc.
0 commit comments