Hi Guys,
is there way to push stream of updates to Zeppelin dashboard ? for example I
get bunch of data to my
spark streaming cluster and as I get more and more data I want to compute and
write it somewhere such that my Zeppelin dashboard is updated? If so, where
would be the best place to write
Hi,
Regarding push update result,
https://gist.github.com/granturing/a09aed4a302a7367be92
can be an interesting example. Which push update map from tweet stream.
Thanks,
moon
On Wed, Aug 24, 2016 at 4:25 AM kant kodali wrote:
> Hi Guys,
> is there way to push stream of updates to Zeppelin dash
Hi Moon,
I don't see any websocket connection from the code you sent so I wonder how is
it getting push updates?
Thanks,Kant
On Wed, Aug 24, 2016 4:27 AM, moon soo Lee m...@apache.org
wrote:
Hi,
Regarding push update result,
https://gist.github.com/granturing/a09aed4a302a7367be92
can b
You can check
http://zeppelin.apache.org/docs/latest/displaysystem/back-end-angular.html to
how front-end / back-end can exchange data and events.
Thanks,
moon
On Wed, Sep 7, 2016 at 12:00 AM kant kodali wrote:
> Hi Moon,
> I don't see any websocket connection from the code you sent so I wonder
Hi Moon,
When I receive the events through a websocket from a server how can I use
Zeppelin charts (The charts that get generated after running a sql command per
say) to display it ?
Thanks,Kant
On Wed, Sep 7, 2016 8:02 AM, moon soo Lee m...@apache.org
wrote:
You can check
http://zeppelin.a
Hi Kant,
The front-end react to multiple websocket events sent by the server to
update its content.
The most usual events regarding the paragraph rendering would be "NOTE" and
"PARAGRAPH"
However those are handled by the server itself.
The latest link from moon is a good example on how it can be
Hi Corneau,
I still don't quite understand (probably because I am more of a backend
engineer). All I want to know is how do I need connect my data that I get
from my websocket to the charts? other words I shouldn't be writing code to
build charts (like bar, pie and so on) I should be able to tell
I explained the workflow a bit more on the other thread.
The front-end react to what the server is sending to him. (through
websocket)
So in the end it's more of a processing issue and
Zeppelin-server/Interpreter communication one.
If you could tell more about the stream updates (technology-wise)