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
The SQL data loader in the web console uses a VALUES query to make a sample dataset for easy previewing. I know the description might make this sounds like a crazy corner case but in actuality this is a very common thing to stumble upon as in a sample of data (20 rows or so) with many column you are very likely to get a column that is all NULL.
Affected Version
All recent Druid versions that I tested including the latest build on master as of this writing and 30.0.0 RC.
Description
Here is a very simple (self contained) query that fails:
2024-05-15T18:43:43,102 WARN [sql[8f567aa7-38c4-4d27-89dc-60189e66f5c9]] org.apache.druid.sql.http.SqlResource - Exception while processing sqlQueryId[8f567aa7-38c4-4d27-89dc-60189e66f5c9] (org.apache.druid.error.DruidException: Unhandled Query Planning Failure, see broker logs for details)
Which is not helpful
Curiously if one of the NULLs is changed to, say a '' it works:
Also if we remove the PARSE_JSON it also works:
From playing around with this it appears that there is some additional processing step that applying a function like PARSE_JSON adds that can not handle a NULL typed column that is being cast.
The text was updated successfully, but these errors were encountered:
The SQL data loader in the web console uses a VALUES query to make a sample dataset for easy previewing. I know the description might make this sounds like a crazy corner case but in actuality this is a very common thing to stumble upon as in a sample of data (20 rows or so) with many column you are very likely to get a column that is all NULL.
Affected Version
All recent Druid versions that I tested including the latest build on master as of this writing and 30.0.0 RC.
Description
Here is a very simple (self contained) query that fails:
All that is logged in the broker is:
Which is not helpful
Curiously if one of the NULLs is changed to, say a
''
it works:Also if we remove the
PARSE_JSON
it also works:From playing around with this it appears that there is some additional processing step that applying a function like
PARSE_JSON
adds that can not handle a NULL typed column that is being cast.The text was updated successfully, but these errors were encountered: