Hi, Chrystophe!
> But do you have a tweak in mind to get better response time on this kind
of request ?
Do you mean queries that return an empty result set? Unfortunately, I'm not
aware of ways of improving performance of such queries.
Also, I don't know the task you're actually solving. Maybe i
Hi Maxim,
Thanks for the details.
But do you have a tweak in mind to get better response time on this kind of
request ?
BR,
Chrystophe Vergnaud
Architect @ Cyblex Technologies
Le jeu. 16 déc. 2021 à 15:09, Maksim Timonin a
écrit :
> Hi, Chrystophe!
>
> Multifield index should perfectly wor
Hi, Chrystophe!
Multifield index should perfectly work for cases with strict equality like:
(a == ? && b == ?) OR (a == ? && b > ?) . But for queries with range
queries for first field "a" ("a" > ? && b ...) you should not expect a
boost of performance. You're right, it's due to B+Tree implementat
Hello Stephen,
I was created with SQL :
CREATE INDEX IF NOT EXISTS "t_idx_1" ON MYSCHEMA."t" ("a", "b", "c");
BR,
Chrystophe Vergnaud
Architect @ Cyblex Technologies
Le jeu. 16 déc. 2021 à 13:51, Stephen Darlington <
stephen.darling...@gridgain.com> a écrit :
> Can you show how you’ve defined
Can you show how you’ve defined your index(es)?
> On 16 Dec 2021, at 12:27, Chrystophe Vergnaud
> wrote:
>
> Hello,
>
> I'm running an ignite 2.10 and I don't understand the behavior of the
> multi-columns index.
>
> For instance, I have a table t(id, a,b,c, d, e, f, g)
> - id is a uuid and
