RE: Binary type has different fields error

Hi Pavel, Snap! I just created https://issues.apache.org/jira/browse/IGNITE-8590 Feel free to delete it. Thanks, Raymond *From:* Pavel Tupitsyn [mailto:ptupit...@apache.org] *Sent:* Thursday, May 24, 2018 7:13 AM *To:* user@ignite.apache.org *Subject:* Re: Binary type has different

Re: C# client too slow to connect.

Hi Pavel, Yes, but thin client cannot perform continuous query. Maybe is there an alternative way to be notified when a cache change? On Tue, May 22, 2018 at 10:04 PM Pavel Tupitsyn wrote: > Hi, > > Have you tried Thin Client mode? >

Re: SEVERE error while starting ignite in embedded mode

Hi, File META-INF/classnames.properties located in ignite-core*.jar. Seems to classloader RuntimeClassLoader is unable to find this resource. Please check your classpath and classloader. 2018-05-22 10:33 GMT+03:00 the_palakkaran : > Hi, > > When I am trying to start

RE: SEVERE error while starting ignite in embedded mode

Sorry, I thought both were different issues. I have deleted the other topic. And yes, it was a problem with my custom class loader and when I set my class loader from my thread context to the ignite configuration and this worked fine. -- Sent from:

Re: LIKE operator in Apache ignite SQL

LIKE in Apache Ignite should work as it is described in SQL standard, where '%' means 'any characters'. Note that indexes can only be used with LIKE if wildcard is not used at first position: foo LIKE '%bar%' - no index. foo LIKE 'bar%' - can use index. Regards, -- Ilya Kasnacheev 2018-05-23

RE: IgniteCheckedException: Failed to validate cache configuration. Cachestore factory is not s erializable.

Look at the bottom exceptions in the chain: = Caused by: class org.apache.ignite.IgniteCheckedException: Failed to find class with given class loader for unmarshalling (make sure same versions of all classes are available on all nodes or enable peer-class-loading)

RE: SEVERE error while starting ignite in embedded mode

This thread seems to be a duplicate of http://apache-ignite-users.70518.x6.nabble.com/Dependencies-required-to-use-ignite-in-embedded-mode-tt21619.html. Let’s stick to the latter one. the_palakkaran, please avoid posting the same question several times. Thanks, Stan From: Pavel Vinokurov Sent:

LIKE operator in Apache ignite SQL

Hi, will like operator work in Apache ignite in the same way as in Oracle? I saw somewhere it should be uses as key=%value%. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: LIKE operator in Apache ignite SQL

@ilya So does this mean an SQL field query executed on a cache as "select custNo from Customer where custId like '%SAM%'" will work and return values ? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Binary type has different fields error

Hello Raymond! This is unusual. Do you have a minimal reproducer by chance? Care to share it on e.g. github? Regards, -- Ilya Kasnacheev 2018-05-22 4:50 GMT+03:00 Raymond Wilson : > Hi Ilya, > > > > I found the folder and removed it. The issue still persist in a

Join Query on two different caches

Hi, Suppose I have two IgniteCaches customerCache and addressCache, which contains data from Customer table and Account table respectively. Is it possible to execute a sql field JOIN query as below? select * from Customer,Address where custNo = adCustNo; (where Customer and Address are the model

Re: LIKE operator in Apache ignite SQL

Yes, it is working. Thanks, Ilya -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Binary type has different fields error

Hi Ilya, I got to the bottom of it today. It is an error on my part. The Ignite exception is correct, but wasn’t initially obvious why it was complaining. We had a pair of classes defined like this: public class A { public int bob; } public class B : A { public int bob; } This

Re: Binary type has different fields error

Hello Raymond! I'm glad that confusion have cleared itself! Still you could fill an issue to Apache Ignite JIRA , see if there's a decision to support this case eventually. The main concern here is that this pattern may arise in some code outside of user's

Re: client service fail when reconnect,all server nodes stopped then restart

Hey! There is a test, that is very similar to what you described: GridServiceProxyClientReconnectSelfTest#testClientReconnect It

Re: LIKE operator in Apache ignite SQL

Hello! I believe this is the case! Have you checked? Regards, -- Ilya Kasnacheev 2018-05-23 12:38 GMT+03:00 the_palakkaran : > @ilya So does this mean an SQL field query executed on a cache as "select > custNo from Customer where custId like '%SAM%'" will work and

Re: Join Query on two different caches

Hello! * Yes it is possible. * For the best results your data should be collocated on custNo. * Otherwise you would need distributed joins. Regards, -- Ilya Kasnacheev 2018-05-23 13:26 GMT+03:00 the_palakkaran : > Hi, > > Suppose I have two IgniteCaches customerCache

Setting DefaultDataRegion to zero size

I'm working on a project where we're using Ignite primarily as a cache for large & complex objects that we need in their entirety. Based on reading elsewhere it seems like our performance would be best if we didn't use off-heap storage at all. To that end, would it make sense (or even work) for me

Re: Setting DefaultDataRegion to zero size

Hi, You can't disable off-heap storage since version 2.0. However, you can use additional onHeap cache for the values stored in offheap using CacheConfiguration.onHeapCacheEnabled:

Re: Binary type has different fields error

Hi Raymond, Many thanks for posting the root cause! I've filed a bug to investigate this: https://issues.apache.org/jira/browse/IGNITE-8588 Pavel On Wed, May 23, 2018 at 2:37 PM, Ilya Kasnacheev wrote: > Hello Raymond! > > I'm glad that confusion have cleared

Re: Setting DefaultDataRegion to zero size

Hi, Thanks for the reply. We have enabled onHeap cache, and I know there's no way to explicitly disable off heap storage. But if I set the default DataRegion to zero size will that /effectively/ disable off-heap storage for all of our data? And would doing that cause anything else to fail?