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
{
"columnName": "col1",
"transformFunction": "CASE WHEN col2 IS NOT NULL THEN col2 ELSE null END"
},
Although the function returns null, typical null value handling does not apply. Ideally, if an ExpressionTransformer returns null, the value can still be filtered via IS NULL/IS NOT NULL. To maintain backwards compatibility we could add a new config per transformFunction, enableNullHandling:
{
"columnName": "col1",
"transformFunction": "CASE WHEN col2 IS NOT NULL THEN col2 ELSE null END",
"enableNullHandling": true
},
The text was updated successfully, but these errors were encountered:
What is the current behavior? What is the value produced when the expression returns null?
We should just use the setting in table config instead of introducing a new flag.
I'd also prefer avoiding a new config, I wasn't sure if this should be considered a bug since changing the behavior would be backwards incompatible. Though looking at this briefly, it seems NullValueTransformer is intended to handle null output from ExpressionTransformer
Take the transformation:
Although the function returns null, typical null value handling does not apply. Ideally, if an
ExpressionTransformer
returns null, the value can still be filtered viaIS NULL/IS NOT NULL
. To maintain backwards compatibility we could add a new config per transformFunction,enableNullHandling
:The text was updated successfully, but these errors were encountered: