回复: Ignite - SQL Column names Case not preserved.

2019-12-27 Thread 张耀文
CacheConfiguration cfg = new CacheConfiguration<>().setSqlEscapeAll(true) This will make sql case sensitive 发送自 Windows 10 版邮件应用 发件人: sr.prane...@gmail.com 发送时间: 2019年12月28日 14:20 收件人: user@ignite.apache.org 主题: Ignite - SQL Column names Case not preserved. Hi Ignite users I have a simple table

Ignite - SQL Column names Case not preserved.

2019-12-27 Thread sr.prane...@gmail.com
Hi Ignite users I have a simple table created in ignite as below. CREATE TABLE acc ( "accId" VARCHAR PRIMARY KEY, "accCol1" VARCHAR, "accCol2" INT, "accCol3" VARCHAR, "accCol4" BOOLEAN ); On the above table from sqlLine client a simple query like below is also failing without recognisin

Found dead lock threads.

2019-12-27 Thread yangjiajun
Hello,ignite community. I use muiti thred to write data to ignite's same table.The table is in memory.I open streaming mode by using 'SET STREAMING ON ORDERED;' before my write,and use 'SET STREAMING OFF;' to flush data.I found that these threads may all wait on condition and never ends. Here is

Re: Issue with replicated cache

2019-12-27 Thread Evgenii Zhuravlev
Hi Prasad, Can you please share logs from all nodes, so I can check what was happening with a cluster before an incident? It would be great to see logs since nodes start. Thanks, Evgenii чт, 26 дек. 2019 г. в 11:42, Denis Magda : > Let me loop in the Ignite dev list as long as I've not heard ab

Re: Embedded ignite and baseline upgrade questions

2019-12-27 Thread djm132
Also when starting second node I am getting this: 2019/12/27 23:39:36.665 [disco-pool-#55] WARN BaselineTopology of joining node (dev-1) is not compatible with BaselineTopology in the cluster. Branching history of cluster BlT ([95475834]) doesn't contain branching point hash of joining node BlT (9

Re: Good metrics to assess affinity quality

2019-12-27 Thread steve.hostettler
Hello, my objective is to come up with a good affinity to optimise data distribution.To reduce local misses by improving co-location. My data structure is however legacy and quite complex and I do not have a clear candidate. Therefore, I would like to test several affinities and to measure what wo

Embedded ignite and baseline upgrade questions

2019-12-27 Thread dobermann132
Hi, I am implementing distributed crawler engine using ignite in embedded mode. Each crawler node have persistence enabled and assigned predefined consistentId (dev-1, dev-2, dev-3, etc). Baseline topology (nodes which store data) can change and configured using config file like this: # Clu

Re: Failed to reinitialize local partitions (rebalancing will be stopped)

2019-12-27 Thread akurbanov
Hello, Is it possible to provide full log? Best regards, Anton -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Cache behind SpringCache annotation taking too much time in get operaton

2019-12-27 Thread tarunk
Can you please see the attached pic now. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Failed to reinitialize local partitions (rebalancing will be stopped)

2019-12-27 Thread ashishb888
I have three server node. Two of them with data-node attribute and remaining one with worker-node attribute. Persistence is enabled on data-nodes. When I try to activate the cluster I get bellow exception on worker node: 2019-12-27 18:22:58.181 ERROR 178084 --- [nge-worker-#103] .c.d.d.p.GridDhtPa

Re: Caused by: org.apache.ignite.IgniteCheckedException: Requested DataRegion is not configured: Data_Region

2019-12-27 Thread ashishb888
As of now will go with workaround. Thank you Ilya! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Caused by: org.apache.ignite.IgniteCheckedException: Requested DataRegion is not configured: Data_Region

2019-12-27 Thread Ilya Kasnacheev
Hello! Then you can make a token (very small) data regions with same names on client node as a workaround. I hope that it would work. Or just wait for 2.8 :) Regards, -- Ilya Kasnacheev пт, 27 дек. 2019 г. в 11:04, ashishb888 : > Removing dataStorageConfiguration entirely from client node wo

Re: Caused by: org.apache.ignite.IgniteCheckedException: Requested DataRegion is not configured: Data_Region

2019-12-27 Thread ashishb888
Removing dataStorageConfiguration entirely from client node worked. If we needed to keep dataStorageConfiguration on client node for some reason, then? BR, Ashish -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/