[ https://issues.apache.org/jira/browse/DRILL-3921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15053590#comment-15053590 ]
Krystal commented on DRILL-3921: -------------------------------- git.commit.id.abbrev=b906811 Verified that hive limit 1 queries completed much faster than before fix. > Hive LIMIT 1 queries take too long > ---------------------------------- > > Key: DRILL-3921 > URL: https://issues.apache.org/jira/browse/DRILL-3921 > Project: Apache Drill > Issue Type: Bug > Components: Execution - Flow > Reporter: Sudheesh Katkam > Assignee: Sudheesh Katkam > Fix For: 1.3.0 > > > Fragment initialization on a Hive table (that is backed by a directory of > many files) can take really long. This is evident through LIMIT 1 queries. > The root cause is that the underlying reader in the HiveRecordReader is > initialized when the ctor is called, rather than when setup is called. > Two changes need to be made: > 1) lazily initialize the underlying record reader in HiveRecordReader > 2) allow for running a callable as a proxy user within an operator (through > OperatorContext). This is required as initialization of the underlying record > reader needs to be done as a proxy user (proxy for owner of the file). > Previously, this was handled while creating the record batch tree. -- This message was sent by Atlassian JIRA (v6.3.4#6332)