maytasm commented on pull request #9773: URL: https://github.com/apache/druid/pull/9773#issuecomment-622535442
@gianm I found something that works for all the new test cases but I am not exactly sure how it works. If we ONLY boost the cost for rels that must always query on DruidQueryRel and NOT DruidJoinQueryRel. Then we also exclude/remove the where filter multiplier (MULTIPLIER_FILTER) for DruidJoinQueryRel. Hence, if we have DruidJoinQueryRel, then the the where filter will not affect the cost of DruidJoinQueryRel. I found that the planner will always (at least for the test cases I added) put the where filter on the topmost/outermost DruidJoinQueryRel. I am not sure how the planner decides this. the cummulative cost will be exactly the same between putting the where filter on the topmost/outermost DruidJoinQueryRel vs. on the inner DruidJoinQueryRel (since where filter does not affect the cost), how does the planner choose which to put the where filter on? ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
