kgyrtkirk commented on code in PR #16248:
URL: https://github.com/apache/druid/pull/16248#discussion_r1557559476
##########
sql/src/main/java/org/apache/druid/sql/calcite/planner/CalciteRulesManager.java:
##########
@@ -82,6 +83,10 @@ public class CalciteRulesManager
private static final int HEP_DEFAULT_MATCH_LIMIT = Integer.parseInt(
System.getProperty(HEP_DEFAULT_MATCH_LIMIT_CONFIG_STRING, "1200")
);
+ private static final String BLOAT_PROPERTY = "druid.sql.planner.bloat";
+ private static final int BLOAT = Integer.parseInt(
+ System.getProperty(BLOAT_PROPERTY, "100")
Review Comment:
I think the druid planner we'll not like at all if multiple projects are kep
on top of eachother...
the
[default](https://github.com/apache/calcite/blob/4e6a320bf476c4b3c313d86f8ff3c6edf4c2a578/core/src/main/java/org/apache/calcite/rel/rules/ProjectMergeRule.java#L49)
seems to be the same (`100`) - what do you think about raising it to a bigger
value; like a few millions - so that its less likely to hit this issue out of
the box ?
--
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]
