Issue with scalar in 1.2.0

[Ognen Duzlevski <og...@gmail.com>]

Hello all,

I have a multi-actor Akka solution that uses Ignite as cache for elastic
(via CacheStore). I have noticed the following from my actors when using
scalar cache$ constructs to get an already existing cache from an Ignite
cluster:

Caused by: org.apache.ignite.IgniteIllegalStateException: Grid instance was
not properly started or was already stopped: null
at org.apache.ignite.internal.IgnitionEx.grid(IgnitionEx.java:1111)
~[ignite-core-1.2.0-incubating.jar:1.2.0-incubating]
at org.apache.ignite.internal.IgnitionEx.grid(IgnitionEx.java:1024)
~[ignite-core-1.2.0-incubating.jar:1.2.0-incubating]
at org.apache.ignite.Ignition.ignite(Ignition.java:470)
~[ignite-core-1.2.0-incubating.jar:1.2.0-incubating]
at org.apache.ignite.scalar.scalar$.cache$(scalar.scala:275)
~[ignite-scalar-1.2.0-incubating.jar:1.2.0-incubating]
at
com.shoutlet.datascience.socialnetworkpollers.FBPostAggregator.<init>(PostAggregator.scala:71)
~[classes/:na]

The grid is running at the time these errors are appearing, in fact, the
grid's logs are not registering any "bad behavior".

The error goes away if I go to the ign.cache() Java API interface directly
instead of using the scalar construct.

Thanks!
Ognen

Re: Issue with scalar in 1.2.0

[Ognen Duzlevski <og...@gmail.com>]

On Wed, Jul 8, 2015 at 11:50 AM, Nikita Ivanov <ni...@gmail.com> wrote:

> Valid point... We should either fix it and maintain it properly - or remove
> it. As of today, special Scala DSL for Ignite provides only limited value
> (essentially, just a collection of implicits). Since Scala 2.10+ Ignite can
> be used almost as is from Scala.
>

Yes it can but is the code you end up writing really in the spirit of what
Scala code should strive to look like? ;)

Re: Issue with scalar in 1.2.0

[Nikita Ivanov <ni...@gmail.com>]

Valid point... We should either fix it and maintain it properly - or remove
it. As of today, special Scala DSL for Ignite provides only limited value
(essentially, just a collection of implicits). Since Scala 2.10+ Ignite can
be used almost as is from Scala.

--
Nikita Ivanov


On Wed, Jul 8, 2015 at 9:43 AM, Dmitriy Setrakyan <ds...@apache.org>
wrote:

> From my side I am a little worried that once we remove scalar, we will
> start getting complaints.
>
> On Wed, Jul 8, 2015 at 9:25 AM, Alexey Kuznetsov <ak...@gridgain.com>
> wrote:
>
> > Yakov, do I correctly understand that issue should be about of removing
> > scalar from Ignite?
> >
> > On Wed, Jul 8, 2015 at 10:34 PM, Yakov Zhdanov <yz...@apache.org>
> > wrote:
> >
> > > Agree with Nikita. Alex Kuznetsov, can you please clarify the scope
> (and
> > > file a ticket)?
> > >
> > > --Yakov
> > >
> > > 2015-07-07 11:01 GMT+03:00 Nikita Ivanov <ni...@gmail.com>:
> > >
> > > > Agree 100%.
> > > >
> > > > --
> > > > Nikita Ivanov
> > > >
> > > >
> > > > On Mon, Jul 6, 2015 at 7:28 PM, Ognen Duzlevski <
> > > ognen.duzlevski@gmail.com
> > > > >
> > > > wrote:
> > > >
> > > > > Nikita, thanks :). The documentation says nothing of the sort.
> > > > >
> > > > > I think we should then aim to remove scalar?
> > > > >
> > > > > Ognen
> > > > >
> > > > > On Mon, Jul 6, 2015 at 7:22 PM, Nikita Ivanov <nivanov30@gmail.com
> >
> > > > wrote:
> > > > >
> > > > > > I would not use Scalar at this point today. Ignite APIs are
> > perfectly
> > > > > > accessible from Scala as is. Scalar's idea was to bring
> convenience
> > > to
> > > > > > Scala 2.7 level Java interop. Scala has improved dramatically
> since
> > > > then
> > > > > > and Ignite can be used as is from Scala (as well as Groovy,
> etc.).
> > > > > >
> > > > > > Thanks,
> > > > > > --
> > > > > > Nikita Ivanov (author of Scalar)
> > > > > >
> > > > > >
> > > > > > On Mon, Jul 6, 2015 at 12:31 PM, Ognen Duzlevski <
> > > > > > ognen.duzlevski@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Hello all,
> > > > > > >
> > > > > > > I have a multi-actor Akka solution that uses Ignite as cache
> for
> > > > > elastic
> > > > > > > (via CacheStore). I have noticed the following from my actors
> > when
> > > > > using
> > > > > > > scalar cache$ constructs to get an already existing cache from
> an
> > > > > Ignite
> > > > > > > cluster:
> > > > > > >
> > > > > > > Caused by: org.apache.ignite.IgniteIllegalStateException: Grid
> > > > instance
> > > > > > was
> > > > > > > not properly started or was already stopped: null
> > > > > > > at
> > org.apache.ignite.internal.IgnitionEx.grid(IgnitionEx.java:1111)
> > > > > > > ~[ignite-core-1.2.0-incubating.jar:1.2.0-incubating]
> > > > > > > at
> > org.apache.ignite.internal.IgnitionEx.grid(IgnitionEx.java:1024)
> > > > > > > ~[ignite-core-1.2.0-incubating.jar:1.2.0-incubating]
> > > > > > > at org.apache.ignite.Ignition.ignite(Ignition.java:470)
> > > > > > > ~[ignite-core-1.2.0-incubating.jar:1.2.0-incubating]
> > > > > > > at org.apache.ignite.scalar.scalar$.cache$(scalar.scala:275)
> > > > > > > ~[ignite-scalar-1.2.0-incubating.jar:1.2.0-incubating]
> > > > > > > at
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> com.shoutlet.datascience.socialnetworkpollers.FBPostAggregator.<init>(PostAggregator.scala:71)
> > > > > > > ~[classes/:na]
> > > > > > >
> > > > > > > The grid is running at the time these errors are appearing, in
> > > fact,
> > > > > the
> > > > > > > grid's logs are not registering any "bad behavior".
> > > > > > >
> > > > > > > The error goes away if I go to the ign.cache() Java API
> interface
> > > > > > directly
> > > > > > > instead of using the scalar construct.
> > > > > > >
> > > > > > > Thanks!
> > > > > > > Ognen
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> >
> >
> > --
> > Alexey Kuznetsov
> > GridGain Systems
> > www.gridgain.com
> >
>

Re: Issue with scalar in 1.2.0

[Dmitriy Setrakyan <ds...@apache.org>]

>From my side I am a little worried that once we remove scalar, we will
start getting complaints.

On Wed, Jul 8, 2015 at 9:25 AM, Alexey Kuznetsov <ak...@gridgain.com>
wrote:

> Yakov, do I correctly understand that issue should be about of removing
> scalar from Ignite?
>
> On Wed, Jul 8, 2015 at 10:34 PM, Yakov Zhdanov <yz...@apache.org>
> wrote:
>
> > Agree with Nikita. Alex Kuznetsov, can you please clarify the scope (and
> > file a ticket)?
> >
> > --Yakov
> >
> > 2015-07-07 11:01 GMT+03:00 Nikita Ivanov <ni...@gmail.com>:
> >
> > > Agree 100%.
> > >
> > > --
> > > Nikita Ivanov
> > >
> > >
> > > On Mon, Jul 6, 2015 at 7:28 PM, Ognen Duzlevski <
> > ognen.duzlevski@gmail.com
> > > >
> > > wrote:
> > >
> > > > Nikita, thanks :). The documentation says nothing of the sort.
> > > >
> > > > I think we should then aim to remove scalar?
> > > >
> > > > Ognen
> > > >
> > > > On Mon, Jul 6, 2015 at 7:22 PM, Nikita Ivanov <ni...@gmail.com>
> > > wrote:
> > > >
> > > > > I would not use Scalar at this point today. Ignite APIs are
> perfectly
> > > > > accessible from Scala as is. Scalar's idea was to bring convenience
> > to
> > > > > Scala 2.7 level Java interop. Scala has improved dramatically since
> > > then
> > > > > and Ignite can be used as is from Scala (as well as Groovy, etc.).
> > > > >
> > > > > Thanks,
> > > > > --
> > > > > Nikita Ivanov (author of Scalar)
> > > > >
> > > > >
> > > > > On Mon, Jul 6, 2015 at 12:31 PM, Ognen Duzlevski <
> > > > > ognen.duzlevski@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Hello all,
> > > > > >
> > > > > > I have a multi-actor Akka solution that uses Ignite as cache for
> > > > elastic
> > > > > > (via CacheStore). I have noticed the following from my actors
> when
> > > > using
> > > > > > scalar cache$ constructs to get an already existing cache from an
> > > > Ignite
> > > > > > cluster:
> > > > > >
> > > > > > Caused by: org.apache.ignite.IgniteIllegalStateException: Grid
> > > instance
> > > > > was
> > > > > > not properly started or was already stopped: null
> > > > > > at
> org.apache.ignite.internal.IgnitionEx.grid(IgnitionEx.java:1111)
> > > > > > ~[ignite-core-1.2.0-incubating.jar:1.2.0-incubating]
> > > > > > at
> org.apache.ignite.internal.IgnitionEx.grid(IgnitionEx.java:1024)
> > > > > > ~[ignite-core-1.2.0-incubating.jar:1.2.0-incubating]
> > > > > > at org.apache.ignite.Ignition.ignite(Ignition.java:470)
> > > > > > ~[ignite-core-1.2.0-incubating.jar:1.2.0-incubating]
> > > > > > at org.apache.ignite.scalar.scalar$.cache$(scalar.scala:275)
> > > > > > ~[ignite-scalar-1.2.0-incubating.jar:1.2.0-incubating]
> > > > > > at
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> com.shoutlet.datascience.socialnetworkpollers.FBPostAggregator.<init>(PostAggregator.scala:71)
> > > > > > ~[classes/:na]
> > > > > >
> > > > > > The grid is running at the time these errors are appearing, in
> > fact,
> > > > the
> > > > > > grid's logs are not registering any "bad behavior".
> > > > > >
> > > > > > The error goes away if I go to the ign.cache() Java API interface
> > > > > directly
> > > > > > instead of using the scalar construct.
> > > > > >
> > > > > > Thanks!
> > > > > > Ognen
> > > > > >
> > > > >
> > > >
> > >
> >
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>

Re: Issue with scalar in 1.2.0

[Alexey Kuznetsov <ak...@gridgain.com>]

Yakov, do I correctly understand that issue should be about of removing
scalar from Ignite?

On Wed, Jul 8, 2015 at 10:34 PM, Yakov Zhdanov <yz...@apache.org> wrote:

> Agree with Nikita. Alex Kuznetsov, can you please clarify the scope (and
> file a ticket)?
>
> --Yakov
>
> 2015-07-07 11:01 GMT+03:00 Nikita Ivanov <ni...@gmail.com>:
>
> > Agree 100%.
> >
> > --
> > Nikita Ivanov
> >
> >
> > On Mon, Jul 6, 2015 at 7:28 PM, Ognen Duzlevski <
> ognen.duzlevski@gmail.com
> > >
> > wrote:
> >
> > > Nikita, thanks :). The documentation says nothing of the sort.
> > >
> > > I think we should then aim to remove scalar?
> > >
> > > Ognen
> > >
> > > On Mon, Jul 6, 2015 at 7:22 PM, Nikita Ivanov <ni...@gmail.com>
> > wrote:
> > >
> > > > I would not use Scalar at this point today. Ignite APIs are perfectly
> > > > accessible from Scala as is. Scalar's idea was to bring convenience
> to
> > > > Scala 2.7 level Java interop. Scala has improved dramatically since
> > then
> > > > and Ignite can be used as is from Scala (as well as Groovy, etc.).
> > > >
> > > > Thanks,
> > > > --
> > > > Nikita Ivanov (author of Scalar)
> > > >
> > > >
> > > > On Mon, Jul 6, 2015 at 12:31 PM, Ognen Duzlevski <
> > > > ognen.duzlevski@gmail.com>
> > > > wrote:
> > > >
> > > > > Hello all,
> > > > >
> > > > > I have a multi-actor Akka solution that uses Ignite as cache for
> > > elastic
> > > > > (via CacheStore). I have noticed the following from my actors when
> > > using
> > > > > scalar cache$ constructs to get an already existing cache from an
> > > Ignite
> > > > > cluster:
> > > > >
> > > > > Caused by: org.apache.ignite.IgniteIllegalStateException: Grid
> > instance
> > > > was
> > > > > not properly started or was already stopped: null
> > > > > at org.apache.ignite.internal.IgnitionEx.grid(IgnitionEx.java:1111)
> > > > > ~[ignite-core-1.2.0-incubating.jar:1.2.0-incubating]
> > > > > at org.apache.ignite.internal.IgnitionEx.grid(IgnitionEx.java:1024)
> > > > > ~[ignite-core-1.2.0-incubating.jar:1.2.0-incubating]
> > > > > at org.apache.ignite.Ignition.ignite(Ignition.java:470)
> > > > > ~[ignite-core-1.2.0-incubating.jar:1.2.0-incubating]
> > > > > at org.apache.ignite.scalar.scalar$.cache$(scalar.scala:275)
> > > > > ~[ignite-scalar-1.2.0-incubating.jar:1.2.0-incubating]
> > > > > at
> > > > >
> > > > >
> > > >
> > >
> >
> com.shoutlet.datascience.socialnetworkpollers.FBPostAggregator.<init>(PostAggregator.scala:71)
> > > > > ~[classes/:na]
> > > > >
> > > > > The grid is running at the time these errors are appearing, in
> fact,
> > > the
> > > > > grid's logs are not registering any "bad behavior".
> > > > >
> > > > > The error goes away if I go to the ign.cache() Java API interface
> > > > directly
> > > > > instead of using the scalar construct.
> > > > >
> > > > > Thanks!
> > > > > Ognen
> > > > >
> > > >
> > >
> >
>



-- 
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

Re: Issue with scalar in 1.2.0

[Yakov Zhdanov <yz...@apache.org>]

Agree with Nikita. Alex Kuznetsov, can you please clarify the scope (and
file a ticket)?

--Yakov

2015-07-07 11:01 GMT+03:00 Nikita Ivanov <ni...@gmail.com>:

> Agree 100%.
>
> --
> Nikita Ivanov
>
>
> On Mon, Jul 6, 2015 at 7:28 PM, Ognen Duzlevski <ognen.duzlevski@gmail.com
> >
> wrote:
>
> > Nikita, thanks :). The documentation says nothing of the sort.
> >
> > I think we should then aim to remove scalar?
> >
> > Ognen
> >
> > On Mon, Jul 6, 2015 at 7:22 PM, Nikita Ivanov <ni...@gmail.com>
> wrote:
> >
> > > I would not use Scalar at this point today. Ignite APIs are perfectly
> > > accessible from Scala as is. Scalar's idea was to bring convenience to
> > > Scala 2.7 level Java interop. Scala has improved dramatically since
> then
> > > and Ignite can be used as is from Scala (as well as Groovy, etc.).
> > >
> > > Thanks,
> > > --
> > > Nikita Ivanov (author of Scalar)
> > >
> > >
> > > On Mon, Jul 6, 2015 at 12:31 PM, Ognen Duzlevski <
> > > ognen.duzlevski@gmail.com>
> > > wrote:
> > >
> > > > Hello all,
> > > >
> > > > I have a multi-actor Akka solution that uses Ignite as cache for
> > elastic
> > > > (via CacheStore). I have noticed the following from my actors when
> > using
> > > > scalar cache$ constructs to get an already existing cache from an
> > Ignite
> > > > cluster:
> > > >
> > > > Caused by: org.apache.ignite.IgniteIllegalStateException: Grid
> instance
> > > was
> > > > not properly started or was already stopped: null
> > > > at org.apache.ignite.internal.IgnitionEx.grid(IgnitionEx.java:1111)
> > > > ~[ignite-core-1.2.0-incubating.jar:1.2.0-incubating]
> > > > at org.apache.ignite.internal.IgnitionEx.grid(IgnitionEx.java:1024)
> > > > ~[ignite-core-1.2.0-incubating.jar:1.2.0-incubating]
> > > > at org.apache.ignite.Ignition.ignite(Ignition.java:470)
> > > > ~[ignite-core-1.2.0-incubating.jar:1.2.0-incubating]
> > > > at org.apache.ignite.scalar.scalar$.cache$(scalar.scala:275)
> > > > ~[ignite-scalar-1.2.0-incubating.jar:1.2.0-incubating]
> > > > at
> > > >
> > > >
> > >
> >
> com.shoutlet.datascience.socialnetworkpollers.FBPostAggregator.<init>(PostAggregator.scala:71)
> > > > ~[classes/:na]
> > > >
> > > > The grid is running at the time these errors are appearing, in fact,
> > the
> > > > grid's logs are not registering any "bad behavior".
> > > >
> > > > The error goes away if I go to the ign.cache() Java API interface
> > > directly
> > > > instead of using the scalar construct.
> > > >
> > > > Thanks!
> > > > Ognen
> > > >
> > >
> >
>

Re: Issue with scalar in 1.2.0

[Nikita Ivanov <ni...@gmail.com>]

Agree 100%.

--
Nikita Ivanov


On Mon, Jul 6, 2015 at 7:28 PM, Ognen Duzlevski <og...@gmail.com>
wrote:

> Nikita, thanks :). The documentation says nothing of the sort.
>
> I think we should then aim to remove scalar?
>
> Ognen
>
> On Mon, Jul 6, 2015 at 7:22 PM, Nikita Ivanov <ni...@gmail.com> wrote:
>
> > I would not use Scalar at this point today. Ignite APIs are perfectly
> > accessible from Scala as is. Scalar's idea was to bring convenience to
> > Scala 2.7 level Java interop. Scala has improved dramatically since then
> > and Ignite can be used as is from Scala (as well as Groovy, etc.).
> >
> > Thanks,
> > --
> > Nikita Ivanov (author of Scalar)
> >
> >
> > On Mon, Jul 6, 2015 at 12:31 PM, Ognen Duzlevski <
> > ognen.duzlevski@gmail.com>
> > wrote:
> >
> > > Hello all,
> > >
> > > I have a multi-actor Akka solution that uses Ignite as cache for
> elastic
> > > (via CacheStore). I have noticed the following from my actors when
> using
> > > scalar cache$ constructs to get an already existing cache from an
> Ignite
> > > cluster:
> > >
> > > Caused by: org.apache.ignite.IgniteIllegalStateException: Grid instance
> > was
> > > not properly started or was already stopped: null
> > > at org.apache.ignite.internal.IgnitionEx.grid(IgnitionEx.java:1111)
> > > ~[ignite-core-1.2.0-incubating.jar:1.2.0-incubating]
> > > at org.apache.ignite.internal.IgnitionEx.grid(IgnitionEx.java:1024)
> > > ~[ignite-core-1.2.0-incubating.jar:1.2.0-incubating]
> > > at org.apache.ignite.Ignition.ignite(Ignition.java:470)
> > > ~[ignite-core-1.2.0-incubating.jar:1.2.0-incubating]
> > > at org.apache.ignite.scalar.scalar$.cache$(scalar.scala:275)
> > > ~[ignite-scalar-1.2.0-incubating.jar:1.2.0-incubating]
> > > at
> > >
> > >
> >
> com.shoutlet.datascience.socialnetworkpollers.FBPostAggregator.<init>(PostAggregator.scala:71)
> > > ~[classes/:na]
> > >
> > > The grid is running at the time these errors are appearing, in fact,
> the
> > > grid's logs are not registering any "bad behavior".
> > >
> > > The error goes away if I go to the ign.cache() Java API interface
> > directly
> > > instead of using the scalar construct.
> > >
> > > Thanks!
> > > Ognen
> > >
> >
>

Re: Issue with scalar in 1.2.0

[Ognen Duzlevski <og...@gmail.com>]

Nikita, thanks :). The documentation says nothing of the sort.

I think we should then aim to remove scalar?

Ognen

On Mon, Jul 6, 2015 at 7:22 PM, Nikita Ivanov <ni...@gmail.com> wrote:

> I would not use Scalar at this point today. Ignite APIs are perfectly
> accessible from Scala as is. Scalar's idea was to bring convenience to
> Scala 2.7 level Java interop. Scala has improved dramatically since then
> and Ignite can be used as is from Scala (as well as Groovy, etc.).
>
> Thanks,
> --
> Nikita Ivanov (author of Scalar)
>
>
> On Mon, Jul 6, 2015 at 12:31 PM, Ognen Duzlevski <
> ognen.duzlevski@gmail.com>
> wrote:
>
> > Hello all,
> >
> > I have a multi-actor Akka solution that uses Ignite as cache for elastic
> > (via CacheStore). I have noticed the following from my actors when using
> > scalar cache$ constructs to get an already existing cache from an Ignite
> > cluster:
> >
> > Caused by: org.apache.ignite.IgniteIllegalStateException: Grid instance
> was
> > not properly started or was already stopped: null
> > at org.apache.ignite.internal.IgnitionEx.grid(IgnitionEx.java:1111)
> > ~[ignite-core-1.2.0-incubating.jar:1.2.0-incubating]
> > at org.apache.ignite.internal.IgnitionEx.grid(IgnitionEx.java:1024)
> > ~[ignite-core-1.2.0-incubating.jar:1.2.0-incubating]
> > at org.apache.ignite.Ignition.ignite(Ignition.java:470)
> > ~[ignite-core-1.2.0-incubating.jar:1.2.0-incubating]
> > at org.apache.ignite.scalar.scalar$.cache$(scalar.scala:275)
> > ~[ignite-scalar-1.2.0-incubating.jar:1.2.0-incubating]
> > at
> >
> >
> com.shoutlet.datascience.socialnetworkpollers.FBPostAggregator.<init>(PostAggregator.scala:71)
> > ~[classes/:na]
> >
> > The grid is running at the time these errors are appearing, in fact, the
> > grid's logs are not registering any "bad behavior".
> >
> > The error goes away if I go to the ign.cache() Java API interface
> directly
> > instead of using the scalar construct.
> >
> > Thanks!
> > Ognen
> >
>

Re: Issue with scalar in 1.2.0

[Nikita Ivanov <ni...@gmail.com>]

I would not use Scalar at this point today. Ignite APIs are perfectly
accessible from Scala as is. Scalar's idea was to bring convenience to
Scala 2.7 level Java interop. Scala has improved dramatically since then
and Ignite can be used as is from Scala (as well as Groovy, etc.).

Thanks,
--
Nikita Ivanov (author of Scalar)


On Mon, Jul 6, 2015 at 12:31 PM, Ognen Duzlevski <og...@gmail.com>
wrote:

> Hello all,
>
> I have a multi-actor Akka solution that uses Ignite as cache for elastic
> (via CacheStore). I have noticed the following from my actors when using
> scalar cache$ constructs to get an already existing cache from an Ignite
> cluster:
>
> Caused by: org.apache.ignite.IgniteIllegalStateException: Grid instance was
> not properly started or was already stopped: null
> at org.apache.ignite.internal.IgnitionEx.grid(IgnitionEx.java:1111)
> ~[ignite-core-1.2.0-incubating.jar:1.2.0-incubating]
> at org.apache.ignite.internal.IgnitionEx.grid(IgnitionEx.java:1024)
> ~[ignite-core-1.2.0-incubating.jar:1.2.0-incubating]
> at org.apache.ignite.Ignition.ignite(Ignition.java:470)
> ~[ignite-core-1.2.0-incubating.jar:1.2.0-incubating]
> at org.apache.ignite.scalar.scalar$.cache$(scalar.scala:275)
> ~[ignite-scalar-1.2.0-incubating.jar:1.2.0-incubating]
> at
>
> com.shoutlet.datascience.socialnetworkpollers.FBPostAggregator.<init>(PostAggregator.scala:71)
> ~[classes/:na]
>
> The grid is running at the time these errors are appearing, in fact, the
> grid's logs are not registering any "bad behavior".
>
> The error goes away if I go to the ign.cache() Java API interface directly
> instead of using the scalar construct.
>
> Thanks!
> Ognen
>