Ignite interpreter for Zeppelin

[Konstantin Boudnik-2]

Guys,

we are working to have Zeppelin as a part of upcoming Bigtop 1.1 stack. Does
anyone here has/can share with us the interpreter.json content for Ignite, so
we don't need to re-invent the wheel?

Thanks in advance!
--
Take care,
        Cos
2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622
Cos' pubkey: http://people.apache.org/~cos/cos.asc

         ---- Wisdom of the hour ----

You will have domestic happiness and faithful friends.

[Andrey Gura]

Cos,

Zeppelin daemon automtically creates interpreter.json file during start
(see conf directory). Ignite related content looks like this:

    "2B44YVSN1": {
      "id": "2B44YVSN1",
      "name": "ignite",
      "group": "ignite",
      "properties": {
        "ignite.peerClassLoadingEnabled": "true",
        "ignite.config.url": "",
        "ignite.jdbc.url": "jdbc:ignite:cfg://default-ignite-jdbc.xml",
        "ignite.clientMode": "true",
        "ignite.addresses": "127.0.0.1:47500..47509"
      },
      "interpreterGroup": [
        {
          "class": "org.apache.zeppelin.ignite.IgniteInterpreter",
          "name": "ignite"
        },
        {
          "class": "org.apache.zeppelin.ignite.IgniteSqlInterpreter",
          "name": "ignitesql"
        }
      ],
      "option": {
        "remote": true
      }
    }


On Wed, Nov 11, 2015 at 12:19 AM, Konstantin Boudnik <[hidden email]> wrote:

> Guys,
>
> we are working to have Zeppelin as a part of upcoming Bigtop 1.1 stack.
> Does
> anyone here has/can share with us the interpreter.json content for Ignite,
> so
> we don't need to re-invent the wheel?
>
> Thanks in advance!
> --
> Take care,
>         Cos
> 2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622
> Cos' pubkey: http://people.apache.org/~cos/cos.asc
>
>          ---- Wisdom of the hour ----
>
> You will have domestic happiness and faithful friends.
>

--
Andrey Gura
GridGain Systems, Inc.
www.gridgain.com

[Konstantin Boudnik-2]

Hi Andrey.

Our situation is a little bit different as we are setting up and tightly
control the configurations during the cluster's deployment phase. Basically,
we provide a template for the interpreters file. Appreciate the example!

Cos

On Wed, Nov 11, 2015 at 01:32PM, Andrey Gura wrote:

> Cos,
>
> Zeppelin daemon automtically creates interpreter.json file during start
> (see conf directory). Ignite related content looks like this:
>
>     "2B44YVSN1": {
>       "id": "2B44YVSN1",
>       "name": "ignite",
>       "group": "ignite",
>       "properties": {
>         "ignite.peerClassLoadingEnabled": "true",
>         "ignite.config.url": "",
>         "ignite.jdbc.url": "jdbc:ignite:cfg://default-ignite-jdbc.xml",
>         "ignite.clientMode": "true",
>         "ignite.addresses": "127.0.0.1:47500..47509"
>       },
>       "interpreterGroup": [
>         {
>           "class": "org.apache.zeppelin.ignite.IgniteInterpreter",
>           "name": "ignite"
>         },
>         {
>           "class": "org.apache.zeppelin.ignite.IgniteSqlInterpreter",
>           "name": "ignitesql"
>         }
>       ],
>       "option": {
>         "remote": true
>       }
>     }
>
>
> On Wed, Nov 11, 2015 at 12:19 AM, Konstantin Boudnik <[hidden email]> wrote:
>
> > Guys,
> >
> > we are working to have Zeppelin as a part of upcoming Bigtop 1.1 stack.
> > Does
> > anyone here has/can share with us the interpreter.json content for Ignite,
> > so
> > we don't need to re-invent the wheel?
> >
> > Thanks in advance!
> > --
> > Take care,
> >         Cos
> > 2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622
> > Cos' pubkey: http://people.apache.org/~cos/cos.asc
> >
> >          ---- Wisdom of the hour ----
> >
> > You will have domestic happiness and faithful friends.
> >
>
>
>
> --
> Andrey Gura
> GridGain Systems, Inc.
> www.gridgain.com