You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2023/06/30 04:37:00 UTC
[jira] [Commented] (IMPALA-12248) Add required Ranger configuration properties after RANGER-2895
[ https://issues.apache.org/jira/browse/IMPALA-12248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17738870#comment-17738870 ]
ASF subversion and git services commented on IMPALA-12248:
----------------------------------------------------------
Commit 0c7f15e8b0d1c9b87a56a878f8b402b5f4e22cfb in impala's branch refs/heads/master from Fang-Yu Rao
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=0c7f15e8b ]
IMPALA-12248: Add three configuration properties after RANGER-2895
This patch adds 3 Ranger configuration properties that will be required
after we start using a build that includes RANGER-2895 so that Ranger's
HTTP server could be properly started.
On the other hand, recall that a Ranger configuration property was
deprecated in RANGER-2895, i.e.,
ranger.jpa.jdbc.idleconnectiontestperiod. Hence, we should also remove
it when starting using a build that contains RANGER-2895. This task will
be tracked by IMPALA-12250.
Testing:
- Verified that with this patch Ranger's HTTP server could be started
and that we will be able to update the users, groups, and policies on
the Ranger server with the current scripts in the Impala repository
whether or not we are using a build that has RANGER-2895.
Change-Id: I19a27e3fe3ab96a9f60566dc2c87bd72636b91ae
Reviewed-on: http://gerrit.cloudera.org:8080/20129
Reviewed-by: Impala Public Jenkins <im...@cloudera.com>
Tested-by: Impala Public Jenkins <im...@cloudera.com>
> Add required Ranger configuration properties after RANGER-2895
> --------------------------------------------------------------
>
> Key: IMPALA-12248
> URL: https://issues.apache.org/jira/browse/IMPALA-12248
> Project: IMPALA
> Issue Type: Task
> Reporter: Fang-Yu Rao
> Assignee: Fang-Yu Rao
> Priority: Major
>
> [RANGER-2895|https://github.com/apache/ranger/commit/846031985cae70f7a8c5e92faf186948a302260e] added and removed some configuration properties.
> [Three new configuration properties were added|https://github.com/apache/ranger/commit/846031985cae70f7a8c5e92faf186948a302260e#diff-dcab4376623684e416c7e60162c7af7a7d3789fe1d61a2cfdaef794334426f05]. We found that once we bump up the build number to include RANGER-2895 and if those new properties do not exist in [ranger-admin-default-site.xml.template|https://github.com/apache/impala/blob/master/testdata/cluster/ranger/ranger-admin-default-site.xml.template] or [ranger-admin-site.xml.template|https://github.com/apache/impala/blob/master/testdata/cluster/ranger/ranger-admin-site.xml.template] then the produced site files for Ranger will not contain those new properties, resulting in some error message like the following in catalina.log. As a result, Ranger's HTTP server could not be properly started.
> {code:java}
> 23/06/25 04:46:01 ERROR context.ContextLoader: Context initialization failed
> org.springframework.beans.factory.BeanDefinitionStoreException: Invalid bean definition with name 'defaultDataSource' defined in ServletContext resource [/META-INF/applicationContext.xml]: Could not resolve placeholder 'ranger.jpa.jdbc.idletimeout' in value "${ranger.jpa.jdbc.idletimeout}"; nested exception is java.lang.IllegalArgumentException: Could not resolve placeholder 'ranger.jpa.jdbc.idletimeout' in value "${ranger.jpa.jdbc.idletimeout}"
> at
> {code}
> There are also some configuration properties removed in RANGER-2895, e.g., [ranger.jpa.jdbc.idleconnectiontestperiod|https://github.com/apache/ranger/commit/846031985cae70f7a8c5e92faf186948a302260e#diff-dcab4376623684e416c7e60162c7af7a7d3789fe1d61a2cfdaef794334426f05L136]. In this regard, we could probably add these 3 new properties first and then remove the unnecessary properties once we have bumped up the build number that includes RANGER-2895.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org