ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nikita Ivanov <nivano...@gmail.com>
Subject Re: Issue with scalar in 1.2.0
Date Tue, 07 Jul 2015 00:22:22 GMT
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.).

Nikita Ivanov (author of Scalar)

On Mon, Jul 6, 2015 at 12:31 PM, Ognen Duzlevski <ognen.duzlevski@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

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message