Hello. Welcome to Zeppelin dev list. In fact, Zeppelin's backend side is mostly written in Java. Therefore fundamentally Zeppelin has better compatibility with Java based software. And yes, for Ignite SQL it won't be that difficult to integrate.
For Api based one, like compute, It really depends on how ignite wanted to be integrated. if you expect interactive code compile and run, it might need two things in general. One is interactive code compiler. So any codes - like you defining your class inside of Zeppelin - should compiled on the fly, line by line, and generates class files. I think Scala or Groovy compiler and many other language that they have REPL can do this, but not sure about Java. Second thing is, generated class files need be somehow transferred and loaded to remote cluster nodes. So i was thought integration code compiler and remote class loading mechanism either Zeppelin side or Ignite side. What do you think? Thanks, moon On Wed, Apr 15, 2015 at 6:10 PM Dmitriy Setrakyan <[email protected]> wrote: > This is my first email to the Zeppelin dev list, so hello everyone. > > I am on the PPMC of Apache Ignite and I would like to start a discussion on > integrating Zeppelin with Apache Ignite. Apache Ignite has a fairly feature > rich family of in-memory components, including distributed caching & data > grid, compute grid, streaming & CEP, etc. It is a JAVA-based product, so > before continuing the discussion, I would like to find out if Zeppelin can > support Java (not Scala) runtime. If it can, I think there is definitely > room for Ignite SQL on Zeppelin, as well as streaming and compute. > > Thoughts? > > D. >
