In this case, it is already implemented. Look at those merged PR:
- https://github.com/apache/incubator-zeppelin/pull/739 - https://github.com/apache/incubator-zeppelin/pull/740 - https://github.com/apache/incubator-zeppelin/pull/741 - https://github.com/apache/incubator-zeppelin/pull/742 - https://github.com/apache/incubator-zeppelin/pull/744 - https://github.com/apache/incubator-zeppelin/pull/745 - https://github.com/apache/incubator-zeppelin/pull/832 There is one last JIRA pending for documentation, I'll do a PR for this next week: https://issues.apache.org/jira/browse/ZEPPELIN-742 On Fri, Apr 22, 2016 at 9:52 PM, Trevor Grant <trevor.d.gr...@gmail.com> wrote: > I want to be able to put/get/watch variables. Specifically so I can > interface with AngularJS for visualizations. > > I've been groking the codebase trying to find a less invasive way to do > this. > > I get wanting to keep the code base clean but sharing variables is a really > nice feature set and shouldn't be that hard to implement? > > Thoughts? > > Trevor Grant > Data Scientist > https://github.com/rawkintrevo > http://stackexchange.com/users/3002022/rawkintrevo > http://trevorgrant.org > > *"Fortunate is he, who is able to know the causes of things." -Virgil* > > > On Fri, Apr 22, 2016 at 1:06 PM, DuyHai Doan <doanduy...@gmail.com> wrote: > > > I think we should rather let ZeppelinContext un-modified. > > > > If we update ZeppelinContext for every kind of interpreter, it would > become > > quickly a behemoth and un-manageable. > > > > The reason ZeppelinContext has some support for Spark is because it's > > historical. Now that the project is going to gain wider audience, we > should > > focus on keeping the code as cleanest and as modular as possible. > > > > Can you explain which feature you want to add to ZeppelinContext that > will > > be useful for Flink ? > > > > > > > > On Fri, Apr 22, 2016 at 7:12 PM, Trevor Grant <trevor.d.gr...@gmail.com> > > wrote: > > > > > If one were to extend the Zeppelin context for Flink, I was thinking it > > > would make the most sense to update > > > > > > ../spark/src/main/java/org/apache/zeppelin/spark/ZeppelinContext.java > > > > > > Any thoughts from those who are more familiar with that end of the code > > > base than I? > > > > > > Ideally we'd have a solution that extend the Zeppelin Context to all > > > interpreters. I know y'all love Spark but there ARE others out > there... > > > > > > Anyone have any branches / previous attempts I could check out? > > > > > > tg > > > > > > > > > Trevor Grant > > > Data Scientist > > > https://github.com/rawkintrevo > > > http://stackexchange.com/users/3002022/rawkintrevo > > > http://trevorgrant.org > > > > > > *"Fortunate is he, who is able to know the causes of things." -Virgil* > > > > > >