Thanks, Tim and Jim! Then I have no other suggestions.+1
At 2018-04-03 10:57:58, "Jim Apple" <[email protected]> wrote: >Additionally, because this patch doesn't break any backwards compatibility, >it's fine to merge it for 2.13 and 3.1 when those releases are cut. And >since there are no minimum waiting period between releases, we could cut >those right after that patch lands if we like. > >On Mon, Apr 2, 2018 at 4:05 PM, Tim Armstrong <[email protected]> >wrote: > >> I don't think we should hold the release for the ORC scanner patch - it's a >> great feature, but there are many other equally important features and >> improvements that have been waiting for months to be released. >> >> Generally, there are always going to be big changes that are "nearly there" >> and I think we're best off releasing frequently rather than trying to hold >> releases for specific features. This is especially true for large features >> where it sometimes take a bit of bake time to flush out all of the issues >> with the initial patch. >> >> - Tim >> >> On Mon, Apr 2, 2018 at 3:49 PM, Quanlong Huang <[email protected]> >> wrote: >> >> > Hi friends, >> > >> > >> > Is it possible to wait until IMPALA-5717 (https://gerrit.cloudera.org/# >> > /c/9134/) is merged? We're eager to upgrade our Impala cluster with the >> > latest ORC-support. I've heard from the community that many other >> companies >> > are waiting for it too. As it's an experimental feature so far, we can >> get >> > more feedback on this release. >> > >> > >> > As Tim said, this patch is closed to be merged. Could you wait until it's >> > merged? >> > >> > >> > Thanks, >> > Quanlong >> > >> > At 2018-04-03 05:56:11, "Jim Apple" <[email protected]> wrote: >> > >agreed. >> > > >> > >On Mon, Apr 2, 2018 at 2:50 PM, Philip Zeyliger <[email protected]> >> > wrote: >> > > >> > >> Sounds like a good plan to me! >> > >> >> > >> -- Philip >> > >> >> > >>
