Yusuf created DRILL-7771:
----------------------------
Summary: Order by and limit transactions in RDBMS cannot be
pushdown
Key: DRILL-7771
URL: https://issues.apache.org/jira/browse/DRILL-7771
Project: Apache Drill
Issue Type: Bug
Components: Query Planning & Optimization
Affects Versions: 1.17.0
Reporter: Yusuf
Attachments: Physical Plan.PNG, query.PNG
hi,
When using ORDER BY, LIMIT and OFFSET in large tables in RDBMS, it draws the
entire table on DRILL and it occurs very slow or heap memory. When we look at
the query plan, instead of having ORDER BY, LIMIT and OFFSET features done by
RDBMS, DRILL does it by pulling all the data on it. It is very critical to
transmit these transactions to the database.
ISSUE # 7490
https://issues.apache.org/jira/browse/drıll-7490
The LIMIT pushdown problem was communicated as resolved but there was a missing
solution. I wrote the necessary comment in the comment section.
Regardless of the number of columns selected, regardless of the number of joins
and tables, pushdown should be done in RDBMS
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
