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 <nivano...@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.duzlev...@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 > > >
