RE: Re: Question about REST/C++ client

2024-02-20 Thread Louis C
more or less what you said (even if > > in this API we do not have to retrieve explicitely the base value). > > Best regards, > > Louis > > -- > > *De :* Stephen Darlington > > *Envoyé :* mardi 13 février 2024 11:22 > > *À :* user@ig

Re: Question about REST/C++ client

2024-02-19 Thread Stephen Darlington
> *De :* Stephen Darlington > *Envoyé :* mardi 13 février 2024 11:22 > *À :* user@ignite.apache.org > *Objet :* Re: Question about REST/C++ client > > The easy answer to the "50 gets in parallel" is to use GetAll. > > On Tue, 13 Feb 2024 at 09:54, Ig

RE: Question about REST/C++ client

2024-02-14 Thread Louis C
the base value). Best regards, Louis De : Stephen Darlington Envoyé : mardi 13 février 2024 11:22 À : user@ignite.apache.org Objet : Re: Question about REST/C++ client The easy answer to the "50 gets in parallel" is to use GetAll. On Tue, 13 Feb 2024 at 0

Re: Question about REST/C++ client

2024-02-13 Thread Stephen Darlington
The easy answer to the "50 gets in parallel" is to use GetAll. On Tue, 13 Feb 2024 at 09:54, Igor Sapego wrote: > 1. There is no such API. Seems like a weird error in documentation. We > will fix it. If you want to make 50 gets in parallel, I think it's better > to run 50 clients with the

Re: Question about REST/C++ client

2024-02-13 Thread Igor Sapego
1. There is no such API. Seems like a weird error in documentation. We will fix it. If you want to make 50 gets in parallel, I think it's better to run 50 clients with the current API. You can use the same client too, but it may be slower, depending on how many nodes you have in a cluster. 2. What

Question about REST/C++ client

2024-02-08 Thread Louis C
Hello, I am trying to use/test Apache Ignite for a particular use case. For background reference, my use case of Ignite is to do 100Ks (to begin with) of "Gets" and of "increments" of values that will be stored in probably multiple caches in Apache Ignite. I read the Ignite documentation, but