ankitsultana commented on issue #10381: URL: https://github.com/apache/pinot/issues/10381#issuecomment-1745744477
Thanks @walterddr for the doc. From a user point of view, I feel we should keep columnLevelNullability as a new feature altogether. So if column level nullability is disabled, things can stay as they are now. If column level nullability is enabled, then we ignore table level nullability altogether, and both v1 and v2 engine should honor it in the same consistent way, which is: 1. During ingestion null vectors would be created based on column level nullability (this is independent of query engine anyways) 2. On query side both v1 and v2 engine would behave the same way when the null handling query option is enabled/disabled. 3. Null filters like IS NULL/IS NOT NULL should work consistently across the two engines. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
