[jira] [Updated] (RANGER-1197) Provide API to get policyVersion in use by Ranger plugins
[ https://issues.apache.org/jira/browse/RANGER-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1197: Attachment: RANGER-1197-3.patch > Provide API to get policyVersion in use by Ranger plugins > - > > Key: RANGER-1197 > URL: https://issues.apache.org/jira/browse/RANGER-1197 > Project: Ranger > Issue Type: Improvement > Components: admin, plugins >Affects Versions: 0.6.1 >Reporter: Madhan Neethiraj >Assignee: Abhay Kulkarni > Fix For: 0.7.0 > > Attachments: RANGER-1197-2.patch, RANGER-1197-3.patch > > > Services like HBase can have a large number of nodes (master, region servers) > that run Ranger authorization plugins. In a large deployment having 100s of > such nodes, it might be challenging to find if all the nodes use the latest > authorization policies from Ranger Admin. An API to get status of the plugins > for a given service will be helpful to troubleshoot any issues. The API > should return the following details: > - plugin hostname > - plugin ip-address > - policyVersion in use > - time the policies were downloaded > - time the policies become effective > - tagVersion in use > - time the tags were downloaded > - time the tags become effective -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RANGER-1197) Provide API to get policyVersion in use by Ranger plugins
[ https://issues.apache.org/jira/browse/RANGER-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829322#comment-15829322 ] Pradeep Agrawal commented on RANGER-1197: - Review request for issue 'non admin user is able to get plugin status info' : https://reviews.apache.org/r/55703/ > Provide API to get policyVersion in use by Ranger plugins > - > > Key: RANGER-1197 > URL: https://issues.apache.org/jira/browse/RANGER-1197 > Project: Ranger > Issue Type: Improvement > Components: admin, plugins >Affects Versions: 0.6.1 >Reporter: Madhan Neethiraj >Assignee: Abhay Kulkarni > Fix For: 0.7.0 > > Attachments: RANGER-1197-2.patch, RANGER-1197-3.patch > > > Services like HBase can have a large number of nodes (master, region servers) > that run Ranger authorization plugins. In a large deployment having 100s of > such nodes, it might be challenging to find if all the nodes use the latest > authorization policies from Ranger Admin. An API to get status of the plugins > for a given service will be helpful to troubleshoot any issues. The API > should return the following details: > - plugin hostname > - plugin ip-address > - policyVersion in use > - time the policies were downloaded > - time the policies become effective > - tagVersion in use > - time the tags were downloaded > - time the tags become effective -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RANGER-655) Review DB schema for max key length restrictions - MySQL
[
https://issues.apache.org/jira/browse/RANGER-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15833987#comment-15833987
]
Pradeep Agrawal commented on RANGER-655:
Issue can be resolved after
[commit|https://github.com/apache/incubator-ranger/commit/c19ec875742665ab96577f5a27ebac2da036d3bc]
User need to refer below instructions to handle key length issue in UTF charset
db environment.
Note : MySQL server 5.6 or higher and MySQL connector 5.1.13 or higher should
be used.
=>To enable UTF support from MySQL DB following steps need to be done :
Create a backup of all the databases on the server you want to upgrade.
Add following properties in respective section of my.cnf
[mysqld]
character-set-client-handshake = 0
character-set-server = utf8mb4
collation-server = utf8mb4_unicode_ci
innodb_file_per_table=true
innodb_file_format=BARRACUDA
innodb_large_prefix
[client]
default-character-set = utf8mb4
[mysql]
default-character-set = utf8mb4
Restart MySQL Server.
=>If user is already using Ranger on MySQL 5.6 then apart from above steps
following steps need to be done to change charset of ranger db to UTF8.
Stop Ranger admin.
Modify databases, tables, and columns : Change the character set and collation
properties of the databases, tables, and columns to use utf8mb4 instead of utf8.
# For each database:
ALTER DATABASE database_name CHARACTER SET = utf8mb4 COLLATE =
utf8mb4_unicode_ci;
# For each table:
ALTER TABLE table_name ROW_FORMAT = DYNAMIC;
ALTER TABLE table_name CONVERT TO CHARACTER SET utf8mb4 COLLATE
utf8mb4_unicode_ci;
# Start Ranger admin
> Review DB schema for max key length restrictions - MySQL
>
>
> Key: RANGER-655
> URL: https://issues.apache.org/jira/browse/RANGER-655
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Affects Versions: 0.5.0
>Reporter: Madhan Neethiraj
>Assignee: Pradeep Agrawal
>
> Ranger DB schema creation failed with error "Specified key was too long; max
> key length is 767 bytes", while installing ranger-0.5 against MySQL 5.5 with
> Tungsten Replication enabled.
> {quote}
> 2015-09-10 14:03:43,123 I Executing patch on ranger from file:
> 009-updated_schema.sql
> Error executing: CREATE TABLE `x_service` ( `id` bigint(20) NOT NULL
> AUTO_INCREMENT , `guid` varchar(1024) DEFAULT NULL, `create_time` datetime
> DEFAULT NULL, `update_time` datetime DEFAULT NULL, `added_by_id` bigint(20)
> DEFAULT NULL, `upd_by_id` bigint(20) DEFAULT NULL, `version` bigint(20)
> DEFAULT NULL, `type` bigint(20) DEFAULT NULL, `name` varchar(512) DEFAULT
> NULL, `policy_version` bigint(20) DEFAULT NULL, `policy_update_time`datetime
> DEFAULT NULL, `description` varchar(1024) DEFAULT NULL, `is_enabled`
> tinyint(1) NOT NULL DEFAULT '0', primary key (`id`), UNIQUE KEY
> `X_service_name` (`name`), KEY `x_service_added_by_id` (`added_by_id`), KEY
> `x_service_upd_by_id` (`upd_by_id`), KEY `x_service_cr_time` (`create_time`),
> KEY `x_service_up_time` (`update_time`), KEY `x_service_type` (`type`),
> CONSTRAINT `x_service_FK_added_by_id` FOREIGN KEY (`added_by_id`) REFERENCES
> `x_portal_user` (`id`), CONSTRAINT `x_service_FK_upd_by_id` FOREIGN KEY
> (`upd_by_id`) REFERENCES `x_portal_user` (`id`), CONSTRAINT
> `x_service_FK_type` FOREIGN KEY (`type`) REFERENCES `x_service_def` (`id`) );
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was
> too long; max key length is 767 bytes
> SQLException : SQL state: 42000
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was
> too long; max key length is 767 bytes ErrorCode: 1071
> 2015-09-10 14:03:43,787 E 009-updated_schema.sql import failed!
> {quote}
> To get the installation to succeed, ranger databases were pre-created by
> explicitly specifying 'latin1' CHARACTER SET, as shown below:
> {quote}
> create database ranger CHARACTER SET=latin1;
> create database ranger_audit CHARACTER SET=latin1;
> {quote}
> Ranger DB schema (and/or schema documentation or creation scripts) should be
> reviewed to address this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (RANGER-655) Review DB schema for max key length restrictions - MySQL
[
https://issues.apache.org/jira/browse/RANGER-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal resolved RANGER-655.
Resolution: Fixed
> Review DB schema for max key length restrictions - MySQL
>
>
> Key: RANGER-655
> URL: https://issues.apache.org/jira/browse/RANGER-655
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Affects Versions: 0.5.0
>Reporter: Madhan Neethiraj
>Assignee: Pradeep Agrawal
>
> Ranger DB schema creation failed with error "Specified key was too long; max
> key length is 767 bytes", while installing ranger-0.5 against MySQL 5.5 with
> Tungsten Replication enabled.
> {quote}
> 2015-09-10 14:03:43,123 I Executing patch on ranger from file:
> 009-updated_schema.sql
> Error executing: CREATE TABLE `x_service` ( `id` bigint(20) NOT NULL
> AUTO_INCREMENT , `guid` varchar(1024) DEFAULT NULL, `create_time` datetime
> DEFAULT NULL, `update_time` datetime DEFAULT NULL, `added_by_id` bigint(20)
> DEFAULT NULL, `upd_by_id` bigint(20) DEFAULT NULL, `version` bigint(20)
> DEFAULT NULL, `type` bigint(20) DEFAULT NULL, `name` varchar(512) DEFAULT
> NULL, `policy_version` bigint(20) DEFAULT NULL, `policy_update_time`datetime
> DEFAULT NULL, `description` varchar(1024) DEFAULT NULL, `is_enabled`
> tinyint(1) NOT NULL DEFAULT '0', primary key (`id`), UNIQUE KEY
> `X_service_name` (`name`), KEY `x_service_added_by_id` (`added_by_id`), KEY
> `x_service_upd_by_id` (`upd_by_id`), KEY `x_service_cr_time` (`create_time`),
> KEY `x_service_up_time` (`update_time`), KEY `x_service_type` (`type`),
> CONSTRAINT `x_service_FK_added_by_id` FOREIGN KEY (`added_by_id`) REFERENCES
> `x_portal_user` (`id`), CONSTRAINT `x_service_FK_upd_by_id` FOREIGN KEY
> (`upd_by_id`) REFERENCES `x_portal_user` (`id`), CONSTRAINT
> `x_service_FK_type` FOREIGN KEY (`type`) REFERENCES `x_service_def` (`id`) );
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was
> too long; max key length is 767 bytes
> SQLException : SQL state: 42000
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was
> too long; max key length is 767 bytes ErrorCode: 1071
> 2015-09-10 14:03:43,787 E 009-updated_schema.sql import failed!
> {quote}
> To get the installation to succeed, ranger databases were pre-created by
> explicitly specifying 'latin1' CHARACTER SET, as shown below:
> {quote}
> create database ranger CHARACTER SET=latin1;
> create database ranger_audit CHARACTER SET=latin1;
> {quote}
> Ranger DB schema (and/or schema documentation or creation scripts) should be
> reviewed to address this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (RANGER-655) Review DB schema for max key length restrictions - MySQL
[
https://issues.apache.org/jira/browse/RANGER-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-655:
---
Fix Version/s: 0.7.0
> Review DB schema for max key length restrictions - MySQL
>
>
> Key: RANGER-655
> URL: https://issues.apache.org/jira/browse/RANGER-655
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Affects Versions: 0.5.0
>Reporter: Madhan Neethiraj
>Assignee: Pradeep Agrawal
> Fix For: 0.7.0
>
>
> Ranger DB schema creation failed with error "Specified key was too long; max
> key length is 767 bytes", while installing ranger-0.5 against MySQL 5.5 with
> Tungsten Replication enabled.
> {quote}
> 2015-09-10 14:03:43,123 I Executing patch on ranger from file:
> 009-updated_schema.sql
> Error executing: CREATE TABLE `x_service` ( `id` bigint(20) NOT NULL
> AUTO_INCREMENT , `guid` varchar(1024) DEFAULT NULL, `create_time` datetime
> DEFAULT NULL, `update_time` datetime DEFAULT NULL, `added_by_id` bigint(20)
> DEFAULT NULL, `upd_by_id` bigint(20) DEFAULT NULL, `version` bigint(20)
> DEFAULT NULL, `type` bigint(20) DEFAULT NULL, `name` varchar(512) DEFAULT
> NULL, `policy_version` bigint(20) DEFAULT NULL, `policy_update_time`datetime
> DEFAULT NULL, `description` varchar(1024) DEFAULT NULL, `is_enabled`
> tinyint(1) NOT NULL DEFAULT '0', primary key (`id`), UNIQUE KEY
> `X_service_name` (`name`), KEY `x_service_added_by_id` (`added_by_id`), KEY
> `x_service_upd_by_id` (`upd_by_id`), KEY `x_service_cr_time` (`create_time`),
> KEY `x_service_up_time` (`update_time`), KEY `x_service_type` (`type`),
> CONSTRAINT `x_service_FK_added_by_id` FOREIGN KEY (`added_by_id`) REFERENCES
> `x_portal_user` (`id`), CONSTRAINT `x_service_FK_upd_by_id` FOREIGN KEY
> (`upd_by_id`) REFERENCES `x_portal_user` (`id`), CONSTRAINT
> `x_service_FK_type` FOREIGN KEY (`type`) REFERENCES `x_service_def` (`id`) );
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was
> too long; max key length is 767 bytes
> SQLException : SQL state: 42000
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was
> too long; max key length is 767 bytes ErrorCode: 1071
> 2015-09-10 14:03:43,787 E 009-updated_schema.sql import failed!
> {quote}
> To get the installation to succeed, ranger databases were pre-created by
> explicitly specifying 'latin1' CHARACTER SET, as shown below:
> {quote}
> create database ranger CHARACTER SET=latin1;
> create database ranger_audit CHARACTER SET=latin1;
> {quote}
> Ranger DB schema (and/or schema documentation or creation scripts) should be
> reviewed to address this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (RANGER-381) Not able to create group with dot character
[ https://issues.apache.org/jira/browse/RANGER-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-381: --- Fix Version/s: 0.7.0 > Not able to create group with dot character > --- > > Key: RANGER-381 > URL: https://issues.apache.org/jira/browse/RANGER-381 > Project: Ranger > Issue Type: Bug >Affects Versions: 0.4.0, 0.4.1 >Reporter: Hanish Bansal >Assignee: Hanish Bansal >Priority: Minor > Labels: patch > Fix For: 0.7.0 > > Attachments: > 0001-RANGER-381-Not-able-to-create-group-with-dot-charact.patch > > > When creating group with dot in name (E.g. "hanish.bansal") from Ranger admin > UI, it gives error message "Please enter valid name". > Since linux group naming convention allow dot (.) character, so same should > be allowed from Ranger admin UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (RANGER-1115) URLEncode and URLDecode methods are mismatch on usersync and admin
[
https://issues.apache.org/jira/browse/RANGER-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal reassigned RANGER-1115:
---
Assignee: Pradeep Agrawal
> URLEncode and URLDecode methods are mismatch on usersync and admin
> --
>
> Key: RANGER-1115
> URL: https://issues.apache.org/jira/browse/RANGER-1115
> Project: Ranger
> Issue Type: Bug
> Components: admin, usersync
>Affects Versions: 0.6.0
>Reporter: ruoyu wang
>Assignee: Pradeep Agrawal
> Attachments:
> 0001-RANGER-1115-URLEncode-and-URLDecode-methods-are-mism.patch
>
>
> I tried to call rest api
> (delete) /service/xusers/group/{groupName}/user/{userName}
> from ugsync (method private void delXUserGroupInfo).
> I pass path parameter, userName like "a b+c". Method called in ugsync,
> UserSyncUtil.encodeURIParam(username) encode userName into "a+b%2Bc" but on
> admin, userName decoded into "a+b+c".
> It seems space is not decoded properly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (RANGER-1115) URLEncode and URLDecode methods are mismatch on usersync and admin
[
https://issues.apache.org/jira/browse/RANGER-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-1115:
Fix Version/s: 0.7.0
> URLEncode and URLDecode methods are mismatch on usersync and admin
> --
>
> Key: RANGER-1115
> URL: https://issues.apache.org/jira/browse/RANGER-1115
> Project: Ranger
> Issue Type: Bug
> Components: admin, usersync
>Affects Versions: 0.6.0
>Reporter: ruoyu wang
>Assignee: Pradeep Agrawal
> Fix For: 0.7.0
>
> Attachments:
> 0001-RANGER-1115-URLEncode-and-URLDecode-methods-are-mism.patch
>
>
> I tried to call rest api
> (delete) /service/xusers/group/{groupName}/user/{userName}
> from ugsync (method private void delXUserGroupInfo).
> I pass path parameter, userName like "a b+c". Method called in ugsync,
> UserSyncUtil.encodeURIParam(username) encode userName into "a+b%2Bc" but on
> admin, userName decoded into "a+b+c".
> It seems space is not decoded properly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (RANGER-1341) Use credential provider files to store passwords rather storing them in config file in clear text format
[ https://issues.apache.org/jira/browse/RANGER-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1341: Attachment: 0001-RANGER-1341-Use-credential-provider-files-to-store-p.patch > Use credential provider files to store passwords rather storing them in > config file in clear text format > > > Key: RANGER-1341 > URL: https://issues.apache.org/jira/browse/RANGER-1341 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.5.0, 0.6.0, 0.7.0 >Reporter: Pradeep Agrawal > Attachments: > 0001-RANGER-1341-Use-credential-provider-files-to-store-p.patch > > > Currently below given password properties contains values in clear text. > these clear text password should be stored in credential provider file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1341) Use credential provider files to store passwords rather storing them in config file in clear text format
[ https://issues.apache.org/jira/browse/RANGER-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1341: Attachment: RANGER-1341-2.patch > Use credential provider files to store passwords rather storing them in > config file in clear text format > > > Key: RANGER-1341 > URL: https://issues.apache.org/jira/browse/RANGER-1341 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.5.0, 0.6.0, 0.7.0 >Reporter: Pradeep Agrawal > Attachments: RANGER-1341-2.patch > > > Currently below given password properties contains values in clear text. > these clear text password should be stored in credential provider file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1341) Use credential provider files to store passwords rather storing them in config file in clear text format
[ https://issues.apache.org/jira/browse/RANGER-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1341: Attachment: (was: 0001-RANGER-1341-Use-credential-provider-files-to-store-p.patch) > Use credential provider files to store passwords rather storing them in > config file in clear text format > > > Key: RANGER-1341 > URL: https://issues.apache.org/jira/browse/RANGER-1341 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.5.0, 0.6.0, 0.7.0 >Reporter: Pradeep Agrawal > Attachments: RANGER-1341-2.patch > > > Currently below given password properties contains values in clear text. > these clear text password should be stored in credential provider file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1341) Use credential provider files to store passwords rather storing them in config file in clear text format
[ https://issues.apache.org/jira/browse/RANGER-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850305#comment-15850305 ] Pradeep Agrawal commented on RANGER-1341: - Review request link : https://reviews.apache.org/r/56163/ > Use credential provider files to store passwords rather storing them in > config file in clear text format > > > Key: RANGER-1341 > URL: https://issues.apache.org/jira/browse/RANGER-1341 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.5.0, 0.6.0, 0.7.0 >Reporter: Pradeep Agrawal > Attachments: RANGER-1341-2.patch > > > Currently below given password properties contains values in clear text. > these clear text password should be stored in credential provider file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (RANGER-1341) Use credential provider files to store passwords rather storing them in config file in clear text format
[ https://issues.apache.org/jira/browse/RANGER-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reassigned RANGER-1341: --- Assignee: Pradeep Agrawal > Use credential provider files to store passwords rather storing them in > config file in clear text format > > > Key: RANGER-1341 > URL: https://issues.apache.org/jira/browse/RANGER-1341 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.5.0, 0.6.0, 0.7.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 0.7.0 > > Attachments: RANGER-1341-2.patch > > > Currently below given password properties contains values in clear text. > these clear text password should be stored in credential provider file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1378) There is Page not found (404) error when clicking Admin tab in Audit.
[ https://issues.apache.org/jira/browse/RANGER-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15867160#comment-15867160 ] Pradeep Agrawal commented on RANGER-1378: - [~zhangqiang2] Which version of MySQL you are using ? > There is Page not found (404) error when clicking Admin tab in Audit. > - > > Key: RANGER-1378 > URL: https://issues.apache.org/jira/browse/RANGER-1378 > Project: Ranger > Issue Type: Bug > Components: admin >Reporter: Qiang Zhang >Assignee: Qiang Zhang > Labels: patch > Attachments: > 0001-RANGER-1378-There-is-Page-not-found-404-error-when-c.patch, > Audit-Admin-error.png > > > There is Page not found (404) error when clicking Admin tab in Audit. > Wrong reason: There is no vx_trx_log table in ranger database. > Exception [EclipseLink-4002] (Eclipse Persistence Services - > 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException > Internal Exception: > com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Expression #1 of > SELECT list is not in GROUP BY clause and contains nonaggregated column > 'ranger.x_trx_log.id' which is not functionally dependent on columns in GROUP > BY clause; this is incompatible with sql_mode=only_full_group_by > Error Code: 1055 > Call: SELECT ID AS a1, ACTION AS a2, ADDED_BY_ID AS a3, ATTR_NAME AS a4, > CREATE_TIME AS a5, NEW_VAL AS a6, CLASS_TYPE AS a7, OBJECT_ID AS a8, > OBJECT_NAME AS a9, PARENT_OBJECT_CLASS_TYPE AS a10, PARENT_OBJECT_ID AS a11, > PARENT_OBJECT_NAME AS a12, PREV_VAL AS a13, REQ_ID AS a14, SESS_ID AS a15, > SESS_TYPE AS a16, TRX_ID AS a17, UPDATE_TIME AS a18, UPD_BY_ID AS a19 FROM > vx_trx_log ORDER BY CREATE_TIME DESC LIMIT ?, ? > bind => [2 parameters bound] > Query: ReadAllQuery(referenceClass=VXXTrxLog sql="SELECT ID AS a1, ACTION AS > a2, ADDED_BY_ID AS a3, ATTR_NAME AS a4, CREATE_TIME AS a5, NEW_VAL AS a6, > CLASS_TYPE AS a7, OBJECT_ID AS a8, OBJECT_NAME AS a9, > PARENT_OBJECT_CLASS_TYPE AS a10, PARENT_OBJECT_ID AS a11, PARENT_OBJECT_NAME > AS a12, PREV_VAL AS a13, REQ_ID AS a14, SESS_ID AS a15, SESS_TYPE AS a16, > TRX_ID AS a17, UPDATE_TIME AS a18, UPD_BY_ID AS a19 FROM vx_trx_log ORDER BY > CREATE_TIME DESC LIMIT ?, ?") -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (RANGER-1378) There is Page not found (404) error when clicking Admin tab in Audit.
[
https://issues.apache.org/jira/browse/RANGER-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15867160#comment-15867160
]
Pradeep Agrawal edited comment on RANGER-1378 at 2/15/17 3:58 AM:
--
[~zhangqiang2] Which version of MySQL are you using ? Also please provide the
output of
{code}show variables like 'SQL_MODE';{code}
was (Author: pradeep.agrawal):
[~zhangqiang2] Which version of MySQL you are using ?
> There is Page not found (404) error when clicking Admin tab in Audit.
> -
>
> Key: RANGER-1378
> URL: https://issues.apache.org/jira/browse/RANGER-1378
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Reporter: Qiang Zhang
>Assignee: Qiang Zhang
> Labels: patch
> Attachments:
> 0001-RANGER-1378-There-is-Page-not-found-404-error-when-c.patch,
> Audit-Admin-error.png
>
>
> There is Page not found (404) error when clicking Admin tab in Audit.
> Wrong reason: There is no vx_trx_log table in ranger database.
> Exception [EclipseLink-4002] (Eclipse Persistence Services -
> 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception:
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Expression #1 of
> SELECT list is not in GROUP BY clause and contains nonaggregated column
> 'ranger.x_trx_log.id' which is not functionally dependent on columns in GROUP
> BY clause; this is incompatible with sql_mode=only_full_group_by
> Error Code: 1055
> Call: SELECT ID AS a1, ACTION AS a2, ADDED_BY_ID AS a3, ATTR_NAME AS a4,
> CREATE_TIME AS a5, NEW_VAL AS a6, CLASS_TYPE AS a7, OBJECT_ID AS a8,
> OBJECT_NAME AS a9, PARENT_OBJECT_CLASS_TYPE AS a10, PARENT_OBJECT_ID AS a11,
> PARENT_OBJECT_NAME AS a12, PREV_VAL AS a13, REQ_ID AS a14, SESS_ID AS a15,
> SESS_TYPE AS a16, TRX_ID AS a17, UPDATE_TIME AS a18, UPD_BY_ID AS a19 FROM
> vx_trx_log ORDER BY CREATE_TIME DESC LIMIT ?, ?
> bind => [2 parameters bound]
> Query: ReadAllQuery(referenceClass=VXXTrxLog sql="SELECT ID AS a1, ACTION AS
> a2, ADDED_BY_ID AS a3, ATTR_NAME AS a4, CREATE_TIME AS a5, NEW_VAL AS a6,
> CLASS_TYPE AS a7, OBJECT_ID AS a8, OBJECT_NAME AS a9,
> PARENT_OBJECT_CLASS_TYPE AS a10, PARENT_OBJECT_ID AS a11, PARENT_OBJECT_NAME
> AS a12, PREV_VAL AS a13, REQ_ID AS a14, SESS_ID AS a15, SESS_TYPE AS a16,
> TRX_ID AS a17, UPDATE_TIME AS a18, UPD_BY_ID AS a19 FROM vx_trx_log ORDER BY
> CREATE_TIME DESC LIMIT ?, ?")
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (RANGER-1378) There is Page not found (404) error when clicking Admin tab in Audit.
[
https://issues.apache.org/jira/browse/RANGER-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15867328#comment-15867328
]
Pradeep Agrawal commented on RANGER-1378:
-
[~zhangqiang2]: Please provide the output of mysql statement :
{code}show variables like 'SQL_MODE';{code}
> There is Page not found (404) error when clicking Admin tab in Audit.
> -
>
> Key: RANGER-1378
> URL: https://issues.apache.org/jira/browse/RANGER-1378
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Reporter: Qiang Zhang
>Assignee: Qiang Zhang
> Labels: patch
> Attachments:
> 0001-RANGER-1378-There-is-Page-not-found-404-error-when-c.patch,
> Audit-Admin-error.png
>
>
> There is Page not found (404) error when clicking Admin tab in Audit.
> Wrong reason: There is no vx_trx_log table in ranger database.
> Exception [EclipseLink-4002] (Eclipse Persistence Services -
> 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception:
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Expression #1 of
> SELECT list is not in GROUP BY clause and contains nonaggregated column
> 'ranger.x_trx_log.id' which is not functionally dependent on columns in GROUP
> BY clause; this is incompatible with sql_mode=only_full_group_by
> Error Code: 1055
> Call: SELECT ID AS a1, ACTION AS a2, ADDED_BY_ID AS a3, ATTR_NAME AS a4,
> CREATE_TIME AS a5, NEW_VAL AS a6, CLASS_TYPE AS a7, OBJECT_ID AS a8,
> OBJECT_NAME AS a9, PARENT_OBJECT_CLASS_TYPE AS a10, PARENT_OBJECT_ID AS a11,
> PARENT_OBJECT_NAME AS a12, PREV_VAL AS a13, REQ_ID AS a14, SESS_ID AS a15,
> SESS_TYPE AS a16, TRX_ID AS a17, UPDATE_TIME AS a18, UPD_BY_ID AS a19 FROM
> vx_trx_log ORDER BY CREATE_TIME DESC LIMIT ?, ?
> bind => [2 parameters bound]
> Query: ReadAllQuery(referenceClass=VXXTrxLog sql="SELECT ID AS a1, ACTION AS
> a2, ADDED_BY_ID AS a3, ATTR_NAME AS a4, CREATE_TIME AS a5, NEW_VAL AS a6,
> CLASS_TYPE AS a7, OBJECT_ID AS a8, OBJECT_NAME AS a9,
> PARENT_OBJECT_CLASS_TYPE AS a10, PARENT_OBJECT_ID AS a11, PARENT_OBJECT_NAME
> AS a12, PREV_VAL AS a13, REQ_ID AS a14, SESS_ID AS a15, SESS_TYPE AS a16,
> TRX_ID AS a17, UPDATE_TIME AS a18, UPD_BY_ID AS a19 FROM vx_trx_log ORDER BY
> CREATE_TIME DESC LIMIT ?, ?")
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (RANGER-1378) There is Page not found (404) error when clicking Admin tab in Audit.
[
https://issues.apache.org/jira/browse/RANGER-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15867438#comment-15867438
]
Pradeep Agrawal commented on RANGER-1378:
-
[~zhangqiang2] Please open mysql config file(my.cnf) file and change/add
sql_mode as given below under [mysqld] section of the file
{code}sql_mode=STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION{code}
Restart mysql server after shaving changes.
Please refer
[link|https://dev.mysql.com/doc/refman/5.7/en/group-by-handling.html] for
detailed description.
> There is Page not found (404) error when clicking Admin tab in Audit.
> -
>
> Key: RANGER-1378
> URL: https://issues.apache.org/jira/browse/RANGER-1378
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Reporter: Qiang Zhang
>Assignee: Qiang Zhang
> Labels: patch
> Attachments:
> 0001-RANGER-1378-There-is-Page-not-found-404-error-when-c.patch,
> Audit-Admin-error.png
>
>
> There is Page not found (404) error when clicking Admin tab in Audit.
> Wrong reason: There is no vx_trx_log table in ranger database.
> Exception [EclipseLink-4002] (Eclipse Persistence Services -
> 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception:
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Expression #1 of
> SELECT list is not in GROUP BY clause and contains nonaggregated column
> 'ranger.x_trx_log.id' which is not functionally dependent on columns in GROUP
> BY clause; this is incompatible with sql_mode=only_full_group_by
> Error Code: 1055
> Call: SELECT ID AS a1, ACTION AS a2, ADDED_BY_ID AS a3, ATTR_NAME AS a4,
> CREATE_TIME AS a5, NEW_VAL AS a6, CLASS_TYPE AS a7, OBJECT_ID AS a8,
> OBJECT_NAME AS a9, PARENT_OBJECT_CLASS_TYPE AS a10, PARENT_OBJECT_ID AS a11,
> PARENT_OBJECT_NAME AS a12, PREV_VAL AS a13, REQ_ID AS a14, SESS_ID AS a15,
> SESS_TYPE AS a16, TRX_ID AS a17, UPDATE_TIME AS a18, UPD_BY_ID AS a19 FROM
> vx_trx_log ORDER BY CREATE_TIME DESC LIMIT ?, ?
> bind => [2 parameters bound]
> Query: ReadAllQuery(referenceClass=VXXTrxLog sql="SELECT ID AS a1, ACTION AS
> a2, ADDED_BY_ID AS a3, ATTR_NAME AS a4, CREATE_TIME AS a5, NEW_VAL AS a6,
> CLASS_TYPE AS a7, OBJECT_ID AS a8, OBJECT_NAME AS a9,
> PARENT_OBJECT_CLASS_TYPE AS a10, PARENT_OBJECT_ID AS a11, PARENT_OBJECT_NAME
> AS a12, PREV_VAL AS a13, REQ_ID AS a14, SESS_ID AS a15, SESS_TYPE AS a16,
> TRX_ID AS a17, UPDATE_TIME AS a18, UPD_BY_ID AS a19 FROM vx_trx_log ORDER BY
> CREATE_TIME DESC LIMIT ?, ?")
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (RANGER-1341) Use credential provider files to store passwords rather storing them in config file in clear text format
[ https://issues.apache.org/jira/browse/RANGER-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1341: Attachment: (was: RANGER-1341-2.patch) > Use credential provider files to store passwords rather storing them in > config file in clear text format > > > Key: RANGER-1341 > URL: https://issues.apache.org/jira/browse/RANGER-1341 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.5.0, 0.6.0, 0.7.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 0.7.0 > > Attachments: RANGER-1341-4.patch > > > Currently below given password properties contains values in clear text. > these clear text password should be stored in credential provider file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1341) Use credential provider files to store passwords rather storing them in config file in clear text format
[ https://issues.apache.org/jira/browse/RANGER-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1341: Attachment: RANGER-1341-4.patch > Use credential provider files to store passwords rather storing them in > config file in clear text format > > > Key: RANGER-1341 > URL: https://issues.apache.org/jira/browse/RANGER-1341 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.5.0, 0.6.0, 0.7.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 0.7.0 > > Attachments: RANGER-1341-4.patch > > > Currently below given password properties contains values in clear text. > these clear text password should be stored in credential provider file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1341) Use credential provider files to store passwords rather storing them in config file in clear text format
[ https://issues.apache.org/jira/browse/RANGER-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1341: Attachment: (was: RANGER-1341-4.patch) > Use credential provider files to store passwords rather storing them in > config file in clear text format > > > Key: RANGER-1341 > URL: https://issues.apache.org/jira/browse/RANGER-1341 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.5.0, 0.6.0, 0.7.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 0.7.0 > > > Currently below given password properties contains values in clear text. > these clear text password should be stored in credential provider file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1341) Use credential provider files to store passwords rather storing them in config file in clear text format
[ https://issues.apache.org/jira/browse/RANGER-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1341: Attachment: RANGER-1341-5.patch > Use credential provider files to store passwords rather storing them in > config file in clear text format > > > Key: RANGER-1341 > URL: https://issues.apache.org/jira/browse/RANGER-1341 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.5.0, 0.6.0, 0.7.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 0.7.0 > > Attachments: RANGER-1341-5.patch > > > Currently below given password properties contains values in clear text. > these clear text password should be stored in credential provider file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1341) Use credential provider files to store passwords rather storing them in config file in clear text format
[ https://issues.apache.org/jira/browse/RANGER-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15869913#comment-15869913 ] Pradeep Agrawal commented on RANGER-1341: - Patch committed in Apache Ranger master branch : https://github.com/apache/ranger/commit/74ec5f38adba600cc79b34880d725e8b0430b31b Patch committed in Apache Ranger ranger-0.7 branch : https://github.com/apache/ranger/commit/a7a631d5d8d102b5ae7eadb24e6781b3809d7d5b > Use credential provider files to store passwords rather storing them in > config file in clear text format > > > Key: RANGER-1341 > URL: https://issues.apache.org/jira/browse/RANGER-1341 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.5.0, 0.6.0, 0.7.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 0.7.0 > > Attachments: RANGER-1341-5.patch > > > Currently below given password properties contains values in clear text. > these clear text password should be stored in credential provider file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1401) Add consolidated db schema script for SQLServer DB flavor
Pradeep Agrawal created RANGER-1401: --- Summary: Add consolidated db schema script for SQLServer DB flavor Key: RANGER-1401 URL: https://issues.apache.org/jira/browse/RANGER-1401 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 0.7.0 Reporter: Pradeep Agrawal Assignee: Pradeep Agrawal A consolidated db schema script for SQLServer DB flavor would be required as execution of db patches and java patches takes lot of time. Before installing Ranger User can separately run this script to reduce db setup and installation time. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1401) Add consolidated db schema script for SQLServer DB flavor
[ https://issues.apache.org/jira/browse/RANGER-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1401: Attachment: RANGER-1401-1.patch > Add consolidated db schema script for SQLServer DB flavor > - > > Key: RANGER-1401 > URL: https://issues.apache.org/jira/browse/RANGER-1401 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Attachments: RANGER-1401-1.patch > > > A consolidated db schema script for SQLServer DB flavor would be required as > execution of db patches and java patches takes lot of time. Before > installing Ranger User can separately run this script to reduce db setup and > installation time. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1401) Add consolidated db schema script for SQLServer DB flavor
[ https://issues.apache.org/jira/browse/RANGER-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1401: Attachment: (was: RANGER-1401-1.patch) > Add consolidated db schema script for SQLServer DB flavor > - > > Key: RANGER-1401 > URL: https://issues.apache.org/jira/browse/RANGER-1401 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.0, 1.0.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 0.7.0, 1.0.0 > > > A consolidated db schema script for SQLServer DB flavor would be required as > execution of db patches and java patches takes lot of time. Before > installing Ranger User can separately run this script to reduce db setup and > installation time. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1401) Add consolidated db schema script for SQLServer DB flavor
[ https://issues.apache.org/jira/browse/RANGER-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1401: Attachment: RANGER-1401-2.patch > Add consolidated db schema script for SQLServer DB flavor > - > > Key: RANGER-1401 > URL: https://issues.apache.org/jira/browse/RANGER-1401 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.0, 1.0.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 0.7.0, 1.0.0 > > Attachments: RANGER-1401-2.patch > > > A consolidated db schema script for SQLServer DB flavor would be required as > execution of db patches and java patches takes lot of time. Before > installing Ranger User can separately run this script to reduce db setup and > installation time. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1409) User role get deleted from table when he tries to update his role to a restricted role
Pradeep Agrawal created RANGER-1409: --- Summary: User role get deleted from table when he tries to update his role to a restricted role Key: RANGER-1409 URL: https://issues.apache.org/jira/browse/RANGER-1409 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 0.6.0, 0.5.0, 0.7.0 Reporter: Pradeep Agrawal Assignee: Pradeep Agrawal *Problem Statement :* User role get deleted from x_portal_user_role table and login does not work when he tries to update his role to a restricted role for his profile by using Post method of API /service/users/ . User having role 'ROLE_SYS_ADMIN' can change his role to 'ROLE_USER' User having role 'ROLE_KEY_ADMIN' can change his role to 'ROLE_USER' User having role 'ROLE_USER' should not able to change his role to any other role. *Proposed solution :* User's new requested role should be validated and if requested role is invalid then server should return error message. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1409) User role get deleted from table when he tries to update his role to a restricted role
[ https://issues.apache.org/jira/browse/RANGER-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1409: Fix Version/s: 0.7.0 > User role get deleted from table when he tries to update his role to a > restricted role > -- > > Key: RANGER-1409 > URL: https://issues.apache.org/jira/browse/RANGER-1409 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.5.0, 0.6.0, 0.7.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 0.7.0 > > > *Problem Statement :* User role get deleted from x_portal_user_role table and > login does not work when he tries to update his role to a restricted role for > his profile by using Post method of API /service/users/ . > User having role 'ROLE_SYS_ADMIN' can change his role to 'ROLE_USER' > User having role 'ROLE_KEY_ADMIN' can change his role to 'ROLE_USER' > User having role 'ROLE_USER' should not able to change his role to any other > role. > *Proposed solution :* User's new requested role should be validated and if > requested role is invalid then server should return error message. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1409) User role get deleted from table when he tries to update his role to a restricted role
[ https://issues.apache.org/jira/browse/RANGER-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1409: Attachment: RANGER-1409-1.patch > User role get deleted from table when he tries to update his role to a > restricted role > -- > > Key: RANGER-1409 > URL: https://issues.apache.org/jira/browse/RANGER-1409 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.5.0, 0.6.0, 0.7.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 0.7.0 > > Attachments: RANGER-1409-1.patch > > > *Problem Statement :* User role get deleted from x_portal_user_role table and > login does not work when he tries to update his role to a restricted role for > his profile by using Post method of API /service/users/ . > User having role 'ROLE_SYS_ADMIN' can change his role to 'ROLE_USER' > User having role 'ROLE_KEY_ADMIN' can change his role to 'ROLE_USER' > User having role 'ROLE_USER' should not able to change his role to any other > role. > *Proposed solution :* User's new requested role should be validated and if > requested role is invalid then server should return error message. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (RANGER-1407) Service update transaction log is not generated in some cases
[ https://issues.apache.org/jira/browse/RANGER-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reassigned RANGER-1407: --- Assignee: Pradeep Agrawal > Service update transaction log is not generated in some cases > - > > Key: RANGER-1407 > URL: https://issues.apache.org/jira/browse/RANGER-1407 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.7.0 >Reporter: Abhay Kulkarni >Assignee: Pradeep Agrawal > Fix For: 0.7.0 > > > If a Ranger service is updated to change its associated tag service name, > then the service-update transaction log is not generated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1407) Service update transaction log is not generated in some cases
[ https://issues.apache.org/jira/browse/RANGER-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1407: Attachment: RANGER-1407-1.patch > Service update transaction log is not generated in some cases > - > > Key: RANGER-1407 > URL: https://issues.apache.org/jira/browse/RANGER-1407 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.7.0 >Reporter: Abhay Kulkarni >Assignee: Pradeep Agrawal > Fix For: 0.7.0 > > Attachments: RANGER-1407-1.patch > > > If a Ranger service is updated to change its associated tag service name, > then the service-update transaction log is not generated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1401) Add consolidated db schema script for SQLServer DB flavor
[ https://issues.apache.org/jira/browse/RANGER-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15888486#comment-15888486 ] Pradeep Agrawal commented on RANGER-1401: - Patch committed in Apache Ranger master branch : https://github.com/apache/ranger/commit/24f053e2636e45171b98e84080ca2b8c3b7cc9c7 Patch committed in Apache Ranger 0.7 branch : https://github.com/apache/ranger/commit/d18af7a942e9cd21b6f93e1ce64a17e416a5d45a > Add consolidated db schema script for SQLServer DB flavor > - > > Key: RANGER-1401 > URL: https://issues.apache.org/jira/browse/RANGER-1401 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.0, 1.0.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 1.0.0, 0.7.1 > > Attachments: RANGER-1401-2.patch > > > A consolidated db schema script for SQLServer DB flavor would be required as > execution of db patches and java patches takes lot of time. Before > installing Ranger User can separately run this script to reduce db setup and > installation time. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1401) Add consolidated db schema script for SQLServer DB flavor
[ https://issues.apache.org/jira/browse/RANGER-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1401: Attachment: (was: RANGER-1401-2.patch) > Add consolidated db schema script for SQLServer DB flavor > - > > Key: RANGER-1401 > URL: https://issues.apache.org/jira/browse/RANGER-1401 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.0, 1.0.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 1.0.0, 0.7.1 > > Attachments: RANGER-1401-3.patch > > > A consolidated db schema script for SQLServer DB flavor would be required as > execution of db patches and java patches takes lot of time. Before > installing Ranger User can separately run this script to reduce db setup and > installation time. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1401) Add consolidated db schema script for SQLServer DB flavor
[ https://issues.apache.org/jira/browse/RANGER-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1401: Attachment: RANGER-1401-3.patch > Add consolidated db schema script for SQLServer DB flavor > - > > Key: RANGER-1401 > URL: https://issues.apache.org/jira/browse/RANGER-1401 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.0, 1.0.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 1.0.0, 0.7.1 > > Attachments: RANGER-1401-3.patch > > > A consolidated db schema script for SQLServer DB flavor would be required as > execution of db patches and java patches takes lot of time. Before > installing Ranger User can separately run this script to reduce db setup and > installation time. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1413) Good coding practice in Ranger recommended by static code analysis
[ https://issues.apache.org/jira/browse/RANGER-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15888530#comment-15888530 ] Pradeep Agrawal commented on RANGER-1413: - Another Patch is posted on the review board: https://reviews.apache.org/r/57125/ > Good coding practice in Ranger recommended by static code analysis > -- > > Key: RANGER-1413 > URL: https://issues.apache.org/jira/browse/RANGER-1413 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.7.0 >Reporter: Abhay Kulkarni >Assignee: Abhay Kulkarni >Priority: Minor > Fix For: 0.7.1 > > > Fix potential run-time issues identified by static code analysis. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1407) Service update transaction log is not generated in some cases
[ https://issues.apache.org/jira/browse/RANGER-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1407: Attachment: (was: RANGER-1407-1.patch) > Service update transaction log is not generated in some cases > - > > Key: RANGER-1407 > URL: https://issues.apache.org/jira/browse/RANGER-1407 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.7.0 >Reporter: Abhay Kulkarni >Assignee: Pradeep Agrawal > Fix For: 0.7.1 > > > If a Ranger service is updated to change its associated tag service name, > then the service-update transaction log is not generated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1407) Service update transaction log is not generated in some cases
[ https://issues.apache.org/jira/browse/RANGER-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1407: Attachment: RANGER-1407-2.patch > Service update transaction log is not generated in some cases > - > > Key: RANGER-1407 > URL: https://issues.apache.org/jira/browse/RANGER-1407 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.7.0 >Reporter: Abhay Kulkarni >Assignee: Pradeep Agrawal > Fix For: 0.7.1 > > Attachments: RANGER-1407-2.patch > > > If a Ranger service is updated to change its associated tag service name, > then the service-update transaction log is not generated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1409) User role get deleted from table when he tries to update his role to a restricted role
[ https://issues.apache.org/jira/browse/RANGER-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889913#comment-15889913 ] Pradeep Agrawal commented on RANGER-1409: - Patch committed in Apache Ranger master branch : https://github.com/apache/ranger/commit/748a84cd409b436b12c720a1c67bae62cee6aa4b Patch committed in Apache Ranger 0.7 branch : https://github.com/apache/ranger/commit/bbaf1e7df65f5da68468b18bdefd3ebdca34bc7f > User role get deleted from table when he tries to update his role to a > restricted role > -- > > Key: RANGER-1409 > URL: https://issues.apache.org/jira/browse/RANGER-1409 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.5.0, 0.6.0, 0.7.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 0.7.1 > > Attachments: RANGER-1409-1.patch > > > *Problem Statement :* User role get deleted from x_portal_user_role table and > login does not work when he tries to update his role to a restricted role for > his profile by using Post method of API /service/users/ . > User having role 'ROLE_SYS_ADMIN' can change his role to 'ROLE_USER' > User having role 'ROLE_KEY_ADMIN' can change his role to 'ROLE_USER' > User having role 'ROLE_USER' should not able to change his role to any other > role. > *Proposed solution :* User's new requested role should be validated and if > requested role is invalid then server should return error message. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1407) Service update transaction log is not generated in some cases
[ https://issues.apache.org/jira/browse/RANGER-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1407: Attachment: (was: RANGER-1407-2.patch) > Service update transaction log is not generated in some cases > - > > Key: RANGER-1407 > URL: https://issues.apache.org/jira/browse/RANGER-1407 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.7.0 >Reporter: Abhay Kulkarni >Assignee: Pradeep Agrawal > Fix For: 0.7.1 > > > If a Ranger service is updated to change its associated tag service name, > then the service-update transaction log is not generated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1407) Service update transaction log is not generated in some cases
[ https://issues.apache.org/jira/browse/RANGER-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891626#comment-15891626 ] Pradeep Agrawal commented on RANGER-1407: - Patch committed in Apache Ranger master branch : https://github.com/apache/ranger/commit/c0c1b155e5edf167b627da9b72d8d3df0ecc13c5 Patch committed in Apache Ranger 0.7 branch : https://github.com/apache/ranger/commit/1eada5de1520c155bd29a43abe252ba00c2a51ba > Service update transaction log is not generated in some cases > - > > Key: RANGER-1407 > URL: https://issues.apache.org/jira/browse/RANGER-1407 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.7.0 >Reporter: Abhay Kulkarni >Assignee: Pradeep Agrawal > Fix For: 0.7.1 > > > If a Ranger service is updated to change its associated tag service name, > then the service-update transaction log is not generated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1407) Service update transaction log is not generated in some cases
[ https://issues.apache.org/jira/browse/RANGER-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1407: Attachment: RANGER-1407-3.patch > Service update transaction log is not generated in some cases > - > > Key: RANGER-1407 > URL: https://issues.apache.org/jira/browse/RANGER-1407 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.7.0 >Reporter: Abhay Kulkarni >Assignee: Pradeep Agrawal > Fix For: 0.7.1 > > Attachments: RANGER-1407-3.patch > > > If a Ranger service is updated to change its associated tag service name, > then the service-update transaction log is not generated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1413) Good coding practice in Ranger recommended by static code analysis
[ https://issues.apache.org/jira/browse/RANGER-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1413: Attachment: RANGER-1413-2.patch > Good coding practice in Ranger recommended by static code analysis > -- > > Key: RANGER-1413 > URL: https://issues.apache.org/jira/browse/RANGER-1413 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.7.0 >Reporter: Abhay Kulkarni >Assignee: Abhay Kulkarni >Priority: Minor > Fix For: 0.7.1 > > Attachments: > 0002-RANGER-1413-Fix-issues-uncovered-by-static-code-anal.patch, > RANGER-1413-2.patch > > > Fix potential run-time issues identified by static code analysis. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1413) Good coding practice in Ranger recommended by static code analysis
[ https://issues.apache.org/jira/browse/RANGER-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1413: Attachment: 0002-RANGER-1413-Fix-issues-uncovered-by-static-code-anal.patch > Good coding practice in Ranger recommended by static code analysis > -- > > Key: RANGER-1413 > URL: https://issues.apache.org/jira/browse/RANGER-1413 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.7.0 >Reporter: Abhay Kulkarni >Assignee: Abhay Kulkarni >Priority: Minor > Fix For: 0.7.1 > > Attachments: > 0002-RANGER-1413-Fix-issues-uncovered-by-static-code-anal.patch, > RANGER-1413-2.patch > > > Fix potential run-time issues identified by static code analysis. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1413) Good coding practice in Ranger recommended by static code analysis
[ https://issues.apache.org/jira/browse/RANGER-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891631#comment-15891631 ] Pradeep Agrawal commented on RANGER-1413: - Patch-1 committed in Apache Ranger master branch : https://github.com/apache/ranger/commit/cd4dbcbdea320f7782a9998a039919694fe544d5 Patch-2 committed in Apache Ranger master branch : https://github.com/apache/ranger/commit/360cdd683c0c74db58f12fa0fb3f912a8b6c6a98 Patch-1 committed in Apache Ranger 0.7 branch : https://github.com/apache/ranger/commit/9afb3eca89e12f2c35c465a727ef498223c5ad86 Patch-2 committed in Apache Ranger 0.7 branch : https://github.com/apache/ranger/commit/b905523b731f20d3fa70221b4de8894bb7ce8d4c > Good coding practice in Ranger recommended by static code analysis > -- > > Key: RANGER-1413 > URL: https://issues.apache.org/jira/browse/RANGER-1413 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.7.0 >Reporter: Abhay Kulkarni >Assignee: Abhay Kulkarni >Priority: Minor > Fix For: 0.7.1 > > Attachments: > 0002-RANGER-1413-Fix-issues-uncovered-by-static-code-anal.patch, > RANGER-1413-2.patch > > > Fix potential run-time issues identified by static code analysis. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1417) Ranger Upgrade is failing for Oracle DB flavor
Pradeep Agrawal created RANGER-1417: --- Summary: Ranger Upgrade is failing for Oracle DB flavor Key: RANGER-1417 URL: https://issues.apache.org/jira/browse/RANGER-1417 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 0.7.0 Reporter: Pradeep Agrawal Assignee: Pradeep Agrawal Fix For: 0.7.1 *Problem Statement :* Ranger Upgrade(0.6 to 0.7) is failing for Oracle DB flavor as the java patches are not marked applied in x_db_version_h table by db_setup.py script in 0.6 version. *Proposed Solution for 0.6 :* db_setup.py script need to be fix so that patches are marked applied after execution of each java patch. *Proposed Solution for 0.7 or later :* From db_setup.py Identify java patches that are marked as 'N' but NOT installed by current Ranger version; marked such entries to 'Y'. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1417) Ranger Upgrade is failing for Oracle DB flavor
[ https://issues.apache.org/jira/browse/RANGER-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1417: Attachment: RANGER-1417-1.patch > Ranger Upgrade is failing for Oracle DB flavor > -- > > Key: RANGER-1417 > URL: https://issues.apache.org/jira/browse/RANGER-1417 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 0.7.1 > > Attachments: RANGER-1417-1.patch > > > *Problem Statement :* Ranger Upgrade(0.6 to 0.7) is failing for Oracle DB > flavor as the java patches are not marked applied in x_db_version_h table by > db_setup.py script in 0.6 version. > *Proposed Solution for 0.6 :* db_setup.py script need to be fix so that > patches are marked applied after execution of each java patch. > *Proposed Solution for 0.7 or later :* From db_setup.py Identify java patches > that are marked as 'N' but NOT installed by current Ranger version; marked > such entries to 'Y'. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (RANGER-1378) There is Page not found (404) error when clicking Admin tab in Audit.
[ https://issues.apache.org/jira/browse/RANGER-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reopened RANGER-1378: - > There is Page not found (404) error when clicking Admin tab in Audit. > - > > Key: RANGER-1378 > URL: https://issues.apache.org/jira/browse/RANGER-1378 > Project: Ranger > Issue Type: Bug > Components: admin >Reporter: Qiang Zhang >Assignee: Pradeep Agrawal > Labels: patch > Attachments: > 0001-RANGER-1378-There-is-Page-not-found-404-error-when-c.patch, > Audit-Admin-error.png > > > There is Page not found (404) error when clicking Admin tab in Audit. > Wrong reason: There is no vx_trx_log table in ranger database. > Exception [EclipseLink-4002] (Eclipse Persistence Services - > 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException > Internal Exception: > com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Expression #1 of > SELECT list is not in GROUP BY clause and contains nonaggregated column > 'ranger.x_trx_log.id' which is not functionally dependent on columns in GROUP > BY clause; this is incompatible with sql_mode=only_full_group_by > Error Code: 1055 > Call: SELECT ID AS a1, ACTION AS a2, ADDED_BY_ID AS a3, ATTR_NAME AS a4, > CREATE_TIME AS a5, NEW_VAL AS a6, CLASS_TYPE AS a7, OBJECT_ID AS a8, > OBJECT_NAME AS a9, PARENT_OBJECT_CLASS_TYPE AS a10, PARENT_OBJECT_ID AS a11, > PARENT_OBJECT_NAME AS a12, PREV_VAL AS a13, REQ_ID AS a14, SESS_ID AS a15, > SESS_TYPE AS a16, TRX_ID AS a17, UPDATE_TIME AS a18, UPD_BY_ID AS a19 FROM > vx_trx_log ORDER BY CREATE_TIME DESC LIMIT ?, ? > bind => [2 parameters bound] > Query: ReadAllQuery(referenceClass=VXXTrxLog sql="SELECT ID AS a1, ACTION AS > a2, ADDED_BY_ID AS a3, ATTR_NAME AS a4, CREATE_TIME AS a5, NEW_VAL AS a6, > CLASS_TYPE AS a7, OBJECT_ID AS a8, OBJECT_NAME AS a9, > PARENT_OBJECT_CLASS_TYPE AS a10, PARENT_OBJECT_ID AS a11, PARENT_OBJECT_NAME > AS a12, PREV_VAL AS a13, REQ_ID AS a14, SESS_ID AS a15, SESS_TYPE AS a16, > TRX_ID AS a17, UPDATE_TIME AS a18, UPD_BY_ID AS a19 FROM vx_trx_log ORDER BY > CREATE_TIME DESC LIMIT ?, ?") -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (RANGER-1378) There is Page not found (404) error when clicking Admin tab in Audit.
[ https://issues.apache.org/jira/browse/RANGER-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reassigned RANGER-1378: --- Assignee: Pradeep Agrawal (was: Qiang Zhang) > There is Page not found (404) error when clicking Admin tab in Audit. > - > > Key: RANGER-1378 > URL: https://issues.apache.org/jira/browse/RANGER-1378 > Project: Ranger > Issue Type: Bug > Components: admin >Reporter: Qiang Zhang >Assignee: Pradeep Agrawal > Labels: patch > Attachments: > 0001-RANGER-1378-There-is-Page-not-found-404-error-when-c.patch, > Audit-Admin-error.png > > > There is Page not found (404) error when clicking Admin tab in Audit. > Wrong reason: There is no vx_trx_log table in ranger database. > Exception [EclipseLink-4002] (Eclipse Persistence Services - > 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException > Internal Exception: > com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Expression #1 of > SELECT list is not in GROUP BY clause and contains nonaggregated column > 'ranger.x_trx_log.id' which is not functionally dependent on columns in GROUP > BY clause; this is incompatible with sql_mode=only_full_group_by > Error Code: 1055 > Call: SELECT ID AS a1, ACTION AS a2, ADDED_BY_ID AS a3, ATTR_NAME AS a4, > CREATE_TIME AS a5, NEW_VAL AS a6, CLASS_TYPE AS a7, OBJECT_ID AS a8, > OBJECT_NAME AS a9, PARENT_OBJECT_CLASS_TYPE AS a10, PARENT_OBJECT_ID AS a11, > PARENT_OBJECT_NAME AS a12, PREV_VAL AS a13, REQ_ID AS a14, SESS_ID AS a15, > SESS_TYPE AS a16, TRX_ID AS a17, UPDATE_TIME AS a18, UPD_BY_ID AS a19 FROM > vx_trx_log ORDER BY CREATE_TIME DESC LIMIT ?, ? > bind => [2 parameters bound] > Query: ReadAllQuery(referenceClass=VXXTrxLog sql="SELECT ID AS a1, ACTION AS > a2, ADDED_BY_ID AS a3, ATTR_NAME AS a4, CREATE_TIME AS a5, NEW_VAL AS a6, > CLASS_TYPE AS a7, OBJECT_ID AS a8, OBJECT_NAME AS a9, > PARENT_OBJECT_CLASS_TYPE AS a10, PARENT_OBJECT_ID AS a11, PARENT_OBJECT_NAME > AS a12, PREV_VAL AS a13, REQ_ID AS a14, SESS_ID AS a15, SESS_TYPE AS a16, > TRX_ID AS a17, UPDATE_TIME AS a18, UPD_BY_ID AS a19 FROM vx_trx_log ORDER BY > CREATE_TIME DESC LIMIT ?, ?") -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1423) CLONE - Ranger Upgrade is failing for Oracle DB flavor
Pradeep Agrawal created RANGER-1423: --- Summary: CLONE - Ranger Upgrade is failing for Oracle DB flavor Key: RANGER-1423 URL: https://issues.apache.org/jira/browse/RANGER-1423 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 0.7.0 Reporter: Pradeep Agrawal Assignee: Pradeep Agrawal Fix For: 0.7.1 *Problem Statement :* Ranger Upgrade(0.6 to 0.7) is failing for Oracle DB flavor as the java patches are not marked applied in x_db_version_h table by db_setup.py script in 0.6 version. *Proposed Solution for 0.6 :* db_setup.py script need to be fix so that patches are marked applied after execution of each java patch. *Proposed Solution for 0.7 or later :* From db_setup.py Identify java patches that are marked as 'N' but NOT installed by current Ranger version; marked such entries to 'Y'. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1423) CLONE - Ranger Upgrade is failing for Oracle DB flavor
[ https://issues.apache.org/jira/browse/RANGER-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1423: Description: *Problem Statement :* Ranger Upgrade(0.6 to 0.7) is failing for Oracle DB flavor as the java patches are not marked applied in x_db_version_h table by db_setup.py script in 0.6 version. *Proposed Solution for 0.6 :* db_setup.py script need to be fix so that patches are marked applied after execution of each java patch. was: *Problem Statement :* Ranger Upgrade(0.6 to 0.7) is failing for Oracle DB flavor as the java patches are not marked applied in x_db_version_h table by db_setup.py script in 0.6 version. *Proposed Solution for 0.6 :* db_setup.py script need to be fix so that patches are marked applied after execution of each java patch. *Proposed Solution for 0.7 or later :* From db_setup.py Identify java patches that are marked as 'N' but NOT installed by current Ranger version; marked such entries to 'Y'. > CLONE - Ranger Upgrade is failing for Oracle DB flavor > -- > > Key: RANGER-1423 > URL: https://issues.apache.org/jira/browse/RANGER-1423 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.6.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 0.6.4 > > > *Problem Statement :* Ranger Upgrade(0.6 to 0.7) is failing for Oracle DB > flavor as the java patches are not marked applied in x_db_version_h table by > db_setup.py script in 0.6 version. > *Proposed Solution for 0.6 :* db_setup.py script need to be fix so that > patches are marked applied after execution of each java patch. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1423) CLONE - Ranger Upgrade is failing for Oracle DB flavor
[ https://issues.apache.org/jira/browse/RANGER-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1423: Fix Version/s: (was: 0.7.1) 0.6.4 > CLONE - Ranger Upgrade is failing for Oracle DB flavor > -- > > Key: RANGER-1423 > URL: https://issues.apache.org/jira/browse/RANGER-1423 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.6.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 0.6.4 > > > *Problem Statement :* Ranger Upgrade(0.6 to 0.7) is failing for Oracle DB > flavor as the java patches are not marked applied in x_db_version_h table by > db_setup.py script in 0.6 version. > *Proposed Solution for 0.6 :* db_setup.py script need to be fix so that > patches are marked applied after execution of each java patch. > *Proposed Solution for 0.7 or later :* From db_setup.py Identify java patches > that are marked as 'N' but NOT installed by current Ranger version; marked > such entries to 'Y'. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1423) CLONE - Ranger Upgrade is failing for Oracle DB flavor
[ https://issues.apache.org/jira/browse/RANGER-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1423: Affects Version/s: (was: 0.7.0) 0.6.0 > CLONE - Ranger Upgrade is failing for Oracle DB flavor > -- > > Key: RANGER-1423 > URL: https://issues.apache.org/jira/browse/RANGER-1423 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.6.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 0.6.4 > > > *Problem Statement :* Ranger Upgrade(0.6 to 0.7) is failing for Oracle DB > flavor as the java patches are not marked applied in x_db_version_h table by > db_setup.py script in 0.6 version. > *Proposed Solution for 0.6 :* db_setup.py script need to be fix so that > patches are marked applied after execution of each java patch. > *Proposed Solution for 0.7 or later :* From db_setup.py Identify java patches > that are marked as 'N' but NOT installed by current Ranger version; marked > such entries to 'Y'. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1423) CLONE - Ranger Upgrade is failing for Oracle DB flavor
[ https://issues.apache.org/jira/browse/RANGER-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1423: Attachment: RANGER-1423-1.patch > CLONE - Ranger Upgrade is failing for Oracle DB flavor > -- > > Key: RANGER-1423 > URL: https://issues.apache.org/jira/browse/RANGER-1423 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.6.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 0.6.4 > > Attachments: RANGER-1423-1.patch > > > *Problem Statement :* Ranger Upgrade(0.6 to 0.7) is failing for Oracle DB > flavor as the java patches are not marked applied in x_db_version_h table by > db_setup.py script in 0.6 version. > *Proposed Solution for 0.6 :* db_setup.py script need to be fix so that > patches are marked applied after execution of each java patch. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1378) There is Page not found (404) error when clicking Admin tab in Audit.
[ https://issues.apache.org/jira/browse/RANGER-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1378: Attachment: RANGER-1378-1.patch > There is Page not found (404) error when clicking Admin tab in Audit. > - > > Key: RANGER-1378 > URL: https://issues.apache.org/jira/browse/RANGER-1378 > Project: Ranger > Issue Type: Bug > Components: admin >Reporter: Qiang Zhang >Assignee: Pradeep Agrawal > Labels: patch > Attachments: > 0001-RANGER-1378-There-is-Page-not-found-404-error-when-c.patch, > Audit-Admin-error.png, RANGER-1378-1.patch > > > There is Page not found (404) error when clicking Admin tab in Audit. > Wrong reason: There is no vx_trx_log table in ranger database. > Exception [EclipseLink-4002] (Eclipse Persistence Services - > 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException > Internal Exception: > com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Expression #1 of > SELECT list is not in GROUP BY clause and contains nonaggregated column > 'ranger.x_trx_log.id' which is not functionally dependent on columns in GROUP > BY clause; this is incompatible with sql_mode=only_full_group_by > Error Code: 1055 > Call: SELECT ID AS a1, ACTION AS a2, ADDED_BY_ID AS a3, ATTR_NAME AS a4, > CREATE_TIME AS a5, NEW_VAL AS a6, CLASS_TYPE AS a7, OBJECT_ID AS a8, > OBJECT_NAME AS a9, PARENT_OBJECT_CLASS_TYPE AS a10, PARENT_OBJECT_ID AS a11, > PARENT_OBJECT_NAME AS a12, PREV_VAL AS a13, REQ_ID AS a14, SESS_ID AS a15, > SESS_TYPE AS a16, TRX_ID AS a17, UPDATE_TIME AS a18, UPD_BY_ID AS a19 FROM > vx_trx_log ORDER BY CREATE_TIME DESC LIMIT ?, ? > bind => [2 parameters bound] > Query: ReadAllQuery(referenceClass=VXXTrxLog sql="SELECT ID AS a1, ACTION AS > a2, ADDED_BY_ID AS a3, ATTR_NAME AS a4, CREATE_TIME AS a5, NEW_VAL AS a6, > CLASS_TYPE AS a7, OBJECT_ID AS a8, OBJECT_NAME AS a9, > PARENT_OBJECT_CLASS_TYPE AS a10, PARENT_OBJECT_ID AS a11, PARENT_OBJECT_NAME > AS a12, PREV_VAL AS a13, REQ_ID AS a14, SESS_ID AS a15, SESS_TYPE AS a16, > TRX_ID AS a17, UPDATE_TIME AS a18, UPD_BY_ID AS a19 FROM vx_trx_log ORDER BY > CREATE_TIME DESC LIMIT ?, ?") -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1378) Update MySQL Schema to fix issues related to only_full_group_by restriction of MySQL 5.7 version
[ https://issues.apache.org/jira/browse/RANGER-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1378: Summary: Update MySQL Schema to fix issues related to only_full_group_by restriction of MySQL 5.7 version (was: There is Page not found (404) error when clicking Admin tab in Audit.) > Update MySQL Schema to fix issues related to only_full_group_by restriction > of MySQL 5.7 version > > > Key: RANGER-1378 > URL: https://issues.apache.org/jira/browse/RANGER-1378 > Project: Ranger > Issue Type: Bug > Components: admin >Reporter: Qiang Zhang >Assignee: Pradeep Agrawal > Labels: patch > Attachments: > 0001-RANGER-1378-There-is-Page-not-found-404-error-when-c.patch, > Audit-Admin-error.png, RANGER-1378-1.patch > > > There is Page not found (404) error when clicking Admin tab in Audit. > Wrong reason: There is no vx_trx_log table in ranger database. > Exception [EclipseLink-4002] (Eclipse Persistence Services - > 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException > Internal Exception: > com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Expression #1 of > SELECT list is not in GROUP BY clause and contains nonaggregated column > 'ranger.x_trx_log.id' which is not functionally dependent on columns in GROUP > BY clause; this is incompatible with sql_mode=only_full_group_by > Error Code: 1055 > Call: SELECT ID AS a1, ACTION AS a2, ADDED_BY_ID AS a3, ATTR_NAME AS a4, > CREATE_TIME AS a5, NEW_VAL AS a6, CLASS_TYPE AS a7, OBJECT_ID AS a8, > OBJECT_NAME AS a9, PARENT_OBJECT_CLASS_TYPE AS a10, PARENT_OBJECT_ID AS a11, > PARENT_OBJECT_NAME AS a12, PREV_VAL AS a13, REQ_ID AS a14, SESS_ID AS a15, > SESS_TYPE AS a16, TRX_ID AS a17, UPDATE_TIME AS a18, UPD_BY_ID AS a19 FROM > vx_trx_log ORDER BY CREATE_TIME DESC LIMIT ?, ? > bind => [2 parameters bound] > Query: ReadAllQuery(referenceClass=VXXTrxLog sql="SELECT ID AS a1, ACTION AS > a2, ADDED_BY_ID AS a3, ATTR_NAME AS a4, CREATE_TIME AS a5, NEW_VAL AS a6, > CLASS_TYPE AS a7, OBJECT_ID AS a8, OBJECT_NAME AS a9, > PARENT_OBJECT_CLASS_TYPE AS a10, PARENT_OBJECT_ID AS a11, PARENT_OBJECT_NAME > AS a12, PREV_VAL AS a13, REQ_ID AS a14, SESS_ID AS a15, SESS_TYPE AS a16, > TRX_ID AS a17, UPDATE_TIME AS a18, UPD_BY_ID AS a19 FROM vx_trx_log ORDER BY > CREATE_TIME DESC LIMIT ?, ?") -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1378) Update MySQL Schema to fix issues related to only_full_group_by restriction of MySQL 5.7 version
[ https://issues.apache.org/jira/browse/RANGER-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900684#comment-15900684 ] Pradeep Agrawal commented on RANGER-1378: - Patch committed in Apache Ranger master branch : https://github.com/apache/ranger/commit/f3473d23fc2c87ff03fc5c2c826a26155742e791 Patch committed in Apache Ranger 0.7 branch : https://github.com/apache/ranger/commit/fa98f45ff26bb67d7685b10a0e17496ba37a5f6b > Update MySQL Schema to fix issues related to only_full_group_by restriction > of MySQL 5.7 version > > > Key: RANGER-1378 > URL: https://issues.apache.org/jira/browse/RANGER-1378 > Project: Ranger > Issue Type: Bug > Components: admin >Reporter: Qiang Zhang >Assignee: Pradeep Agrawal > Labels: patch > Fix For: 0.7.1 > > Attachments: > 0001-RANGER-1378-There-is-Page-not-found-404-error-when-c.patch, > Audit-Admin-error.png, RANGER-1378-1.patch > > > There is Page not found (404) error when clicking Admin tab in Audit. > Wrong reason: There is no vx_trx_log table in ranger database. > Exception [EclipseLink-4002] (Eclipse Persistence Services - > 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException > Internal Exception: > com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Expression #1 of > SELECT list is not in GROUP BY clause and contains nonaggregated column > 'ranger.x_trx_log.id' which is not functionally dependent on columns in GROUP > BY clause; this is incompatible with sql_mode=only_full_group_by > Error Code: 1055 > Call: SELECT ID AS a1, ACTION AS a2, ADDED_BY_ID AS a3, ATTR_NAME AS a4, > CREATE_TIME AS a5, NEW_VAL AS a6, CLASS_TYPE AS a7, OBJECT_ID AS a8, > OBJECT_NAME AS a9, PARENT_OBJECT_CLASS_TYPE AS a10, PARENT_OBJECT_ID AS a11, > PARENT_OBJECT_NAME AS a12, PREV_VAL AS a13, REQ_ID AS a14, SESS_ID AS a15, > SESS_TYPE AS a16, TRX_ID AS a17, UPDATE_TIME AS a18, UPD_BY_ID AS a19 FROM > vx_trx_log ORDER BY CREATE_TIME DESC LIMIT ?, ? > bind => [2 parameters bound] > Query: ReadAllQuery(referenceClass=VXXTrxLog sql="SELECT ID AS a1, ACTION AS > a2, ADDED_BY_ID AS a3, ATTR_NAME AS a4, CREATE_TIME AS a5, NEW_VAL AS a6, > CLASS_TYPE AS a7, OBJECT_ID AS a8, OBJECT_NAME AS a9, > PARENT_OBJECT_CLASS_TYPE AS a10, PARENT_OBJECT_ID AS a11, PARENT_OBJECT_NAME > AS a12, PREV_VAL AS a13, REQ_ID AS a14, SESS_ID AS a15, SESS_TYPE AS a16, > TRX_ID AS a17, UPDATE_TIME AS a18, UPD_BY_ID AS a19 FROM vx_trx_log ORDER BY > CREATE_TIME DESC LIMIT ?, ?") -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1417) Ranger Upgrade is failing for Oracle DB flavor
[ https://issues.apache.org/jira/browse/RANGER-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900688#comment-15900688 ] Pradeep Agrawal commented on RANGER-1417: - Patch committed in Apache Ranger master branch : https://github.com/apache/ranger/commit/759a7b3e61bf281906c6384d47a7f6de25dc791c Patch committed in Apache Ranger 0.7 branch : https://github.com/apache/ranger/commit/16cc0d30c08dd7ffe17095c451062203f32c26db > Ranger Upgrade is failing for Oracle DB flavor > -- > > Key: RANGER-1417 > URL: https://issues.apache.org/jira/browse/RANGER-1417 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 0.7.1 > > Attachments: RANGER-1417-1.patch > > > *Problem Statement :* Ranger Upgrade(0.6 to 0.7) is failing for Oracle DB > flavor as the java patches are not marked applied in x_db_version_h table by > db_setup.py script in 0.6 version. > *Proposed Solution for 0.6 :* db_setup.py script need to be fix so that > patches are marked applied after execution of each java patch. > *Proposed Solution for 0.7 or later :* From db_setup.py Identify java patches > that are marked as 'N' but NOT installed by current Ranger version; marked > such entries to 'Y'. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1423) CLONE - Ranger Upgrade is failing for Oracle DB flavor
[ https://issues.apache.org/jira/browse/RANGER-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900697#comment-15900697 ] Pradeep Agrawal commented on RANGER-1423: - Patch committed in Ranger 0.6 branch : https://github.com/apache/ranger/commit/9561f0d5b31f2bf48147df2171b0dceff8f5000c > CLONE - Ranger Upgrade is failing for Oracle DB flavor > -- > > Key: RANGER-1423 > URL: https://issues.apache.org/jira/browse/RANGER-1423 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.6.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 0.6.4 > > Attachments: RANGER-1423-1.patch > > > *Problem Statement :* Ranger Upgrade(0.6 to 0.7) is failing for Oracle DB > flavor as the java patches are not marked applied in x_db_version_h table by > db_setup.py script in 0.6 version. > *Proposed Solution for 0.6 :* db_setup.py script need to be fix so that > patches are marked applied after execution of each java patch. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1440) Improve install script to retry failing statement
Pradeep Agrawal created RANGER-1440: --- Summary: Improve install script to retry failing statement Key: RANGER-1440 URL: https://issues.apache.org/jira/browse/RANGER-1440 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 0.7.0 Reporter: Pradeep Agrawal Assignee: Pradeep Agrawal Fix For: 0.7.1 Improve install script to retry failing statement as some time create/update statement may fail due to network latency or during parallel install in Ranger HA environment. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1442) https port not configurable
[ https://issues.apache.org/jira/browse/RANGER-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15904408#comment-15904408 ] Pradeep Agrawal commented on RANGER-1442: - Hi [~yujie.li] , Please do not mix the shutdown port with the start port. From the patch it seems you are proposing to assign value of property 'ranger.service.https.port' to shutdown port. I agree that shutdown property 'ranger.service.shutdown.port' is not there in ranger-admin-site.xml but its there in ranger-admin-default-site.xml. In Ranger 0.6 version of EmbeddedServer.java 'ranger-admin-default-site.xml' in not being read and that's why it seems an issue. To solve this issue you can add below property in your ranger-admin-site.xml and restart Ranger. Apart from this property other properties of ranger-admin-default-site.xml can be overridden in ranger-admin-site.xml file. If a property is available at both file then value from ranger-admin-site.xml shall be used. ranger.service.shutdown.port 6185 Please note that EmbeddedServer.java code of Ranger 0.7 branch has the provision to read value from both config file (ranger-admin-default-site.xml and ranger-admin-site.xml) > https port not configurable > --- > > Key: RANGER-1442 > URL: https://issues.apache.org/jira/browse/RANGER-1442 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.6.2 >Reporter: Yujie Li > Fix For: 0.6.2 > > Attachments: 0001-RANGER-1442-https-port-not-configurable.patch > > > Ranger doesn't take the https port value (default 6182) from > ranger-admin-site.xml and uses hardcoded value (6185) after enabling SSL -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (RANGER-1442) https port not configurable
[ https://issues.apache.org/jira/browse/RANGER-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reassigned RANGER-1442: --- Assignee: Pradeep Agrawal > https port not configurable > --- > > Key: RANGER-1442 > URL: https://issues.apache.org/jira/browse/RANGER-1442 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.6.2 >Reporter: Yujie Li >Assignee: Pradeep Agrawal > Fix For: 0.6.2 > > Attachments: 0001-RANGER-1442-https-port-not-configurable.patch > > > Ranger doesn't take the https port value (default 6182) from > ranger-admin-site.xml and uses hardcoded value (6185) after enabling SSL -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1443) Ranger binds to 127.0.0.1 after enabling ssl
[ https://issues.apache.org/jira/browse/RANGER-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15904411#comment-15904411 ] Pradeep Agrawal commented on RANGER-1443: - [~yujie.li] Please provide more details on this and add steps to reproduce the case. > Ranger binds to 127.0.0.1 after enabling ssl > > > Key: RANGER-1443 > URL: https://issues.apache.org/jira/browse/RANGER-1443 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.6.2 >Reporter: Yujie Li > > With http, Ranger binds with 0.0.0.0. But after enabling ssl, it only listens > to 127.0.0.1 (localhost). Other IPs can't access to Ranger UI. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (RANGER-1443) Ranger binds to 127.0.0.1 after enabling ssl
[ https://issues.apache.org/jira/browse/RANGER-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reassigned RANGER-1443: --- Assignee: Pradeep Agrawal > Ranger binds to 127.0.0.1 after enabling ssl > > > Key: RANGER-1443 > URL: https://issues.apache.org/jira/browse/RANGER-1443 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.6.2 >Reporter: Yujie Li >Assignee: Pradeep Agrawal > > With http, Ranger binds with 0.0.0.0. But after enabling ssl, it only listens > to 127.0.0.1 (localhost). Other IPs can't access to Ranger UI. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1442) https port not configurable
[ https://issues.apache.org/jira/browse/RANGER-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15904838#comment-15904838 ] Pradeep Agrawal commented on RANGER-1442: - [~yujie.li] Can you attach your ranger-admin-site.xml and ranger-admin-default-site.xml ; i want to see what configuration you are providing and on which port service is running. Also attach the screen shot of Ranger UI to know on which port ranger is running. > https port not configurable > --- > > Key: RANGER-1442 > URL: https://issues.apache.org/jira/browse/RANGER-1442 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.6.2 >Reporter: Yujie Li >Assignee: Pradeep Agrawal > Fix For: 0.6.2 > > Attachments: 0001-RANGER-1442-https-port-not-configurable.patch > > > Ranger doesn't take the https port value (default 6182) from > ranger-admin-site.xml and uses hardcoded value (6185) after enabling SSL -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1440) Improve install script to retry failing statement
[ https://issues.apache.org/jira/browse/RANGER-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1440: Attachment: RANGER-1440-1.patch > Improve install script to retry failing statement > - > > Key: RANGER-1440 > URL: https://issues.apache.org/jira/browse/RANGER-1440 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 0.7.1 > > Attachments: RANGER-1440-1.patch > > > Improve install script to retry failing statement as some time create/update > statement may fail due to network latency or during parallel install in > Ranger HA environment. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1440) Improve install script to retry failing statement
[ https://issues.apache.org/jira/browse/RANGER-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15905448#comment-15905448 ] Pradeep Agrawal commented on RANGER-1440: - Patch committed in Apache Ranger master branch : https://github.com/apache/ranger/commit/284ca416a60533139889a0c3f68f20ae12fdd3cc Patch committed in Apache Ranger 0.7 branch : https://github.com/apache/ranger/commit/8f825cad14ede10bfd090e53a1d05c39fbabc6b5 > Improve install script to retry failing statement > - > > Key: RANGER-1440 > URL: https://issues.apache.org/jira/browse/RANGER-1440 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 0.7.1 > > Attachments: RANGER-1440-1.patch > > > Improve install script to retry failing statement as some time create/update > statement may fail due to network latency or during parallel install in > Ranger HA environment. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1442) https port not configurable
[ https://issues.apache.org/jira/browse/RANGER-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1442: Fix Version/s: (was: 0.6.2) > https port not configurable > --- > > Key: RANGER-1442 > URL: https://issues.apache.org/jira/browse/RANGER-1442 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.6.2 >Reporter: Yujie Li >Assignee: Pradeep Agrawal > Attachments: 0001-RANGER-1442-https-port-not-configurable.patch > > > Ranger doesn't take the https port value (default 6182) from > ranger-admin-site.xml and uses hardcoded value (6185) after enabling SSL -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (RANGER-1442) https port not configurable
[ https://issues.apache.org/jira/browse/RANGER-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal resolved RANGER-1442. - Resolution: Invalid > https port not configurable > --- > > Key: RANGER-1442 > URL: https://issues.apache.org/jira/browse/RANGER-1442 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.6.2 >Reporter: Yujie Li >Assignee: Pradeep Agrawal > Attachments: 0001-RANGER-1442-https-port-not-configurable.patch > > > Ranger doesn't take the https port value (default 6182) from > ranger-admin-site.xml and uses hardcoded value (6185) after enabling SSL -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1186) Ranger Source: eclipse
[ https://issues.apache.org/jira/browse/RANGER-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15950321#comment-15950321 ] Pradeep Agrawal commented on RANGER-1186: - [~jonesn] We can commit a fix specific to eclipse IDE. If you see a fix is needed then mvn build should also work with proposed fix. Accordingly you can propose and/or create RR. > Ranger Source: eclipse > -- > > Key: RANGER-1186 > URL: https://issues.apache.org/jira/browse/RANGER-1186 > Project: Ranger > Issue Type: Bug > Components: documentation >Affects Versions: 0.7.0 > Environment: eclipse neon, ubuntu 16.10 >Reporter: Nigel Jones >Assignee: Pradeep Agrawal > Labels: VirtualDataConnector > Attachments: RANGER-1186_Ranger_Source_Eclipse.pdf, ranger_me0.PNG, > ranger_me1.PNG > > > I can happily build ranger in my Ubuntu 16.10 environment with > - open jdk 1.8.0_102 > - maven 3.3.9 > I also have eclipse neon installed in this environment > The build/setup instructions at > http://ranger.apache.org/quick_start_guide.html have minimal instructions for > eclipse. > I imported the top level ranger directory using the m2e plugin as provided in > neon. > This failed with numerous errors > Is anyone actively building with eclipse? If so can we update the website > with current setup information? > If not I'll use this JIRA to record the issues & hope to address them & > update the docs ;-) > Screenshots to follow -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1490) Increase size of sort_order column of x_policy_resource_map
Pradeep Agrawal created RANGER-1490: --- Summary: Increase size of sort_order column of x_policy_resource_map Key: RANGER-1490 URL: https://issues.apache.org/jira/browse/RANGER-1490 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 0.7.0, 0.6.0, 0.5.0 Reporter: Pradeep Agrawal Assignee: Pradeep Agrawal Fix For: 1.0.0 Problem Statement : Currently data type of sort_order column is tinyint which can accept maximum 128 unsigned number; if any policy is having more than 128 resource entries then data truncation error might be generated at DB end and application will not be able to insert entry of any more resources for specific policy. Proposed Solution : Change data type of sort_order column of 'x_policy_resource_map' from tinyint to integer(4 byte) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1522) Update consolidated db schema script for SQLServer DB flavor to reduce execution time
Pradeep Agrawal created RANGER-1522: --- Summary: Update consolidated db schema script for SQLServer DB flavor to reduce execution time Key: RANGER-1522 URL: https://issues.apache.org/jira/browse/RANGER-1522 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 1.0.0, 0.7.1 Reporter: Pradeep Agrawal Assignee: Pradeep Agrawal Fix For: 1.0.0, 0.7.1 Modify the schema file to exclude the GO statements or use the minimum number of GO Statement. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1522) Update consolidated db schema script for SQLServer DB flavor to reduce execution time
[ https://issues.apache.org/jira/browse/RANGER-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1522: Attachment: RANGER-1522-master-branch.patch RANGER-1522-ranger-0.7-branch.patch > Update consolidated db schema script for SQLServer DB flavor to reduce > execution time > - > > Key: RANGER-1522 > URL: https://issues.apache.org/jira/browse/RANGER-1522 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0, 0.7.1 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 1.0.0, 0.7.1 > > Attachments: RANGER-1522-master-branch.patch, > RANGER-1522-ranger-0.7-branch.patch > > > Modify the schema file to exclude the GO statements or use the minimum number > of GO Statement. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1521) Ranger database script for mysql requires admin privileges for replicated database
[
https://issues.apache.org/jira/browse/RANGER-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15972680#comment-15972680
]
Pradeep Agrawal commented on RANGER-1521:
-
According to my understanding from
[link|https://dev.mysql.com/doc/refman/5.7/en/create-procedure.html] it can't
be a deterministic function as there are insert SQL statement in these
functions.
> Ranger database script for mysql requires admin privileges for replicated
> database
> --
>
> Key: RANGER-1521
> URL: https://issues.apache.org/jira/browse/RANGER-1521
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Affects Versions: 0.6.2
>Reporter: Eric Yang
> Attachments: RANGER-1521.patch
>
>
> When running install or upgrade on replicated MySQL or MariaDB, ranger
> installation might fail with:
> {code}
> Error executing: CREATE FUNCTION `getTempPolicyCount`(assetId bigint, resId
> bigint) RETURNS int(11) BEGIN DECLARE tempPolicyCount int default 1; DECLARE
> dbResourceId bigint; DECLARE exitLoop int DEFAULT FALSE; DECLARE policyList
> CURSOR FOR SELECT id from x_resource where asset_id = assetId; DECLARE
> CONTINUE HANDLER FOR NOT FOUND SET exitLoop = true; OPEN policyList;
> readPolicy : LOOP FETCH policyList into dbResourceId; IF exitLoop THEN set
> tempPolicyCount = tempPolicyCount + 1; LEAVE readPolicy; END IF; IF (resId =
> dbResourceId) THEN LEAVE readPolicy; END IF; set tempPolicyCount =
> tempPolicyCount + 1; END LOOP; CLOSE policyList; RETURN tempPolicyCount; END
> java.sql.SQLException: This function has none of DETERMINISTIC, NO SQL, or
> READS SQL DATA in its declaration and binary logging is enabled (you *might*
> want to use the less safe log_bin_trust_function_creators variable)
> SQLException : SQL state: HY000 java.sql.SQLException: This function has none
> of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary
> logging is enabled (you *might* want to use the less safe
> log_bin_trust_function_creators variable) ErrorCode: 1418 2017-04-05
> 22:59:00,345 [JISQL]
> /usr/jdk64/java-1.8.0-openjdk-1.8.0.121-0.b13.el7_3.x86_64/bin/java -cp
> /usr/iop/current/ranger-admin/ews/lib/mysql-connector-java.jar:/usr/iop/current/ranger-admin/jisql/lib/*
> org.apache.util.sql.Jisql -driver mysqlconj -cstring
> jdbc:mysql://tmh21-3-dal10-bi-mn000.fyre.ibm.com/ranger -u 'ranger' -p
> '' -noheader -trim -c \; -query "delete from x_db_version_h where
> version='007' and active='N' and
> updated_by='tmh21-3-dal10-bi-mn004.fyre.ibm.com';" 2017-04-05 22:59:00,781
> [E] 007-updateBlankPolicyName.sql import failed!
> {code}
> Two files under ranger-admin/db/mysql/patches:
> 007-updateBlankPolicyName.sql and 008-removeTrailingSlash.sql are using
> rand() functions to generate transaction ID, which makes them
> non-deterministic functions and are causing failures on replicated MySQL
> database.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (RANGER-1522) Update consolidated db schema script for SQLServer DB flavor to reduce execution time
[ https://issues.apache.org/jira/browse/RANGER-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1522: Attachment: (was: RANGER-1522-master-branch.patch) > Update consolidated db schema script for SQLServer DB flavor to reduce > execution time > - > > Key: RANGER-1522 > URL: https://issues.apache.org/jira/browse/RANGER-1522 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0, 0.7.1 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 1.0.0, 0.7.1 > > > Modify the schema file to exclude the GO statements or use the minimum number > of GO Statement. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1522) Update consolidated db schema script for SQLServer DB flavor to reduce execution time
[ https://issues.apache.org/jira/browse/RANGER-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1522: Attachment: (was: RANGER-1522-ranger-0.7-branch.patch) > Update consolidated db schema script for SQLServer DB flavor to reduce > execution time > - > > Key: RANGER-1522 > URL: https://issues.apache.org/jira/browse/RANGER-1522 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0, 0.7.1 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 1.0.0, 0.7.1 > > > Modify the schema file to exclude the GO statements or use the minimum number > of GO Statement. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1522) Update consolidated db schema script for SQLServer DB flavor to reduce execution time
[ https://issues.apache.org/jira/browse/RANGER-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1522: Attachment: RANGER-1522-0.7-branch.patch RANGER-1522-master-branch.patch > Update consolidated db schema script for SQLServer DB flavor to reduce > execution time > - > > Key: RANGER-1522 > URL: https://issues.apache.org/jira/browse/RANGER-1522 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0, 0.7.1 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 1.0.0, 0.7.1 > > Attachments: RANGER-1522-0.7-branch.patch, > RANGER-1522-master-branch.patch > > > Modify the schema file to exclude the GO statements or use the minimum number > of GO Statement. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1522) Update consolidated db schema script for SQLServer DB flavor to reduce execution time
[ https://issues.apache.org/jira/browse/RANGER-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974394#comment-15974394 ] Pradeep Agrawal commented on RANGER-1522: - RR for Ranger master branch: https://reviews.apache.org/r/58525/ RR for Ranger 0.7 branch: https://reviews.apache.org/r/58526/ > Update consolidated db schema script for SQLServer DB flavor to reduce > execution time > - > > Key: RANGER-1522 > URL: https://issues.apache.org/jira/browse/RANGER-1522 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0, 0.7.1 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 1.0.0, 0.7.1 > > Attachments: RANGER-1522-0.7-branch.patch, > RANGER-1522-master-branch.patch > > > Modify the schema file to exclude the GO statements or use the minimum number > of GO Statement. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1490) Increase size of sort_order column of x_policy_resource_map
[ https://issues.apache.org/jira/browse/RANGER-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1490: Attachment: RANGER-1490-master-branch.patch > Increase size of sort_order column of x_policy_resource_map > --- > > Key: RANGER-1490 > URL: https://issues.apache.org/jira/browse/RANGER-1490 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.5.0, 0.6.0, 0.7.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 1.0.0 > > Attachments: RANGER-1490-master-branch.patch > > > Problem Statement : Currently data type of sort_order column is tinyint which > can accept maximum 128 unsigned number; if any policy is having more than 128 > resource entries then data truncation error might be generated at DB end and > application will not be able to insert entry of any more resources for > specific policy. > Proposed Solution : Change data type of sort_order column of > 'x_policy_resource_map' from tinyint to integer(4 byte) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1490) Increase size of sort_order column of x_policy_resource_map
[ https://issues.apache.org/jira/browse/RANGER-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15983753#comment-15983753 ] Pradeep Agrawal commented on RANGER-1490: - Committed to ranger 0.7 branch: https://github.com/apache/ranger/commit/c6f5f101b75f8ae0386a94ffa36e8b3653649c7a Committed to the ranger master branch: https://github.com/apache/ranger/commit/37667d7faf87ece5d236a19891046d66f1c1 > Increase size of sort_order column of x_policy_resource_map > --- > > Key: RANGER-1490 > URL: https://issues.apache.org/jira/browse/RANGER-1490 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.5.0, 0.6.0, 0.7.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 1.0.0, 0.7.1 > > Attachments: RANGER-1490-master-branch.patch > > > Problem Statement : Currently data type of sort_order column is tinyint which > can accept maximum 128 unsigned number; if any policy is having more than 128 > resource entries then data truncation error might be generated at DB end and > application will not be able to insert entry of any more resources for > specific policy. > Proposed Solution : Change data type of sort_order column of > 'x_policy_resource_map' from tinyint to integer(4 byte) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1481) Capture cluster name in ranger audit info
[ https://issues.apache.org/jira/browse/RANGER-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15983766#comment-15983766 ] Pradeep Agrawal commented on RANGER-1481: - Committed to ranger 0.7 branch: https://github.com/apache/ranger/commit/1bd34894bdae33e159b2de89c503b060ff8351e9 Committed to the ranger master branch: https://github.com/apache/ranger/commit/ac24f705fb7d1902c8f8553ed98b988ac59678ec > Capture cluster name in ranger audit info > - > > Key: RANGER-1481 > URL: https://issues.apache.org/jira/browse/RANGER-1481 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: bhavik patel >Assignee: bhavik patel > Fix For: 1.0.0, 0.7.1 > > Attachments: RANGER-1481-07-1.patch, RANGER-1481-07-2.patch, > RANGER-1481-07-3.patch, RANGER-1481-07.patch, RANGER-1481-master-1.patch, > RANGER-1481-master-2.patch, RANGER-1481-master-3.patch, > RANGER-1481-master-4.patch, RANGER-1481-master.patch > > > In order to support Ranger authorization from multiple clusters, it will be > useful to capture details of Ambari cluster name, Ranger needs to make > provision to capture that info to be shown in Audit Access logs. > This will be helpful when centralized Ranger is used to authorize hadoop > components across multiple clusters setup by Ambari. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1550) HDFS test connection and resource lookup failing
Pradeep Agrawal created RANGER-1550: --- Summary: HDFS test connection and resource lookup failing Key: RANGER-1550 URL: https://issues.apache.org/jira/browse/RANGER-1550 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 1.0.0, 0.7.1 Reporter: Pradeep Agrawal Assignee: Pradeep Agrawal Fix For: 1.0.0, 0.7.1 Test connection is failing with below message on UI. Connection Failed. Unable to retrieve any files using given parameters, You can still save the repository and start creating policies, but you would not be able to use autocomplete for resource names. Check ranger_admin.log for more info. java.lang.NullPointerException. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1550) HDFS test connection and resource lookup failing
[ https://issues.apache.org/jira/browse/RANGER-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1550: Attachment: RANGER-1550-ranger-0.7-branch.patch RANGER-1550-master-branch.patch > HDFS test connection and resource lookup failing > > > Key: RANGER-1550 > URL: https://issues.apache.org/jira/browse/RANGER-1550 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0, 0.7.1 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 1.0.0, 0.7.1 > > Attachments: RANGER-1550-master-branch.patch, > RANGER-1550-ranger-0.7-branch.patch > > > Test connection is failing with below message on UI. > Connection Failed. > Unable to retrieve any files using given parameters, You can still save the > repository and start creating policies, but you would not be able to use > autocomplete for resource names. Check ranger_admin.log for more info. > java.lang.NullPointerException. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1550) HDFS test connection and resource lookup failing
[ https://issues.apache.org/jira/browse/RANGER-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993234#comment-15993234 ] Pradeep Agrawal commented on RANGER-1550: - Patch committed in master branch: https://github.com/apache/ranger/commit/21066540d388402d12413144e63a2d74becf1fd1 Patch committed in ranger-0.7 branch: https://github.com/apache/ranger/commit/4ff214e0bcc43e737783461f99cf63123ea56f63 > HDFS test connection and resource lookup failing > > > Key: RANGER-1550 > URL: https://issues.apache.org/jira/browse/RANGER-1550 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0, 0.7.1 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 1.0.0, 0.7.1 > > Attachments: RANGER-1550-master-branch.patch, > RANGER-1550-ranger-0.7-branch.patch > > > Test connection is failing with below message on UI. > Connection Failed. > Unable to retrieve any files using given parameters, You can still save the > repository and start creating policies, but you would not be able to use > autocomplete for resource names. Check ranger_admin.log for more info. > java.lang.NullPointerException. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1557) Add Nifi as default in supported component list
Pradeep Agrawal created RANGER-1557: --- Summary: Add Nifi as default in supported component list Key: RANGER-1557 URL: https://issues.apache.org/jira/browse/RANGER-1557 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 0.7.0, 1.0.0 Reporter: Pradeep Agrawal Assignee: Pradeep Agrawal Fix For: 1.0.0, 0.7.1 Add Nifi as default in supported component list -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1557) Add Nifi as default in supported component list
[ https://issues.apache.org/jira/browse/RANGER-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1557: Attachment: RANGER-1557-master.patch > Add Nifi as default in supported component list > --- > > Key: RANGER-1557 > URL: https://issues.apache.org/jira/browse/RANGER-1557 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.0, 1.0.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 1.0.0, 0.7.1 > > Attachments: RANGER-1557-master.patch > > > Add Nifi as default in supported component list -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1557) Add Nifi as default in supported component list
[ https://issues.apache.org/jira/browse/RANGER-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997754#comment-15997754 ] Pradeep Agrawal commented on RANGER-1557: - Committed to master branch : https://github.com/apache/ranger/commit/ba122d3adc0722e62df8abe61319bea23a784a66 Committed to 0.7 branch : https://github.com/apache/ranger/commit/b623fd3aca34a48768bf06d9bda02791a42c14dd > Add Nifi as default in supported component list > --- > > Key: RANGER-1557 > URL: https://issues.apache.org/jira/browse/RANGER-1557 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.0, 1.0.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 1.0.0, 0.7.1 > > Attachments: RANGER-1557-master.patch > > > Add Nifi as default in supported component list -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (RANGER-1612) When servicedef is accessed, one of the properties "enableDenyPolicies" is returned as "false" if there is no value set for it.
[ https://issues.apache.org/jira/browse/RANGER-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reassigned RANGER-1612: --- Assignee: Pradeep Agrawal > When servicedef is accessed, one of the properties "enableDenyPolicies" is > returned as "false" if there is no value set for it. > --- > > Key: RANGER-1612 > URL: https://issues.apache.org/jira/browse/RANGER-1612 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Anuja Leekha >Assignee: Pradeep Agrawal > Labels: ranger > Fix For: 1.0.0, 0.7.1 > > > During the migration of hive service def When servicedef is accessed, one of > the properties "enableDenyPolicies" is returned as "false" if there is no > value set for it. > Now, hive service def has changed (because URL as a resource is added to it). > So when servicedef is updated, enableDenyPolicies property is updated in the > database to be "false" which should not happen. > The migration script for service-def needs to check what the real value of > this property is in the database and preserve it across migration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1612) When servicedef is accessed, one of the properties "enableDenyPolicies" is returned as "false" if there is no value set for it.
[ https://issues.apache.org/jira/browse/RANGER-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1612: Attachment: RANGER-1612-1.patch > When servicedef is accessed, one of the properties "enableDenyPolicies" is > returned as "false" if there is no value set for it. > --- > > Key: RANGER-1612 > URL: https://issues.apache.org/jira/browse/RANGER-1612 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Anuja Leekha >Assignee: Pradeep Agrawal > Labels: ranger > Fix For: 1.0.0, 0.7.1 > > Attachments: RANGER-1612-1.patch > > > During the migration of hive service def When servicedef is accessed, one of > the properties "enableDenyPolicies" is returned as "false" if there is no > value set for it. > Now, hive service def has changed (because URL as a resource is added to it). > So when servicedef is updated, enableDenyPolicies property is updated in the > database to be "false" which should not happen. > The migration script for service-def needs to check what the real value of > this property is in the database and preserve it across migration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1612) When servicedef is accessed, one of the properties "enableDenyAndExceptionsInPolicies" is returned as "false" if there is no value set for it.
[ https://issues.apache.org/jira/browse/RANGER-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1612: Summary: When servicedef is accessed, one of the properties "enableDenyAndExceptionsInPolicies" is returned as "false" if there is no value set for it. (was: When servicedef is accessed, one of the properties "enableDenyPolicies" is returned as "false" if there is no value set for it.) > When servicedef is accessed, one of the properties > "enableDenyAndExceptionsInPolicies" is returned as "false" if there is no > value set for it. > -- > > Key: RANGER-1612 > URL: https://issues.apache.org/jira/browse/RANGER-1612 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Anuja Leekha >Assignee: Pradeep Agrawal > Labels: ranger > Fix For: 1.0.0, 0.7.1 > > Attachments: RANGER-1612-1.patch > > > During the migration of hive service def When servicedef is accessed, one of > the properties "enableDenyPolicies" is returned as "false" if there is no > value set for it. > Now, hive service def has changed (because URL as a resource is added to it). > So when servicedef is updated, enableDenyPolicies property is updated in the > database to be "false" which should not happen. > The migration script for service-def needs to check what the real value of > this property is in the database and preserve it across migration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1612) When servicedef is accessed, one of the properties "enableDenyAndExceptionsInPolicies" is returned as "false" if there is no value set for it.
[ https://issues.apache.org/jira/browse/RANGER-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1612: Description: During the migration of hive service def When servicedef is accessed, one of the properties "enableDenyAndExceptionsInPolicies" is returned as "false" if there is no value set for it. Now, hive service def has changed (because URL as a resource is added to it). So when servicedef is updated, enableDenyPolicies property is updated in the database to be "false" which should not happen. The migration script for service-def needs to check what the real value of this property is in the database and preserve it across migration. was: During the migration of hive service def When servicedef is accessed, one of the properties "enableDenyPolicies" is returned as "false" if there is no value set for it. Now, hive service def has changed (because URL as a resource is added to it). So when servicedef is updated, enableDenyPolicies property is updated in the database to be "false" which should not happen. The migration script for service-def needs to check what the real value of this property is in the database and preserve it across migration. > When servicedef is accessed, one of the properties > "enableDenyAndExceptionsInPolicies" is returned as "false" if there is no > value set for it. > -- > > Key: RANGER-1612 > URL: https://issues.apache.org/jira/browse/RANGER-1612 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Anuja Leekha >Assignee: Pradeep Agrawal > Labels: ranger > Fix For: 1.0.0, 0.7.1 > > Attachments: RANGER-1612-1.patch > > > During the migration of hive service def When servicedef is accessed, one of > the properties "enableDenyAndExceptionsInPolicies" is returned as "false" if > there is no value set for it. > Now, hive service def has changed (because URL as a resource is added to it). > So when servicedef is updated, enableDenyPolicies property is updated in the > database to be "false" which should not happen. > The migration script for service-def needs to check what the real value of > this property is in the database and preserve it across migration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1612) When servicedef is accessed, one of the properties "enableDenyAndExceptionsInPolicies" is returned as "false" if there is no value set for it.
[ https://issues.apache.org/jira/browse/RANGER-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16026226#comment-16026226 ] Pradeep Agrawal commented on RANGER-1612: - committed to Apache Ranger master branch : https://github.com/apache/ranger/commit/0f0bfc6dcece0c19d353cc54c5d08416afa38493 committed to Apache Ranger 0.7 branch : https://github.com/apache/ranger/commit/cf01599b8724e080bcb760ef207fcf9fe9943396 > When servicedef is accessed, one of the properties > "enableDenyAndExceptionsInPolicies" is returned as "false" if there is no > value set for it. > -- > > Key: RANGER-1612 > URL: https://issues.apache.org/jira/browse/RANGER-1612 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Anuja Leekha >Assignee: Pradeep Agrawal > Labels: ranger > Fix For: 1.0.0, 0.7.1 > > Attachments: RANGER-1612-1.patch > > > During the migration of hive service def When servicedef is accessed, one of > the properties "enableDenyAndExceptionsInPolicies" is returned as "false" if > there is no value set for it. > Now, hive service def has changed (because URL as a resource is added to it). > So when servicedef is updated, enableDenyPolicies property is updated in the > database to be "false" which should not happen. > The migration script for service-def needs to check what the real value of > this property is in the database and preserve it across migration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (RANGER-1638) Improve the password validation from Ranger API
[ https://issues.apache.org/jira/browse/RANGER-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reopened RANGER-1638: - Reopening this as new external user creation is failing when the attempt is made through /users/userinfo REST. > Improve the password validation from Ranger API > --- > > Key: RANGER-1638 > URL: https://issues.apache.org/jira/browse/RANGER-1638 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.7.0 >Reporter: Mehul Parikh >Assignee: Gautam Borad > Fix For: 1.0.0, 0.7.2 > > Attachments: RANGER-1638.1.patch, RANGER-1638.patch > > > Ranger API should apply password validation in sync with what UI is applying > for all users. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (RANGER-1727) Ranger allows user to change an external user's password with 'null' old password
Pradeep Agrawal created RANGER-1727: --- Summary: Ranger allows user to change an external user's password with 'null' old password Key: RANGER-1727 URL: https://issues.apache.org/jira/browse/RANGER-1727 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Pradeep Agrawal Assignee: Pradeep Agrawal Fix For: 1.0.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (RANGER-1774) When the security admin and mysql service is not the same computer, the security admin was installed failed.
[
https://issues.apache.org/jira/browse/RANGER-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16164107#comment-16164107
]
Pradeep Agrawal commented on RANGER-1774:
-
[~peng.jianhua] : Can you attach the output of below SQL statement:
{code:java}
select user,host from mysql.user;
{code}
Also please provide the output of /etc/hosts file from both the machines.
> When the security admin and mysql service is not the same computer, the
> security admin was installed failed.
>
>
> Key: RANGER-1774
> URL: https://issues.apache.org/jira/browse/RANGER-1774
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Affects Versions: 1.0.0, master
>Reporter: peng.jianhua
>Assignee: peng.jianhua
> Labels: patch
> Attachments: mysql-version.png
>
>
> The security admin installed fail based on mysql 5.5.35-log version(refer to
> mysql-version.png). The error log is as following:
> {code}
> 2017-09-12 13:21:05,525 [JISQL] /usr/java/jdk/bin/java -cp
> /usr/share/java/mysql-connector-java.jar:/opt/ZDH/parcels/lib/ranger/ranger-admin/jisql/lib/*
> org.apache.util.sql.Jisql -driver mysqlconj -cstring
> jdbc:mysql://10.43.183.132/ranger -u 'rangeradmin' -p '' -noheader
> -trim -c \; -query "SELECT version();"
> SQLException : SQL state: 28000 java.sql.SQLException: Access denied for user
> 'rangeradmin'@'dap134-183' (using password: YES) ErrorCode: 1045
> {code}
> We should explicitly assign the ranger machine to access mysql using 'grant
> all privileges' command. That is the following code segment should be add the
> IP of the computer running security admin installer.
> {code:title=ranger/security-admin/scripts/dba_script.py|borderStyle=solid}
> hosts_arr =["%", "localhost"]
> if not self.host == "localhost": hosts_arr.append(self.host)
> for host in hosts_arr:
> ..
> query = get_cmd + " -query \"grant all privileges on %s.* to '%s'@'%s' with
> grant option;\"" %(db_name,db_user, host)
> ..
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (RANGER-1765) Add unique key constraint in x_group and x_group_users table
[ https://issues.apache.org/jira/browse/RANGER-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16164713#comment-16164713 ] Pradeep Agrawal commented on RANGER-1765: - Patch committed to Apache master branch : https://github.com/apache/ranger/commit/b83b168791ad7adb8d46032d0c111ee86c004fb8 Patch committed to Apache 0.7 branch : https://github.com/apache/ranger/commit/309abeff4118fc373d842297612bad18ebece2a1 > Add unique key constraint in x_group and x_group_users table > > > Key: RANGER-1765 > URL: https://issues.apache.org/jira/browse/RANGER-1765 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: bhavik patel >Assignee: bhavik patel >Priority: Critical > Fix For: 1.0.0, 0.7.2 > > Attachments: RANGER-1765-master.patch, RANGER-1765-ranger07.patch > > > Currently, concurrent request to create a group or create group-users mapping > is causing duplicate entries of the same group in x_group table. This need to > be restricted in DB tables by creating relevant constraint on the table. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (RANGER-1774) When the security admin and mysql service is not the same computer, the security admin was installed failed.
[
https://issues.apache.org/jira/browse/RANGER-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16165763#comment-16165763
]
Pradeep Agrawal commented on RANGER-1774:
-
Ranger is supported on MySQL 5.6 version onwards, though it can be installed on
5.1 and 5.5. Check the prerequisite section
[here|https://cwiki.apache.org/confluence/display/RANGER/Ranger+Installation+Guide].
If the issue is specific to your environment then you can use manual
workaround; if you are facing the same issue with any sub version of MySQL 5.6
then let me know.
> When the security admin and mysql service is not the same computer, the
> security admin was installed failed.
>
>
> Key: RANGER-1774
> URL: https://issues.apache.org/jira/browse/RANGER-1774
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Affects Versions: 1.0.0, master
>Reporter: peng.jianhua
>Assignee: peng.jianhua
> Labels: patch
> Attachments: grant-privileges.png, mysql-version.png
>
>
> The security admin installed fail based on mysql 5.5.35-log version(refer to
> mysql-version.png). The error log is as following:
> {code}
> 2017-09-12 13:21:05,525 [JISQL] /usr/java/jdk/bin/java -cp
> /usr/share/java/mysql-connector-java.jar:/opt/ZDH/parcels/lib/ranger/ranger-admin/jisql/lib/*
> org.apache.util.sql.Jisql -driver mysqlconj -cstring
> jdbc:mysql://10.43.183.132/ranger -u 'rangeradmin' -p '' -noheader
> -trim -c \; -query "SELECT version();"
> SQLException : SQL state: 28000 java.sql.SQLException: Access denied for user
> 'rangeradmin'@'dap134-183' (using password: YES) ErrorCode: 1045
> {code}
> We should explicitly assign the ranger machine to access mysql using 'grant
> all privileges' command. That is the following code segment should be add the
> IP of the computer running security admin installer.
> {code:title=ranger/security-admin/scripts/dba_script.py|borderStyle=solid}
> hosts_arr =["%", "localhost"]
> if not self.host == "localhost": hosts_arr.append(self.host)
> for host in hosts_arr:
> ..
> query = get_cmd + " -query \"grant all privileges on %s.* to '%s'@'%s' with
> grant option;\"" %(db_name,db_user, host)
> ..
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (RANGER-1774) When the security admin and mysql service is not the same computer, the security admin was installed failed.
[
https://issues.apache.org/jira/browse/RANGER-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16165993#comment-16165993
]
Pradeep Agrawal commented on RANGER-1774:
-
[~peng.jianhua] I will try in 5.5.35 version and shall share my observations.
> When the security admin and mysql service is not the same computer, the
> security admin was installed failed.
>
>
> Key: RANGER-1774
> URL: https://issues.apache.org/jira/browse/RANGER-1774
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Affects Versions: 1.0.0, master
>Reporter: peng.jianhua
>Assignee: peng.jianhua
> Labels: patch
> Attachments: grant-privileges.png, mysql-version.png
>
>
> The security admin installed fail based on mysql 5.5.35-log version(refer to
> mysql-version.png). The error log is as following:
> {code}
> 2017-09-12 13:21:05,525 [JISQL] /usr/java/jdk/bin/java -cp
> /usr/share/java/mysql-connector-java.jar:/opt/ZDH/parcels/lib/ranger/ranger-admin/jisql/lib/*
> org.apache.util.sql.Jisql -driver mysqlconj -cstring
> jdbc:mysql://10.43.183.132/ranger -u 'rangeradmin' -p '' -noheader
> -trim -c \; -query "SELECT version();"
> SQLException : SQL state: 28000 java.sql.SQLException: Access denied for user
> 'rangeradmin'@'dap134-183' (using password: YES) ErrorCode: 1045
> {code}
> We should explicitly assign the ranger machine to access mysql using 'grant
> all privileges' command. That is the following code segment should be add the
> IP of the computer running security admin installer.
> {code:title=ranger/security-admin/scripts/dba_script.py|borderStyle=solid}
> hosts_arr =["%", "localhost"]
> if not self.host == "localhost": hosts_arr.append(self.host)
> for host in hosts_arr:
> ..
> query = get_cmd + " -query \"grant all privileges on %s.* to '%s'@'%s' with
> grant option;\"" %(db_name,db_user, host)
> ..
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (RANGER-1774) When the security admin and mysql service is not the same computer, the security admin was installed failed.
[
https://issues.apache.org/jira/browse/RANGER-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16166068#comment-16166068
]
Pradeep Agrawal commented on RANGER-1774:
-
I installed MySQL 5.5.35 on centos :
{code:java}
mysql> select version();
+---+
| version() |
+---+
| 5.5.35|
+---+
1 row in set (0.00 sec)
{code}
After Install entries in mysql.user table was like this :
{code:java}
mysql> select user,host from mysql.user;
+--+--+
| user | host |
+--+--+
| root | 127.0.0.1|
| root | ::1 |
| root | localhost|
| root | pk-ear6694-1 |
+--+--+
{code}
After that, I created root user with '%' host and granted privileges.
{code:java}
mysql>create user 'root'@'%' identified by 'root';
mysql>GRANT ALL PRIVILEGES ON *.* TO 'root'@'%' IDENTIFIED BY 'root' WITH GRANT
OPTION;
mysql> select user,host from mysql.user;
+--+--+
| user | host |
+--+--+
| root | %|
| root | 127.0.0.1|
| root | ::1 |
| root | localhost|
| root | pk-ear6694-1 |
+--+--+
{code}
Added Ranger Host and MYSQL host entry in /etc/hosts file of both the node. For
example in my case both the node have below given entries in /etc/hosts file.
{code:java}
172.22.112.148 pagrawal-mysql-ssl-1.openstacklocal pagrawal-mysql-ssl-1
pagrawal-mysql-ssl-1.openstacklocal.
172.22.93.14pk-ear6694-1.openstacklocal pk-ear6694-1
pk-ear6694-1.openstacklocal.
{code}
On node *pagrawal-mysql-ssl-1* executed setup.sh script with below config :
{code:java}
db_root_user=root
db_root_password=root
db_host=pk-ear6694-1.openstacklocal
db_name=ranger091401
db_user=ranger091401
db_password=ranger091401
{code}
Ranger installation completed successfully and entries in mysql.user are like
this :
{code:java}
mysql> select user,host from mysql.user;
+--+-+
| user | host|
+--+-+
| ranger091401 | % |
| root | % |
| root | 127.0.0.1 |
| root | ::1 |
| ranger091401 | localhost |
| root | localhost |
| root | pk-ear6694-1|
| ranger091401 | pk-ear6694-1.openstacklocal |
+--+-+
{code}
After above tried to run script with short host name; please refer below config
for ranger installation
{code:java}
db_root_user=root
db_root_password=root
db_host=pk-ear6694-1
db_name=ranger091403
db_user=ranger091403
db_password=ranger091403
{code}
Ranger installation completed successfully and entries in mysql.user are like
this :
{code:java}
mysql> select user,host from mysql.user order by user;
+--+-+
| user | host|
+--+-+
| ranger091401 | % |
| ranger091401 | pk-ear6694-1.openstacklocal |
| ranger091401 | localhost |
| ranger091403 | localhost |
| ranger091403 | pk-ear6694-1|
| ranger091403 | % |
| root | % |
| root | ::1 |
| root | 127.0.0.1 |
| root | pk-ear6694-1|
| root | localhost |
+--+-+
{code}
==> So its not reproducing at my end.
> When the security admin and mysql service is not the same computer, the
> security admin was installed failed.
>
>
> Key: RANGER-1774
> URL: https://issues.apache.org/jira/browse/RANGER-1774
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Affects Versions: 1.0.0, master
>Reporter: peng.jianhua
>Assignee: peng.jianhua
> Labels: patch
> Attachments: grant-privileges.png, mysql-version.png
>
>
> The security admin installed fail based on mysql 5.5.35-log version(refer to
> mysql-version.png). The error log is as following:
> {code}
> 2017-09-12 13:21:05,525 [JISQL] /usr/java/jdk/bin/java -cp
> /usr/share/java/mysql-connector-java.jar:/opt/ZDH/parcels/lib/ranger/ranger-admin/jisql/lib/*
> org.apache.util.sql.Jisql -driver mysqlconj -cstring
> jdbc:mysql://10.43.183.132/ranger -u 'rangeradmin' -p '' -noheader
> -trim -c \; -query "SELECT version();"
> SQLException : SQL state: 28000 java.sql.SQLException: Access denied for user
> 'rangeradmin'@'dap134-183' (using password: YES) ErrorCode: 1045
> {code}
> We s
[jira] [Commented] (RANGER-1651) Improve Ranger and Ranger KMS REST Api documentation
[ https://issues.apache.org/jira/browse/RANGER-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167785#comment-16167785 ] Pradeep Agrawal commented on RANGER-1651: - +1 for patch [^RANGER-1651.2.patch] > Improve Ranger and Ranger KMS REST Api documentation > > > Key: RANGER-1651 > URL: https://issues.apache.org/jira/browse/RANGER-1651 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.7.1 >Reporter: Mehul Parikh >Assignee: Mehul Parikh > Fix For: 1.0.0, 0.7.2 > > Attachments: RANGER-1651.2.patch, RANGER-1651.patch, > RANGER-1651-ranger-0.7.patch > > > Improve the existing Ranger and Ranger KMS API documentation that is > published on the Apache Ranger website (http://ranger.apache.org/) > This can be automated using some tool like Enunciate. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (RANGER-1748) User is unable to update existing policy while importing policy from file
[ https://issues.apache.org/jira/browse/RANGER-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16181962#comment-16181962 ] Pradeep Agrawal commented on RANGER-1748: - Committed to master branch: https://github.com/apache/ranger/commit/a95606928d372f5214b0b55500408ad66a831bc0 Committed to ranger-0.7 branch: https://github.com/apache/ranger/commit/90ed7025d9abfdd98b72349bf54b19957065a5e2 > User is unable to update existing policy while importing policy from file > - > > Key: RANGER-1748 > URL: https://issues.apache.org/jira/browse/RANGER-1748 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: bhavik patel >Assignee: bhavik patel > Fix For: 0.7.2 > > Attachments: RANGER-1748-master-01.patch, RANGER-1748-master.patch, > RANGER-1748-ranger07-1.patch, RANGER-1748-ranger07.patch > > > Currently if user importing policy from file and if policy already exist then > it is't not allowing to update that policy. > Adding a flag(updateIfExists) in API to update existing policy during import > operation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
