Hi,
Has anyone tried to connect AWS managed ElasticSearch cluster to Zeppelin? Our
managed elastic-search domain end-point look something like this:
https://search-abc-xyz-prod-fdizuwhbc4663qlh2tqghghydajycyu.us-east-1.es.amazonaws.com
I have successfully added the elasticsearch interpreter i
Thank you for creating an issue and future fix.
Regards,
Soonoh
On 1 September 2017 at 18:50, Jeff Zhang wrote:
>
> It is due to only spark.* is accepted as spark properties, it seems
> there's still some libraaries using non spark.*.
>
> I created https://issues.apache.org/jira/browse/ZEPPELIN
It is due to only spark.* is accepted as spark properties, it seems there's
still some libraaries using non spark.*.
I created https://issues.apache.org/jira/browse/ZEPPELIN-2893 for that. And
will fix it in 0.7.3
Jung, Soonoh 于2017年9月1日周五 下午5:33写道：
> Hi zeppelin users,
>
> I have an issue when
Hi zeppelin users,
I have an issue when I upgraded zeppelin to 0.7.2 from 0.6.2
I am using spark-redis 0.3.2 library to load redis values.
To use that library, I have to set "redis.host" property on spark config
instance
It used to work on zeppelin 0.6.2 but not in 0.7.2.
How can I set spark co
Hi,
thanks for your answer. Actually this was/is my backup plan... I wanted to
avoid throwing in another service and thus was looking for a solution with
Zeppelin only...
best regards
On Friday, September 1, 2017 5:25:21 AM CEST Park Hoon wrote:
> Hi, If you are using nginx or webserver like
I tried in spark-shell, and the result is same.
Then, Spark causes this problem. I think Spark doesn't support Apache Tajo.
Cinyoung
2017-09-01 12:00 GMT+09:00 Jianfeng (Jeff) Zhang :
>
> Have tried that in spark-shell ?
>
> Best Regard,
> Jeff Zhang
>
>
> From: Cinyoung Hur
> Reply-To: "users@
