Re: Review Request 57443: Useless configuration in unixauthservice pom.xml lead to project compiler error in eclipse
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/57443/
---
(Updated 七月 5, 2017, 3:37 a.m.)
Review request for ranger, Ankita Sinha, Don Bosco Durai, Colm O hEigeartaigh,
Gautam Borad, Madhan Neethiraj, Ramesh Mani, Selvamohan Neethiraj, and
Velmurugan Periasamy.
Bugs: RANGER-1438
https://issues.apache.org/jira/browse/RANGER-1438
Repository: ranger
Description
---
Useless configuration in unixauthservice pom.xml lead to project compiler error
in eclipse
Steps
In windows environment, enter into ranger project root directory
1.Execute : mvn clean compile package install assembly:assembly -DskipTests -X
2.Execute :mvn eclipse:eclipse -X
When the maven project convert into eclipse project occurred error:
[[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-eclipse-plugin:2.10:eclipse (default-cli) on
project unixauthservice: Cant canonicalize system path:
{0}: -> [Help 1]
Caused by: org.apache.maven.plugin.MojoExecutionException: Cant canonicalize
system path: {0}
]
3.Remove unless code in unixauthservice pom.xml
$
{project.build.outputDirectory}
conf.dist
log4j.properties
4.Rerun : mvn clean compile package install assembly:assembly -DskipTests -X
5.Rerun :mvn eclipse:eclipse -X (result:sucessed)
6.Check whether affect the Usersync Components work
1).Install the ranger-1.0.0-SNAPSHOT-usersync module in a new machine
2).and Reinstall the ranger-1.0.0-SNAPSHOT-usersync module in original machine
3)result:both work well ( Log upload in the attachment)
Diffs (updated)
-
unixauthservice/pom.xml cc8fb1c
unixauthservice/src/main/resources/log4j.properties PRE-CREATION
Diff: https://reviews.apache.org/r/57443/diff/3/
Changes: https://reviews.apache.org/r/57443/diff/2-3/
Testing
---
tested it
Thanks,
Qiang Zhang
Re: Review Request 57443: Useless configuration in unixauthservice pom.xml lead to project compiler error in eclipse
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/57443/
---
(Updated 七月 5, 2017, 3:30 a.m.)
Review request for ranger, Ankita Sinha, Don Bosco Durai, Colm O hEigeartaigh,
Gautam Borad, Madhan Neethiraj, Ramesh Mani, Selvamohan Neethiraj, and
Velmurugan Periasamy.
Changes
---
Create resource add log4j.properties
Bugs: RANGER-1438
https://issues.apache.org/jira/browse/RANGER-1438
Repository: ranger
Description
---
Useless configuration in unixauthservice pom.xml lead to project compiler error
in eclipse
Steps
In windows environment, enter into ranger project root directory
1.Execute : mvn clean compile package install assembly:assembly -DskipTests -X
2.Execute :mvn eclipse:eclipse -X
When the maven project convert into eclipse project occurred error:
[[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-eclipse-plugin:2.10:eclipse (default-cli) on
project unixauthservice: Cant canonicalize system path:
{0}: -> [Help 1]
Caused by: org.apache.maven.plugin.MojoExecutionException: Cant canonicalize
system path: {0}
]
3.Remove unless code in unixauthservice pom.xml
$
{project.build.outputDirectory}
conf.dist
log4j.properties
4.Rerun : mvn clean compile package install assembly:assembly -DskipTests -X
5.Rerun :mvn eclipse:eclipse -X (result:sucessed)
6.Check whether affect the Usersync Components work
1).Install the ranger-1.0.0-SNAPSHOT-usersync module in a new machine
2).and Reinstall the ranger-1.0.0-SNAPSHOT-usersync module in original machine
3)result:both work well ( Log upload in the attachment)
Diffs (updated)
-
unixauthservice/pom.xml cc8fb1c
unixauthservice/src/main/resources/log4j.properties PRE-CREATION
Diff: https://reviews.apache.org/r/57443/diff/2/
Changes: https://reviews.apache.org/r/57443/diff/1-2/
Testing
---
tested it
Thanks,
Qiang Zhang
[jira] [Commented] (RANGER-1672) Ranger supports plugin to enable, monitor and manage apache kylin
[ https://issues.apache.org/jira/browse/RANGER-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073995#comment-16073995 ] Srikanth Venkat commented on RANGER-1672: - This is a great feature to add, thanks Qiang for the contribution. Few questions: 1) Where are the OLAP cubes and project information associated with Kylin stored? In HDFS or externally? 2) A Ranger plugin without auditing feature is not very useful for the community from a security perspective, so this plugin should support writing audits using Ranger's audit framework (writing raw audits to HDFS and indexing in Solr for querying). Kylin Ranger plugin should support auditing to capture the same level of audit event metadata that other services in Hadoop provide. 3) Does Kylin have a server side component (such as HiveServer2) or is only a client set of libraries? How will this plugin be deployed if it is client side only? Does Kylin support doAs (impersonation) if there is a server side component? 4) Is there a need to support dynamic policies for authorizing OLAP cubes and projects? 5) Does Kylin already have any LDAP/AD authentication integration and support the Hadoop user-group mapping facility? Without this group resolution will need to be thought through carefully for the plugin implementation. > Ranger supports plugin to enable, monitor and manage apache kylin > - > > Key: RANGER-1672 > URL: https://issues.apache.org/jira/browse/RANGER-1672 > Project: Ranger > Issue Type: New Feature > Components: plugins >Reporter: Qiang Zhang >Assignee: Qiang Zhang > Labels: newbie, patch > > Apache Kylin is an open source Distributed Analytics Engine designed to > provide SQL interface and multi-dimensional analysis (OLAP) on Hadoop > supporting extremely large datasets, original contributed from eBay Inc. > Apache Kylin lets user query massive data set at sub-second latency in 3 > steps. > 1. Identify a Star Schema on Hadoop. > 2. Build Cube from the identified tables. > 3. Query with ANSI-SQL and get results in sub-second, via ODBC, JDBC or > RESTful API. > We should support that using Ranger to control kylin's access rights for > project and cube. > Specific implementation plan is as following: > On the ranger website, administrators can configure policies to control user > access to projects and cube permissions. > Kylin provides an abstract class and authorization interfaces for use by the > ranger plugin. kylin instantiates ranger plugin’s implementation class when > starting(this class extends the abstract class provided by kylin). > Ranger plugin periodically polls ranger admin, updates the policy to the > local, and updates project and cube access rights based on policy information. > In the Kylin side： > 1. Kylin provides an abstract class that enables the ranger plugin's > implementation class to extend. > 2. Add configuration item. 1) ranger authorization switch, 2) ranger plugin > implementation class's name. > 3. Instantiate the ranger plugin implementation class when starting kylin. > 4. kylin provides authorization interfaces for ranger plugin calls. > 5. According to the ranger authorization configuration item, hide kylin's > authorization management page. > 6. Using ranger manager access rights of the kylin does not affect kylin's > existing permissions functions and logic. > In the Ranger side： > 1. Ranger plugin will periodically polls ranger admin, updates the policy to > the local. > 2. The ranger plugin invoking the authorization interfaces provided by kylin > to updates the project and cube access rights based on the policy information. > reference link:https://issues.apache.org/jira/browse/KYLIN-2703 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (RANGER-1674) IMPORT START audit is not appearing on audit page
Deepak Sharma created RANGER-1674:
-
Summary: IMPORT START audit is not appearing on audit page
Key: RANGER-1674
URL: https://issues.apache.org/jira/browse/RANGER-1674
Project: Ranger
Issue Type: Bug
Components: Ranger
Affects Versions: 0.7.2
Reporter: Deepak Sharma
Fix For: 0.7.2
IMPORT START audit is not appearing on audit page
IMPORT START audit is not appearing on audit page
https://:6182/service/assets/report?action=IMPORT+START
{code}
200
0
0
10
{code}
{code}
MariaDB [ranger]> select * from x_trx_log where action='IMPORT START';
+--+-+-+-+---++---+--+--++-+---+--+-+--+--+-+--+--+
| id | create_time | update_time | added_by_id | upd_by_id |
class_type | object_id | parent_object_id | parent_object_class_type |
parent_object_name | object_name | attr_name | prev_val | new_val | trx_id
| action | sess_id | req_id | sess_type
|
+--+-+-+-+---++---+--+--++-+---+--+-+--+--+-+--+--+
| 3476 | 2017-07-04 14:04:23 | 2017-07-04 14:04:23 | 1 | 1 |
1020 | NULL | NULL |0 | NULL
| NULL| NULL | NULL | NULL| 4046595386478510685
| IMPORT START | 513 | 4046595386478510685 | Spring Authenticated Session |
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
Review Request 60635: RANGER-1673 - The default plugin configuration file is not readable
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/60635/ --- Review request for ranger. Bugs: RANGER-1673 https://issues.apache.org/jira/browse/RANGER-1673 Repository: ranger Description --- When installing the Hive plugin, the default configuration file is written out (hiveserver2-site.xml) but it is not readable by the group or others, unlike all of the other configuration files. Diffs - agents-common/scripts/enable-agent.sh 562a404d Diff: https://reviews.apache.org/r/60635/diff/1/ Testing --- Tested that the file has the correct permissions after installing the Hive plugin. Thanks, Colm O hEigeartaigh
[jira] [Updated] (RANGER-1673) The default plugin configuration file is not readable
[ https://issues.apache.org/jira/browse/RANGER-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1673: Attachment: 0001-RANGER-1673-The-default-plugin-configuration-file-is.patch > The default plugin configuration file is not readable > - > > Key: RANGER-1673 > URL: https://issues.apache.org/jira/browse/RANGER-1673 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Trivial > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1673-The-default-plugin-configuration-file-is.patch > > > When installing the Hive plugin, the default configuration file is written > out (hiveserver2-site.xml) but it is not readable by the group or others, > unlike all of the other configuration files. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (RANGER-1673) The default plugin configuration file is not readable
Colm O hEigeartaigh created RANGER-1673: --- Summary: The default plugin configuration file is not readable Key: RANGER-1673 URL: https://issues.apache.org/jira/browse/RANGER-1673 Project: Ranger Issue Type: Improvement Components: plugins Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Priority: Trivial Fix For: 1.0.0 When installing the Hive plugin, the default configuration file is written out (hiveserver2-site.xml) but it is not readable by the group or others, unlike all of the other configuration files. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
