You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@zeppelin.apache.org by David Howell <da...@zipmoney.com.au> on 2017/11/01 09:30:59 UTC
RE: Zeppelin 0.7.2 integration with Presto 0.184
I’ve done this previously, my answer here https://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<ma...@yahoo.com>
Sent: Wednesday, 1 November 2017 9:35 AM
To: Users<ma...@zeppelin.apache.org>
Subject: Zeppelin 0.7.2 integration with Presto 0.184
I am not sure Zeppelin 0.7.2 is compatible with Presto 0.184
here are the steps:
1. create new presto interpreter
[Inline image]
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<https://github.com/prestodb/presto/blob/431f8701899145a62ab51a30d0b6ef9fe139dd76/presto-jdbc/src/main/java/com/facebook/presto/jdbc/PrestoDriverUri.java#L292>
<https://github.com/prestodb/presto/blob/431f8701899145a62ab51a30d0b6ef9fe139dd76/presto-jdbc/src/main/java/com/facebook/presto/jdbc/PrestoDriverUri.java#L292>
[https://s.yimg.com/nq/storm/assets/enhancrV2/23/logos/github.png]
prestodb/presto
presto - Distributed SQL query engine for big data
Re: Zeppelin 0.7.2 integration with Presto 0.184
Posted by Richard Xin <ri...@yahoo.com>.
Zeppelin 0.7.2 works ok with Presto 0.170, we just downgraded presto to avoid troubles.
On Thursday, November 2, 2017, 9:42:55 AM PDT, Felix Cheung <fe...@hotmail.com> wrote:
I guess we could add a switch on the Zeppelin side to not pass through properties when set? How do we know if a property is a good one for Presto or not?
From: David Howell <da...@zipmoney.com.au>
Sent: Wednesday, November 1, 2017 5:04:05 PM
To: Richard Xin; Users
Subject: RE: RE: Zeppelin 0.7.2 integration with Presto 0.184 #yiv9746054128 #yiv9746054128 _filtered #yiv9746054128 {font-family:Calibri;}#yiv9746054128 p.yiv9746054128MsoNormal, #yiv9746054128 li.yiv9746054128MsoNormal, #yiv9746054128 div.yiv9746054128MsoNormal {margin:0cm;margin-bottom:.0001pt;font-size:11.0pt;}#yiv9746054128 h2 {margin-right:0cm;margin-left:0cm;font-size:18.0pt;}#yiv9746054128 a:link, #yiv9746054128 span.yiv9746054128MsoHyperlink {color:blue;text-decoration:underline;}#yiv9746054128 a:visited, #yiv9746054128 span.yiv9746054128MsoHyperlinkFollowed {color:#954F72;text-decoration:underline;}#yiv9746054128 pre {margin:0cm;margin-bottom:.0001pt;font-size:10.0pt;}#yiv9746054128 span.yiv9746054128Heading2Char {font-weight:bold;}#yiv9746054128 p.yiv9746054128ydp3ae6d857card-description, #yiv9746054128 li.yiv9746054128ydp3ae6d857card-description, #yiv9746054128 div.yiv9746054128ydp3ae6d857card-description {margin-right:0cm;margin-left:0cm;font-size:11.0pt;}#yiv9746054128 p.yiv9746054128ydpcc4a0123card-description, #yiv9746054128 li.yiv9746054128ydpcc4a0123card-description, #yiv9746054128 div.yiv9746054128ydpcc4a0123card-description {margin-right:0cm;margin-left:0cm;font-size:11.0pt;}#yiv9746054128 span.yiv9746054128HTMLPreformattedChar {}#yiv9746054128 p.yiv9746054128msonormal, #yiv9746054128 li.yiv9746054128msonormal, #yiv9746054128 div.yiv9746054128msonormal {margin-right:0cm;margin-left:0cm;font-size:11.0pt;}#yiv9746054128 p.yiv9746054128ydpa2ef8223card-description, #yiv9746054128 li.yiv9746054128ydpa2ef8223card-description, #yiv9746054128 div.yiv9746054128ydpa2ef8223card-description {margin-right:0cm;margin-left:0cm;font-size:11.0pt;}#yiv9746054128 .yiv9746054128MsoChpDefault {} _filtered #yiv9746054128 {margin:72.0pt 72.0pt 72.0pt 72.0pt;}#yiv9746054128 div.yiv9746054128WordSection1 {}#yiv9746054128
Hmm yes it does look like that.
Aren't the interpreter settings stored inside some json file? Perhaps you could try editing the file to removing those properties, or rename them to what Presto expects, then restart the Zeppelin service.
I think its a silly Patch on the Presto side, way too opinionated. They shouldn’t be failing on properties that aren't required, only when required properties are missing. The justification that it “prevents typos of required properties” is misguided. It now just throws exceptions even if all the required properties are supplied, that’s not “strict” that's OCD.
Meanwhile are these standard JDBC properties or just standard Zeppelin properties? I would have thought all JDBC connections require a URL and a driver, so patching Zeppelin to remove these is now an imposition on all JDBC interpreters. Or alternatively Presto is now different enough from generic JDBC to warrant it's own interpreter, which could be fairly easily added by modifying the generic JDBC one and changing those properties.
Dave
From: Richard Xin
Sent: Thursday, 2 November 2017 7:12 AM
To: Users; David Howell
Subject: Re: RE: Zeppelin 0.7.2 integration with Presto 0.184
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 <ri...@yahoo.com> 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 <da...@zipmoney.com.au> wrote:
#yiv9746054128 #yiv9746054128 -- -- filtered {font-family:Calibri;}#yiv9746054128 p.yiv9746054128MsoNormal, #yiv9746054128 li.yiv9746054128MsoNormal, #yiv9746054128 div.yiv9746054128MsoNormal {margin:0cm;margin-bottom:.0001pt;font-size:11.0pt;}#yiv9746054128 h2 {margin-right:0cm;margin-left:0cm;font-size:18.0pt;}#yiv9746054128 a:link, #yiv9746054128 span.yiv9746054128MsoHyperlink {color:blue;text-decoration:underline;}#yiv9746054128 a:visited, #yiv9746054128 span.yiv9746054128MsoHyperlinkFollowed {color:#954F72;text-decoration:underline;}#yiv9746054128 pre {margin:0cm;margin-bottom:.0001pt;font-size:10.0pt;}#yiv9746054128 span.yiv9746054128Heading2Char {font-weight:bold;}#yiv9746054128 p.yiv9746054128ydpa2ef8223card-description, #yiv9746054128 li.yiv9746054128ydpa2ef8223card-description, #yiv9746054128 div.yiv9746054128ydpa2ef8223card-description {margin-right:0cm;margin-left:0cm;font-size:11.0pt;}#yiv9746054128 filtered {margin:72.0pt 72.0pt 72.0pt 72.0pt;}#yiv9746054128
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
|
|
|
Re: Zeppelin 0.7.2 integration with Presto 0.184
Posted by Felix Cheung <fe...@hotmail.com>.
I guess we could add a switch on the Zeppelin side to not pass through properties when set? How do we know if a property is a good one for Presto or not?
________________________________
From: David Howell <da...@zipmoney.com.au>
Sent: Wednesday, November 1, 2017 5:04:05 PM
To: Richard Xin; Users
Subject: RE: RE: Zeppelin 0.7.2 integration with Presto 0.184
Hmm yes it does look like that.
Aren't the interpreter settings stored inside some json file? Perhaps you could try editing the file to removing those properties, or rename them to what Presto expects, then restart the Zeppelin service.
I think its a silly Patch on the Presto side, way too opinionated. They shouldn’t be failing on properties that aren't required, only when required properties are missing. The justification that it “prevents typos of required properties” is misguided. It now just throws exceptions even if all the required properties are supplied, that’s not “strict” that's OCD.
Meanwhile are these standard JDBC properties or just standard Zeppelin properties? I would have thought all JDBC connections require a URL and a driver, so patching Zeppelin to remove these is now an imposition on all JDBC interpreters. Or alternatively Presto is now different enough from generic JDBC to warrant it's own interpreter, which could be fairly easily added by modifying the generic JDBC one and changing those properties.
Dave
From: Richard Xin<ma...@yahoo.com>
Sent: Thursday, 2 November 2017 7:12 AM
To: Users<ma...@zeppelin.apache.org>; David Howell<ma...@zipmoney.com.au>
Subject: Re: RE: Zeppelin 0.7.2 integration with Presto 0.184
the issue I am seeing is related to this: [ZEPPELIN-2891] Impossible to use jdbc interface with presto-jdbc >= 0.180 - ASF JIRA<https://issues.apache.org/jira/browse/ZEPPELIN-2891>
<https://issues.apache.org/jira/browse/ZEPPELIN-2891>
[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<https://github.com/prestodb/presto/issues/9254>
<https://github.com/prestodb/presto/issues/9254>
[https://s.yimg.com/nq/storm/assets/enhancrV2/23/logos/github.png]
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 <ri...@yahoo.com> 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<https://github.com/prestodb/presto/blob/431f8701899145a62ab51a30d0b6ef9fe139dd76/presto-jdbc/src/main/java/com/facebook/presto/jdbc/PrestoDriverUri.java#L290-L294>
<https://github.com/prestodb/presto/blob/431f8701899145a62ab51a30d0b6ef9fe139dd76/presto-jdbc/src/main/java/com/facebook/presto/jdbc/PrestoDriverUri.java#L290-L294>
[https://s.yimg.com/nq/storm/assets/enhancrV2/23/logos/github.png]
prestodb/presto
presto - Distributed SQL query engine for big data
On Wednesday, November 1, 2017, 2:31:04 AM PDT, David Howell <da...@zipmoney.com.au> wrote:
I’ve done this previously, my answer here https://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<ma...@yahoo.com>
Sent: Wednesday, 1 November 2017 9:35 AM
To: Users<ma...@zeppelin.apache.org>
Subject: Zeppelin 0.7.2 integration with Presto 0.184
I am not sure Zeppelin 0.7.2 is compatible with Presto 0.184
here are the steps:
1. create new presto interpreter
[Inline image]
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<https://github.com/prestodb/presto/blob/431f8701899145a62ab51a30d0b6ef9fe139dd76/presto-jdbc/src/main/java/com/facebook/presto/jdbc/PrestoDriverUri.java#L292>
<https://github.com/prestodb/presto/blob/431f8701899145a62ab51a30d0b6ef9fe139dd76/presto-jdbc/src/main/java/com/facebook/presto/jdbc/PrestoDriverUri.java#L292>
[https://s.yimg.com/nq/storm/assets/enhancrV2/23/logos/github.png]
prestodb/presto
presto - Distributed SQL query engine for big data
RE: RE: Zeppelin 0.7.2 integration with Presto 0.184
Posted by David Howell <da...@zipmoney.com.au>.
Hmm yes it does look like that.
Aren't the interpreter settings stored inside some json file? Perhaps you could try editing the file to removing those properties, or rename them to what Presto expects, then restart the Zeppelin service.
I think its a silly Patch on the Presto side, way too opinionated. They shouldn’t be failing on properties that aren't required, only when required properties are missing. The justification that it “prevents typos of required properties” is misguided. It now just throws exceptions even if all the required properties are supplied, that’s not “strict” that's OCD.
Meanwhile are these standard JDBC properties or just standard Zeppelin properties? I would have thought all JDBC connections require a URL and a driver, so patching Zeppelin to remove these is now an imposition on all JDBC interpreters. Or alternatively Presto is now different enough from generic JDBC to warrant it's own interpreter, which could be fairly easily added by modifying the generic JDBC one and changing those properties.
Dave
From: Richard Xin<ma...@yahoo.com>
Sent: Thursday, 2 November 2017 7:12 AM
To: Users<ma...@zeppelin.apache.org>; David Howell<ma...@zipmoney.com.au>
Subject: Re: RE: Zeppelin 0.7.2 integration with Presto 0.184
the issue I am seeing is related to this: [ZEPPELIN-2891] Impossible to use jdbc interface with presto-jdbc >= 0.180 - ASF JIRA<https://issues.apache.org/jira/browse/ZEPPELIN-2891>
<https://issues.apache.org/jira/browse/ZEPPELIN-2891>
[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<https://github.com/prestodb/presto/issues/9254>
<https://github.com/prestodb/presto/issues/9254>
[https://s.yimg.com/nq/storm/assets/enhancrV2/23/logos/github.png]
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 <ri...@yahoo.com> 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<https://github.com/prestodb/presto/blob/431f8701899145a62ab51a30d0b6ef9fe139dd76/presto-jdbc/src/main/java/com/facebook/presto/jdbc/PrestoDriverUri.java#L290-L294>
<https://github.com/prestodb/presto/blob/431f8701899145a62ab51a30d0b6ef9fe139dd76/presto-jdbc/src/main/java/com/facebook/presto/jdbc/PrestoDriverUri.java#L290-L294>
[https://s.yimg.com/nq/storm/assets/enhancrV2/23/logos/github.png]
prestodb/presto
presto - Distributed SQL query engine for big data
On Wednesday, November 1, 2017, 2:31:04 AM PDT, David Howell <da...@zipmoney.com.au> wrote:
I’ve done this previously, my answer here https://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<ma...@yahoo.com>
Sent: Wednesday, 1 November 2017 9:35 AM
To: Users<ma...@zeppelin.apache.org>
Subject: Zeppelin 0.7.2 integration with Presto 0.184
I am not sure Zeppelin 0.7.2 is compatible with Presto 0.184
here are the steps:
1. create new presto interpreter
[Inline image]
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<https://github.com/prestodb/presto/blob/431f8701899145a62ab51a30d0b6ef9fe139dd76/presto-jdbc/src/main/java/com/facebook/presto/jdbc/PrestoDriverUri.java#L292>
<https://github.com/prestodb/presto/blob/431f8701899145a62ab51a30d0b6ef9fe139dd76/presto-jdbc/src/main/java/com/facebook/presto/jdbc/PrestoDriverUri.java#L292>
[https://s.yimg.com/nq/storm/assets/enhancrV2/23/logos/github.png]
prestodb/presto
presto - Distributed SQL query engine for big data
Re: RE: Zeppelin 0.7.2 integration with Presto 0.184
Posted by Richard Xin <ri...@yahoo.com>.
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 <ri...@yahoo.com> 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 <da...@zipmoney.com.au> 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
|
|
|
Re: RE: Zeppelin 0.7.2 integration with Presto 0.184
Posted by Richard Xin <ri...@yahoo.com>.
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 <da...@zipmoney.com.au> wrote:
#yiv9822418077 #yiv9822418077 -- _filtered #yiv9822418077 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}#yiv9822418077 #yiv9822418077 p.yiv9822418077MsoNormal, #yiv9822418077 li.yiv9822418077MsoNormal, #yiv9822418077 div.yiv9822418077MsoNormal {margin:0cm;margin-bottom:.0001pt;font-size:11.0pt;}#yiv9822418077 h2 {margin-right:0cm;margin-left:0cm;font-size:18.0pt;}#yiv9822418077 a:link, #yiv9822418077 span.yiv9822418077MsoHyperlink {color:blue;text-decoration:underline;}#yiv9822418077 a:visited, #yiv9822418077 span.yiv9822418077MsoHyperlinkFollowed {color:#954F72;text-decoration:underline;}#yiv9822418077 pre {margin:0cm;margin-bottom:.0001pt;font-size:10.0pt;}#yiv9822418077 span.yiv9822418077Heading2Char {font-weight:bold;}#yiv9822418077 span.yiv9822418077HTMLPreformattedChar {}#yiv9822418077 p.yiv9822418077ydpa2ef8223card-description, #yiv9822418077 li.yiv9822418077ydpa2ef8223card-description, #yiv9822418077 div.yiv9822418077ydpa2ef8223card-description {margin-right:0cm;margin-left:0cm;font-size:11.0pt;}#yiv9822418077 .yiv9822418077MsoChpDefault {} _filtered #yiv9822418077 {margin:72.0pt 72.0pt 72.0pt 72.0pt;}#yiv9822418077 div.yiv9822418077WordSection1 {}#yiv9822418077
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
|
|
|