UPDATE query with JOIN

Hi, Does ignite v2.1 support UPDATE queries with JOINS? I tried a SELECT query as follows and it worked fine - select count(*) from fulfill_order fo join table(id bigint = ?) t on fo.fulfill_order_status_code = t.id"; SqlFieldsQuery enhanceQuery = new SqlFieldsQuery(cacheQuery); ArrayList list =

Re: UPDATE query with JOIN

Hi Alexander, I will try what you have suggested. Thanks for the suggestions! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Comparing Strings in SQL statements

Hi, I am trying to fetch records from my cache based on the value of a column which is a STRING datatype. My string column has a few trailing spaces as such - "ABC". When I use the below SQL statement - SELECT * from Person where fNmae = "ABC"; I find no matches. However, when I use the bel

Re: Comparing Strings in SQL statements

I have used Informix DB before. In Informix string comparisons such as - SELECT * from Person where fName = "ABC"; return rows even if the column value has trailing spaces. The Informix engine internally trims strings before comparison. It would be great if a similar feature could be added to Ig

Cache Indexes not getting created Ignite v2.1

*Hi, I have a setup with 20 ignite cache servers (v2.1). I create my cache using a client, steps are as follows - 1. Client connects to the ignite cluster during startup. 2. During startup, client checks if my cache is already created (cache name - "Person") 3. If cache is already created, client

Re: Cache Indexes not getting created Ignite v2.1

*I get metadata using REST API -* http://localhost:8080/ignite?cmd=metadata *SQL Query -* Select * from "PersonCache".Person where name = "ABC"; As I already mentioned, I am able to retrieve records using Key, but SQL query is not able to get any data. -- Sent from: http://apache-ignite-user

Re: Cache Indexes not getting created Ignite v2.1

Hi, I have marked all my fields with @QuerySqlField annotation because I want to expose all my fields to SQL Query. I do not want to create an index on "name". I use the same setup across all my environments. In my lower environments, I am able to retrieve data using both SQL query on DBeaver and

Re: Cache Indexes not getting created Ignite v2.1

Hi, any update on this? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Ignite cache transaction timeout

Hi, We are observing cache transaction timeout in our Ignite v2.1 cluster. The setup comprises 20 ignite servers and 20 clients. Error log - spring_264202322.log:Caused by: org.apache.ignite.internal.transactions.IgniteTxTimeoutCheckedException: Cache transaction timed out: GridNearTxLocal [mappi

Failed to query ignite

*Hi, I have created a table in my ignite cluster (v2.1) using the following DDL -* CREATE TABLE test ( id LONG, name VARCHAR, PRIMARY KEY (id) ) WITH "backups=1,affinityKey=id"; *I am trying to query the table using IgniteJdbcThinDriver. The code to query is as fo

Re: Failed to query ignite

Hi Andrew, The result set was /null/ because the query failed in ignite. This is the only stack trace printed. The problem occurs only when I query on LONG column "id". When I query on VARCHAR column "name" (/eg. select * from test where name = "abc"/), I am able to get the result set. What is

Re: Failed to query ignite

Hi Andrew, I created a table with BIGINT instead of LONG data type in cache. I am still getting the same error when I try to query using java.Lang.Long DDL- CREATE TABLE test4 ( id /BIGINT/, name VARCHAR, PRIMARY KEY (id) ) WITH "backups=1,affinityKey=id"; --

Re: Failed to query ignite

I think i have found the problem here. When I query my cache on the PRIMARY KEY, the query throws exception. When I removed PRIMARY KEY from "id", query is working fine. How do I query on the PRIMARY KEY ? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Failed to query ignite

Reproducer code- ResultSet rs = null; try { Class.forName("org.apache.ignite.IgniteJdbcThinDriver"); Connection conn = DriverManager .getConnection("jdbc:ignite:thin://127.0.0.1/"); //

Re: Failed to query ignite

One more thing to add - when I remove "affinityKey" from ID, I am able to query successfully. The error occurs when I set "ID" as my affinityKey. Is it a known bug? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

JDBC Thin Client with Transactions

Hi, Is it possible to perform Transactional SQL INSERT, UPDATE, DELETE statements with IgniteJdbcThinDriver? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: JDBC Thin Client with Transactions

Found a ticket for this feature. Are there alternate ways to achieve TRANSACTIONAL sql using JDBC Thin Driver? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: JDBC Thin Client with Transactions

So the transactional guarantees apply only to cache.get() and cache.put() category of APIs? What about SqlFieldsQuery? Does it also support transactional commits/rollbacks? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Poor cross cache join SQL performance (v2.0.0)

Hi, I have 2 caches, each with POJO values that look like - public class Value1 { @QuerySqlField(index = true) private Long a; @QuerySqlField(index = true) private String b; } public class Value2 { @QuerySqlField(index = true) private

Re: Poor cross cache join SQL performance (v2.0.0)

Hi Alex, Yes Value2.class was already added to indextypes. I am only reading the value which is why copyOnRead is set to "false". -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Poor-cross-cache-join-SQL-performance-v2-0-0-tp14373p14382.html Sent from the Apach

Re: Poor cross cache join SQL performance (v2.0.0)

Hi, Apologies for the delayed response. Implementing appropriate group indexes solved the problem for me. One question - can I create a group index across caches? Or group index can be created only within one cache? Thanks! :) -- View this message in context: http://apache-ignite-users.7051

Question about QueryTextField

Hi, Instead of performing a text query on the entire cache object as mentioned here (https://apacheignite.readme.io/v2.0/docs/cache-queries#text-queries), can I perform a text query on a single attribute in my cache value object? Example - public class my_object { @QuerySqlField(index =

Re: Question about QueryTextField

I know how to use @QueryTextField (as can be seen in my example). When I perform a TextQuery it scans on all fields that I have used the annotation on. I want the TextQuery to run only on one field and not on all fields in my cache object. Is my question clear? -- View this message in context:

Re: Question about QueryTextField

When I use search as -> "A:123" it does not give me any result even though there is a cache entry with A = 123. Can somebody please help me? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Question-about-QueryTextField-tp15111p15162.html Sent from the Apache Igni

Re: Question about QueryTextField

I corrected the problem. Like you suggested, using capital "A" does not work. I have to use exact name of my attribute (which is small "a"). Thanks! -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Question-about-QueryTextField-tp15111p15164.html Sent from the Ap

Pagination with TextQuery

Hi, How to implement pagination with TextQuery? I want to fetch only the first 10 matches for my text query on the first page and the next 10 (from 11 to 20) on the second page. Thanks! -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Pagination-with-TextQuery-t

Error : Commit produced a runtime exception

Hi, My ignite cluster hung producing the following error trace. Can someone help me identify the reason for the failure and cluster hang? [09:57:38,964][INFO][grid-timeout-worker-#19%null%][IgniteKernal] FreeList [name=null, buckets=256, dataPages=1208250, reusePages=0] [09:58:38,963][INFO][grid-

Re: Error : Commit produced a runtime exception

Ignite logs show the following heap statistics before the failure. Shows 79.94% free heap memory. [09:57:38,964][INFO][grid-timeout-worker-#19%null%][IgniteKernal] FreeList [name=null, buckets=256, dataPages=1208250, reusePages=0] [09:58:38,963][INFO][grid-timeout-worker-#19%null%][IgniteKernal]

Re: Error : Commit produced a runtime exception

Attaching the complete error log file ignite_error_log.log -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Error-Commit-produced-a-runtime-exception-tp15768p15780.html Sent from

Re: Error : Commit produced a runtime exception

*Server configuration* http://www.springframework.org/schema/beans"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation=" http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd";>

Re: Error : Commit produced a runtime exception

Hi Nikolai, Did you get a chance to look at this? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Error-Commit-produced-a-runtime-exception-tp15768p15812.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Error : Commit produced a runtime exception

I have already shared the cache configuration in my post above. Reposting below- Cache configuration :- cacheConfig.setAtomicityMode(TRANSACTIONAL); cacheConfig.setCacheMode(PARTITIONED); cacheConfig.setBackups(1); cacheConfig.setCopyOnRead(TRUE); cacheConfig.setPartitionLossPolicy(IGNORE);

Re: Error : Commit produced a runtime exception

No I have not set any memory configuration -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Error-Commit-produced-a-runtime-exception-tp15768p15824.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Query about running SQL with durable memory

Hi, I want to understand how SQL queries work when persistence store is enabled in v2.1. Suppose I have 10 Person entries in the disk, out of which only 5 are in-memory. Now if I run a SQL query which is expected to count the number of entries in Person cache, will the query run only on the disk

Cache.get does not move entry from disk to RAM

Hi, I am using v2.1 with persistence store enabled. I observed that cache.get() does not move requested entry from the disk to the RAM. Is this an expected behaviour? Is there any best practice to warm-up RAM with a subset of data from the durable memory when I restart my cluster. Thanks! --

Warming up RAM from durable memory

Hi, Is there a way to warm-up the RAM with a subset of data from the durable memory after cluster deployment? Thanks! -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Warming-up-RAM-from-durable-memory-tp16017.html Sent from the Apache Ignite Users mailing list

Re: Warming up RAM from durable memory

so a query like "SELECT * from PERSON;" will automatically copy entries from disk to RAM? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Warming-up-RAM-from-durable-memory-tp16017p16047.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Activating Cluster taking too long

Hi! I am experimenting with v2.1 persistence store enabled. 1. Created 8 caches and pumped data into them. 2. Restarted the ignite cluster. 3. Waited for all server nodes to join the cluster. 4. called Ignite.active(true); I observed the cluster activation time is more than 1 hour with the follo

Re: Activation: slow and: Ignite node crashed in the middle of checkpoint.

Hi Roger, I have experienced a similar issue during cluster activation in my setup as well. I had shared my logs here - http://apache-ignite-users.70518.x6.nabble.com/Activating-Cluster-taking-too-long-td16093.html Eagerly seeking a root cause and resolution for this. -- View this message in c

SqlFieldsQuery NPE on my schema

My cache configuration is as follows - CacheConfiguration cacheConfig = new CacheConfiguration<>(); cacheConfig.setAtomicityMode(TRANSACTIONAL); cacheConfig.setCacheMode(PARTITIONED); cacheConfig.setBackups(1); cacheConfig.setCopyOnRead(TRUE); cacheConfig.setPartitionLossPolicy(IGNORE); cacheConf

Re: SqlFieldsQuery NPE on my schema

Changing the query to include setParitions solved the problem with SELECT query. However, SQL statements with DELETE and UPDATE are still not working. Change made - SqlFieldsQuery folquery = new SqlFieldsQuery("UPDATE A set b = 111 where c = ?").setArgs(someArg); folquery.setDistributedJoins(fals