+1 Nothing else comes to mind. Kudos for finding the bug.
J-D On Wed, Apr 12, 2017 at 2:42 PM, Todd Lipcon <[email protected]> wrote: > This morning we found a serious issue (KUDU-1968) which can eat data at a > relatively high rate on clusters after a failure. We need to get 1.3.1 out > ASAP. I'd like to build a release candidate tonight or tomorrow. > > Are there any other patches that we should be cherry-picking into 1.3.1? > Reminder that point-releases like this should be critical fixes (data loss, > incorrect results, crashes, etc) only. > > -Todd > -- > Todd Lipcon > Software Engineer, Cloudera >
