Re: KafkaStreamer, how to manage (stop consumming, resume) on client disconnection

flush() guarantees completion of all futures returned by addData(Object, Object) https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/IgniteDataStreamer.html#flush-- flush() will send the batch, but it is still possible for the server to crash before the message reaches it. If you

Re: KafkaStreamer, how to manage (stop consumming, resume) on client disconnection

Thanks for the answers. I resolved the problem of reconnection using events. It worked very well. What I found, is the following... The KafkaStreamer consumes records and send them to the IgniteDataStreamer. It doesn't handle the IgniteFuture returned. If the connection with the server is

Re: KafkaStreamer, how to manage (stop consumming, resume) on client disconnection

Hi, I think listening to events would be a good solution for you. There are two discovery events that are triggered on the client node when it is disconnected from or reconnected to the cluster: EVT_CLIENT_NODE_DISCONNECTED EVT_CLIENT_NODE_RECONNECTED see:

C# CacheStoreAdapter - Customizing Load, LoadCache methods

Hello, I have some confusion about implementing my own Load and LoadCache methods - I am trying to load data from an underlying Oracle database into cache, and the entries are key-value pairs where the key is the Associate ID and the value is the entire Associate object. *(1)* Regarding the

IgniteSecurity vs GridSecurityProcessor

Hi, We were using 2.7.6 and had implemented a custom security plugin for authorization and authentication by implementing GridSecurityProcessor. Now in 2.9 we see that a new interface is provided IgniteSecurity. May I know what is the difference between the interfaces, as both look similar and

Re: [2.8.1]Checking optimistic transaction state on remote nodes

Hello! It will happen when the node has left but the transaction has to be committed. Most operations on transactional cache will involve implicit transactions so there you go. Regards, -- Ilya Kasnacheev чт, 19 нояб. 2020 г. в 16:46, 38797715 <38797...@qq.com>: > Hi community, > > Although

Re: Configuration Files and storage location

Hello! Too many unrelated issues are wrapped together here. First, you do not need to have identical config for all nodes in the cluster. Paths may surely differ. Some property need to be the same, some don't. Second, you may change the node's consistentId to specify which persistence files to

Re: Ignite Visor cmd cannot connect...

Hello! I think that C++ node would enforce some binary configuration, so you will have to repeat the exact one in the XML file for Visor CMD: https://ignite.apache.org/docs/latest/cpp-specific/cpp-platform-interoperability I recommend using control.sh or GGCC for Apache Ignite in place of Visor

Ignite Visor cmd cannot connect...

Hi, I tried using ignitevisorcmd.sh -cfg= however I'm getting the following error message: Local node's binary configuration is not equal to remote node's binary configuration It further states: localBinaryCfg=null rmtBinaryCfg={globIdMapper ... I'm using the exact same xml configuration

Re: Updating a field using a SQL subquery

Apparently, this functionality is not supported. https://apacheignite-sql.readme.io/docs/how-ignite-sql-works#known-limitations -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Updating a field using a SQL subquery

Hello. I am trying to update a field using a SQL subquery, but I get an incorrect result. Do I need to create a bug or am I doing something wrong? UpdateWithSubQueryTest.java -- Sent from:

Configuration Files and storage location

Hi community, I have a question regarding the xml configuration which is used in clients / servers and thinclients. Is it really necessary that each node is using the same configuration? I'm just asking because I'm trying out to setup multiple servers in one machine which totally is nonsense

Re: How to get data for subqueries with aggregate functions in Ignite Thick client mode

Hi Shravya! It caused by bug in H2 parser which erases information about type of the column expression of subqueries and reports it just like ‘column’, so Ignite can’t properly split the query. For thin client the splitting is not always needed since the requests starts its execution on the