[
https://issues.apache.org/jira/browse/IMPALA-11060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17652345#comment-17652345
]
ASF subversion and git services commented on IMPALA-11060:
----------------------------------------------------------
Commit db1cac2a495fa393f407d72775c072551a43dab4 in impala's branch
refs/heads/master from Fang-Yu Rao
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=db1cac2a4 ]
IMPALA-10399, IMPALA-11060, IMPALA-11788: Reset Ranger policy repository in an
E2E test
test_show_grant_hive_privilege() uses Ranger's REST API to get all the
existing policies from the Ranger server after creating a policy that
grants the LOCK and SELECT privileges on all the tables and columns in
the unique database in order to verify the granted privileges indeed
exist in Ranger's policy repository.
The way we download all the policies from the Ranger server in
test_show_grant_hive_privilege(), however, did not
always work. Specifically, when there were already a lot of existing
policies in Ranger, the policy that granted the LOCK and SELECT
privileges would not be included in the result returned via one single
GET request. We found that to reproduce the issue it suffices to add 300
Ranger policies before adding the policy granting those 2 privileges.
Moreover, we found that even we set the argument 'stream' of
requests.get() to True and used iter_content() to read the response in
chunks, we still could not retrieve the policy added in
test_show_grant_hive_privilege().
As a workaround, instead of changing how we download all the policies
from the Ranger server, this patch resets Ranger's policy repository for
Impala before we create the policy granting those 2 privileges so that
this test will be more resilient to the number of existing policies in
the repository.
Change-Id: Iff56ec03ceeb2912039241ea302f4bb8948d61f8
Reviewed-on: http://gerrit.cloudera.org:8080/19373
Tested-by: Impala Public Jenkins <[email protected]>
Reviewed-by: Quanlong Huang <[email protected]>
> Add option in create-load-data.sh to run setup-ranger only
> ----------------------------------------------------------
>
> Key: IMPALA-11060
> URL: https://issues.apache.org/jira/browse/IMPALA-11060
> Project: IMPALA
> Issue Type: Task
> Components: Infrastructure
> Reporter: Quanlong Huang
> Assignee: Fang-Yu Rao
> Priority: Major
>
> Each time when we bump the GBN, ranger will fail to launch. We need to rerun
> the setup-ranger() part inside testdata/bin/create-load-data.sh. It'd be good
> if we have an option to only run it, or exact it into a dedicate script so we
> can easily reuse it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
