Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix struct flattening to add a validity column only when the input column has null element #8374

Merged
merged 4 commits into from
May 27, 2021
Merged
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 9 additions & 4 deletions cpp/src/structs/utilities.cpp
Original file line number Diff line number Diff line change
Expand Up @@ -93,11 +93,16 @@ struct flattened_table {
order col_order,
null_order col_null_order)
{
if (nullability == column_nullability::FORCE || col.nullable()) {
// nullable columns could be required for comparisions such as joins
// Even if it is not required to extract the bitmask to a separate column,
// we should always do that if the structs column has any null element.
// In addition, we should check for null by calling to `has_nulls()`, not `nullable()`.
// This is because when comparing structs columns, if one column has bitmask while the other
// does not (and both columns do not have any null element) then flattening them using
// `nullable()` will result in tables with different number of columns.
ttnghia marked this conversation as resolved.
Show resolved Hide resolved
if (nullability == column_nullability::FORCE || col.has_nulls()) {
validity_as_column.push_back(cudf::is_valid(col));
if (col.nullable()) {
// copy bitmask only works if the column is nullable
if (col.has_nulls()) {
// copy bitmask is needed only if the column has null
validity_as_column.back()->set_null_mask(copy_bitmask(col));
}
flat_columns.push_back(validity_as_column.back()->view());
Expand Down