Null query result when using SQL CASE expression

[MohTaheri]

Affected Version

Druid 32.0.0

Description

After upgrading to version 32, where the druid.generic.useDefaultValueForNull=true feature is deprecated, we’re getting incorrect results when executing SQL queries using CASE.
The query is supposed to return a result based on a given condition, but when a type value doesn’t match any condition, it returns NULL instead of the expected ELSE value or COALESCE result.

SELECT
        t.id,
        SUM(CASE WHEN type = 'X'
            THEN NVL(amount, 0)
            ELSE 0
        END) AS total_amount
    FROM
        example t
    GROUP BY t.id

We followed all the steps in the migration guide, and no null values were inserted during ingestion. All raw data contains non-null values.

[MohTaheri]

@clintropolis Sorry, do you have any idea how the new release will affect that?