clintropolis commented on issue #10102: URL: https://github.com/apache/druid/issues/10102#issuecomment-1521095129
>I believe this was addressed in #11184. @clintropolis could you confirm please? Yeah, I believe so. Semi related, there are still a handful of filters which have non-sql compliant behavior, including the `NotFilter`, e.g. `x != 'a'` will take the `x = 'a'` bitmap and then invert it, which means that it matches null values, which is incorrect. This should be fixed by probably pushing the inversion into the child index computation so that child filters can do whatever is appropriate to invert the filter, such as filtering out nulls for the selector, etc. Talking about filters, the bound filter is also not sql compliant, since it treats a missing lower bound as a "should match null values", which is hard to reason about. In the super near future I would like to add new equality, null, and range filters to replace selector and bound filters to try to be more sql compliant, and have a switch in the planner to use these better behaved filters without impacting the existing behavior. -- 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]
