[jira] [Updated] (RANGER-2579) Support for configuration of Solr Zookeeper ensemble in the Solr service
[ https://issues.apache.org/jira/browse/RANGER-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wu.kehua updated RANGER-2579: - Attachment: 0001-RANGER-2579-Support-for-configuration-of-Solr-Zookee.patch > Support for configuration of Solr Zookeeper ensemble in the Solr service > > > Key: RANGER-2579 > URL: https://issues.apache.org/jira/browse/RANGER-2579 > Project: Ranger > Issue Type: New Feature > Components: Ranger >Affects Versions: 2.1.0 >Reporter: wu.kehua >Assignee: wu.kehua >Priority: Major > Labels: patch > Attachments: > 0001-RANGER-2579-Support-for-configuration-of-Solr-Zookee.patch > > > When creating a Solr service, only one Solr URL is supported. For SolrCloud > mode, when a Solr node fails, the SolrCloud should work normally, and the > current implementation will make the Solr service unavailable. > Therefore, we should use SolrCloud's ZooKeeper address as the optimal > connection method to deal with some Solr node failure scenarios. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-2579) Support for configuration of Solr Zookeeper ensemble in the Solr service
wu.kehua created RANGER-2579: Summary: Support for configuration of Solr Zookeeper ensemble in the Solr service Key: RANGER-2579 URL: https://issues.apache.org/jira/browse/RANGER-2579 Project: Ranger Issue Type: New Feature Components: Ranger Affects Versions: 2.1.0 Reporter: wu.kehua Assignee: wu.kehua When creating a Solr service, only one Solr URL is supported. For SolrCloud mode, when a Solr node fails, the SolrCloud should work normally, and the current implementation will make the Solr service unavailable. Therefore, we should use SolrCloud's ZooKeeper address as the optimal connection method to deal with some Solr node failure scenarios. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2562) Support for configuration of multiple Solr URLs in the Solr service
[ https://issues.apache.org/jira/browse/RANGER-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wu.kehua updated RANGER-2562: - Description: When create a new Solr service, we can set only one Solr URL, but as we know Solr cloud model has more than one Solr service, so we should support for configuration of multiple Solr URLs in the Solr service. eg. When I set "http://192.166.1.1:18983/solr; for "Solr URL" in the Solr service, I click the "Test Connection" button, it will be ok, it shows "Connected Successfully." But when I set "http://192.166.1.1:18983/solr,http://192.166.1.2:28983/solr; for "Solr URL" in the Solr service, I click the "Test Connection" button, it will show "Connection Failed.", as follows: !image-2019-09-09-16-13-27-219.png! was: When create a new Solr service, we can set only one Solr URL, but as we know Solr cloud model has more than one Solr service, so we should support for configuration of multiple Solr URLs in the Solr service. eg. When I set "http://192.166.1.1:18983/solr; for "Solr URL" in the Solr service, I click the "Test Connection" button, it will be ok, it shows "Connected Successfully." But when I set "http://192.166.1.1:18983/solr,[http://192.166.1.2:28983/solr]; for "Solr URL" in the Solr service, I click the "Test Connection" button, it will show "Connection Failed.", as follows: !image-2019-09-09-16-13-27-219.png! > Support for configuration of multiple Solr URLs in the Solr service > --- > > Key: RANGER-2562 > URL: https://issues.apache.org/jira/browse/RANGER-2562 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 2.1.0 >Reporter: wu.kehua >Assignee: wu.kehua >Priority: Major > Labels: patch > Attachments: > 0001-RANGER-2562-Support-for-configuration-of-multiple-So.patch, > image-2019-09-09-16-13-27-219.png > > > When create a new Solr service, we can set only one Solr URL, but as we know > Solr cloud model has more than one Solr service, so we should support for > configuration of multiple Solr URLs in the Solr service. > eg. > When I set "http://192.166.1.1:18983/solr; for "Solr URL" in the Solr > service, I click the "Test Connection" button, it will be ok, it shows > "Connected Successfully." > But when I set "http://192.166.1.1:18983/solr,http://192.166.1.2:28983/solr; > for "Solr URL" in the Solr service, I click the "Test Connection" button, it > will show "Connection Failed.", as follows: > !image-2019-09-09-16-13-27-219.png! -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (RANGER-2562) Support for configuration of multiple Solr URLs in the Solr service
[ https://issues.apache.org/jira/browse/RANGER-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wu.kehua updated RANGER-2562: - Description: When create a new Solr service, we can set only one Solr URL, but as we know Solr cloud model has more than one Solr service, so we should support for configuration of multiple Solr URLs in the Solr service. eg. When I set "http://192.166.1.1:18983/solr; for "Solr URL" in the Solr service, I click the "Test Connection" button, it will be ok, it shows "Connected Successfully." But when I set "http://192.166.1.1:18983/solr,[http://192.166.1.2:28983/solr]; for "Solr URL" in the Solr service, I click the "Test Connection" button, it will show "Connection Failed.", as follows: !image-2019-09-09-16-13-27-219.png! was: When create a new Solr service, we can set only one Solr URL, but as we know Solr cloud model has more than one Solr service, so we should support for configuration of multiple Solr URLs in the Solr service. eg. When I set "http://10.43.33.175:18983/solr; for "Solr URL" in the Solr service, I click the "Test Connection" button, it will be ok, it shows "Connected Successfully." But when I set "http://10.43.33.175:18983/solr,[http://10.43.33.175:28983/solr]; for "Solr URL" in the Solr service, I click the "Test Connection" button, it will show "Connection Failed.", as follows: !image-2019-09-09-16-13-27-219.png! > Support for configuration of multiple Solr URLs in the Solr service > --- > > Key: RANGER-2562 > URL: https://issues.apache.org/jira/browse/RANGER-2562 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 2.1.0 >Reporter: wu.kehua >Assignee: wu.kehua >Priority: Major > Labels: patch > Attachments: > 0001-RANGER-2562-Support-for-configuration-of-multiple-So.patch, > image-2019-09-09-16-13-27-219.png > > > When create a new Solr service, we can set only one Solr URL, but as we know > Solr cloud model has more than one Solr service, so we should support for > configuration of multiple Solr URLs in the Solr service. > eg. > When I set "http://192.166.1.1:18983/solr; for "Solr URL" in the Solr > service, I click the "Test Connection" button, it will be ok, it shows > "Connected Successfully." > But when I set > "http://192.166.1.1:18983/solr,[http://192.166.1.2:28983/solr]; for "Solr > URL" in the Solr service, I click the "Test Connection" button, it will show > "Connection Failed.", as follows: > !image-2019-09-09-16-13-27-219.png! -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (RANGER-2562) Support for configuration of multiple Solr URLs in the Solr service
[ https://issues.apache.org/jira/browse/RANGER-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wu.kehua updated RANGER-2562: - Attachment: 0001-RANGER-2562-Support-for-configuration-of-multiple-So.patch > Support for configuration of multiple Solr URLs in the Solr service > --- > > Key: RANGER-2562 > URL: https://issues.apache.org/jira/browse/RANGER-2562 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 2.1.0 >Reporter: wu.kehua >Assignee: wu.kehua >Priority: Major > Labels: patch > Attachments: > 0001-RANGER-2562-Support-for-configuration-of-multiple-So.patch, > image-2019-09-09-16-13-27-219.png > > > When create a new Solr service, we can set only one Solr URL, but as we know > Solr cloud model has more than one Solr service, so we should support for > configuration of multiple Solr URLs in the Solr service. > eg. > When I set "http://10.43.33.175:18983/solr; for "Solr URL" in the Solr > service, I click the "Test Connection" button, it will be ok, it shows > "Connected Successfully." > But when I set > "http://10.43.33.175:18983/solr,[http://10.43.33.175:28983/solr]; for "Solr > URL" in the Solr service, I click the "Test Connection" button, it will show > "Connection Failed.", as follows: > !image-2019-09-09-16-13-27-219.png! -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (RANGER-2562) Support for configuration of multiple Solr URLs in the Solr service
wu.kehua created RANGER-2562: Summary: Support for configuration of multiple Solr URLs in the Solr service Key: RANGER-2562 URL: https://issues.apache.org/jira/browse/RANGER-2562 Project: Ranger Issue Type: Improvement Components: Ranger Affects Versions: 2.1.0 Reporter: wu.kehua Assignee: wu.kehua Attachments: image-2019-09-09-16-13-27-219.png When create a new Solr service, we can set only one Solr URL, but as we know Solr cloud model has more than one Solr service, so we should support for configuration of multiple Solr URLs in the Solr service. eg. When I set "http://10.43.33.175:18983/solr; for "Solr URL" in the Solr service, I click the "Test Connection" button, it will be ok, it shows "Connected Successfully." But when I set "http://10.43.33.175:18983/solr,http://10.43.33.175:28983/solr; for "Solr URL" in the Solr service, I click the "Test Connection" button, it will show "Connection Failed.", as follows: !image-2019-09-09-16-12-00-122.png! -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (RANGER-2562) Support for configuration of multiple Solr URLs in the Solr service
[ https://issues.apache.org/jira/browse/RANGER-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wu.kehua updated RANGER-2562: - Description: When create a new Solr service, we can set only one Solr URL, but as we know Solr cloud model has more than one Solr service, so we should support for configuration of multiple Solr URLs in the Solr service. eg. When I set "http://10.43.33.175:18983/solr; for "Solr URL" in the Solr service, I click the "Test Connection" button, it will be ok, it shows "Connected Successfully." But when I set "http://10.43.33.175:18983/solr,[http://10.43.33.175:28983/solr]; for "Solr URL" in the Solr service, I click the "Test Connection" button, it will show "Connection Failed.", as follows: !image-2019-09-09-16-13-27-219.png! was: When create a new Solr service, we can set only one Solr URL, but as we know Solr cloud model has more than one Solr service, so we should support for configuration of multiple Solr URLs in the Solr service. eg. When I set "http://10.43.33.175:18983/solr; for "Solr URL" in the Solr service, I click the "Test Connection" button, it will be ok, it shows "Connected Successfully." But when I set "http://10.43.33.175:18983/solr,http://10.43.33.175:28983/solr; for "Solr URL" in the Solr service, I click the "Test Connection" button, it will show "Connection Failed.", as follows: !image-2019-09-09-16-12-00-122.png! > Support for configuration of multiple Solr URLs in the Solr service > --- > > Key: RANGER-2562 > URL: https://issues.apache.org/jira/browse/RANGER-2562 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 2.1.0 >Reporter: wu.kehua >Assignee: wu.kehua >Priority: Major > Labels: patch > Attachments: image-2019-09-09-16-13-27-219.png > > > When create a new Solr service, we can set only one Solr URL, but as we know > Solr cloud model has more than one Solr service, so we should support for > configuration of multiple Solr URLs in the Solr service. > eg. > When I set "http://10.43.33.175:18983/solr; for "Solr URL" in the Solr > service, I click the "Test Connection" button, it will be ok, it shows > "Connected Successfully." > But when I set > "http://10.43.33.175:18983/solr,[http://10.43.33.175:28983/solr]; for "Solr > URL" in the Solr service, I click the "Test Connection" button, it will show > "Connection Failed.", as follows: > !image-2019-09-09-16-13-27-219.png! -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (RANGER-2562) Support for configuration of multiple Solr URLs in the Solr service
[ https://issues.apache.org/jira/browse/RANGER-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wu.kehua updated RANGER-2562: - Attachment: image-2019-09-09-16-13-27-219.png > Support for configuration of multiple Solr URLs in the Solr service > --- > > Key: RANGER-2562 > URL: https://issues.apache.org/jira/browse/RANGER-2562 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 2.1.0 >Reporter: wu.kehua >Assignee: wu.kehua >Priority: Major > Labels: patch > Attachments: image-2019-09-09-16-13-27-219.png > > > When create a new Solr service, we can set only one Solr URL, but as we know > Solr cloud model has more than one Solr service, so we should support for > configuration of multiple Solr URLs in the Solr service. > eg. > When I set "http://10.43.33.175:18983/solr; for "Solr URL" in the Solr > service, I click the "Test Connection" button, it will be ok, it shows > "Connected Successfully." > But when I set > "http://10.43.33.175:18983/solr,http://10.43.33.175:28983/solr; for "Solr > URL" in the Solr service, I click the "Test Connection" button, it will show > "Connection Failed.", as follows: > !image-2019-09-09-16-12-00-122.png! -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (RANGER-2560) Solve the problem of the order of the configuration items of the Solr plugin
[
https://issues.apache.org/jira/browse/RANGER-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wu.kehua updated RANGER-2560:
-
Description:
There is one problem in the method "init()" of class "RangerSolrAuthorizer".
Firstly, the code logic is to get the parameters "useProxyIP", "proxyIPHeader"
and "solrAppName" from RangerConfiguration, as follows:
{code:java}
useProxyIP = RangerConfiguration.getInstance().getBoolean(useProxyIP =
RangerConfiguration.getInstance().getBoolean( PROP_USE_PROXY_IP, useProxyIP);
proxyIPHeader = RangerConfiguration.getInstance().get( PROP_PROXY_IP_HEADER,
proxyIPHeader);
// First get from the -D property
solrAppName = System.getProperty("solr.kerberos.jaas.appname", solrAppName);
// Override if required from Ranger properties
solrAppName = RangerConfiguration.getInstance().get( PROP_SOLR_APP_NAME,
solrAppName);
{code}
But after that, the code logic is to call "solrPlugin.init()" to parse the
configuration file, as follows:
{code:java}
configuration.addResourcesForServiceType(serviceType);
{code}
Due to the opposite logic, the values of the parameters "useProxyIP",
"proxyIPHeader","solrAppName" and "solrAppName" are not available.
was:
There is one problem in the method "init()" of class "RangerSolrAuthorizer".
Firstly, the code logic is to get the parameters "useProxyIP",
"proxyIPHeader","solrAppName" and "solrAppName" from RangerConfiguration, as
follows:
{code:java}
useProxyIP = RangerConfiguration.getInstance().getBoolean(useProxyIP =
RangerConfiguration.getInstance().getBoolean( PROP_USE_PROXY_IP, useProxyIP);
proxyIPHeader = RangerConfiguration.getInstance().get( PROP_PROXY_IP_HEADER,
proxyIPHeader);
// First get from the -D property
solrAppName = System.getProperty("solr.kerberos.jaas.appname", solrAppName);
// Override if required from Ranger properties
solrAppName = RangerConfiguration.getInstance().get( PROP_SOLR_APP_NAME,
solrAppName);
{code}
But after that, the code logic is to call "solrPlugin.init()" to parse the
configuration file, as follows:
{code:java}
configuration.addResourcesForServiceType(serviceType);
{code}
Due to the opposite logic, the values of the parameters "useProxyIP",
"proxyIPHeader","solrAppName" and "solrAppName" are not available.
> Solve the problem of the order of the configuration items of the Solr plugin
>
>
> Key: RANGER-2560
> URL: https://issues.apache.org/jira/browse/RANGER-2560
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: wu.kehua
>Assignee: wu.kehua
>Priority: Major
> Labels: patch
> Fix For: 2.1.0
>
> Attachments:
> 0001-RANGER-2560-Solve-the-problem-of-the-order-of-the-co.patch
>
>
> There is one problem in the method "init()" of class "RangerSolrAuthorizer".
> Firstly, the code logic is to get the parameters "useProxyIP",
> "proxyIPHeader" and "solrAppName" from RangerConfiguration, as follows:
> {code:java}
> useProxyIP = RangerConfiguration.getInstance().getBoolean(useProxyIP =
> RangerConfiguration.getInstance().getBoolean( PROP_USE_PROXY_IP, useProxyIP);
> proxyIPHeader = RangerConfiguration.getInstance().get( PROP_PROXY_IP_HEADER,
> proxyIPHeader);
> // First get from the -D property
> solrAppName = System.getProperty("solr.kerberos.jaas.appname", solrAppName);
> // Override if required from Ranger properties
> solrAppName = RangerConfiguration.getInstance().get( PROP_SOLR_APP_NAME,
> solrAppName);
> {code}
> But after that, the code logic is to call "solrPlugin.init()" to parse the
> configuration file, as follows:
> {code:java}
> configuration.addResourcesForServiceType(serviceType);
> {code}
> Due to the opposite logic, the values of the parameters "useProxyIP",
> "proxyIPHeader","solrAppName" and "solrAppName" are not available.
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (RANGER-2560) Solve the problem of the order of the configuration items of the Solr plugin
[
https://issues.apache.org/jira/browse/RANGER-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wu.kehua updated RANGER-2560:
-
Description:
There is one problem in the method "init()" of class "RangerSolrAuthorizer".
Firstly, the code logic is to get the parameters "useProxyIP",
"proxyIPHeader","solrAppName" and "solrAppName" from RangerConfiguration, as
follows:
{code:java}
useProxyIP = RangerConfiguration.getInstance().getBoolean(useProxyIP =
RangerConfiguration.getInstance().getBoolean( PROP_USE_PROXY_IP, useProxyIP);
proxyIPHeader = RangerConfiguration.getInstance().get( PROP_PROXY_IP_HEADER,
proxyIPHeader);
// First get from the -D property
solrAppName = System.getProperty("solr.kerberos.jaas.appname", solrAppName);
// Override if required from Ranger properties
solrAppName = RangerConfiguration.getInstance().get( PROP_SOLR_APP_NAME,
solrAppName);
{code}
But after that, the code logic is to call "solrPlugin.init()" to parse the
configuration file, as follows:
{code:java}
configuration.addResourcesForServiceType(serviceType);
{code}
Due to the opposite logic, the values of the parameters "useProxyIP",
"proxyIPHeader","solrAppName" and "solrAppName" are not available.
was:
There is one problem in the method "init()" of class "RangerSolrAuthorizer".
Firstly, the code logic is to get the parameters "useProxyIP",
"useProxyIP","solrAppName" and "solrAppName" from RangerConfiguration, as
follows:
{code:java}
useProxyIP = RangerConfiguration.getInstance().getBoolean(useProxyIP =
RangerConfiguration.getInstance().getBoolean( PROP_USE_PROXY_IP, useProxyIP);
proxyIPHeader = RangerConfiguration.getInstance().get( PROP_PROXY_IP_HEADER,
proxyIPHeader);
// First get from the -D property
solrAppName = System.getProperty("solr.kerberos.jaas.appname", solrAppName);
// Override if required from Ranger properties
solrAppName = RangerConfiguration.getInstance().get( PROP_SOLR_APP_NAME,
solrAppName);
{code}
But after that, the code logic is to call "solrPlugin.init()" to parse the
configuration file, as follows:
{code:java}
configuration.addResourcesForServiceType(serviceType);
{code}
Due to the opposite logic, the values of the parameters "useProxyIP",
"useProxyIP","solrAppName" and "solrAppName" are not available.
> Solve the problem of the order of the configuration items of the Solr plugin
>
>
> Key: RANGER-2560
> URL: https://issues.apache.org/jira/browse/RANGER-2560
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: wu.kehua
>Assignee: wu.kehua
>Priority: Major
> Labels: patch
> Fix For: 2.1.0
>
> Attachments:
> 0001-RANGER-2560-Solve-the-problem-of-the-order-of-the-co.patch
>
>
> There is one problem in the method "init()" of class "RangerSolrAuthorizer".
> Firstly, the code logic is to get the parameters "useProxyIP",
> "proxyIPHeader","solrAppName" and "solrAppName" from RangerConfiguration, as
> follows:
> {code:java}
> useProxyIP = RangerConfiguration.getInstance().getBoolean(useProxyIP =
> RangerConfiguration.getInstance().getBoolean( PROP_USE_PROXY_IP, useProxyIP);
> proxyIPHeader = RangerConfiguration.getInstance().get( PROP_PROXY_IP_HEADER,
> proxyIPHeader);
> // First get from the -D property
> solrAppName = System.getProperty("solr.kerberos.jaas.appname", solrAppName);
> // Override if required from Ranger properties
> solrAppName = RangerConfiguration.getInstance().get( PROP_SOLR_APP_NAME,
> solrAppName);
> {code}
> But after that, the code logic is to call "solrPlugin.init()" to parse the
> configuration file, as follows:
> {code:java}
> configuration.addResourcesForServiceType(serviceType);
> {code}
> Due to the opposite logic, the values of the parameters "useProxyIP",
> "proxyIPHeader","solrAppName" and "solrAppName" are not available.
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (RANGER-2560) Solve the problem of the order of the configuration items of the Solr plugin
[
https://issues.apache.org/jira/browse/RANGER-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wu.kehua updated RANGER-2560:
-
External issue URL: (was: https://reviews.apache.org/r/71438/)
> Solve the problem of the order of the configuration items of the Solr plugin
>
>
> Key: RANGER-2560
> URL: https://issues.apache.org/jira/browse/RANGER-2560
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: wu.kehua
>Assignee: wu.kehua
>Priority: Major
> Labels: patch
> Fix For: 2.1.0
>
> Attachments:
> 0001-RANGER-2560-Solve-the-problem-of-the-order-of-the-co.patch
>
>
> There is one problem in the method "init()" of class "RangerSolrAuthorizer".
> Firstly, the code logic is to get the parameters "useProxyIP",
> "useProxyIP","solrAppName" and "solrAppName" from RangerConfiguration, as
> follows:
> {code:java}
> useProxyIP = RangerConfiguration.getInstance().getBoolean(useProxyIP =
> RangerConfiguration.getInstance().getBoolean( PROP_USE_PROXY_IP, useProxyIP);
> proxyIPHeader = RangerConfiguration.getInstance().get( PROP_PROXY_IP_HEADER,
> proxyIPHeader);
> // First get from the -D property
> solrAppName = System.getProperty("solr.kerberos.jaas.appname", solrAppName);
> // Override if required from Ranger properties
> solrAppName = RangerConfiguration.getInstance().get( PROP_SOLR_APP_NAME,
> solrAppName);
> {code}
> But after that, the code logic is to call "solrPlugin.init()" to parse the
> configuration file, as follows:
> {code:java}
> configuration.addResourcesForServiceType(serviceType);
> {code}
> Due to the opposite logic, the values of the parameters "useProxyIP",
> "useProxyIP","solrAppName" and "solrAppName" are not available.
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (RANGER-2560) Solve the problem of the order of the configuration items of the Solr plugin
[
https://issues.apache.org/jira/browse/RANGER-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wu.kehua updated RANGER-2560:
-
External issue URL: https://reviews.apache.org/r/71438/
> Solve the problem of the order of the configuration items of the Solr plugin
>
>
> Key: RANGER-2560
> URL: https://issues.apache.org/jira/browse/RANGER-2560
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: wu.kehua
>Assignee: wu.kehua
>Priority: Major
> Labels: patch
> Fix For: 2.1.0
>
> Attachments:
> 0001-RANGER-2560-Solve-the-problem-of-the-order-of-the-co.patch
>
>
> There is one problem in the method "init()" of class "RangerSolrAuthorizer".
> Firstly, the code logic is to get the parameters "useProxyIP",
> "useProxyIP","solrAppName" and "solrAppName" from RangerConfiguration, as
> follows:
> {code:java}
> useProxyIP = RangerConfiguration.getInstance().getBoolean(useProxyIP =
> RangerConfiguration.getInstance().getBoolean( PROP_USE_PROXY_IP, useProxyIP);
> proxyIPHeader = RangerConfiguration.getInstance().get( PROP_PROXY_IP_HEADER,
> proxyIPHeader);
> // First get from the -D property
> solrAppName = System.getProperty("solr.kerberos.jaas.appname", solrAppName);
> // Override if required from Ranger properties
> solrAppName = RangerConfiguration.getInstance().get( PROP_SOLR_APP_NAME,
> solrAppName);
> {code}
> But after that, the code logic is to call "solrPlugin.init()" to parse the
> configuration file, as follows:
> {code:java}
> configuration.addResourcesForServiceType(serviceType);
> {code}
> Due to the opposite logic, the values of the parameters "useProxyIP",
> "useProxyIP","solrAppName" and "solrAppName" are not available.
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (RANGER-2560) Solve the problem of the order of the configuration items of the Solr plugin
[
https://issues.apache.org/jira/browse/RANGER-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wu.kehua updated RANGER-2560:
-
Attachment: 0001-RANGER-2560-Solve-the-problem-of-the-order-of-the-co.patch
> Solve the problem of the order of the configuration items of the Solr plugin
>
>
> Key: RANGER-2560
> URL: https://issues.apache.org/jira/browse/RANGER-2560
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: wu.kehua
>Assignee: wu.kehua
>Priority: Major
> Labels: patch
> Fix For: 2.1.0
>
> Attachments:
> 0001-RANGER-2560-Solve-the-problem-of-the-order-of-the-co.patch
>
>
> There is one problem in the method "init()" of class "RangerSolrAuthorizer".
> Firstly, the code logic is to get the parameters "useProxyIP",
> "useProxyIP","solrAppName" and "solrAppName" from RangerConfiguration, as
> follows:
> {code:java}
> useProxyIP = RangerConfiguration.getInstance().getBoolean(useProxyIP =
> RangerConfiguration.getInstance().getBoolean( PROP_USE_PROXY_IP, useProxyIP);
> proxyIPHeader = RangerConfiguration.getInstance().get( PROP_PROXY_IP_HEADER,
> proxyIPHeader);
> // First get from the -D property
> solrAppName = System.getProperty("solr.kerberos.jaas.appname", solrAppName);
> // Override if required from Ranger properties
> solrAppName = RangerConfiguration.getInstance().get( PROP_SOLR_APP_NAME,
> solrAppName);
> {code}
> But after that, the code logic is to call "solrPlugin.init()" to parse the
> configuration file, as follows:
> {code:java}
> configuration.addResourcesForServiceType(serviceType);
> {code}
> Due to the opposite logic, the values of the parameters "useProxyIP",
> "useProxyIP","solrAppName" and "solrAppName" are not available.
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Created] (RANGER-2560) Solve the problem of the order of the configuration items of the Solr plugin
wu.kehua created RANGER-2560:
Summary: Solve the problem of the order of the configuration items
of the Solr plugin
Key: RANGER-2560
URL: https://issues.apache.org/jira/browse/RANGER-2560
Project: Ranger
Issue Type: Bug
Components: Ranger
Reporter: wu.kehua
Assignee: wu.kehua
Fix For: 2.1.0
There is one problem in the method "init()" of class "RangerSolrAuthorizer".
Firstly, the code logic is to get the parameters "useProxyIP",
"useProxyIP","solrAppName" and "solrAppName" from RangerConfiguration, as
follows:
{code:java}
useProxyIP = RangerConfiguration.getInstance().getBoolean(useProxyIP =
RangerConfiguration.getInstance().getBoolean( PROP_USE_PROXY_IP, useProxyIP);
proxyIPHeader = RangerConfiguration.getInstance().get( PROP_PROXY_IP_HEADER,
proxyIPHeader);
// First get from the -D property
solrAppName = System.getProperty("solr.kerberos.jaas.appname", solrAppName);
// Override if required from Ranger properties
solrAppName = RangerConfiguration.getInstance().get( PROP_SOLR_APP_NAME,
solrAppName);
{code}
But after that, the code logic is to call "solrPlugin.init()" to parse the
configuration file, as follows:
{code:java}
configuration.addResourcesForServiceType(serviceType);
{code}
Due to the opposite logic, the values of the parameters "useProxyIP",
"useProxyIP","solrAppName" and "solrAppName" are not available.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (RANGER-2560) Solve the problem of the order of the configuration items of the Solr plugin
[
https://issues.apache.org/jira/browse/RANGER-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wu.kehua updated RANGER-2560:
-
Description:
There is one problem in the method "init()" of class "RangerSolrAuthorizer".
Firstly, the code logic is to get the parameters "useProxyIP",
"useProxyIP","solrAppName" and "solrAppName" from RangerConfiguration, as
follows:
{code:java}
useProxyIP = RangerConfiguration.getInstance().getBoolean(useProxyIP =
RangerConfiguration.getInstance().getBoolean( PROP_USE_PROXY_IP, useProxyIP);
proxyIPHeader = RangerConfiguration.getInstance().get( PROP_PROXY_IP_HEADER,
proxyIPHeader);
// First get from the -D property
solrAppName = System.getProperty("solr.kerberos.jaas.appname", solrAppName);
// Override if required from Ranger properties
solrAppName = RangerConfiguration.getInstance().get( PROP_SOLR_APP_NAME,
solrAppName);
{code}
But after that, the code logic is to call "solrPlugin.init()" to parse the
configuration file, as follows:
{code:java}
configuration.addResourcesForServiceType(serviceType);
{code}
Due to the opposite logic, the values of the parameters "useProxyIP",
"useProxyIP","solrAppName" and "solrAppName" are not available.
was:
There is one problem in the method "init()" of class "RangerSolrAuthorizer".
Firstly, the code logic is to get the parameters "useProxyIP",
"useProxyIP","solrAppName" and "solrAppName" from RangerConfiguration, as
follows:
{code:java}
useProxyIP = RangerConfiguration.getInstance().getBoolean(useProxyIP =
RangerConfiguration.getInstance().getBoolean( PROP_USE_PROXY_IP, useProxyIP);
proxyIPHeader = RangerConfiguration.getInstance().get( PROP_PROXY_IP_HEADER,
proxyIPHeader);
// First get from the -D property
solrAppName = System.getProperty("solr.kerberos.jaas.appname", solrAppName);
// Override if required from Ranger properties
solrAppName = RangerConfiguration.getInstance().get( PROP_SOLR_APP_NAME,
solrAppName);
{code}
But after that, the code logic is to call "solrPlugin.init()" to parse the
configuration file, as follows:
{code:java}
configuration.addResourcesForServiceType(serviceType);
{code}
Due to the opposite logic, the values of the parameters "useProxyIP",
"useProxyIP","solrAppName" and "solrAppName" are not available.
> Solve the problem of the order of the configuration items of the Solr plugin
>
>
> Key: RANGER-2560
> URL: https://issues.apache.org/jira/browse/RANGER-2560
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: wu.kehua
>Assignee: wu.kehua
>Priority: Major
> Labels: patch
> Fix For: 2.1.0
>
>
> There is one problem in the method "init()" of class "RangerSolrAuthorizer".
> Firstly, the code logic is to get the parameters "useProxyIP",
> "useProxyIP","solrAppName" and "solrAppName" from RangerConfiguration, as
> follows:
> {code:java}
> useProxyIP = RangerConfiguration.getInstance().getBoolean(useProxyIP =
> RangerConfiguration.getInstance().getBoolean( PROP_USE_PROXY_IP, useProxyIP);
> proxyIPHeader = RangerConfiguration.getInstance().get( PROP_PROXY_IP_HEADER,
> proxyIPHeader);
> // First get from the -D property
> solrAppName = System.getProperty("solr.kerberos.jaas.appname", solrAppName);
> // Override if required from Ranger properties
> solrAppName = RangerConfiguration.getInstance().get( PROP_SOLR_APP_NAME,
> solrAppName);
> {code}
> But after that, the code logic is to call "solrPlugin.init()" to parse the
> configuration file, as follows:
> {code:java}
> configuration.addResourcesForServiceType(serviceType);
> {code}
> Due to the opposite logic, the values of the parameters "useProxyIP",
> "useProxyIP","solrAppName" and "solrAppName" are not available.
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (RANGER-2549) There are two logic errors when installing the solr audit log module
[
https://issues.apache.org/jira/browse/RANGER-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wu.kehua updated RANGER-2549:
-
Attachment: 0001-RANGER-2549-There-are-two-logic-errors-when-installi.patch
> There are two logic errors when installing the solr audit log module
>
>
> Key: RANGER-2549
> URL: https://issues.apache.org/jira/browse/RANGER-2549
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.1.0
>Reporter: wu.kehua
>Assignee: wu.kehua
>Priority: Major
> Labels: patch
> Attachments:
> 0001-RANGER-2549-There-are-two-logic-errors-when-installi.patch
>
>
> The install.sh will print 'Command not found' when installing the solr audit
> log module, as follow:
> {code:java}
> [root@wkh001 solr_for_audit_setup]# ./setup.sh
> ./setup.sh: line 29: log: Command not found
> {code}
> Then I analyse the install.sh, there is one error code, as follow:
> {code:java}
> if test -z "$validateProperty" ; then log "[E] '$1' not found in $2 file
> while getting!!"; exit 1; fi
> {code}
> Because the function log is undefined, and in other places, we use echo to
> print log, We need to be unified as 'echo'.
> When I modify this bug, then execute setup.sh, it shows another error, as
> follow:
> {code:java}
> setup.sh: line 68:[: Too many parameters
> {code}
> Then I find another logic bug, if you don't config JAVA_HOME in
> install.properties, CONFIG_JAVA_HOME will get an error message and influence
> subsequent processe.
> {code:java}
> CONFIG_JAVA_HOME=$(get_prop 'JAVA_HOME' $PROPFILE)
> JAVA_HOME=${CONFIG_JAVA_HOME:-$JAVA_HOME}
> {code}
> So I modified two places, and test in three scenes, first is that JAVA_HOME
> is nonexistent, second is that JAVA_HOME is not configured, like
> 'JAVA_HOME=', third is that JAVA_HOME is configured.
> Please check my patch, thanks.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (RANGER-2549) There are two logic errors when installing the solr audit log module
[
https://issues.apache.org/jira/browse/RANGER-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wu.kehua updated RANGER-2549:
-
Description:
The install.sh will print 'Command not found' when installing the solr audit
log module, as follow:
{code:java}
[root@wkh001 solr_for_audit_setup]# ./setup.sh
./setup.sh: line 29: log: Command not found
{code}
Then I analyse the install.sh, there is one error code, as follow:
{code:java}
if test -z "$validateProperty" ; then log "[E] '$1' not found in $2 file while
getting!!"; exit 1; fi
{code}
Because the function log is undefined, and in other places, we use echo to
print log, We need to be unified as 'echo'.
When I modify this bug, then execute setup.sh, it shows another error, as
follow:
{code:java}
setup.sh: line 68:[: Too many parameters
{code}
Then I find another logic bug, if you don't config JAVA_HOME in
install.properties, CONFIG_JAVA_HOME will get an error message and influence
subsequent processe.
{code:java}
CONFIG_JAVA_HOME=$(get_prop 'JAVA_HOME' $PROPFILE)
JAVA_HOME=${CONFIG_JAVA_HOME:-$JAVA_HOME}
{code}
So I modified two places, and test in three scenes, first is that JAVA_HOME is
nonexistent, second is that JAVA_HOME is not configured, like 'JAVA_HOME=',
third is that JAVA_HOME is configured.
Please check my patch, thanks.
was:
The install.sh will print 'Command not found' when installing the solr audit
log module, as follow:
{code:java}
[root@wkh001 solr_for_audit_setup]# ./setup.sh
./setup.sh: line 29: log: Command not found
{code}
Then I analyse the install.sh, there is one error code, as follow:
{code:java}
if test -z "$validateProperty" ; then log "[E] '$1' not found in $2 file while
getting!!"; exit 1; fi
{code}
Because the function log is undefined, and in other places, we use echo to
print log, We need to be unified as 'echo'.
When I modify this bug, then execute setup.sh, it shows another error, as
follow:
{code:java}
setup.sh: line 68:[: Too many parameters
{code}
Then I find another logic bug, if you don't config JAVA_HOME in
install.properties, CONFIG_JAVA_HOME will get an error message and influence
subsequent processe.
{code:java}
CONFIG_JAVA_HOME=$(get_prop 'JAVA_HOME' $PROPFILE)
JAVA_HOME=${CONFIG_JAVA_HOME:-$JAVA_HOME}
{code}
So I modified two places, and test in two scenes, one is that JAVA_HOME is not
configured, another is JAVA_HOME is configured.
Please check my patch, thanks.
> There are two logic errors when installing the solr audit log module
>
>
> Key: RANGER-2549
> URL: https://issues.apache.org/jira/browse/RANGER-2549
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.1.0
>Reporter: wu.kehua
>Assignee: wu.kehua
>Priority: Major
> Labels: patch
> Attachments:
> 0001-RANGER-2549-There-are-two-logic-errors-when-installi.patch
>
>
> The install.sh will print 'Command not found' when installing the solr audit
> log module, as follow:
> {code:java}
> [root@wkh001 solr_for_audit_setup]# ./setup.sh
> ./setup.sh: line 29: log: Command not found
> {code}
> Then I analyse the install.sh, there is one error code, as follow:
> {code:java}
> if test -z "$validateProperty" ; then log "[E] '$1' not found in $2 file
> while getting!!"; exit 1; fi
> {code}
> Because the function log is undefined, and in other places, we use echo to
> print log, We need to be unified as 'echo'.
> When I modify this bug, then execute setup.sh, it shows another error, as
> follow:
> {code:java}
> setup.sh: line 68:[: Too many parameters
> {code}
> Then I find another logic bug, if you don't config JAVA_HOME in
> install.properties, CONFIG_JAVA_HOME will get an error message and influence
> subsequent processe.
> {code:java}
> CONFIG_JAVA_HOME=$(get_prop 'JAVA_HOME' $PROPFILE)
> JAVA_HOME=${CONFIG_JAVA_HOME:-$JAVA_HOME}
> {code}
> So I modified two places, and test in three scenes, first is that JAVA_HOME
> is nonexistent, second is that JAVA_HOME is not configured, like
> 'JAVA_HOME=', third is that JAVA_HOME is configured.
> Please check my patch, thanks.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (RANGER-2549) There are two logic errors when installing the solr audit log module
[
https://issues.apache.org/jira/browse/RANGER-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wu.kehua updated RANGER-2549:
-
Attachment: 0001-RANGER-2549-There-are-two-logic-errors-when-installi.patch
> There are two logic errors when installing the solr audit log module
>
>
> Key: RANGER-2549
> URL: https://issues.apache.org/jira/browse/RANGER-2549
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.1.0
>Reporter: wu.kehua
>Assignee: wu.kehua
>Priority: Major
> Labels: patch
> Attachments:
> 0001-RANGER-2549-There-are-two-logic-errors-when-installi.patch
>
>
> The install.sh will print 'Command not found' when installing the solr audit
> log module, as follow:
> {code:java}
> [root@wkh001 solr_for_audit_setup]# ./setup.sh
> ./setup.sh: line 29: log: Command not found
> {code}
> Then I analyse the install.sh, there is one error code, as follow:
> {code:java}
> if test -z "$validateProperty" ; then log "[E] '$1' not found in $2 file
> while getting!!"; exit 1; fi
> {code}
> Because the function log is undefined, and in other places, we use echo to
> print log, We need to be unified as 'echo'.
> When I modify this bug, then execute setup.sh, it shows another error, as
> follow:
> {code:java}
> setup.sh: line 68:[: Too many parameters
> {code}
> Then I find another logic bug, if you don't config JAVA_HOME in
> install.properties, CONFIG_JAVA_HOME will get an error message and influence
> subsequent processe.
> {code:java}
> CONFIG_JAVA_HOME=$(get_prop 'JAVA_HOME' $PROPFILE)
> JAVA_HOME=${CONFIG_JAVA_HOME:-$JAVA_HOME}
> {code}
> So I modified two places, and test in two scenes, one is that JAVA_HOME is
> not configured, another is JAVA_HOME is configured.
> Please check my patch, thanks.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (RANGER-2549) There are two logic errors when installing the solr audit log module
[
https://issues.apache.org/jira/browse/RANGER-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wu.kehua updated RANGER-2549:
-
Attachment: (was:
0001-RANGER-2549-There-is-two-logic-errors-when-installin.patch)
> There are two logic errors when installing the solr audit log module
>
>
> Key: RANGER-2549
> URL: https://issues.apache.org/jira/browse/RANGER-2549
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.1.0
>Reporter: wu.kehua
>Assignee: wu.kehua
>Priority: Major
> Labels: patch
>
> The install.sh will print 'Command not found' when installing the solr audit
> log module, as follow:
> {code:java}
> [root@wkh001 solr_for_audit_setup]# ./setup.sh
> ./setup.sh: line 29: log: Command not found
> {code}
> Then I analyse the install.sh, there is one error code, as follow:
> {code:java}
> if test -z "$validateProperty" ; then log "[E] '$1' not found in $2 file
> while getting!!"; exit 1; fi
> {code}
> Because the function log is undefined, and in other places, we use echo to
> print log, We need to be unified as 'echo'.
> When I modify this bug, then execute setup.sh, it shows another error, as
> follow:
> {code:java}
> setup.sh: line 68:[: Too many parameters
> {code}
> Then I find another logic bug, if you don't config JAVA_HOME in
> install.properties, CONFIG_JAVA_HOME will get an error message and influence
> subsequent processe.
> {code:java}
> CONFIG_JAVA_HOME=$(get_prop 'JAVA_HOME' $PROPFILE)
> JAVA_HOME=${CONFIG_JAVA_HOME:-$JAVA_HOME}
> {code}
> So I modified two places, and test in two scenes, one is that JAVA_HOME is
> not configured, another is JAVA_HOME is configured.
> Please check my patch, thanks.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (RANGER-2549) There are two logic errors when installing the solr audit log module
[
https://issues.apache.org/jira/browse/RANGER-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wu.kehua updated RANGER-2549:
-
Summary: There are two logic errors when installing the solr audit log
module (was: There is two logic errors when installing the solr audit log
module)
> There are two logic errors when installing the solr audit log module
>
>
> Key: RANGER-2549
> URL: https://issues.apache.org/jira/browse/RANGER-2549
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.1.0
>Reporter: wu.kehua
>Assignee: wu.kehua
>Priority: Major
> Labels: patch
> Attachments:
> 0001-RANGER-2549-There-is-two-logic-errors-when-installin.patch
>
>
> The install.sh will print 'Command not found' when installing the solr audit
> log module, as follow:
> {code:java}
> [root@wkh001 solr_for_audit_setup]# ./setup.sh
> ./setup.sh: line 29: log: Command not found
> {code}
> Then I analyse the install.sh, there is one error code, as follow:
> {code:java}
> if test -z "$validateProperty" ; then log "[E] '$1' not found in $2 file
> while getting!!"; exit 1; fi
> {code}
> Because the function log is undefined, and in other places, we use echo to
> print log, We need to be unified as 'echo'.
> When I modify this bug, then execute setup.sh, it shows another error, as
> follow:
> {code:java}
> setup.sh: line 68:[: Too many parameters
> {code}
> Then I find another logic bug, if you don't config JAVA_HOME in
> install.properties, CONFIG_JAVA_HOME will get an error message and influence
> subsequent processe.
> {code:java}
> CONFIG_JAVA_HOME=$(get_prop 'JAVA_HOME' $PROPFILE)
> JAVA_HOME=${CONFIG_JAVA_HOME:-$JAVA_HOME}
> {code}
> So I modified two places, and test in two scenes, one is that JAVA_HOME is
> not configured, another is JAVA_HOME is configured.
> Please check my patch, thanks.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (RANGER-2549) There is two logic errors when installing the solr audit log module
[
https://issues.apache.org/jira/browse/RANGER-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wu.kehua updated RANGER-2549:
-
Attachment: 0001-RANGER-2549-There-is-two-logic-errors-when-installin.patch
> There is two logic errors when installing the solr audit log module
> ---
>
> Key: RANGER-2549
> URL: https://issues.apache.org/jira/browse/RANGER-2549
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.1.0
>Reporter: wu.kehua
>Assignee: wu.kehua
>Priority: Major
> Labels: patch
> Attachments:
> 0001-RANGER-2549-There-is-two-logic-errors-when-installin.patch
>
>
> The install.sh will print 'Command not found' when installing the solr audit
> log module, as follow:
> {code:java}
> [root@wkh001 solr_for_audit_setup]# ./setup.sh
> ./setup.sh: line 29: log: Command not found
> {code}
> Then I analyse the install.sh, there is one error code, as follow:
> {code:java}
> if test -z "$validateProperty" ; then log "[E] '$1' not found in $2 file
> while getting!!"; exit 1; fi
> {code}
> Because the function log is undefined, and in other places, we use echo to
> print log, We need to be unified as 'echo'.
> When I modify this bug, then execute setup.sh, it shows another error, as
> follow:
> {code:java}
> setup.sh: line 68:[: Too many parameters
> {code}
> Then I find another logic bug, if you don't config JAVA_HOME in
> install.properties, CONFIG_JAVA_HOME will get an error message and influence
> subsequent processe.
> {code:java}
> CONFIG_JAVA_HOME=$(get_prop 'JAVA_HOME' $PROPFILE)
> JAVA_HOME=${CONFIG_JAVA_HOME:-$JAVA_HOME}
> {code}
> So I modified two places, and test in two scenes, one is that JAVA_HOME is
> not configured, another is JAVA_HOME is configured.
> Please check my patch, thanks.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (RANGER-2549) There is two logic errors when installing the solr audit log module
[
https://issues.apache.org/jira/browse/RANGER-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wu.kehua updated RANGER-2549:
-
Priority: Major (was: Trivial)
> There is two logic errors when installing the solr audit log module
> ---
>
> Key: RANGER-2549
> URL: https://issues.apache.org/jira/browse/RANGER-2549
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.1.0
>Reporter: wu.kehua
>Assignee: wu.kehua
>Priority: Major
> Labels: patch
>
> The install.sh will print 'Command not found' when installing the solr audit
> log module, as follow:
> {code:java}
> [root@wkh001 solr_for_audit_setup]# ./setup.sh
> ./setup.sh: line 29: log: Command not found
> {code}
> Then I analyse the install.sh, there is one error code, as follow:
> {code:java}
> if test -z "$validateProperty" ; then log "[E] '$1' not found in $2 file
> while getting!!"; exit 1; fi
> {code}
> Because the function log is undefined, and in other places, we use echo to
> print log, We need to be unified as 'echo'.
> When I modify this bug, then execute setup.sh, it shows another error, as
> follow:
> {code:java}
> setup.sh: line 68:[: Too many parameters
> {code}
> Then I find another logic bug, if you don't config JAVA_HOME in
> install.properties, CONFIG_JAVA_HOME will get an error message and influence
> subsequent processe.
> {code:java}
> CONFIG_JAVA_HOME=$(get_prop 'JAVA_HOME' $PROPFILE)
> JAVA_HOME=${CONFIG_JAVA_HOME:-$JAVA_HOME}
> {code}
> So I modified two places, and test in two scenes, one is that JAVA_HOME is
> not configured, another is JAVA_HOME is configured.
> Please check my patch, thanks.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (RANGER-2549) There is two logic errors when installing the solr audit log module
[
https://issues.apache.org/jira/browse/RANGER-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wu.kehua updated RANGER-2549:
-
Description:
The install.sh will print 'Command not found' when installing the solr audit
log module, as follow:
{code:java}
[root@wkh001 solr_for_audit_setup]# ./setup.sh
./setup.sh: line 29: log: Command not found
{code}
Then I analyse the install.sh, there is one error code, as follow:
{code:java}
if test -z "$validateProperty" ; then log "[E] '$1' not found in $2 file while
getting!!"; exit 1; fi
{code}
Because the function log is undefined, and in other places, we use echo to
print log, We need to be unified as 'echo'.
When I modify this bug, then execute setup.sh, it shows another error, as
follow:
{code:java}
setup.sh: line 68:[: Too many parameters
{code}
Then I find another logic bug, if you don't config JAVA_HOME in
install.properties, CONFIG_JAVA_HOME will get an error message and influence
subsequent processe.
{code:java}
CONFIG_JAVA_HOME=$(get_prop 'JAVA_HOME' $PROPFILE)
JAVA_HOME=${CONFIG_JAVA_HOME:-$JAVA_HOME}
{code}
So I modified two places, and test in two scenes, one is that JAVA_HOME is not
configured, another is JAVA_HOME is configured.
Please check my patch, thanks.
was:
The install.sh will print 'Command not found' when installing the solr audit
log module, as follow:
{code:java}
[root@wkh001 solr_for_audit_setup]# ./setup.sh
./setup.sh: line 29: log: Command not found
{code}
Then I analyse the install.sh, there is one error code, as follow:
{code:java}
if test -z "$validateProperty" ; then log "[E] '$1' not found in $2 file while
getting!!"; exit 1; fi
{code}
Because the function log is undefined, and in other places, we use echo to
print log, We need to be unified as 'echo'.
When I modify this bug, then execute setup.sh, it shows another error, as
follow:
{code:java}
setup.sh: line 68:[: Too many parameters
{code}
Then I find another logic bug, if you don't config JAVA_HOME in
install.properties, CONFIG_JAVA_HOME will get an error message and influence
subsequent processe.
{code:java}
CONFIG_JAVA_HOME=$(get_prop 'JAVA_HOME' $PROPFILE)
JAVA_HOME=${CONFIG_JAVA_HOME:-$JAVA_HOME}
{code}
So I modified two places, and test in two scenes, one is that JAVA_HOME is not
configured, another is JAVA_HOME is configured.
Please check my patch, thanks.
> There is two logic errors when installing the solr audit log module
> ---
>
> Key: RANGER-2549
> URL: https://issues.apache.org/jira/browse/RANGER-2549
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.1.0
>Reporter: wu.kehua
>Assignee: wu.kehua
>Priority: Trivial
> Labels: patch
>
> The install.sh will print 'Command not found' when installing the solr audit
> log module, as follow:
> {code:java}
> [root@wkh001 solr_for_audit_setup]# ./setup.sh
> ./setup.sh: line 29: log: Command not found
> {code}
> Then I analyse the install.sh, there is one error code, as follow:
> {code:java}
> if test -z "$validateProperty" ; then log "[E] '$1' not found in $2 file
> while getting!!"; exit 1; fi
> {code}
> Because the function log is undefined, and in other places, we use echo to
> print log, We need to be unified as 'echo'.
> When I modify this bug, then execute setup.sh, it shows another error, as
> follow:
> {code:java}
> setup.sh: line 68:[: Too many parameters
> {code}
> Then I find another logic bug, if you don't config JAVA_HOME in
> install.properties, CONFIG_JAVA_HOME will get an error message and influence
> subsequent processe.
> {code:java}
> CONFIG_JAVA_HOME=$(get_prop 'JAVA_HOME' $PROPFILE)
> JAVA_HOME=${CONFIG_JAVA_HOME:-$JAVA_HOME}
> {code}
> So I modified two places, and test in two scenes, one is that JAVA_HOME is
> not configured, another is JAVA_HOME is configured.
> Please check my patch, thanks.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (RANGER-2549) There is two logic errors when installing the solr audit log module
[
https://issues.apache.org/jira/browse/RANGER-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wu.kehua updated RANGER-2549:
-
Summary: There is two logic errors when installing the solr audit log
module (was: There is an error log when installing the solr audit log module)
> There is two logic errors when installing the solr audit log module
> ---
>
> Key: RANGER-2549
> URL: https://issues.apache.org/jira/browse/RANGER-2549
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.1.0
>Reporter: wu.kehua
>Assignee: wu.kehua
>Priority: Trivial
> Labels: patch
>
> The install.sh will print 'Command not found' when installing the solr audit
> log module, as follow:
>
> {code:java}
> [root@wkh001 solr_for_audit_setup]# ./setup.sh
> ./setup.sh: line 29: log: Command not found
> {code}
> Then I analyse the install.sh, there is one error code, as follow:
>
>
> {code:java}
> if test -z "$validateProperty" ; then log "[E] '$1' not found in $2 file
> while getting!!"; exit 1; fi
> {code}
> Because the function log is undefined, and in other places, we use echo to
> print log, We need to be unified as 'echo'.
>
> When I modify this bug, then execute setup.sh, it shows another error, as
> follow:
>
> {code:java}
> setup.sh: line 68:[: Too many parameters
> {code}
> Then I find another logic bug, if you don't config JAVA_HOME in
> install.properties, CONFIG_JAVA_HOME will get an error message and influence
> subsequent processe.
>
>
> {code:java}
> CONFIG_JAVA_HOME=$(get_prop 'JAVA_HOME' $PROPFILE)
> JAVA_HOME=${CONFIG_JAVA_HOME:-$JAVA_HOME}
> {code}
> So I modified two places, and test in two scenes, one is that JAVA_HOME is
> not configured, another is JAVA_HOME is configured.
>
> Please check my patch, thanks.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Created] (RANGER-2549) There is an error log when installing the solr audit log module
wu.kehua created RANGER-2549:
Summary: There is an error log when installing the solr audit log
module
Key: RANGER-2549
URL: https://issues.apache.org/jira/browse/RANGER-2549
Project: Ranger
Issue Type: Bug
Components: Ranger
Affects Versions: 2.1.0
Reporter: wu.kehua
Assignee: wu.kehua
The install.sh will print 'Command not found' when installing the solr audit
log module, as follow:
{code:java}
[root@wkh001 solr_for_audit_setup]# ./setup.sh
./setup.sh: line 29: log: Command not found
{code}
Then I analyse the install.sh, there is one error code, as follow:
{code:java}
if test -z "$validateProperty" ; then log "[E] '$1' not found in $2 file while
getting!!"; exit 1; fi
{code}
Because the function log is undefined, and in other places, we use echo to
print log, We need to be unified as 'echo'.
When I modify this bug, then execute setup.sh, it shows another error, as
follow:
{code:java}
setup.sh: line 68:[: Too many parameters
{code}
Then I find another logic bug, if you don't config JAVA_HOME in
install.properties, CONFIG_JAVA_HOME will get an error message and influence
subsequent processe.
{code:java}
CONFIG_JAVA_HOME=$(get_prop 'JAVA_HOME' $PROPFILE)
JAVA_HOME=${CONFIG_JAVA_HOME:-$JAVA_HOME}
{code}
So I modified two places, and test in two scenes, one is that JAVA_HOME is not
configured, another is JAVA_HOME is configured.
Please check my patch, thanks.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (RANGER-2540) When we create a new Solr service, the 'Solr URL' doesn't show a hit that we don't know how to use it.
[ https://issues.apache.org/jira/browse/RANGER-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wu.kehua updated RANGER-2540: - Affects Version/s: 2.1.0 1.2.0 > When we create a new Solr service, the 'Solr URL' doesn't show a hit that we > don't know how to use it. > -- > > Key: RANGER-2540 > URL: https://issues.apache.org/jira/browse/RANGER-2540 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.2.0, 2.1.0 >Reporter: wu.kehua >Assignee: wu.kehua >Priority: Trivial > Labels: patch > Attachments: > 0001-RANGER-2540-When-we-create-a-new-Solr-service-the-So.patch, > image-2019-08-20-09-09-44-818.png > > > When we create a new Solr service, the 'Solr URL' doesn't show a hit that we > don't know how to use it. As follow picture: > !image-2019-08-20-09-09-44-818.png! -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (RANGER-2540) When we create a new Solr service, the 'Solr URL' doesn't show a hit that we don't know how to use it.
[ https://issues.apache.org/jira/browse/RANGER-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wu.kehua updated RANGER-2540: - Fix Version/s: (was: 2.1.0) (was: 1.2.0) > When we create a new Solr service, the 'Solr URL' doesn't show a hit that we > don't know how to use it. > -- > > Key: RANGER-2540 > URL: https://issues.apache.org/jira/browse/RANGER-2540 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: wu.kehua >Assignee: wu.kehua >Priority: Trivial > Labels: patch > Attachments: > 0001-RANGER-2540-When-we-create-a-new-Solr-service-the-So.patch, > image-2019-08-20-09-09-44-818.png > > > When we create a new Solr service, the 'Solr URL' doesn't show a hit that we > don't know how to use it. As follow picture: > !image-2019-08-20-09-09-44-818.png! -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Issue Comment Deleted] (RANGER-2540) When we create a new Solr service, the 'Solr URL' doesn't show a hit that we don't know how to use it.
[ https://issues.apache.org/jira/browse/RANGER-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wu.kehua updated RANGER-2540: - Comment: was deleted (was: Hi, [~vperiasamy] Please added me as contributor and assigned this Jira to me, thank you very much.) > When we create a new Solr service, the 'Solr URL' doesn't show a hit that we > don't know how to use it. > -- > > Key: RANGER-2540 > URL: https://issues.apache.org/jira/browse/RANGER-2540 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: wu.kehua >Assignee: wu.kehua >Priority: Trivial > Labels: patch > Fix For: 1.2.0, 2.1.0 > > Attachments: > 0001-RANGER-2540-When-we-create-a-new-Solr-service-the-So.patch, > image-2019-08-20-09-09-44-818.png > > > When we create a new Solr service, the 'Solr URL' doesn't show a hit that we > don't know how to use it. As follow picture: > !image-2019-08-20-09-09-44-818.png! -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (RANGER-2540) When we create a new Solr service, the 'Solr URL' doesn't show a hit that we don't know how to use it.
[ https://issues.apache.org/jira/browse/RANGER-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wu.kehua reassigned RANGER-2540: Assignee: wu.kehua > When we create a new Solr service, the 'Solr URL' doesn't show a hit that we > don't know how to use it. > -- > > Key: RANGER-2540 > URL: https://issues.apache.org/jira/browse/RANGER-2540 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: wu.kehua >Assignee: wu.kehua >Priority: Trivial > Labels: patch > Fix For: 1.2.0, 2.1.0 > > Attachments: > 0001-RANGER-2540-When-we-create-a-new-Solr-service-the-So.patch, > image-2019-08-20-09-09-44-818.png > > > When we create a new Solr service, the 'Solr URL' doesn't show a hit that we > don't know how to use it. As follow picture: > !image-2019-08-20-09-09-44-818.png! -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (RANGER-2540) When we create a new Solr service, the 'Solr URL' doesn't show a hit that we don't know how to use it.
[ https://issues.apache.org/jira/browse/RANGER-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wu.kehua updated RANGER-2540: - Attachment: (was: 0001-RANGER-2540-When-we-create-a-new-Solr-service-the-So.patch) > When we create a new Solr service, the 'Solr URL' doesn't show a hit that we > don't know how to use it. > -- > > Key: RANGER-2540 > URL: https://issues.apache.org/jira/browse/RANGER-2540 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: wu.kehua >Priority: Trivial > Labels: patch > Fix For: 1.2.0, 2.1.0 > > Attachments: > 0001-RANGER-2540-When-we-create-a-new-Solr-service-the-So.patch, > image-2019-08-20-09-09-44-818.png > > > When we create a new Solr service, the 'Solr URL' doesn't show a hit that we > don't know how to use it. As follow picture: > !image-2019-08-20-09-09-44-818.png! -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (RANGER-2540) When we create a new Solr service, the 'Solr URL' doesn't show a hit that we don't know how to use it.
[ https://issues.apache.org/jira/browse/RANGER-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wu.kehua updated RANGER-2540: - Attachment: 0001-RANGER-2540-When-we-create-a-new-Solr-service-the-So.patch > When we create a new Solr service, the 'Solr URL' doesn't show a hit that we > don't know how to use it. > -- > > Key: RANGER-2540 > URL: https://issues.apache.org/jira/browse/RANGER-2540 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: wu.kehua >Priority: Trivial > Labels: patch > Fix For: 1.2.0, 2.1.0 > > Attachments: > 0001-RANGER-2540-When-we-create-a-new-Solr-service-the-So.patch, > image-2019-08-20-09-09-44-818.png > > > When we create a new Solr service, the 'Solr URL' doesn't show a hit that we > don't know how to use it. As follow picture: > !image-2019-08-20-09-09-44-818.png! -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (RANGER-2540) When we create a new Solr service, the 'Solr URL' doesn't show a hit that we don't know how to use it.
[ https://issues.apache.org/jira/browse/RANGER-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wu.kehua updated RANGER-2540: - Fix Version/s: 1.2.0 2.1.0 > When we create a new Solr service, the 'Solr URL' doesn't show a hit that we > don't know how to use it. > -- > > Key: RANGER-2540 > URL: https://issues.apache.org/jira/browse/RANGER-2540 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: wu.kehua >Priority: Trivial > Labels: patch > Fix For: 1.2.0, 2.1.0 > > Attachments: > 0001-RANGER-2540-When-we-create-a-new-Solr-service-the-So.patch, > image-2019-08-20-09-09-44-818.png > > > When we create a new Solr service, the 'Solr URL' doesn't show a hit that we > don't know how to use it. As follow picture: > !image-2019-08-20-09-09-44-818.png! -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (RANGER-2540) When we create a new Solr service, the 'Solr URL' doesn't show a hit that we don't know how to use it.
[ https://issues.apache.org/jira/browse/RANGER-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wu.kehua updated RANGER-2540: - Attachment: 0001-RANGER-2540-When-we-create-a-new-Solr-service-the-So.patch > When we create a new Solr service, the 'Solr URL' doesn't show a hit that we > don't know how to use it. > -- > > Key: RANGER-2540 > URL: https://issues.apache.org/jira/browse/RANGER-2540 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: wu.kehua >Priority: Trivial > Labels: patch > Attachments: > 0001-RANGER-2540-When-we-create-a-new-Solr-service-the-So.patch, > image-2019-08-20-09-09-44-818.png > > > When we create a new Solr service, the 'Solr URL' doesn't show a hit that we > don't know how to use it. As follow picture: > !image-2019-08-20-09-09-44-818.png! -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (RANGER-2540) When we create a new Solr service, the 'Solr URL' doesn't show a hit that we don't know how to use it.
[ https://issues.apache.org/jira/browse/RANGER-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16911012#comment-16911012 ] wu.kehua commented on RANGER-2540: -- Hi, [~vperiasamy] Please added me as contributor and assigned this Jira to me, thank you very much. > When we create a new Solr service, the 'Solr URL' doesn't show a hit that we > don't know how to use it. > -- > > Key: RANGER-2540 > URL: https://issues.apache.org/jira/browse/RANGER-2540 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: wu.kehua >Priority: Trivial > Labels: patch > Attachments: image-2019-08-20-09-09-44-818.png > > > When we create a new Solr service, the 'Solr URL' doesn't show a hit that we > don't know how to use it. As follow picture: > !image-2019-08-20-09-09-44-818.png! -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (RANGER-2540) When we create a new Solr service, the 'Solr URL' doesn't show a hit that we don't know how to use it.
[ https://issues.apache.org/jira/browse/RANGER-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16910879#comment-16910879 ] wu.kehua commented on RANGER-2540: -- Please assign this issue to me, thanks. > When we create a new Solr service, the 'Solr URL' doesn't show a hit that we > don't know how to use it. > -- > > Key: RANGER-2540 > URL: https://issues.apache.org/jira/browse/RANGER-2540 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: wu.kehua >Priority: Trivial > Labels: patch > Attachments: image-2019-08-20-09-09-44-818.png > > > When we create a new Solr service, the 'Solr URL' doesn't show a hit that we > don't know how to use it. As follow picture: > !image-2019-08-20-09-05-39-546.png! -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (RANGER-2540) When we create a new Solr service, the 'Solr URL' doesn't show a hit that we don't know how to use it.
[ https://issues.apache.org/jira/browse/RANGER-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wu.kehua updated RANGER-2540: - Description: When we create a new Solr service, the 'Solr URL' doesn't show a hit that we don't know how to use it. As follow picture: !image-2019-08-20-09-09-44-818.png! was: When we create a new Solr service, the 'Solr URL' doesn't show a hit that we don't know how to use it. As follow picture: !image-2019-08-20-09-05-39-546.png! > When we create a new Solr service, the 'Solr URL' doesn't show a hit that we > don't know how to use it. > -- > > Key: RANGER-2540 > URL: https://issues.apache.org/jira/browse/RANGER-2540 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: wu.kehua >Priority: Trivial > Labels: patch > Attachments: image-2019-08-20-09-09-44-818.png > > > When we create a new Solr service, the 'Solr URL' doesn't show a hit that we > don't know how to use it. As follow picture: > !image-2019-08-20-09-09-44-818.png! -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (RANGER-2540) When we create a new Solr service, the 'Solr URL' doesn't show a hit that we don't know how to use it.
[ https://issues.apache.org/jira/browse/RANGER-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wu.kehua updated RANGER-2540: - Attachment: image-2019-08-20-09-09-44-818.png > When we create a new Solr service, the 'Solr URL' doesn't show a hit that we > don't know how to use it. > -- > > Key: RANGER-2540 > URL: https://issues.apache.org/jira/browse/RANGER-2540 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: wu.kehua >Priority: Trivial > Labels: patch > Attachments: image-2019-08-20-09-09-44-818.png > > > When we create a new Solr service, the 'Solr URL' doesn't show a hit that we > don't know how to use it. As follow picture: > !image-2019-08-20-09-05-39-546.png! -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (RANGER-2540) When we create a new Solr service, the 'Solr URL' doesn't show a hit that we don't know how to use it.
wu.kehua created RANGER-2540: Summary: When we create a new Solr service, the 'Solr URL' doesn't show a hit that we don't know how to use it. Key: RANGER-2540 URL: https://issues.apache.org/jira/browse/RANGER-2540 Project: Ranger Issue Type: Bug Components: Ranger Reporter: wu.kehua When we create a new Solr service, the 'Solr URL' doesn't show a hit that we don't know how to use it. As follow picture: !image-2019-08-20-09-05-39-546.png! -- This message was sent by Atlassian Jira (v8.3.2#803003)
