Re: Achieve uniform data distribution easily

Thank you for your answer. We are aware of that our approach is not the clean one as the one with explicitly defined affinity keys would be. But still for the sake of data distribution defining affinityKeys, in this example this would be cacheName/key for a given key, should be equivalent to overri

Re: Ignite SqlFieldQuery Unicode Characters Support

Hi, We have started our ignite nodes (server & client) with mentioned jvm parameter and it works fine. Thanks for the quick response. Regards, Ravi Makwana On Mon, 8 Jun 2020 at 18:49, Ilya Kasnacheev wrote: > Hello! > > I have met an error like this one, and my recommendation is that on all

Re: How to fix Ignite node segmentation without restart

>I do not want to restart it and I cannot do a failover because a network issue just happened and the stand-by may be invalid. The fix is to always restart the slave. You can enable CacheWriteSynchronizationMode.FULL_SYNC and there will be no differences between primary and backup partitions. In th

Re: Atomic Sequence/Auto Increment via IgniteClient - Thin Client - Ignite 2.8.1

Hi Manesh, Thin clients don't support this API yet. As a workaround, see if you can implement a custom SQL function [1] and call it from an INSERT statement issued by the thin client - "INSERT INTO table(id, name, age) VALUES (generateIdFunction(), 'Mark', 40)". I haven't tried this approach and

Re: Best practices for WalArchive when using EFS

Raymond, I agree with you that the existence of the WAL should be more than enough to ensure data consistency. The documentation suggests that the archives help to speed up the rebalancing procedures (refer to the Pros and Cons of WAL Archiving callout): https://apacheignite.readme.io/docs/write-

Re: sqlline

You can always send a compute task via one of IgniteCompute.affinityX() methods and run a *local* SQL query on that node: - affinity calls: https://apacheignite.readme.io/docs/collocate-compute-and-data#affinity-call-and-run-methods - local SQL queries: https://apacheignite-sql.readme

Re: sqlline

My selects are complex but they do use the primary keys for the partitioned tables/caches participating in the query. But they perform poorly if the data is distributed across multiple nodes. On Wed, Jun 17, 2020 at 8:04 PM narges saleh wrote: > Thanks Denis. In case of selects, can I push ignit

Re: Ignite Webconsole (console.gridgain.com) login not not working

Thanks Dennis for the response and fixing it. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: sqlline

Thanks Denis. In case of selects, can I push ignite to broadcast the sql to where the data is, say by using employing services deployed on the targeted data nodes, or utilizing affinity calls (with the sql as part of the logic)? On Wed, Jun 17, 2020 at 7:02 PM Denis Magda wrote: > Narges, > > IN

Re: sqlline

Narges, INSERTS/UPDATES/DELETES will be forwarded to primary nodes based on the value of primary keys you pass into queries. Ignite maps a primary key to a partition and, finally, to a primary node that holds that partition. All this happens transparently in Ignite. You don't need to do anything e

Re: Achieve uniform data distribution easily

Hi, see: https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/affinity/Affinity.html Can you see the key to partition mappings: https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/affinity/Affinity.html#mapKeyToPrimaryAndBackups-K- to see what your

Re: HashMap warning when using PutAll()

Hi Ilya, Thank you for the SortedDictionary pointer. I am not sure what you mean by 'size-1 collections'. Is there an issue here that requires fixing in Ignite, or just the use of SortedDIctionary in my client code? Thanks, Raymond. On Thu, Jun 18, 2020 at 3:45 AM Ilya Kasnacheev wrote: > Hel

Re: Size of an object in Ignite cache

Hi, Ignite converts your object to a binaryObject before storing it: https://apacheignite.readme.io/docs/binary-marshaller You can take a look at the binary object format: https://cwiki.apache.org/confluence/display/IGNITE/Binary+object+format Also see this answer: https://stackoverf

Re: sqlline

Thanks Denis. Will watch the video. One more question, related to SQL execution. If I issue a SQL from a client, how would ignite know which node to run the SQL query on? I assume the SQL is parsed on the server nodes, and I will still need to direct the SQL to be executed on the right server node

Re: sqlline

The collocated flag is an extra optimization hint for SQL queries with GROUP BYs. The parameter requests to group records locally on the nodes that participated in the query execution. For instance, if your application sends a query with GROUP BY to a couple of server nodes, then the nodes will gro

Achieve uniform data distribution easily

In our project a lot of data records share the same keys, i.e. a given key might exist in several of our caches (with different values though). We suspect that this is the reason for our non-uniform data-distribution over the cluster-nodes that we are facing since all data-records that share the sa

Re: sqlline

Then can you please explain what the option collocated=true for JDBC url is for? Should I assume that if the table is defined with affinity set, then compute collocation, including sql execution will happen automatically? I am sorry if this is just a basic question. On Wed, Jun 17, 2020 at 12:57 P

Re: sqlline

If the data is already co-located you don't need to pass in any other parameters. - Denis On Wed, Jun 17, 2020 at 10:13 AM narges saleh wrote: > Hi Denis. The tables are defined with affinity keys specified. What I am > asking whether to set the collection option when I insert or query the dat

Re: sqlline

Hi Denis. The tables are defined with affinity keys specified. What I am asking whether to set the collection option when I insert or query the data via SQL line. thanks On Wed, Jun 17, 2020 at 11:39 AM Denis Magda wrote: > Hi, > > You need to pass the required parameters to the JDBC driver's c

Re: sqlline

Hi, You need to pass the required parameters to the JDBC driver's connection URL: https://apacheignite-sql.readme.io/docs/jdbc-driver#parameters However, I'm not quite sure what you mean under the "collocation" in the following context. All your data needs to be co-located beforehand (ensure you

sqlline

Hi All, Is collocation enforced when SQL is issues in sqline command line or do I need to give the option when I start sqlline? thanks.

Atomic Sequence/Auto Increment via IgniteClient - Thin Client - Ignite 2.8.1

Hello, Is there a way to access ignite Atomic Sequence via thin client apis? We have a situation where we have thick clients (java micro-services) and thin clients (Spark) and both need to generate IDs for inserting data into tables. regards Mahesh

Re: Data streamer hangs

Hi, Are you seeing pool starvation messages? How long does it stay in this state? Are you not seeing any data saved, even when you close the jdbc connection? Are you able to reproduce this scenario? If so please describe steps/send a reproducer and send full logs. Data Streamer pool

Re: HashMap warning when using PutAll()

Hello! The warning should not be issued for size-1 collections. In dotnet, you should use SortedDictionary with putAll. Regards, -- Ilya Kasnacheev сб, 13 июн. 2020 г. в 09:43, Raymond Wilson : > If the answer is that the consumer of the C# client should order the items > before calling PutAl

Re: Ignite Webconsole (console.gridgain.com) login not not working

Tarun, Thanks for the report! We've had an issue with the service. It's back on now. Denis ср, 17 июн. 2020 г. в 16:17, tarunk : > Hi All, > > I have been using ignite webconsole with my login hosted at > https://console.gridgain.com/signin. > I remember using it till ~a month back, while loggi

Re: PIVOT with SQL

Hi, At present, PIVOT functionn is not supported. SQL function reference: https://apacheignite-sql.readme.io/docs/sql-reference-overview Thanks, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Problem with writeBehind Apache Ignite 2.8.1

Hello, I use Apache Ignite with MariaDB (RDBMS Integration), all works properly except "writeBehind", if I activate "writeBehind" and I insert for example 200 instances with PHP PDO I receive a exception on console of Ignite, the exception is the following: jun 17, 2020 4:03:45 PM org.apache.igni

Ignite Webconsole (console.gridgain.com) login not not working

Hi All, I have been using ignite webconsole with my login hosted at https://console.gridgain.com/signin. I remember using it till ~a month back, while logging in today, am getting below error. 404 Not Found -- nginx Has there been any changes to this ? Even trying to setup a new

Best practices for WalArchive when using EFS

We are deploying an Ignite application to a Kubernetes cluster in AWS EKS and are planning to use EFS for persistent data. I have been reading through the tuning options for the Write Ahead Log Archive, trying to understand if we can safely turn off the archive to save the IO related to copying a

Non collocated subqueries

Hello, It seems that SqlFieldsQuery.setCollocated and SqlFieldsQuery.setDistributedJoins has no affect on subqueries under IN and EXISTS expressions. I didn’t find any information about subqueries specific in actual documentation. Subqueries is important part of sql, please describe it in documents

Size of an object in Ignite cache

How one can know the exact size of an object stored on Ignite cache? Can we use below to get the size? byte[] arr = ignite.configuration().getMarshaller().marshal(new Person(10L, "first", "last")); -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/