Re: Apache Ignite and the log4j Vulnerability.

That’s a good summary, thanks. For people who do use log4j2 with Ignite, this is the best public summary I’ve seen so far: https://www.gridgain.com/resources/blog/what-you-need-know-about-log4j-vulnerabilities-apache-ignite-and-gridgain In summary, there are immediate mitigations you can apply a

using multiple columns Index

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 is the key - a is a TIMESTAMP - b is a SMALLINT - c is a TINYINT - e, f, g are VARCHAR this table have around 200M lines I

Re: using multiple columns Index

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

Re: using multiple columns Index

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

Re: using multiple columns Index

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

Re: using multiple columns Index

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

Log4j response

Is the Apache Ignite group aware of any current vulnerabilities presented by log4j within Ignite or planning on issuing any guidance or advice in regards to log4j and Ignite? Thank you, Randall

Re: using multiple columns Index

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

Re: Log4j response

This is the best public summary I’ve seen so far: https://www.gridgain.com/resources/blog/what-you-need-know-about-log4j-vulnerabilities-apache-ignite-and-gridgain In summary, the

Re: Transactional Reader Writer Locks

Hi. You can try OPTIMISTIC SERIALIZABLE isolation, it might have better throughput in contending scenarios. But this is not the same as RW lock, because a tx can be invalidated after a commit if a lock conflict is detected. No RW lock of any kind is planned, AFAIK. вт, 7 дек. 2021 г. в 23:22, :

RE: Transactional Reader Writer Locks

Hi Alexei Thanks for your note. We have actually considered optimistic transactional transactions before but to be honest we’re not entirely sure how to address this: Wiki: “When using OPTIMISTIC transactions, full read consistency can be achieved by disallowing potential conflicts betwe