I know there are people expecting 2.0 release in January, so it is for
their information.
It turns out we have fixed foreign key handling so well, that it
resulted in a performance regression (ineffective parallel applying).
Although it affects only foreign key users, we decided not to let it
out and fix it for good. There are no other outstanding issues. The
release should happen within a week.
Yes, however until you upgrade all the nodes to 2.x they will be working on 1.x protocol, so no IST and other fancies. Also, protocol downgrade is not supported, so you won't be able to join 1.x node to 2.x cluster.
> I know there are people expecting 2.0 release in January, so it is for > their information.
> It turns out we have fixed foreign key handling so well, that it > resulted in a performance regression (ineffective parallel applying). > Although it affects only foreign key users, we decided not to let it > out and fix it for good. There are no other outstanding issues. The > release should happen within a week.
and we need to fix these before the release. ETA for these fixes is this week and if no more issues appear and packaging works without problems, we should be able to publish the release early next week.
> Any eta for 2.0 release ? specifically for ubuntu/debian
> Thanks
> On 2/1/2012 5:25 PM, Alexey Yurchenko wrote: >> Hi,
>> I know there are people expecting 2.0 release in January, so it is for >> their information.
>> It turns out we have fixed foreign key handling so well, that it >> resulted in a performance regression (ineffective parallel applying). >> Although it affects only foreign key users, we decided not to let it >> out and fix it for good. There are no other outstanding issues. The >> release should happen within a week.
