Hi Sudheesh and Zelaine,
Thank you both for the reply.
Unfortunately I wasn't able to recreate the scenario with a small set of
tables and dummy records, but I created the issue 4818 -
https://issues.apache.org/jira/browse/DRILL-4818 on Jira and attached the
query, the physical plan and the Json
Note though that the decision on whether to push down the join is dependent
on the cost of doing so relative to other options. I believe there are
currently limitations in the costing model of the JDBC storage plugin that
prevent the optimizer from choosing the "correct" plan in all cases.
But
Hi Marcus,
I am glad that you are exploring Drill! Per RDBMS storage plugin documentation
[1], join pushdown is supported. So the scenario you described is likely a bug;
can you open a ticket [2] with the details on how to reproduce the issue?
Thank you,
Sudheesh
[1]
Hi all,
I started to teste Drill and I'm very excited about the possibilities.
By now I'm trying to map ours databases running on Oracle 11g. After try
some queries I realized that the amount of time Drill takes to complete is
bigger than a general sql client takes. Looking the execution plan I
