ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Posledov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (RANGER-2114) Internal Exception: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for column 'content' at row 1
Date Fri, 01 Jun 2018 13:42:00 GMT

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

Alexander Posledov commented on RANGER-2114:
--------------------------------------------

[~pradeep.agrawal] : we use use long names for services, policies and service definitions,
thus JSON may be 70-80k.  But even standard ranger rows where obj_name="tag" could have content
values of 12000 characters or more, so I would propose to change this column's type to MEDIUMTEXT 

> Internal Exception: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long
for column 'content' at row 1
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: RANGER-2114
>                 URL: https://issues.apache.org/jira/browse/RANGER-2114
>             Project: Ranger
>          Issue Type: Bug
>          Components: Ranger
>            Reporter: Alexander Posledov
>            Priority: Major
>
> An attempt to delete a service definition ends with:
>  
> {code:java}
> // Internal Exception: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too
long for column 'content' at row 1
> Error Code: 1406
> Call: INSERT INTO x_data_hist (action, content, CREATE_TIME, from_time, obj_class_type,
obj_guid, obj_id, obj_name, to_time, UPDATE_TIME, version) VALUES (?, ?, ?, ?, ?, ?, ?, ?,
?, ?, ?)
> bind =&gt; [11 parameters bound]
> {code}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message