RE: ScanQuery with predicate always returns empty result.

2018-01-29 Thread Thomas Isaksen
Actually it didn't help to get the cache with the correct types: Ignition.setClientMode(true); Ignite ignite = Ignition.start("/config/gatekeeper-token-config.xml"); ignite.active(true); IgniteCache skipCache = ignite.cache("skipCache").withKeepBinary(); ScanQuery scan2 = new ScanQuery<>((key, v

RE: Question about data distribution

2018-01-29 Thread Stanislav Lukyanov
AFAIU you simultaneously have about 1 million entries which correspond to 5-10 groups (measurements). Is that correct? If so, that might be the reason of the distribution that you see. Even though you have a lot of entries, you only have a few affinity mapped groups. Ignite tries keep all entries

Re: setNodeFilter throwing a CacheException

2018-01-29 Thread dkarachentsev
Hi Shravya, To understand what's going on in your cluster I need full logs from all nodes. Please, share all files, if it's possible. Thanks! -Dmitry -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: One problem about Cluster Configuration(cfg)

2018-01-29 Thread Andrey Mashenkov
Hi, I've tried to run test several times with code\configs attached on my notebook and still can't reproduce. Please try to upgrade to the latest version of Ignite, if you think there is a bug in Ignite. I can't reproduce the issue neither on 1.9, nor 2.1 nor 2.3 versions. On Mon, Jan 29, 2018 a

Re: ScanQuery with predicate always returns empty result.

2018-01-29 Thread Evgenii Zhuravlev
Then you have one more mistake in your code. Here is the example, which using Scan query with predicate: https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/datagrid/CacheQueryExample.java If you want the community to help you, please share full reproduce

RE: starting Ignite server in embedded mode

2018-01-29 Thread Stanislav Lukyanov
Hi, You can start Ignite in the same JVM as your application by using Ignition.start() method. You can start multiple Ignite instances, just create different IgniteConfiguration for them with different instance names. IgniteConfiguration serverConfig = new IgniteConfiguration()

Re: cache configuration without Key

2018-01-29 Thread ilya.kasnacheev
Hello Rajesh! In Ignite, cache (and SQL table) maps not to one object but to two - key and value. Keys are unique per cache per cluster. They act as primary key in SQL and as, well, keys in cache API. So yes, you need to specify key type (or compound object) too. Regards, Ilya. -- Sent from:

Re: Ignite query performance

2018-01-29 Thread Andrey Mashenkov
Hi, 1. Please, check if index is used for field you use in order by clause. You can check this with EXPLAIN command [1]. If you see wrong index is used, then try hint [2] ignite for proper index. 2. FYI: there is limit and offset in query. For partitioned cache, Ignite will fetch 200 (limit + off

RE: Question about data distribution

2018-01-29 Thread svonn
Yes - so I've been merely observing some 'unlucky' distribution if it's solely chance-based. Since the real data will consist of thousands of measurements it should be fine as it is, thanks! Best regards svonn -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Index question.

2018-01-29 Thread Mikael
Question 1: I am using a class that have readObject/writeObject methods so I get this warning: 2018-01-24T16:15:49,248 [exchange-worker-#42] WARN : Some classes in query configuration cannot be written in binary format because they either implement Externalizable interface or have writeObjec

default location for ignite file db

2018-01-29 Thread Rajesh Kishore
Hi All. How do we determine the default location for ignite file based DB Thanks in advance -Rajesh

Re: starting Ignite server in embedded mode

2018-01-29 Thread Rajesh Kishore
Thanks it perfectly answers my query Thanks, Rajesh On Mon, Jan 29, 2018 at 3:31 PM, Stanislav Lukyanov wrote: > Hi, > > > > You can start Ignite in the same JVM as your application by using > Ignition.start() method. You can start multiple Ignite instances, > > just create different IgniteConf

RE: default location for ignite file db

2018-01-29 Thread Stanislav Lukyanov
It will be under ${IGNITE_HOME}/work/db. Please refer to https://apacheignite.readme.io/docs/distributed-persistent-store which covers this topic in details. Stan From: Rajesh Kishore Sent: 29 января 2018 г. 15:04 To: user@ignite.apache.org Subject: default location for ignite file db Hi All.

Re: default location for ignite file db

2018-01-29 Thread Rajesh Kishore
Thanks Stan, I just extracted the zip , and I am starting the ignite server in embedded mode. I dont see DB files getting created at the ${IGNITE_HOME}/work/db. More specifically how embedded mode server would get to know about the env variable r ${IGNITE_HOME} , as in my classpath of application

Re: default location for ignite file db

2018-01-29 Thread Mikael
You can set it in your XML file or Ingnite configuration from Java.         class="org.apache.ignite.configuration.DataStorageConfiguration">                     Den 2018-01-29 kl. 13:18,

Re: horizontal scaling

2018-01-29 Thread ezhuravlev
Hi, > Right now we are running 4 nodes (same physical system) Do you mean that you run 4 nodes on the same physical machine and after this, you add 2 additional nodes on the same physical machine? Evgenii -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: default location for ignite file db

2018-01-29 Thread Stanislav Lukyanov
Make sure you have persistence enabled as described at https://apacheignite.readme.io/docs/distributed-persistent-store. Also, make sure you don’t already have a custom setting for the StoragePath, WalPath or WalArchivePath. Making an environment variable visible to your process is OS-specific.

Re: No transaction is currently active || Not allowed to create transaction on shared EntityManager - use Spring transactions or EJB CMT instead

2018-01-29 Thread ezhuravlev
Hi, I think now you need to start and commit transaction manually in your code: em.getTransaction().begin(); em.getTransaction().commit(); At least I've tried it some time ago and it worked. Please check this example on github: https://github.com/ezhuravl/i

Re: ClassCastException: DataPageIO cannot be cast to BPlusIO

2018-01-29 Thread Ilya Kasnacheev
Hello! I believe the root cause is this part of log: Caused by: java.nio.channels.ClosedByInterruptException at java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:202) at sun.nio.ch.FileChannelImpl.readInternal(FileChannelImpl.java:746)

Re: horizontal scaling

2018-01-29 Thread Rajarshi Pain
Hi Evgenii, Yes for now we are running all the nodes on same physical server. Thanks, Raj On Mon, Jan 29, 2018 at 7:03 PM, ezhuravlev wrote: > Hi, > > > Right now we are running 4 nodes (same physical system) > > Do you mean that you run 4 nodes on the same physical machine and after > this,

Re: horizontal scaling

2018-01-29 Thread Evgenii Zhuravlev
Well, then it's not a horizontal scaling at all. I don't understand how do you want to achieve more throughput while all your nodes will compete for the same physical resources(CPU, network, IO). If you want horizontal scaling, you need to run all nodes on separate physical machines. Evgenii 201

Re: cache configuration without Key

2018-01-29 Thread Rajesh Kishore
Thanks Ilya it answers my question On 29 Jan 2018 3:34 p.m., "ilya.kasnacheev" wrote: > Hello Rajesh! > > In Ignite, cache (and SQL table) maps not to one object but to two - key > and > value. > > Keys are unique per cache per cluster. They act as primary key in SQL and > as, well, keys in cach

RE: default location for ignite file db

2018-01-29 Thread Rajesh Kishore
Perfect Stan On 29 Jan 2018 7:23 p.m., "Stanislav Lukyanov" wrote: > Make sure you have persistence enabled as described at > https://apacheignite.readme.io/docs/distributed-persistent-store. > > Also, make sure you don’t already have a custom setting for the > StoragePath, WalPath or WalArchive

Re: Index question.

2018-01-29 Thread Amir Akhmedov
Hi Mikael, 1. This is just a warning informing you that Ignite's object serialization will differ from yours Externalizable implementation. By default Ignite will serialize all fields in object and if you want to customize then you need implement Binarylizable interface or set custom serializer as

Re: No transaction is currently active || Not allowed to create transaction on shared EntityManager - use Spring transactions or EJB CMT instead

2018-01-29 Thread Amir Akhmedov
Also, please make sure you registered Ignite's Spring Transaction Manager. As an example for Ignite and Spring Transaction you can check https://github.com/apache/ignite/tree/master/modules/spring/src/test/java/org/apache/ignite/transactions/spring Thanks, Amir On Mon, Jan 29, 2018 at 9:38 AM, ez

Re: Index question.

2018-01-29 Thread Mikael
Thanks, the reason I need SQL is that my key is not a primitive, it's a class made of 2 int and one String and I need to query on parts of the key and not the entire key, like select all keys where one of the integers is equal to 55 for example. Mikael Den 2018-01-29 kl. 19:05, skrev Amir Ak

Re: ClassCastException: DataPageIO cannot be cast to BPlusIO

2018-01-29 Thread Arseny Kovalchuk
Thanks Ilya, I'll try mentioned argument. ​ Arseny Kovalchuk Senior Software Engineer at Synesis skype: arseny.kovalchuk mobile: +375 (29) 666-16-16 ​LinkedIn Profile ​ On 29 January 2018 at 18:58, Ilya Kasnacheev wrote: > Hello! > > I believe the

Re: Index question.

2018-01-29 Thread Amir Akhmedov
Ok, then it makes sense. You cannot pass null into setIndexedTypes(). But if you don't put any @QuerySqlField annotation in value class or declare fields/indexes through Java API then no columns/indexes will be created in SQL storage. On Mon, Jan 29, 2018 at 3:59 PM, Mikael wrote: > Thanks, the

Re: Apache Ignite & unixODBC and truncating text

2018-01-29 Thread Rick Alexander
Hey Igor or anyone who knows, Looking to see when this will be released as well. You mention 2.4 but the task says 2.5 release. Please help! My project is at a stand-still... On Mon, Jan 15, 2018 at 9:33 AM, bagsiur wrote: > ok, > > I ask becouse I wont to be sure. Fix will be included in Ign

Re: No transaction is currently active || Not allowed to create transaction on shared EntityManager - use Spring transactions or EJB CMT instead

2018-01-29 Thread rizal123
Hi Evgenii , Yes i have try that. Without Spring Transaction. private int sequenceManual(String seqName) { int seq = 0; Query query; try { em.getTransaction().begin(); query = this.em.createNativeQuery("UPDATE SEQUENCE SET SEQ_COUNT = SEQ_COUNT + " + INCREMENT + " WHERE SEQ_NAME =

Re: No transaction is currently active || Not allowed to create transaction on shared EntityManager - use Spring transactions or EJB CMT instead

2018-01-29 Thread rizal123
Hi Amir, How to registered Ignite's Spring Transaction Manager? Would you mind share your code... Thanks for your help Amir -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: No transaction is currently active || Not allowed to create transaction on shared EntityManager - use Spring transactions or EJB CMT instead

2018-01-29 Thread Amir Akhmedov
You need to register a bean as follow Please check the link a sent you earlier it has tests with all required configurations. It can serve as a good example.

Re: No transaction is currently active || Not allowed to create transaction on shared EntityManager - use Spring transactions or EJB CMT instead

2018-01-29 Thread Evgenii Zhuravlev
Unfortunately, there is more than one file and it will look unreadable here. All code can be accessed on github via the link I've provided earlier. Evgenii 2018-01-30 7:10 GMT+03:00 Amir Akhmedov : > You need to register a bean as follow > > class="org.apache.ignite.transactions.spring.SpringTr