NVIDIA / NVIDIA/cudf

Identify appropriate return type for empty aggregation results with UDF aggregations

Open
#8,394 1 comment 0 reactions 0 assignees View on GitHub
improvement libcudf Python
Dominant language
C++
Stars
9.8k
Forks
1.1k
Avg merge
3d 6m
Merged PRs (30d)
278

Description

In #8274 the output of aggregations returning empty data sets was changed so that the output type of nested columns would match the expected type even when it is empty. However, this led to a separate edge case, which is determining what data type to return when performing a UDF aggregation that returns an empty column. A numba-compiled Python UDF provides enough information to infer the output type, but we need to assess the extent to which UDFs returning nested are/should be supported in cudf Python to determine whether/how to pass this information down to `libcudf` to ensure that the appropriate types are returned. As of #8274 such aggregations simply mimic the input data type for the returned column.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.