Looks like DRILL-5547: Linking config options with system option manager (
https://github.com/apache/drill/commit/a51c98b8bf210bbe9d3f4018361d937252d1226d
) introduced a change in the computation, which is based on the number of cores.
Hi Team,
Did default value for configuration parameter 'planner.width.max_per_node'
change between Drill 1.10 and 1.11 versions? Also, does default value of 70% of
total cores still hold true?
-- Drill 1.11
0: jdbc:drill:drillbit=localhost> select * from sys.options where name like
Hello Apache Supporters and Enthusiasts
This is your FINAL reminder that the Call for Papers (CFP) for the
Apache EU Roadshow is closing soon. Our Apache EU Roadshow will focus on
Cloud, IoT, Apache Tomcat, Apache Http and will run from 13-14 June 2018
in Berlin.
Note that the CFP deadline
Hi all!
Looks like the above issue is connected to much expressions in the
generated code. I believe it can be resolved by reducing the value for
"exec.java.compiler.exp_in_method_size" option on the session or system
level [1]. If it is not working, it means that logic is not implemented
for
