Can JAVA API SqlQuery query a cache create by SQL DDL?

2017-11-14 Thread gunman524
Hi guys, I use JDBC client driver to create a table,like: stmt.executeUpdate("CREATE TABLE IF NOT EXISTS person ( id int,orgId LONG, name VARCHAR, salary LONG ,PRIMARY KEY (id)) WITH \"backups=1, affinityKey=id\""); Could I use SqlQuery API to query this cache? I tried this way but does not work

Re: Can JAVA API SqlQuery query a cache create by SQL DDL?

2017-11-15 Thread gunman524
vkulichenko, thanks for your advice。 It works, by setting value_type=person during DDL, then running SqlQuery sql = new SqlQuery("person","id >? and id http://apache-ignite-users.70518.x6.nabble.com/

"Duplicate field ID" Error when register a contentious query

2017-11-15 Thread gunman524
Hi guys, I met a issue that "Duplicate field ID" Error occurs when register a contentious query. Here is my case: 1. Start a jdbc client and use SQL to create table and insert record 2. Start a another client and using contentious query to monitor table and insert the income data to another My

Apache Ignite binary type invalidation

2017-11-15 Thread gunman524
I've createted the binary type with the name 'someField' and the field type is "String". Now I want to change it from string to int. But I don't want to change the name of the type, but I got an exception while cache populating: javax.cache.CacheException:class org.apache.ignite.binary.Binary0bje

Initial query resent the data when client got reconnect

2017-11-15 Thread gunman524
I tried to use contentious query to monitor a cache and set initial query, LocalListener and RemoteFilter as example did. The issue I met is when client reconnect to Ignite cluster, the initial query will query the data from cache which the client might already got before. I tried to use unchange

Failed to run map query remotely

2017-11-16 Thread gunman524
Hi, guys I meet a error when using SQL to query cache. It happens when Ignite server restart after OOEM issue. Could you help me figure out why this happens? [2017-11-16T14:59:36,937][ERROR][client-connector-#45][JdbcRequestHandler] Failed to execute SQL query [reqId=0, req=JdbcQueryExecuteRequ

Re: Initial query resent the data when client got reconnect

2017-11-16 Thread gunman524
Alexey, thanks for reply. I wondered does Ignite will set a incremental value for incoming data so can help people to do stuff like you said? You know for isolate data pushers are not easy to generate a unique incremental value. I know many distribute data store,like elastisearch,mango has those

Re: Using event to reconnect spring created cache client to server

2017-11-16 Thread gunman524
guil, could you share your solution? Many thanks -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Scan query failed if set deploymentMode to Private

2017-11-16 Thread gunman524
Hi there, I found a issue that if we set deploymentMode to Private and using ScanQuery for in InitialQuery. The inital query will failed for *Class not found* error. Meanwhile, the remoteFilter and LocalListener works fine. After change ScanQuery to SQLQuery, everything works fine. Is this a b

Failed to connect to address issue

2017-11-17 Thread gunman524
Hi there, My cluster always has the exception like below at org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1874) [ignite-core-2.3.0.jar!/:2.3.0] at org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1758)

Re: Initial query resent the data when client got reconnect

2017-11-19 Thread gunman524
Thanks, Alexey. I think it's a valuable feature and ask for an enhancement. I knew AtomicSequence but in my case I might prefer to JDBC thin client for data injecting, so might not able to use AtomicSequence -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Scan query failed if set deploymentMode to Private

2017-11-19 Thread gunman524
Thanks, Mikhail. It can be reproduce by using example code *CacheContinuousQueryExample.java* -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Apache Ignite binary type invalidation

2017-11-19 Thread gunman524
Alexey, that's cool. I'll try it out -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Failed to connect to address issue

2017-11-19 Thread gunman524
Mikhail, The log is not easy to get and I'll try to get it. The top of my cluster looks like Hosts: 2 +==+ | Int./Ext. IPs| Node ID8(@)| Node Type | O

Re: Initial query resent the data when client got reconnect

2017-11-21 Thread gunman524
Mike, double checked Mongodb way, their ObjectID only provide a unique ID, sorry for my info. But there is open source project provide the auto increment feature for mongodb. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Register Contentious query quit slow

2017-11-21 Thread gunman524
Hi there, I have write an app with contentious query feature and pack as a single jar, as depend on some 3rd party lib so it's quite big, 40M. For local cluster, the app start quit fast and can be startup within 20 secs. But after add one more cross region node, this app need around 10 mins to st

Re: Register Contentious query quit slow

2017-11-21 Thread gunman524
BTW, the deployment mode I use is PRIVATE, does it matter? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Register Contentious query quit slow

2017-11-21 Thread gunman524
1. *For Ignite cluster initialization, here is the log * [2017-11-22T08:01:56,975][INFO ][main][IgniteKernal] Non-loopback local IPs: 10.41.91.200 [2017-11-22T08:01:56,975][INFO ][main][IgniteKernal] Enabled local MACs: 286ED488CFC0 [2017-11-22T08:03:36,496][INFO ][tcp-disco-srvr-#2][TcpDiscovery

Re: Register Contentious query quit slow

2017-11-22 Thread gunman524
2 After I copied jar file to Ignite libs and start my app, the log on server side shows: [2017-11-22T08:14:17,585][INFO ][tcp-disco-msg-worker-#3][GridDeploymentLocalStore] Class locally deployed: class org.apache.ignite.configuration.CacheConfiguration$IgniteAllNodesPredicate [2017-11-22T08:14:17

Re: Initial query resent the data when client got reconnect

2017-11-22 Thread gunman524
Voted. Appreciated and looking for it. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Register Contentious query quit slow

2017-11-25 Thread gunman524
Denis, thanks for your explain. I debugged the client side and found after I run cache.query(qry), the client seems to deserialize all classes my code references to [2017-11-25T15:47:50,347][DEBUG][disco-event-worker-#36][GridCachePartitionExchangeManager] Do not start exchange for discovery eve

Re: Register Contentious query quit slow

2017-11-27 Thread gunman524
Dennis, Sorry for my misleading. The slow thing is register CQ but not connect to cluster (this might take round 1 min). Thanks for your remind and after removed intial query, the whole process become very quick and there is no more "binary metadata update messages". So if there do have initia

Re: Register Contentious query quit slow

2017-11-27 Thread gunman524
Denis, For this cross region case, I've some thought to share and please help verify whether they are already here. 1. Two DC, A ---corss region--- B 2. A have several ignite node, A1,A2,A3 and B have several ignite node, B1,B2,B3 ..., there are in a same cluster 3. In ingite, A1,A2, A3

Re: JDBC thin client load balancing and failover support

2017-11-27 Thread gunman524
That's exactly what I expected -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Register Contentious query quit slow

2017-12-04 Thread gunman524
Denis, I can understand the meta data need to be updated when the CQ has initial query(IQ) or remote filter(RF). But my understading is only the object within IQ and RF need to be updated and the stuff in Local listeners does not. In my case, the logic in IQ and RF is simple string compare

Re: Register Contentious query quit slow

2017-12-07 Thread gunman524
Denis, Thanks for your reply and the code as well I'll try what you suggested. Thanks again BR. Jin -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

“Failed to communicate with Ignite cluster" error when using JDBC Thin driver

2017-12-20 Thread gunman524
Hi guys, When I use ignite jdbc thin driver connect Ignite cluster, sometimes will meet the errors below. Do you have any idea what cause this error? many thanks! org.springframework.dao.DataAccessResourceFailureException: ### Error updating database. Cause: java.sql.SQLException: Failed to c

Re: “Failed to communicate with Ignite cluster" error when using JDBC Thin driver

2017-12-20 Thread gunman524
It could not be a version issue, the thin driver and cluster version are exactly same. It can happened on any query but can not be reproduce 100%, it only happened "some times". In Log, I found "Caused by: java.io.IOException: Failed to read incoming message (not enough data). " Firstly I gu

Re: “Failed to communicate with Ignite cluster" error when using JDBC Thin driver

2017-12-22 Thread gunman524
We are using mybatis to manage connection, is that matters? BTW, I check the code in JdbcThinTcpIo method sendRequest JdbcResponse sendRequest(JdbcRequest req) throws IOException { int cap = guessCapacity(req); BinaryWriterExImpl writer = new BinaryWriterExImpl(null, new Binary

Can writeSynchronizationMode be modified online?

2018-01-24 Thread gunman524
Hi there, A simple question, can writeSynchronizationMode be modified online? As my cache currently in 'full_sync" mode, can it be modified to 'primary_sync' online? like by restful or visor? BTW, the cache I created by DDL CREATE TABLE IF NOT EXISTS person ( id int,orgId LONG, name VARCHAR, s