Hi Sergei,

Picking up this thread again.  The problem appears to be getting worse.  10.1.35 shipped with old TokuDB despite there being a Percona 5.6 release in May.

Given the next 10.0 (10.0.37) is not scheduled for 19 October, are we to assume that the next 10.1 release (10.1.36) will still not get a TokuDB merge?  So we're going to have 10.1.36 in September, that will have an 8 month old version of TokuDB, despite new versions of Percona 5.6 being released in May and August.

You mentioned in this thread ideas around merging TokuDB straight into 10.1 or 10.2 to avoid the 10.0->10.1->10.2->10.3 lag .. what's the latest thinking on this?
Also, will you consider merging from Percona 5.7 instead of 5.6, as it gets much more regular releases.



On Mon, Jul 10, 2017 at 11:30 PM Sergei Golubchik <serg@mariadb.org> wrote:
Hi, Jocelyn!

On Jul 05, jocelyn fournier wrote:
> Le 05/07/2017 ą 15:36, Sergei Golubchik a écrit :
> > On Jun 25, Phil Sweeney wrote:
> >> Hi Sergei,
> >>
> >> Appreciate you considering other options.  Unfortunately in this case
> >> it seems Percona did not release a new 5.6 version in time for this
> >> 10.1.25 merge.
> >>
> >> However, interestingly, they did tag a release for 5.7.18-15 in the
> >> PerconaFT repository (which is common to both 5.6 and 5.7) in late
> >> May, that did include the fix I wanted :)
> >>
> >> Percona tells me that they will only be doing a 5.6 release once
> >> Oracle releases 5.6.37, which could be quite some time (plus the time
> >> for Percona to do their thing).
> >>
> >> Is there potentially a way to deal with this, e.g. accept any tagged
> >> release from PerconaFT (be it 5.6 or 5.7 .. but perhaps use a
> >> different versioning indicator for consistency)
> > Yes. Technically, we can merge TokuDB from 5.7 into 10.2.
> > May be we start doing it later, after a first few GA releases of 10.2
> This fix is really critical for TokuDB users, right now it's almost
> unusable (I have to fix the server for one of my customer several time a
> week because the cardinality reaches 0 due to this bug).
> So the sooner the better :)

Understood, thanks.

So far it looks like next 10.0 and 10.1 releases will be after Oracle
July 2017 CPU, so hopefully Percona will release new 5.6 TokuDB in time
for us to merge it. But if not - I'll try to grab it from 5.7, if it'll
be usable.

Chief Architect MariaDB
and security@mariadb.org