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 "Fang-Yu Rao (Jira)" <ji...@apache.org> on 2023/06/27 22:05:00 UTC
[jira] [Updated] (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:all-tabpanel ]
Fang-Yu Rao updated IMPALA-12248:
---------------------------------
Description:
[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.
was:
[RANGER-2895|https://github.com/apache/ranger/commit/846031985cae70f7a8c5e92faf186948a302260e] added and removed some configuration properties.
Three new configuration properties were added. 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.
> 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