[
https://issues.apache.org/jira/browse/DRILL-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14548289#comment-14548289
]
Daniel Barclay (Drill) commented on DRILL-2343:
-----------------------------------------------
Instructions (also see Javadoc for
{{org.apache.drill.jbdbc.proxy.TracingProxyDriver}}):
- reconfigure the JDBC client to use a driver class of
{{org.apache.drill.jbdbc.proxy.TracingProxyDriver}},
- use a connection URL that consists of
"{{jdbc:proxy:org.apache.drill.jdbc.Driver:}}" prepended to the original URL
(e.g., "{{jdbc:drill:zk=local}}"),
- open a connection to that URL,
- use that connection and look wherever stderr (the standard error output
stream; Java's {{System.err}}) is configured to be sent (e.g., the terminal, a
log file, etc.). There should be lots of lines about calls and returns to
JDBC-defined methods.
> Create JDBC tracing proxy driver.
> ---------------------------------
>
> Key: DRILL-2343
> URL: https://issues.apache.org/jira/browse/DRILL-2343
> Project: Apache Drill
> Issue Type: New Feature
> Components: Client - JDBC
> Reporter: Daniel Barclay (Drill)
> Assignee: Daniel Barclay (Drill)
> Fix For: Future
>
> Attachments: DRILL-2343.4.patch.txt
>
>
> Create JDBC driver that functions as proxy to Drill (or other) JDBC driver in
> order to report calls made across the JDBC API.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
