Re: NPE on control.sh --cache indexes_force_rebuild

Please use --cache-names parameter (not --cache_names) Ilya ср, 14 апр. 2021 г. в 16:17, 38797715 <38797...@qq.com>: > 2.10 > > at > org.apache.ignite.internal.commandline.cache.CacheIndexesForceRebuild.parseArguments(CacheIndexesForceRebuild.java:210) > > From the code point of view, this

Ignite unable to understand recursive query.

I am having a problem with the following query which results in this error: javax.cache.CacheException: Failed to parse query. Column "S.TAGID" not found; SQL statement: >From reading it looks like the reason for this is explained in this

ClassNotFoundException in Ignite cron occasionally

I am running ignite cron in ignite version 2.8.1. But I am facing the below exception occasionally on corn runs on ignite node servers. I have enable peer to peer ignite configuration still facing this issue sometimes. Below is the code and exception. Have tried removing withBinary option in cache

Re: Ignite AWS library to support spark 3.0.1 and scala 2.12.12 version

Hi, Spark 3.0 is not supported for Apache Ignite, nor in the GridGain plugin. Supported Spark versions: 2.3 and 2.4. BR, Andrei 3/31/2021 9:49 PM, ChandanS пишет: Hi All, Can anyone please let me know which apache or grid-gain ignite library for AWS EC2 instance deployment will support AWS

Re: Read through Write Through Example

Have a look at "ADO.NET As Ignite.NET Cache Store" blog post [1] It links to an example [2]. The code is a bit old and uses SQL Server Compact, but still demonstrates the point. It also uses KeepBinaryInStore, which is optional. Let me know if you need more details. [1]

Generated affinity key from multiple fields and SQL partition pruning

Hello team, If we generate @AffinityKeyMapped field from multiple other fields and then use those original fields in SQL WHERE condition, they are not used for partition pruning: https://ignite.apache.org/docs/latest/perf-and-troubleshooting/sql-tuning#partition-pruning Because Ignite doesn't

Read through Write Through Example

We are trying to evaluate Ignite and could not find an example of the read through write through to a MS SQL Db. Is there one you can point to, preferably in .NET Code to show how this works? The information contained in this email message is being

Re: Fastest way to iterate over a persistence cache

Hello! We had a per-page scanning of caches once, but it is disabled for some time because it was causing synchronization issues. Apache Ignite is still a memory-centric database, which assumed that data is either in memory or may be loaded to memory relatively quickly. So I guess the only

Re: Abrupt stop of application on using sql

Hello! You should probably decrease maxSize until you stop seeing this issue, and then some more. Regards, -- Ilya Kasnacheev ср, 14 апр. 2021 г. в 13:09, rakshita04 : > Hi Ilya, > > We only have one node. > Attached is our DataBaseConfig.xml file for your reference > DataBaseConfig.xml > <

Re: Abrupt stop of application on using sql

Hi Ilya, We only have one node. Attached is our DataBaseConfig.xml file for your reference DataBaseConfig.xml -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: reading encrypted password from Ignite config file

Hello! There are a couple of third party implementations of security plugins, but I doubt that there are any walkthroughs on implementing your own. Regards, -- Ilya Kasnacheev вт, 13 апр. 2021 г. в 20:31, shivakumar : > Hi Ilya, > if I have to use username/password is it possible to

Re: Abrupt stop of application on using sql

Hello! How many nodes do you have? Maybe when you start killing nodes, remaining nodes start rebalancing data and they keep more data locally than fits in your memory. The recommendation stays the same - decrease your data regions' and heap size until it fits comfortably in the available memory

Re: NPE on control.sh --cache indexes_force_rebuild

2.10 at org.apache.ignite.internal.commandline.cache.CacheIndexesForceRebuild.parseArguments(CacheIndexesForceRebuild.java:210) From the code point of view, this line of code does appear null pointer. 在 2021/4/14 下午3:56, Ilya Kazakov 写道: Hello! What version do you use? Ilya ср, 14 апр.

Re: NPE on control.sh --cache indexes_force_rebuild

Hello! What version do you use? Ilya ср, 14 апр. 2021 г. в 14:57, 38797715 <38797...@qq.com>: > Hello, > > Does indexes_force_rebuild command have a demo to run? > > The following error will be thrown during current execution: > > ./control.sh --cache indexes_force_rebuild --cache_names City >

Re: Cannot start ignite nodes with shared memory - Ignite version 2.10.0

Hello. It will be great if you can share some simple reproducer. ср, 14 апр. 2021 г. в 03:39, sarahsamji : > Hi, > > * > Tested with:* > - Ignite version - 2.10.0 > - Multinode cluster on single/different JVM - localhost > - First node successfully starts, shared memory endpoint also starts but

NPE on control.sh --cache indexes_force_rebuild

 Hello, Does indexes_force_rebuild command have a demo to run? The following error will be thrown during current execution: ./control.sh --cache indexes_force_rebuild --cache_names City Time: 2021-04-14T14:46:10.485 java.lang.NullPointerException Command [] finished with code: 4 Error stack