clintropolis commented on issue #17891: URL: https://github.com/apache/druid/issues/17891#issuecomment-2787719181
>For the different query plan, it should be related to the #14542 because I did see equality filter is used for the id column in this case. (This is also another weired problem that the query plan now shows the equals filter is used instead of previous boundfilter) I think this should be better behaved in even more recent versions of Druid since https://github.com/apache/druid/pull/16039 which allowed us to move away from the OR of bound/range filters to handle numeric types (check out some of the test changes in that PR to see what i mean). I think 27 might have ended up in a bit of a sub-optimal state out of the box being released in the middle of some of those transitions from filters matching everything as strings to where we are now by default which is the native layer handles matching directly in the match value type. You might be able to set context parameter `sqlUseBoundAndSelectors` to prevent the planner from using the new type aware filters in 27, but shouldn't be needed in 30 or newer since the typed in filter can handle either case. >For backward compatibility druid.sql.planner.metadataColumnTypeMergePolicy should be set to latestInterval. But this is not mentioned in the Upgrade notes and incompatible changes section of the release note: https://github.com/apache/druid/releases/tag/druid-27.0.0 I think this is an oversight that the behavior change wasn't called out there, though the new default is generally better behavior in most use cases I think since it allows you to query all of your data correctly -- 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]
