[GitHub] [pinot] Jackie-Jiang commented on issue #10907: Enabling Null Support after table creation results in incorrect results for `IS [NOT] NULL` expressions

["Jackie-Jiang (via GitHub)" <gi...@apache.org>]

Jackie-Jiang commented on issue #10907:
URL: https://github.com/apache/pinot/issues/10907#issuecomment-1595571975

   We don't want to enforce user to re-create the table when they want to enable null handling because a lot of users are okay to have old segments not handling null and just the new segments handling null.
   Currently we cannot auto generate null value vector after segment is created because the null value is already replaced by the default value, and the null information is already lost. What we can do is to allow user to config some columns, and pinot just treat the default value as null for the configured columns. Then we can generate the null value vector for these columns.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org
For additional commands, e-mail: commits-help@pinot.apache.org