RE: Zeppelin 0.5.6 Disconnected

2016-04-04 Thread Oren Shani
Hello, Yes it works now. And I understand that this: https://issues.apache.org/jira/browse/ZEPPELIN-173 Is no longer a concern, right? Many thanks, Oren From: astros...@gmail.com [mailto:astros...@gmail.com] On Behalf Of Hyung Sung Shim Sent: Tuesday, April 5, 2016 6:56 AM To: users@zeppeli

Re: Zeppelin 0.5.6 Disconnected

2016-04-04 Thread Hyung Sung Shim
Hello. I just did test same with your environment and I got success working. All your configuration seems good except the "zeppelin.server.allowed.origins" config. Can you try to set the "zeppelin.server.allowed.origins" value to "*" like the following? *# conf/zeppelin-site.xml* ** * zeppelin.se

Re: z.angularbind from sql

2016-04-04 Thread DuyHai Doan
Once https://github.com/apache/incubator-zeppelin/pull/745 will be merged, you can control dynamic variable of a paragraph from another paragraph using AngularJS function 'z.angularBind()' as shown in the screen shot of the PR On Mon, Apr 4, 2016 at 7:20 PM, Randy Gelhausen wrote: > https://gist

z.angularbind from sql

2016-04-04 Thread Randy Gelhausen
https://gist.github.com/randerzander/fb4a4ff1fcb84f9304b9 In the example above, I'm using $spark to access z.angularbind -- is there a way to access it directly from %sql instead of needing to wrap my queries in Scala?

Re: Zeppelin 0.5.6 Disconnected

2016-04-04 Thread Hyung Sung Shim
Hello. I think the "Disconnected" problem is the websocket connection problem. The *"zeppelin.ssl.keystore.path"* should be under "~/$ZEPPELIN_HOME/conf/" path. If it's still not working, can you send the zeppelin log files that is under the "~/$ZEPPELIN_HOME/logs" ? Thanks. 2016-04-05 0:05 GM

RE: Zeppelin 0.5.6 Disconnected

2016-04-04 Thread Oren Shani
Hi, Nginx should be configured OK now, but still disconnected. Could it be something else? For example, did I have to install Spark and/or Hadoop? Oren From: astros...@gmail.com [mailto:astros...@gmail.com] On Behalf Of Hyung Sung Shim Sent: Monday, April 4, 2016 5:17 PM To: users@zeppelin.in

Re: Zeppelin 0.5.6 Disconnected

2016-04-04 Thread Hyung Sung Shim
hi. You could refer to https://github.com/apache/incubator-zeppelin/pull/814. I just tested on Ubuntu 14.04.3 and it's working well. Thanks. 2016-04-04 21:08 GMT+09:00 Oren Shani : > Sung Shim, > > > > > > I wasn't sure what http://backend and http://backendWS should refer to > so I defined bot

Re: Spark Job Server

2016-04-04 Thread John Omernik
Interesting. Has https://github.com/spark-jobserver/spark-jobserver been compared to toree and Livy? What is the licensing on Livy, could that cause issues down stream? (I am new to some of these things). John On Mon, Apr 4, 2016 at 6:35 AM, moon soo Lee wrote: > Hi John, > > A proposal [1] a

RE: Zeppelin 0.5.6 Disconnected

2016-04-04 Thread Oren Shani
Sung Shim, I wasn't sure what http://backend and http://backendWS should refer to so I defined both as upstream to localhost:8080 Also when I defined the following: proxy_set_header X-Real-IP $proxy_protocol_addr; proxy_set_header X-Forwarded-For $proxy_protocol_addr; Nginx co

Re: Spark Job Server

2016-04-04 Thread moon soo Lee
Hi John, A proposal [1] attached in ZEPPELIN-773 [2] shows spark interpreter based on livy [3]. I think this is similar to what you think. Please take a look. Thanks, moon [1] https://docs.google.com/document/d/1AVGcviyVqWmmbHJmkgUo76ZDSwWAMjwHxmKBhZdAav4/edit#heading=h.5uzzc48tw5d8 [2] https://

Re: Zeppelin 0.5.6 Disconnected

2016-04-04 Thread Hyung Sung Shim
Hello. Since 0.5.5, Zeppelin uses single port for REST and websocket. so Could you try to use same port like follow Nginx configuration? server { listen 80 ; server_name _; location / { proxy_set_header Host$host; proxy_set_header X-Real-IP $proxy_protocol_addr;

Zeppelin 0.5.6 Disconnected

2016-04-04 Thread Oren Shani
Hello, I installed Zeppelin 0.5.6 on Ubuntu server 14.04, behind Nginx. Zeppelin comes up but shows "Disconnected" in the top right corner. I found several references to a similar problem on the web and most of them suggest that the problem has to do with access to Zeppelin's winsock port (80