I agree with Adar regarding the fix, we should avoid knowingly releasing a
version with an issue we can't fix down the road due to backwards-compatibility
issues.
I also agree with Alexey that we can revert the change introducing
live_row_count instead of waiting for the fix, at least if it takes
I think we can cut another RC if we really think that incorporating these
fixes makes the release candidate more robust and sound. I'm not sure what
is time-based limit there, but it would be great if we could wrap it up in
one week or so.
>From the other side, as PlanB we could rollback the
+0
Built on Ubuntu 18.04 and CentOS 6.6. Ran DEBUG tests in slow mode. No failures.
I do wish the release incorporated the fix for KUDU-2980, but that
hasn't even been published to CR yet. Plus it won't break backwards
compatibility if we fix it later.
On the other hand,