Sure. I think "fine-grained privileges" always introduce small changes in
behaviors, i.e. unprivileged users used to be able to do something but they
can't do so after an upgrade. We accept it since it's reasonable.
There're incompatible changes too in the previous releases:
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
> cherry-pick
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 IMPALA-6479 being
> picked
>>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 comment in the
>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 comment in the
Yes, there are two discussion threads before that are relative to this. One
for stopping the cherrypick-2.x-and-test jenkins job:
https://lists.apache.org/thread.html/2b4b62d4c07661b27a5203618cb0425a429f6460f2eb505acbcd26c6@%3Cdev.impala.apache.org%3E
The other for removing support for hadoop 2
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
