ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Max Timonin <timonin.ma...@gmail.com>
Subject Re: [DISCCUSS] Ignite 2.9.2. Index compatibility issue 2.x -> 2.9
Date Mon, 01 Mar 2021 10:06:05 GMT
Ok, I see, thanks for the answer!

On Fri, Feb 26, 2021 at 2:13 PM Ilya Kasnacheev <ilya.kasnacheev@gmail.com>
wrote:

> Hello!
>
> I don't think we should fix it in 2.9.2 if the fix will already be
> available in 2.10.
>
> Anyone who sees this bug is welcome to upgrade to 2.10.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пт, 26 февр. 2021 г. в 11:32, Max Timonin <timonin.maxim@gmail.com>:
>
> > Hi, Igniters!
> >
> > There was a compatibility issue [1] with upgrading an old version of
> Ignite
> > to 2.9. Inlined JavaObjects just are skipped and then it leads to
> undefined
> > behavior:
> > 1. In best case it just fails with BPlusTreeCorruptedException;
> > 2. But in some cases Ignite may *silently* make a wrong decision while
> > comparing, then results of queries will be invalid.
> >
> > Workaround is to rebuild indexes.
> >
> > For the new release 2.10 this bug was fixed today (commits are [2], [3]).
> >
> > WDYT, is it worth to backport those commits to the previous Ignite
> version?
> >
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-14206
> > [2]
> >
> >
> https://github.com/apache/ignite/commit/851f650ba03e0b6c081cfe23f411fd2bf6be0228
> > [3]
> >
> >
> https://github.com/apache/ignite/commit/93b74922bd04b164301d7bc5a2788b9693d4a8a4
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message