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 ae5cbe3
Browse filesBrowse the repository at this point in the historyBrowse files
test: cover booleans in native explode output past the first batch
The native explode slices each output batch out of the exploded child
instead of gathering it, so an exploded boolean, or a boolean field of an
exploded struct, leaves native at a non-zero bit offset. Arrow Java ignores
that offset on import, so on 1.1.0-rc1 these booleans came back wrong from
the second output batch on. apache#6339 already fixed this on main by zeroing
offsets at every level before export, but none of its tests go through
explode.
Add tests to CometGenerateExecSuite for explode, explode_outer, posexplode
and posexplode_outer of structs with boolean fields, for one row longer
than the batch size, and for a native named_struct and a boolean Scala UDF
over an exploded boolean. All of them fail when native zeroes only
top-level offsets and leaves the UDF bridge inputs alone, as rc1 does.
Closesapache#6464.
0 commit comments