Gian Merlino f643abdad9 SQL planning: Consider subqueries in fewer scenarios. (#14123) ... * SQL planning: Consider subqueries in fewer scenarios. Further adjusts logic in DruidRules that was previously adjusted in #13902. The reason for the original change was that the comment "Subquery must be a groupBy, so stage must be >= AGGREGATE" was no longer accurate. Subqueries do not need to be groupBy anymore; they can really be any type of query. If I recall correctly, the change was needed for certain window queries to be able to plan on top of Scan queries. However, this impacts performance negatively, because it causes many additional outer-query scenarios to be considered, which is expensive. So, this patch updates the matching logic to consider fewer scenarios. The skipped scenarios are ones where we expect that, for one reason or another, it isn't necessary to consider a subquery. * Remove unnecessary escaping. * Fix test.		2023-04-21 08:32:13 -07:00
..
src	SQL planning: Consider subqueries in fewer scenarios. (#14123)	2023-04-21 08:32:13 -07:00
pom.xml	Bump up the version in pom to 27.0.0 in preparation of release (#14051)	2023-04-10 14:56:59 +05:30