You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@zeppelin.apache.org by Mich Talebzadeh <mi...@gmail.com> on 2018/07/07 17:34:07 UTC
Connecting from Zeppelin 0.7.3 to Oracle 12c semds Spark 2.3.0 is not supported
This simple connection has been working for 2 years.
Recently upgraded Zeppelin to 0.7.3 and my current Spark is 2.3.
However, this is a simple Oracle JDBC connection from Zeppelin to Oracle
12c and has nothing to do with Spark. So why the plot fails with Spark
2.3.0 is not supported?
Thanks
Dr Mich Talebzadeh
LinkedIn * https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw
<https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw>*
http://talebzadehmich.wordpress.com
*Disclaimer:* Use it at your own risk. Any and all responsibility for any
loss, damage or destruction of data or any other property which may arise
from relying on this email's technical content is explicitly disclaimed.
The author will in no case be liable for any monetary damages arising from
such loss, damage or destruction.
Re: Connecting from Zeppelin 0.7.3 to Oracle 12c semds Spark 2.3.0 is
not supported
Posted by Mich Talebzadeh <mi...@gmail.com>.
sure thanks I sorted it out.
regards,
Dr Mich Talebzadeh
LinkedIn * https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw
<https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw>*
http://talebzadehmich.wordpress.com
*Disclaimer:* Use it at your own risk. Any and all responsibility for any
loss, damage or destruction of data or any other property which may arise
from relying on this email's technical content is explicitly disclaimed.
The author will in no case be liable for any monetary damages arising from
such loss, damage or destruction.
On Sun, 8 Jul 2018 at 02:38, Jeff Zhang <zj...@gmail.com> wrote:
>
> Zeppelin 0.7.3 doesn't support spark 2.3, you can use zeppelin 0.8.0 which
> support spark 2.3
>
> Mich Talebzadeh <mi...@gmail.com>于2018年7月8日周日 上午1:34写道：
>
>> This simple connection has been working for 2 years.
>>
>> Recently upgraded Zeppelin to 0.7.3 and my current Spark is 2.3.
>>
>> However, this is a simple Oracle JDBC connection from Zeppelin to Oracle
>> 12c and has nothing to do with Spark. So why the plot fails with Spark
>> 2.3.0 is not supported?
>>
>> Thanks
>>
>> Dr Mich Talebzadeh
>>
>>
>>
>> LinkedIn * https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw
>> <https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw>*
>>
>>
>>
>> http://talebzadehmich.wordpress.com
>>
>>
>> *Disclaimer:* Use it at your own risk. Any and all responsibility for
>> any loss, damage or destruction of data or any other property which may
>> arise from relying on this email's technical content is explicitly
>> disclaimed. The author will in no case be liable for any monetary damages
>> arising from such loss, damage or destruction.
>>
>>
>>
>
Re: Connecting from Zeppelin 0.7.3 to Oracle 12c semds Spark 2.3.0 is
not supported
Posted by Jeff Zhang <zj...@gmail.com>.
Zeppelin 0.7.3 doesn't support spark 2.3, you can use zeppelin 0.8.0 which
support spark 2.3
Mich Talebzadeh <mi...@gmail.com>于2018年7月8日周日 上午1:34写道：
> This simple connection has been working for 2 years.
>
> Recently upgraded Zeppelin to 0.7.3 and my current Spark is 2.3.
>
> However, this is a simple Oracle JDBC connection from Zeppelin to Oracle
> 12c and has nothing to do with Spark. So why the plot fails with Spark
> 2.3.0 is not supported?
>
> Thanks
>
> Dr Mich Talebzadeh
>
>
>
> LinkedIn * https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw
> <https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw>*
>
>
>
> http://talebzadehmich.wordpress.com
>
>
> *Disclaimer:* Use it at your own risk. Any and all responsibility for any
> loss, damage or destruction of data or any other property which may arise
> from relying on this email's technical content is explicitly disclaimed.
> The author will in no case be liable for any monetary damages arising from
> such loss, damage or destruction.
>
>
>