Hi All, I am using Pinot 1.1 and I want to store ...
# troubleshooting
r
Hi All, I am using Pinot 1.1 and I want to store null for my DOUBLE column.. For that I have used below confs:
nullHandlingEnabled=true at table config level
enableColumnBasedNullHandling": true at schema level
Copy code
{
      "name": "notNullColumn",
      "dataType": "DOUBLE",
      "notNull": False
 }
Still when I am querying, I am getting "0" instead of null. How can I fix this issue where I want to see null (original value) instead of 0 in query response without adding "SET enableNullHandling=true" in my query
x
this
notNull": False
should be
true
?
r
I want to store null values, so notNull should be false right ?
in my case 0 and null have different meaning, so I want to get null in my response instead of 0
x
ah, yes then
during query ,did you add
SET enableNullHandling=true
r
This is my doubt, Even when I am querying with condition : select column1,* from abc where column1 is null. This returns null values are 0 for column1.
users doesn't want to include "SET enableNullHandling=true" in their query and want null in result
is this possible in Pinot 1.1 ?
x
so by adding
SET enableNullHandling=true
you will be able to see the correct results?
I think you need to apply this to each query
or if users are querying with client
you can ask to make a query template
or query option
r
I see... So on adding SET enableNullHandling=true, I am able to see column1 nul data as -- instead of 0
correct me if I am wrong For DOUBLE metric field After Enabling the null handling at ingestion level, user needs to add "SET enableNullHandling=true" every time in their query to get response as null instead of 0 no other way to get null (original value) in response correct?
x
correct
this is how nullHandling is implemented
r
Thanks @Xiang Fu, i ll go through it.