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
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
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:
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,
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
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
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
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:
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
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
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
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=TestTable1Cache=select+id+from++testtable1
no data response.
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
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
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",
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
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:
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:
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
19 matches
Mail list logo