This message was deleted.
# general
s
This message was deleted.
s
So... I'd like to know the answer to this question as well, but I can tell you what I have found... I had a unit test that failed under
jdk8, sql-compat=true
but passed under
jdk8, sql-compat=false
Trying to replicate that locally, I found this in `.github/workflows/reusable-unit-tests.yml`:
Copy code
if (${{ inputs.sql_compatibility }} == true); then
  echo "DRUID_USE_DEFAULT_VALUE_FOR_NULL=false" >> $GITHUB_ENV
else
  echo "DRUID_USE_DEFAULT_VALUE_FOR_NULL=true" >> $GITHUB_ENV
fi
However, I still saw the test pass in a jdk8 container with this environment variable set: DRUID_USE_DEFAULT_VALUE_FOR_NULL=false 🤷
Also, just found this, which explains the origin of the SQL compatibility flag: https://druid.apache.org/docs/latest/configuration/index.html#sql-compatible-null-handling
a
yeah, you can set the default value for null to true or false. For example, the following command runs tests in the sql module with default value for null as false:
mvn test -pl sql -Ddruid.generic.useDefaultValueForNull=false