Github user laurentgo commented on a diff in the pull request:
https://github.com/apache/drill/pull/858#discussion_r123294241
--- Diff:
exec/jdbc/src/main/java/org/apache/drill/jdbc/impl/DrillStatementImpl.java ---
@@ -38,8 +44,12 @@
// methods for compatibility.)
class DrillStatementImpl extends AvaticaStatement implements
DrillStatement,
DrillRemoteStatement {
+ //Not using the DrillbitContext's ExecutorService as this is threadPool
is light-weight (threads wake up to cancel tasks) but needs a low response time
+ private static ExecutorService queryTimeoutTaskPool =
Executors.newCachedThreadPool(new NamedThreadFactory("q-timeout-"));
--- End diff --
I believe this is unnecessary: DrillClient provides an asynchronous API,
which is used by the JDBC driver, so all the timeout logic could be done
without the use of thread pool. You might want to look at DrillCursor which is
where all the magic happens I believe.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
