the issue I am seeing is related to this: [ZEPPELIN-2891] Impossible to use
jdbc interface with presto-jdbc >= 0.180 - ASF JIRA
|
|
| |
[ZEPPELIN-2891] Impossible to use jdbc interface with presto-jdbc >= 0.1...
|
|
|
and I have also filed an issue against presto, but people believes that should
be fixed on Zeppelin side.
Is strict config checking really needed? · Issue #9254 · prestodb/presto
|
|
|
| | |
|
|
|
| |
Is strict config checking really needed? · Issue #9254 · prestodb/presto
A strict config check was added in this commit
defabcb#diff-fc7374097aa800bd529f476b35716019 Any unrecognized co...
|
|
|
On Wednesday, November 1, 2017, 9:15:20 AM PDT, Richard Xin
<[email protected]> wrote:
the problem looks like the strict check introduced a few month ago by presto
throws exception when unrecognized properties are added, and default.url is
unrecognized by presto
prestodb/presto
|
|
|
| | |
|
|
|
| |
prestodb/presto
presto - Distributed SQL query engine for big data
|
|
|
On Wednesday, November 1, 2017, 2:31:04 AM PDT, David Howell
<[email protected]> wrote:
#yiv3292286389 -- filtered {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2
4;}#yiv3292286389 p.yiv3292286389MsoNormal, #yiv3292286389
li.yiv3292286389MsoNormal, #yiv3292286389 div.yiv3292286389MsoNormal
{margin:0cm;margin-bottom:.0001pt;font-size:11.0pt;}#yiv3292286389 h2
{margin-right:0cm;margin-left:0cm;font-size:18.0pt;}#yiv3292286389 a:link,
#yiv3292286389 span.yiv3292286389MsoHyperlink
{color:blue;text-decoration:underline;}#yiv3292286389 a:visited, #yiv3292286389
span.yiv3292286389MsoHyperlinkFollowed
{color:#954F72;text-decoration:underline;}#yiv3292286389 pre
{margin:0cm;margin-bottom:.0001pt;font-size:10.0pt;}#yiv3292286389
span.yiv3292286389Heading2Char {font-weight:bold;}#yiv3292286389
span.yiv3292286389HTMLPreformattedChar {}#yiv3292286389
p.yiv3292286389ydpa2ef8223card-description, #yiv3292286389
li.yiv3292286389ydpa2ef8223card-description, #yiv3292286389
div.yiv3292286389ydpa2ef8223card-description
{margin-right:0cm;margin-left:0cm;font-size:11.0pt;}#yiv3292286389
.yiv3292286389MsoChpDefault {}#yiv3292286389 filtered {margin:72.0pt 72.0pt
72.0pt 72.0pt;}#yiv3292286389 div.yiv3292286389WordSection1 {}#yiv3292286389
I’ve done this previously, my answer
herehttps://stackoverflow.com/a/44238195/1335793
I was using an older version though.
Did you try appending catalog, or a catalog & schema to the url?
Error message suggests problem is with the “default.url” in the interpreter
settings.
On another note, AWS has released Athena (managed version of presto) so when
it's available in my region I will look at using that.
Dave
From: Richard Xin
Sent: Wednesday, 1 November 2017 9:35 AM
To: Users
Subject: Zeppelin 0.7.2 integration with Presto 0.184
I am not sure Zeppelin 0.7.2 is compatible with Presto 0.184here are the steps:
1. create new presto interpreter
2. %presto
show tables
java.sql.SQLException: Unrecognized connection property 'url'at
com.facebook.presto.jdbc.PrestoDriverUri.validateConnectionProperties(PrestoDriverUri.java:292)at
com.facebook.presto.jdbc.PrestoDriverUri.<init>(PrestoDriverUri.java:89)at
com.facebook.presto.jdbc.PrestoDriverUri.<init>(PrestoDriverUri.java:79)at
com.facebook.presto.jdbc.PrestoDriver.connect(PrestoDriver.java:86)at
java.sql.DriverManager.getConnection(DriverManager.java:664)at
java.sql.DriverManager.getConnection(DriverManager.java:208)at
org.apache.commons.dbcp2.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:79)at
org.apache.commons.dbcp2.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:205)at
org.apache.commons.pool2.impl.GenericObjectPool.create(GenericObjectPool.java:836)at
org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:434)at
org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:361)at
org.apache.commons.dbcp2.PoolingDriver.connect(PoolingDriver.java:129)
...
it seems that presto has some strict property name checking, I believe it's not
uncommon that people want to use presto in Zeppelin, is there any work-around?
I am on AWS EMR
related presto code:prestodb/presto
|
|
|
| | |
|
|
|
| |
prestodb/presto
presto - Distributed SQL query engine for big data
|
|
|
