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

Re: Comparing Strings in SQL statements

On Thu, Sep 14, 2017 at 7:10 PM, iostream wrote: > > 1. Whether Ignite does not TRIM strings internally when doing comparisons? > I don't think Ignite trims strings for comparison. You should use TRIM() function explicitly when inserting or comparing strings. > 2. Is there a way to configure m

Re: Indexing collection fields

Hey Val! Thanks for your reply! Unfortunately, I didn't quite get it what you're suggesting. Could you please explain how it can be done given this cache value class? class Pojo { long id; Collection stringCollection; Collection intCollection; } Thanks again! Andrey ___

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: 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/

Re:Re: Re: Re: Fetched result set too large

Yes,It work. Thank you. At 2017-09-14 00:26:07, "Alexey Kuznetsov" wrote: Hi Lucky, You can build Ignite from sources. Will this work for you? On Wed, Sep 13, 2017 at 9:07 PM, Lucky wrote: Oh,No! This is the worst news today. I have to try another way to resolve it. Anyway,Thanks

Re: Indexing collection fields

Hi Andrey, No, you can't index data that is inside a collection. To achieve that, you should create a separate entry for each element of this transaction and save them in a cache separately. -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: A quick question on WAL and Transaction

Yes, in this mode fsync for this mode is applied for every update. LOG_ONLY mode writes update to FS buffers, but not necessary to disk itself, so it's obviously faster. However, in this mode there is a chance to lose some of the updates in case of power loss (but not in case of node process failur

Re: [Announcement] Talk: Real-time Data Analysis with Apache Ignite High-Performance In-memory Platform

Great news, Roman! Please share some photos and give us a short report of the conference afterward if you get a chance. Tom > On Sep 14, 2017, at 5:24 PM, Denis Magda wrote: > > Good luck, Roman! > > Community please help to spread the word! > > — > Denis > >> On Sep 13, 2017, at 6:1

A quick question on WAL and Transaction

Hi, Is an Ignite transaction, *with a recovery guarantee of power loss (WALMode.DEFAULT),* considered committed only after its WAL log file has been successfully *full-sync* written to disk? If so, doesn't this incur a major slow down? Thanks, WALMode: https://github.com/apache/ignite/blob/15613

Re: [Announcement] Talk: Real-time Data Analysis with Apache Ignite High-Performance In-memory Platform

Good luck, Roman! Community please help to spread the word! — Denis > On Sep 13, 2017, at 6:11 PM, Roman Shtykh wrote: > > Hi, > > I will be making a short presentation at Data Platform Conference Tokyo 2017 > on Apache Ignite with emphasis on IoT. > Attending is free. Please come if you are

Indexing collection fields

Hello, My POJO has a collection field (e.g. a list of strings). Is indexing such fields supported? If not, what are my options in terms of being able to look up data by any element in the collection? Thanks Andrey

Re: Cannot start/stop cache within lock or transaction

This Threads seems to be stuck: - Name: exchange-worker-#34%null% State: TIMED_WAITING Total blocked: 3 Total waited: 28 Stack trace: sun.misc.Unsafe.park(Native Method) java.util.concurrent.locks.LockSupport.parkNanos(Unknown Source) org.apache.ignite.internal.util.future.GridFu

Re: UPDATE query with JOIN

Hello Sidds, UPDATE with JOINs is not supported in Ignite as long as H2 database grammar Ignite relies on does not support it too [1]. AFAIK, they are not part of ANSI SQL 99 either, and thus different DB engines have different syntax and capabilities to support it. However, I believe I understand

Re: Cannot start/stop cache within lock or transaction

The issue cannot be reproduced in 1.4.0. It seems the bug was introduced in 1.5.0 -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Error : Commit produced a runtime exception

My configuration is as follows:

Re: Error : Commit produced a runtime exception

I am experiencing the same problem with Ignite 2.1 when I have persistence configured. I can start a single node successfully (I have 1M entries persisted) but a second identical node fails with the error. SEVERE: Failed to reinitialize local partitions (preloading will be stopped): GridDhtPartiti

Re: Existing queue can't be accessed on client node

Hi Edward, Thank you for the code snippet, I was able to reproduce the issue. I need time to investigate it, if there's no problem with the code, I'll file the issue to Ignite's jira to fix it. Thanks, Mike. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Cannot start/stop cache within lock or transaction

Hi Yakov, This is pretty easy to repro. Please find attached the source code project which reproduces this 100% of the time. If you could please suggest a workaround or time line for the fix. thanks and Regards, Rajeev ignite-deadlock.zip

Re: Cannot start/stop cache within lock or transaction

Naresh, The case you described should work. Can you please create a reproducer that I can run locally? I also filed this to make best effort to avoid deadlocks - https://issues.apache.org/jira/browse/IGNITE-6380 --Yakov