[
https://issues.apache.org/jira/browse/RANGER-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15823659#comment-15823659
]
Pradeep Agrawal commented on RANGER-1308:
-----------------------------------------
1. 'DEFAULT CHARSET=latin1' clause need to be removed from 'create table
statements' in order to store unicode characters in ranger db.
2. 'ROW_FORMAT=DYNAMIC' clause need to be added in 'create table statements' in
order to store large index key prefixes (up to 3072 bytes)as UTF8 may take 3 to
4 byte per character. InnoDB ROW_FORMAT options include COMPACT, REDUNDANT,
DYNAMIC, and COMPRESSED. For InnoDB tables, rows are stored in COMPACT format
(ROW_FORMAT=COMPACT) by default.
When a table is created with ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED,
InnoDB can store long variable-length column values (for VARCHAR, VARBINARY,
and BLOB and TEXT types) fully off-page, with the clustered index record
containing only a 20-byte pointer to the overflow page. InnoDB also encodes
fixed-length fields greater than or equal to 768 bytes in length as
variable-length fields. For example, a CHAR(255) column can exceed 768 bytes if
the maximum byte length of the character set is greater than 3, as it is with
utf8mb4. Refer [Limits on InnoDB
Tables|https://dev.mysql.com/doc/refman/5.6/en/innodb-restrictions.html].
> Remove DEFAULT CHARSET 'latin1' from ranger db schema script to enable
> support of unicode or any other charset
> ---------------------------------------------------------------------------------------------------------------
>
> Key: RANGER-1308
> URL: https://issues.apache.org/jira/browse/RANGER-1308
> 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
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
