Re: Migrating from Oracle to Apache Ignite.

Hi Denis, My cluster node still cannot distribute the data. Here is my experiment: *My Client Apps*: Client using JDBC Thin Ignite. Connection conn = DriverManager.getConnection("jdbc:ignite:thin://10.1.12.67"); And

RE: Problem enabling read-through on cache - no suitable driver

Hi Slava, Thank you so much for your reply it is most helpful! I'm a little confused by all of this because I have been connecting with DBeaver to jdbc:ignite:thin://127.0.0.1/ and I can create tables there if I use the predefined templates PARTITIONED or REPLICATED, however, when I try using

Re: Apache Ignite & unixODBC and truncating text

Well, yes, it's a bug. I hope to close it by the end of the next week, so the fix could be included in the Ignite 2.4 Best Regards, Igor On Wed, Jan 10, 2018 at 3:42 PM, bagsiur wrote: > Ok, thank you very much for your time nad reply. > > So, if I understend corectly, this is bug of Apache Ign

Re: IgniteOutOfMemoryException when using putAll instead of put

Hi, You are right, "evicts=0" is related to cache evictions for on-heap caching [1]. It should be always 0 for you. I tried your case (with the same configs as you) and page evictions work fine with cache store enabled and indexed types. It seems that you have some misconfiguration. What are yo

Re: off heap memory usage

Hi Colin, You should use TotalAllocatedPages if you have persistence disabled. There is an know issue with PhysicalMemoryPages: https://issues.apache.org/jira/browse/IGNITE-6963 Thank you, Alexey -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: failed to find sql table for type:

Hi, Do you still have this issue? Can you share your code? Ignite.NET solution has a QueryExample.cs, you can use it as a reference code. Thank you, Alexey From: kenn_thomp...@qat.com Sent: Wednesday, January 10, 2018 5:56 PM To: user@ignite.apache.org Subject: failed to find sql table for typ

Re: Use SQL to query IgniteRDD with scala at Zeppelin

Hi, Please note that REST protocol puts keys as String. So you have 3 Integer keys and 1 String key in a cache. That is the reason for your results. You can find details in topic [1] [1] http://apache-ignite-users.70518.x6.nabble.com/Rest-API-PUT-command-syntax-tc19158.html Thank you, Alexey

Re: Migrating from Oracle to Apache Ignite.

Hello! > ipFinder.setAddresses(Arrays.asList("127.0.0.1:47500..47510")); > discovery.setLocalAddress("127.0.0.1"); It seems that you don't have a cluster of 3 nodes, but rather 3 different localhost-only clusters. No wonder data doesn't get distributed. I would expect something between the lines

Re: No user-defined default MemoryPolicy found

I checked the code Actually, you can ignore this warning ("WARNING: No user-defined default MemoryPolicy found; system default of 1GB size will be used."). Apache Ignite applies your defaultMemoryPolicySize Or you can change your config to avoid such warning:

Re: Apache Ignite best practice

Hi Sergey, There could not be an exact answer to your question. It depends mostly on your use-case. 1. first of all, you should look at CPU/mem/network usage 2. and then you should check SQL debugging guide, starting from EXPLAIN for your query. Please see [1] for details. 3. you could enable dat

ignite.sh spring xml file secret.properties file not found error

Hi, I have specified secret.properties file location in the spring xml file and when it start ignite.sh, I see the below error as its not able to find the secret.properties file. - Where does ignite.sh look for this file? & how do I specify the right path for this file. $bin/ignite.sh ganesh.xml c

Exception Occuredjava.sql.BatchUpdateException: ORA-00001: unique constraint

Hi, We were doing a POC(Ignite 2.3 - oracle) to check how cache Persistence Store works using writeBehind, We are updating data as a batch rather than updating one by one record. though there are no duplication record but still getting "unique constraint" exception. We couldnt find any root caus

Re: ignite.sh spring xml file secret.properties file not found error

Ganesh, ignite.sh itself doesn't look for any properties files, it's your XML that has a reference to one. Looks like currently it's looking for a classpath resource. Make sure it's available there, or fix the path in the XML is location should be different. -Val -- Sent from: http://apache-ig

Re: IgniteOutOfMemoryException when using putAll instead of put

Alexey, The runtime class is used so I can have a common method to create any cache type and index the key and value types of the cache. To simplify things, attached is a tar file that is a small program that throws an OOM exception for me. I get the OOM when loading from the cache store on miss

ignite c++ client CacheEntryEventFilter has no effect!

Hello Everyone, I use c++ client library to connect to ignite server node as a client node（），then run continuous-query-example，I find the RangeFilter（RangeFilter : event::CacheEntryEventFilter） doesn't have any effect, because Listener （Listener : public event::CacheEntryEventListener） print all th