[
https://issues.apache.org/jira/browse/DRILL-8057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17451154#comment-17451154
]
ASF GitHub Bot commented on DRILL-8057:
---------------------------------------
dzamo commented on pull request #2388:
URL: https://github.com/apache/drill/pull/2388#issuecomment-982678036
@cgivre let's hold off I think. While the change here would reasonably be
mergeable (once checkstyle was satisfied), it does not bring any meaningful
benefit if the earlier plugin scanning stays the way it is. I'm still hopeful
that something can be done
--
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]
> INFORMATION_SCHEMA filter push down is inefficient
> --------------------------------------------------
>
> Key: DRILL-8057
> URL: https://issues.apache.org/jira/browse/DRILL-8057
> Project: Apache Drill
> Issue Type: Improvement
> Components: Storage - Information Schema
> Affects Versions: 1.19.0
> Reporter: James Turton
> Assignee: James Turton
> Priority: Major
> Fix For: 1.20.0
>
>
> WHERE clauses in queries against INFORMATION_SCHEMA do not stop Drill from
> fetching a schema hierarchy from all enabled storage configs. This results
> in abysmal performance when unresponsive data sources are enabled, as
> reported by users in the Apache Drill Slack channels.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
