[
https://issues.apache.org/jira/browse/DRILL-7698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17102115#comment-17102115
]
Paul Rogers commented on DRILL-7698:
------------------------------------
In Drill 1.18 (Snapshot), we skip over drivers that cannot be loaded. Prior
versions failed all queries in this case. Added logging, at the warning level,
when we skip a plugin. The logging includes the error.
In my initial test, using the config in the description, the plugin failed to
load because the driver name is wrong. The name of the Driver class from the
link provided is `com.facebook.presto.jdbc.PrestoDriver` not
`io.prestosql.jdbc.PrestoDriver`.
Once we get past that, then we hit another issue when trying to load the
schemas: `Method ResultSet.getStatement is not yet implemented` returned from
the Presto JDBC driver.
The logic to get schemas appears to be something added to the code about 7
months ago, using the "Hikari" library.
This seems to be an issue with the Hikari-based design and will take
substantial investigation.
> RDBMS Plugin Not Returning Results from Presto
> ----------------------------------------------
>
> Key: DRILL-7698
> URL: https://issues.apache.org/jira/browse/DRILL-7698
> Project: Apache Drill
> Issue Type: Bug
> Components: Storage - JDBC
> Affects Versions: 1.18.0
> Reporter: Charles Givre
> Priority: Blocker
> Attachments: Screen Shot 2020-04-12 at 2.43.33 PM.png, Screen Shot
> 2020-04-12 at 2.56.10 PM.png, Screen Shot 2020-04-12 at 3.00.00 PM.png,
> Screen Shot 2020-04-12 at 3.01.37 PM.png
>
>
> Using the RDBMS storage plugin, Drill is unable to connect to Presto. More
> specifically, Drill seems to be connecting and sending queries to Presto, but
> then nothing happens with the query results.
> I verified the configuration using DBBeaver and was able to successfully
> query Presto. See screenshot below for config.
> !Screen Shot 2020-04-12 at 2.43.33 PM.png!
> Presto ships with a few sample databases as shown below, and these should be
> visible in Drill but are not.
> !Screen Shot 2020-04-12 at 2.56.10 PM.png!
> From the logs below, Presto is clearly receiving the queries from Drill, and
> the queries are returning results, but Drill seems to be dropping the
> results. While this may seem like a silly exercise, querying Presto from
> Drill, the fact that it didn't work makes me think we may have a bug in the
> JDBC Storage Plugin.
> !Screen Shot 2020-04-12 at 3.01.37 PM.png!
> !Screen Shot 2020-04-12 at 3.00.00 PM.png!
> h2. Steps to Reproduce
> 1. Download and start Docker container with Presto.
> 2. Download Presto JDBC driver (https://prestodb.io/download.html) and copy
> to Drill classpath.
> 3. Create RDBMS storage plugin instance using default config below:
> {code:java}
> {
> "type": "jdbc",
> "driver": "io.prestosql.jdbc.PrestoDriver",
> "url": "jdbc:presto://localhost:8080/tpch/sf1",
> "username": "user",
> "password": null,
> "caseInsensitiveTableNames": true,
> "sourceParameters": {},
> "enabled": true
> }
> {code}
> 4. Execute a SHOW DATABASES query and you will see that no presto related
> results are returned. Various queries to the INFORMATION SCHEMA reveal the
> same thing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
