uanlong Huang
> wrote:
>
> > I'm afraid the difference between branch-2.x and Cloudera's branch is
> > larger than the difference between branch-2.x and master branch.
> Cloudera's
> > branch already ignored lots of commits, which causes the gap. I've tried
> >
On Wed, Jan 30, 2019 at 12:21 AM Quanlong Huang
wrote:
> I'm afraid the difference between branch-2.x and Cloudera's branch is
> larger than the difference between branch-2.x and master branch. Cloudera's
> branch already ignored lots of commits, which causes the gap. I've tried
>
I'm afraid the difference between branch-2.x and Cloudera's branch is
larger than the difference between branch-2.x and master branch. Cloudera's
branch already ignored lots of commits, which causes the gap. I've tried
cherry-pick from master or Cloudera's branch and found it's much easier to
pick
On Mon, Jan 28, 2019 at 11:36 PM Quanlong Huang
wrote:
> >>For the first patch, "0b540b025 IMPALA-7128 (part 1) Refactor interfaces
> for Db, View, Table, Partition", the cherry-pick conflicts is due to the
> revert of IMPALA-6479 in 2.x. I'm testing branch-2.x with I
>>For the first patch, "0b540b025 IMPALA-7128 (part 1) Refactor interfaces
for Db, View, Table, Partition", the cherry-pick conflicts is due to the
revert of IMPALA-6479 in 2.x. I'm testing branch-2.x with IMPALA-6479 being
picked back. Does anyone know why we revert it?
>For the first patch, "0b540b025 IMPALA-7128 (part 1) Refactor interfaces
for Db, View, Table, Partition", the cherry-pick conflicts is due to the
revert of IMPALA-6479 in 2.x. I'm testing branch-2.x with IMPALA-6479 being
picked back. Does anyone know why we revert it? (I also commen
in master branch:
https://lists.apache.org/thread.html/49f9b68ed3d6d2c0fdee16a877b259922545e4824e1233479227a657@%3Cdev.impala.apache.org%3E
I'm +1 with the second thread that we only support Hadoop 2 in branch-2.x
and support Hadoop 3 in the master branch to be more focused. I'm also
agree
As for Quanlong's question, I think the answer is however the folks who
want to do the work prefer to do it. As you noticed in the CDH changelists,
Cloudera's distribution has opted for something more like approach (a),
choosing to backport individual features. For a while, we were doing
Hi Quanlong,
I created a JIRA for that: https://issues.apache.org/jira/browse/IMPALA-7922
CR is here: https://gerrit.cloudera.org/c/12027/
On Mon, Dec 3, 2018 at 3:07 AM Quanlong Huang
wrote:
> Hi all,
>
> I encountered a maven failure while building branch-2.x:
>
> *Scanni
Is it possible that we only apply bug fixes to the 2.x branch? Or can we wait
until the master branch become healthy from broken/flasky tests and then
cherry-pick all the bug fixes to the 2.x branch? It'd be great if we can at
least release 2.13 so our works after 2.12 won't be wasted.
In
Hi Quanlong,
If someone wishes to step up and maintain the 2.x branch, they're very
welcome to. To be transparent, some of the Cloudera employees are focusing
considerably more on the 3.x line and aren't currently planning to release
manage additional 2.x releases.
On Wed, Jun 20, 2018 at 1:56
Sorry, Philip. Do you mean we won't apply new patches to the 2.x branch? I
thought you just mean to disable the automatic cherry-pick job.
In my limited understanding, there're two major breaking changes for the 3.x
branch:
* Standard SQL syntax: legacy HQL may fail on syntax errors in
This just came up - do we want to backport bug or test fixes to 2.x or
nothing at all?
https://gerrit.cloudera.org/#/c/10722/
On Mon, Jun 18, 2018 at 10:48 AM, Tim Armstrong
wrote:
> Thanks Phil, I think it will be good not to have to maintain this.
>
> On Mon, Jun 18, 2018 at 9:40 AM, Philip
Thanks Phil, I think it will be good not to have to maintain this.
On Mon, Jun 18, 2018 at 9:40 AM, Philip Zeyliger <
phi...@cloudera.com.invalid> wrote:
> I've not heard anything, so I've removed the "trigger" for job
> https://jenkins.impala.io/job/cherrypick-2.x-and-test/. It used to "Poll
>
I've not heard anything, so I've removed the "trigger" for job
https://jenkins.impala.io/job/cherrypick-2.x-and-test/. It used to "Poll
SCM" at an "@hourly" rate, looking for changes in asf/master.
Thanks!
-- Philip
On Fri, Jun 15, 2018 at 11:23 AM Philip Zeyliger
wrote:
> Hi folks,
>
> As
Hi folks,
As you know, many of us have been maintaining the 2.x branch by having a
cherry-pick job (https://jenkins.impala.io/job/cherrypick-2.x-and-test/)
and, when it fails, manually pushing through the issues. This has proven to
be quite the burden, and I'm planning on disabling the automatic
16 matches
Mail list logo
