Hi, Pavel. I've found a bug in BinaryTupleComparator, which is used by Indexes, that byte[] comparison is non-conformed with SQL standard. The fix is ready [1] and merged to master. The fix breaks ordering in Indexes for byte strings that affects binary compatibility between versions.
Can we add a fix to the 3.0? [1] https://issues.apache.org/jira/browse/IGNITE-24176 On Mon, Jan 13, 2025 at 7:30 PM Pavel Tupitsyn <ptupit...@apache.org> wrote: > Mikhail, no objections. Please merge to main and cherry-pick to ignite-3.0 > (I've set the fix version accordingly). > > Looks like we have to postpone the code freeze, I'll post an update > tomorrow. > > On Mon, Jan 13, 2025 at 6:15 PM Mikhail Pochatkin <m.a.pochat...@gmail.com > > > wrote: > > > Hi, guys. I have fixed a bug in CLI with incorrect SQL exception handling > > (IGNITE-24179). Any objections to merge it before code freeze? > > > > пн, 13 янв. 2025 г. в 08:45, Pavel Tupitsyn <ptupit...@apache.org>: > > > > > > Found a very nasty error IGNITE-24186, I think it's worth adding, > since > > > we might not be able to restart the cluster. > > > > > > Kirill, are you going to work on this? Any ETA? > > > > > > > > > > worth adding this performance fix into the scope IGNITE-24163 > > > > > > Already done and cherry-picked, nice. > > > > > > On Sun, Jan 12, 2025 at 10:00 PM Nusrat Shakarov <nusrat...@gmail.com> > > > wrote: > > > > > > > Considering that we have EventLog-related tickets in the scope, I > think > > > it > > > > is also worth adding this performance fix into the scope IGNITE-24163 > > > > > > > > On Sat, 11 Jan 2025 at 11:18, ткаленко кирилл <tkalkir...@yandex.ru> > > > > wrote: > > > > > > > > > Found a very nasty error IGNITE-24186, I think it's worth adding, > > since > > > > we > > > > > might not be able to restart the cluster. > > > > > > > > > > > > > > > > > > -- > > best regards, > > Pochatkin Mikhail. > > > -- Best regards, Andrey V. Mashenkov