[
https://issues.apache.org/jira/browse/DRILL-3921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14954125#comment-14954125
]
ASF GitHub Bot commented on DRILL-3921:
---------------------------------------
Github user sudheeshkatkam commented on a diff in the pull request:
https://github.com/apache/drill/pull/197#discussion_r41815941
--- Diff:
exec/java-exec/src/main/java/org/apache/drill/exec/ops/OperatorContextImpl.java
---
@@ -44,6 +53,11 @@
private final boolean applyFragmentLimit;
private DrillFileSystem fs;
+ /**
+ * This lazily initialized service is used to submit {@link Callable
tasks} that need a proxy user.
+ */
+ private ListeningExecutorService proxyUgiExecutor;
--- End diff --
What's a better name for this?
> 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
>
> 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)
