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 <[email protected]> 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* >
