Re: AWS ElasticSearch Service with Zeppelin

2017-09-04 Thread Patrick Maroney
4663qlh2tqghghydajycyu.us-east-1.es.amazonaws.com/> elasticsearch.port 80 5) Test the note with the ES query. Thanks, Saksham From: Park Hoon <1am...@gmail.com> Sent: Monday, September 4, 2017 7:59:26 AM To: users@zeppelin.apache.org Subject: Re: AWS ElasticSearch Service with Zeppelin Hi, I think u nee

Re: AWS ElasticSearch Service with Zeppelin

2017-09-04 Thread Saksham Srivastava
sers@zeppelin.apache.org Subject: Re: AWS ElasticSearch Service with Zeppelin Hi, I think u need to use 9200 or 9300 depending on the client. - https://stackoverflow.com/questions/42721259/elasticsearch-interpreter-can-not-connect-to-database/42731420#42731420 Regard, On Fri, Sep 1,

Re: AWS ElasticSearch Service with Zeppelin

2017-09-03 Thread Park Hoon
Hi, I think u need to use 9200 or 9300 depending on the client. - https://stackoverflow.com/questions/42721259/elasticsearch-interpreter-can-not-connect-to-database/42731420#42731420 Regard, On Fri, Sep 1, 2017 at 10:46 PM, Saksham Srivastava wrote: > Hi, > > > Has anyone tried to connect

AWS ElasticSearch Service with Zeppelin

2017-09-01 Thread Saksham Srivastava
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