ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pradeep Agrawal (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (RANGER-2109) Ranger mysql db does not allow creation of many service definitions
Date Mon, 04 Jun 2018 11:46:00 GMT

    [ https://issues.apache.org/jira/browse/RANGER-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16500112#comment-16500112

Pradeep Agrawal commented on RANGER-2109:

[~aposledov] : Ranger is having support of only 15 service defs (tag, hdfs, hbase, hive, kms, knox,
storm, yarn, kafka, solr, atlas, nifi, sqoop, kylin) of which json structure is already
defined and a unique id has been assigned to each service def in those json files. So
are you reusing the existing service def json files with different Id and name or are you
planning to add a new service def?

Can you please provide more details about your requirement, testing approach and impact area 
as per your product requirements.

> Ranger mysql db does not allow creation of many service definitions
> -------------------------------------------------------------------
>                 Key: RANGER-2109
>                 URL: https://issues.apache.org/jira/browse/RANGER-2109
>             Project: Ranger
>          Issue Type: Bug
>          Components: Ranger
>            Reporter: Alexander Posledov
>            Priority: Major
> We need to add many service definitions to Ranger. After some time, service definitions
cannot be added, and the following error is returned:
> {code:java}
> Reply from service: {"statusCode":1,"msgDesc":"Exception [EclipseLink-4002] (Eclipse
Persistence Services - 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException\nInternal
Exception: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Out of range value for column
'sort_order' at row 1\nError Code: 1264\nCall: INSERT INTO x_access_type_def (ADDED_BY_ID,
CREATE_TIME, datamask_options, def_id, item_id, label, name, sort_order, rb_key_label, rowfilter_options,
UPDATE_TIME, UPD_BY_ID) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)\n\tbind => [12 parameters
bound]\nQuery: InsertObjectQuery(XXAccessTypeDef [XXDBBase={createTime={Fri Apr 06 16:15:17
UTC 2018} updateTime={Fri May 18 17:58:12 UTC 2018} addedByUserId={1} updatedByUserId={1}
} id=null, defId=100, itemId=837838, name=c9999990-def-51c64923-3650-48b4-b4e9-abfd9fe0ed7a-1526666291595:read,
label=Read, rbKeyLabel=null, dataMaskOptions=null, rowFilterOptions=null, order=128])"}
> {code}
> changing sort_order column type to INT helps, but I think this should be done in the
initial Ranger setup.

This message was sent by Atlassian JIRA

View raw message