Re: Hibernate loadcache error?

2016-03-28 Thread vkulichenko
Ravi, I have no idea about specifics of your project. The example that is included in Ignite is a part of working project and it does work properly. I will not be able to provide anything above that without knowing how your application works. Do you have a project that you can show and that we can

Re: Hibernate loadcache error?

2016-03-28 Thread Ravi Puri
Already tried everything.I didnt think u understnd it. Do me a favour can u provide the working prjct related to hibernate integrated with ignite at ravikumarpur...@gmail.com . NOTE: PLEASE DO NOT SEND THE below LINK . PROVIDE ME THE WORKING THING as it does not work with dynamic web project as j

Re: Ignite terminology

2016-03-28 Thread vkulichenko
Alexander, Every time you call Ignition.start(..), a new node is started and a new instance of Ignite is created. If you start several instances in the same JVM, they are required to have unique names, which you then can use to acquire concrete instance using Ignition.ignite(..) method. (Note that

Ignite Cache and Compute Performance

2016-03-28 Thread abarbaro
Hello Ignite Community I'm trying to evaluate the performance of Ignite Cache and Distributed Computing. To do so, I have set up a very simple example that is a simplification of the real-life examples for which we plan to use Ignite. To my surprise, the results show that Ignite is a significant

Re: Error in cache.loadCache(null,ENTRY_COUNT);

2016-03-28 Thread vkulichenko
This seems to be a duplicate of this thread: http://apache-ignite-users.70518.x6.nabble.com/Hibernate-loadcache-error-td3534.html Let's continue discussion there. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Error-in-cache-loadCache-null-ENTRY-COUNT-tp3

Re: Hibernate loadcache error?

2016-03-28 Thread vkulichenko
Ravi, The trace clearly shows that loadCache() method is called, so I'm not sure I understand what you just said. Please let me know if I'm wrong. According to trace, there is some kind of a classpath issue not caused by Ignite. Most likely you have two versions of Hibernate at the same time, tak

Re: Ignite Cache - High Memory Overhead caused by GridCircularBuffer$Item instances

2016-03-28 Thread abarbaro
Ok, I have done more research and I think I understand the effect of these two parameters. I think my original question is resolved. Also, I have found that this parameter has a huge performance impact as well: ... ... When eagerTtl is true (

Re: Host Arrays in C++ API

2016-03-28 Thread arthi
Hi Vladimir Please find the code attached here. Please let me know if you need any more details. Thanks! Arthi code.zip -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Host-Arrays-in-C-API-

Re: Host Arrays in C++ API

2016-03-28 Thread Vladimir Ozerov
Hi Arthi, I think first of all we should understand how much time is spent on query itself and how much time is spent on deserialization. Yoo already provided XML configuration. Could you please also provide your CPP classes, your code to query Ignite and SQL query itself? Vladimir On Mon, Mar 2

Re: Host Arrays in C++ API

2016-03-28 Thread arthi
Here is the query - String sql = "SELECT sid_per_id, sid_mah_id, sid_itm_id, sid_prm_id, sid_cha_code, sid_service, sid_itm_dist " + " FROM \"" + SHOP_ITEM_BITMAP_CACHE + "\".ShopItemBitmap as bitmap " + " JOIN \"" + PROD_HIER_CACHE

Re: Host Arrays in C++ API

2016-03-28 Thread arthi
Hi Igor, The result set has 907171 rows. I am running a 4 node cluster. The query hits three caches with rows 30024916,20196,4892601. The results are columns from SHOP_ITEM_BITMAP_CACHE. Here is the config -

Re: Host Arrays in C++ API

2016-03-28 Thread Igor Sapego
Arthi, How big your objects are? What is the size of the result set that takes 25 secs to be fetched? Best Regards, Igor On Mon, Mar 28, 2016 at 6:58 PM, arthi wrote: > Thanks Igor. > > I use SQL queries, and the result sets could grow to million rows. > we tried GetAll too, but, its also runs

Re: Host Arrays in C++ API

2016-03-28 Thread arthi
Thanks Igor. I use SQL queries, and the result sets could grow to million rows. we tried GetAll too, but, its also runs for 25 secs or more. Is there a better way to derive the results? Please advice. Thanks, Arthi -- View this message in context: http://apache-ignite-users.70518.x6.nabble.

Re: Host Arrays in C++ API

2016-03-28 Thread Igor Sapego
Hi Arthi, Ignite currently does not support host arrays currently. Which type of queries do you use? If you use SqlQuery you can use QueryCursor::GetAll() method though you cant control number of records you fetch this way and may run into trouble if your result set is too large. Best Regards,

ignite not support expression: EXISTS?

2016-03-28 Thread minisoft_rm
dear experts, I knew ignite supports ANSI 99 SQL. but seemed not support expression: EXISTS... really? Our company sw uses this keyword lots of times. My testing sql is:" select * from products as a where exists(select * from productslp as b where a.pk=b.itempk and a.pcode='100124'); " and ignite

Re: Error Starting Node from .net

2016-03-28 Thread Murthy Kakarlamudi
That resolved the error. Thanks much. On Mon, Mar 28, 2016 at 4:08 AM, Vladimir Ozerov wrote: > Hi, > > In Ignite 1.5 binary protocol for .NET doesn't support one optimization > called "compact footers" which is supported by Java. This optimization will > be added in Ignite 1.6. For now please a

Re: Ignite terminology

2016-03-28 Thread alexGalushka
Vladimir, Thank you so much for your answer, things are starting making a bit more sense now, but I still confuse about the the Ignition.ignite("Grid_Instance_Name") javadoc: "Note that Java VM can run multiple grid instances and every *grid instance (and its node)* can belong to a different grid

Re: SqlQuery Error

2016-03-28 Thread 16616...@qq.com
hi yakov, Thank you very much for you reply. Now I can execute sql query and fields query correctly. But I still can not execute sql query by rest api. For example: http://localhost:8080/ignite?cmd=qryfldexe&cacheName=TestTable1Cache&qry=select+id+from++testtable1 no data response. http://loca

Host Arrays in C++ API

2016-03-28 Thread arthi
Hi Ignite Gurus, I am currently using ignite to cache data on a cluster, and I have a C++ client that reads the data from the cache using SQL. The API allows execution of the queries in milli secs, but, there is a delay when we loop through the results (we are currently looping one by one using ge

Re: HDFS as persistent store for data grid

2016-03-28 Thread Denis Magda
I would also add that despite of the fact that Ignite doesn't provide HDFS based persistent store implementation/example out of the box, it doesn't mean that you can't use HDFS as a persistent store. Absolutely you can. What is your use case? -- Denis On 3/28/2016 11:11 AM, Vladimir Ozerov wr

Re: SqlQuery Error

2016-03-28 Thread Yakov Zhdanov
There is an issue in your query entity configuration. After I changed it (see below) sql query and fields query started to work. fields.put("id", "java.lang.String"); fields.put("attribute1", "java.lang.String"); fields.put("attribute2", "java.lang.String"); fields.put("attribute3", "java.lang.St

Error in cache.loadCache(null,ENTRY_COUNT);

2016-03-28 Thread Ravi Puri
Error at cache.loadCache(null,100_000) Caused by: class org.apache.ignite.compute.ComputeUserUndeclaredException: Failed to execute job due to unexpected runtime exception [jobId=a2275acb351-93f69876-63cd-4130-b8b6-b82956f489f1, ses=GridJobSessionImpl [ses=GridTaskSessionImpl [taskName=org.apache

Re: HDFS as persistent store for data grid

2016-03-28 Thread Vladimir Ozerov
Hi Kushai, Ignite does not have integration with HDFS in terms of cache persistent store. Instead, Ignite comes with IGFS - in-memory file system - which is able to cache data from HDFS and thus speed-up Hadoop jobs. See this document for more info: https://apacheignite-fs.readme.io/docs/in-memory

Re: Error Starting Node from .net

2016-03-28 Thread Vladimir Ozerov
Hi, In Ignite 1.5 binary protocol for .NET doesn't support one optimization called "compact footers" which is supported by Java. This optimization will be added in Ignite 1.6. For now please add the following property to configuration of our Java node:

Re: Ignite terminology

2016-03-28 Thread Vladimir Ozerov
Hi Alexander, Basically, "grid" == "Ignite cluster" and "grid instance" == "ignite node". "Grid" terms came from old GridGain days. I suggest you to operate on terms "node" and "cluster". Ignition.ignite(String) returns a node with a given name started in current JVM. If you re-start the node wit