Hi, I looked for the Ignite SQL Interpreter and it works. Awesome! :)
Unfortunately I was not able to run ignite (scalar version). Moon, could you please provide your test example? Some notes/comments: 1. Maybe it would be better if Ignite URL will look like JDBC URL for consistency with other inerpreters like Tajo or Hive? Or is it deliberate decision in order to provide one URL for both (%ignite and %ignitesql) interpreters? 2. "Scheduler already terminated" error occurs after configuration settings changes and interpreter restart. Is it normal behavior? Only restart of Zeppelin daemon fix this problem. 3. Interpreter doesn't retrieve any error if SQL query refers to unknown table. Thanks, Andrey. On Mon, Jun 8, 2015 at 12:40 PM, Andrey Gura <[email protected]> wrote: > Moon, thanks! > > I'll try it today and look to implementation. > > On Sun, Jun 7, 2015 at 1:46 AM, moon soo Lee <[email protected]> wrote: > >> Hi, >> >> It's okay to try jdbc based one using %ignitesql. >> >> %ignite is the one for ignite API, which embeds scala REPL. >> 'ignite' is automatically injected. if you can try this one and give any >> feedback, it'll be very much appreciated. >> >> >> Thanks, >> moon >> >> On Tue, May 26, 2015 at 3:07 AM Dmitriy Setrakyan <[email protected]> >> wrote: >> >>> Moon, >>> >>> Do you think we can try this out already, or is it still too early? >>> >>> D. >>> >>> On Sat, May 23, 2015 at 1:45 AM, Leemoonsoo <[email protected]> wrote: >>> >>> > GitHub user Leemoonsoo opened a pull request: >>> > >>> > https://github.com/apache/incubator-zeppelin/pull/78 >>> > >>> > [ZEPPELIN-63] add interpreter for Apache Ignite >>> > >>> > Currently it is very early stage of implementation. >>> > My idea is implementing 2 interpreter for ignite, >>> > >>> > * [ ] IgniteInterpreter - Let user use ignite API (scala) by >>> > embedding scala compiler. >>> > * [ ] IgniteSqlInterpreter - use JDBC driver to make sql query >>> > >>> > While IgniteSqlInterpreter can be simply implemented using JDBC >>> > driver, i'd like to work on IgniteSqlInterpreter first and than work on >>> > IgniteInterpreter. >>> > >>> > Work in progress .. >>> > >>> > You can merge this pull request into a Git repository by running: >>> > >>> > $ git pull https://github.com/Leemoonsoo/incubator-zeppelin ignite >>> > >>> > Alternatively you can review and apply these changes as the patch at: >>> > >>> > https://github.com/apache/incubator-zeppelin/pull/78.patch >>> > >>> > To close this pull request, make a commit to your master/trunk branch >>> > with (at least) the following in the commit message: >>> > >>> > This closes #78 >>> > >>> > ---- >>> > commit 10654215bdf0cf52a06887aca8a8c4cd38eeee37 >>> > Author: Lee moon soo <[email protected]> >>> > Date: 2015-05-23T08:25:30Z >>> > >>> > add interpreter for Apache Ignite >>> > >>> > ---- >>> > >>> > >>> > --- >>> > If your project is set up for it, you can reply to this email and have >>> your >>> > reply appear on GitHub as well. If your project does not have this >>> feature >>> > enabled and wishes so, or if the feature is enabled but not working, >>> please >>> > contact infrastructure at [email protected] or file a JIRA >>> ticket >>> > with INFRA. >>> > --- >>> > >>> >> > > > -- > Andrey Gura > GridGain Systems, Inc. > www.gridgain.com > -- Andrey Gura GridGain Systems, Inc. www.gridgain.com
