[ 
https://issues.apache.org/jira/browse/DRILL-8057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17468690#comment-17468690
 ] 

ASF GitHub Bot commented on DRILL-8057:
---------------------------------------

lgtm-com[bot] commented on pull request #2388:
URL: https://github.com/apache/drill/pull/2388#issuecomment-1004908325


   This pull request **introduces 5 alerts** when merging 
ce046faa50fa78857640ca7546336e733cf9d965 into 
fa2cb0f4937c0d8e797a675d8d6c13c316e48d4c - [view on 
LGTM.com](https://lgtm.com/projects/g/apache/drill/rev/pr-de882f8198d8945d6a7c877a69fe541f9266856f)
   
   **new alerts:**
   
   * 5 for Spurious Javadoc @param tags


-- 
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)

Reply via email to