Re: Using event to reconnect spring created cache client to server

Is there a recommended pattern for reconnecting continuous queries after a disconnect event? Thanks ! Cheers, Guilherme Melo www.gmelo.org On 16 November 2017 at 20:25, ezhuravlev <e.zhuravlev...@gmail.com> wrote: > It's not recommended to access caches from listeners. It's

Re: Using event to reconnect spring created cache client to server

That worked, is it a reentry issue? Should be flagged as a bug? Because reconnecting a continuous query from a disconnect event should be standard right? On 14 Nov 2017 6:35 p.m., "ezhuravlev" wrote: > Try to start a new thread and access cache from it. > > Evgenii > >

Re: Using event to reconnect spring created cache client to server

That's the problem, after the call to cache ("my-cache") it just holds, which is quite odd, because the call to get all cache names works normally, but attempting to get the instance fails. I can see from the topology that it connects to the correct cluster. Thanks On 9 Nov 2017 11:55 p.m.,

Using event to reconnect spring created cache client to server

Hello all, am having a issue with reconnection to a spring created ignite cluster, both instances are wrapped in spring boot 1.5.8.RELEASE and Ignite 1.9 Server: @Autowired ApplicationContext context; @Bean public Ignite igniteClient() throws IgniteCheckedException { IgniteConfiguration

Re: Transformer not called on every ScanQuery

mpleOnlyValueTransformer()).getAll(); try { returned.forEach(i -> doNothing(i)); } catch (Exception e) { System.out.println(e); } cache.clear(); cache.destroy(); Ignition.stop(true); } public static void doNothing(Integer i) { } Cheers, Guilherme Melo

Transformer not called on every ScanQuery

Hello, Has anyone had issues with Transformers not being called on every instance of the scanQuery? only about 10% of the objects get transformed, the rest are added to the list returned from cache.query() are IgniteBiTuple, not what was passed to the Transformer. this does not happen when running

Re: Group By on Scan query

p phase. On Thu, Jul 13, 2017 at 4:21 PM, Guilherme Melo <guilhe...@gmelo.org> wrote: > Hello, > I have been reading, and I have not figured out if it is possible to > perforn agregation on a scan query, I am aware I can use the stream api to > do a few things once I've gotte

Group By on Scan query

, Guilherme Melo www.gmelo.org

Re: Passing parameters to IgniteBiPredicate

Hello Taras, thanks, this example is showing a normal query with a fixed value, this is working, the problem is passing a parameter to the predicate. Cheers, Guilherme Melo www.gmelo.org On 6 July 2017 at 22:18, Taras Ledkov <tled...@gridgain.com> wrote: > Hi, > > Sure, ple

Passing parameters to IgniteBiPredicate

Hello, I am having problems submitting a query to the service from a client. Using the example from the documentation: IgniteCache cache = ignite.cache("mycache"); int sal = 100// Find only persons earning more than 1,000.try (QueryCursor cursor = cache.query(new ScanQuery((k, p) ->

Re: How to do write-behind caching?

Hello Ricky, I've had a similar issue, is write through enabled as well? On 27 Apr 2017 11:14 a.m., "Ricky Nauvaldy Ruliputra" < ricky.nauva...@sci.ui.ac.id> wrote: > sorry, I pasted the wrong configuration file, I was checking on whether the > program can write through the database if

Re: Unable to inject spring configuration on Cachestore

Thats great, Thank you very much Andrey. Cheers, Guilherme Melo www.gmelo.org On 25 April 2017 at 01:04, Andrey Gura <ag...@apache.org> wrote: > Hi Guilherme, > > Ignite creates Spring application context only if started using > Ignition.start(springUrlCfg) method and can

Unable to inject spring configuration on Cachestore

public void writeAll(Collection<Cache.Entry> entries) throws CacheWriterException { } @Override public void delete(Object key) throws CacheWriterException { } @Override public void deleteAll(Collection keys) throws CacheWriterException { } } Cheers, Guilherme Melo www.gmelo.org

Re: LocalDateTime field being ignored on Cassandra write through

Thank you Dimitry, I will take a look Cheers, Guilherme Melo www.gmelo.org On 18 April 2017 at 22:08, dkarachentsev <dkarachent...@gridgain.com> wrote: > Guilherme, > > You may track feature development here [1] or contribute it by yourself. > > [1] https://issues.apache.o

Re: LocalDateTime field being ignored on Cassandra write through

Hello Dimitry, Thanks, it looks like if I add all the fields on the persist.xml (even though in the documentation it says that it is not required, for Pojo)the date is stored as a blob. I've added annotations to the class to use a custom codec, however it is ignored. Is this a bug or are Cassandra

Re: LocalDateTime field being ignored on Cassandra write through

I've also tried: @Field(codec = LocalDateTimeCodec.class) private LocalDateTime timestampVal; But to no avail. Thanks Dmitry Guilherme Melo www.gmelo.org

LocalDateTime field being ignored on Cassandra write through

is null. There are no error messages on either side, and when I pull the object from the cache the value is there, therefore the problem is with the cache store. Has anyone dealt with anything similar, I am using the latest version of ignite and the cassandra client. Thank you, Guilherme Melo