You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ranger.apache.org by "Mahesh Hanumant Bandal (Jira)" <ji...@apache.org> on 2020/07/23 12:08:00 UTC

[jira] [Commented] (RANGER-2923) Changing data type of sync_source_info column to accommodate more characters

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

Mahesh Hanumant Bandal commented on RANGER-2923:
------------------------------------------------

Patch is available at the review board: [https://reviews.apache.org/r/72702/]

> Changing data type of sync_source_info column to accommodate more characters
> ----------------------------------------------------------------------------
>
>                 Key: RANGER-2923
>                 URL: https://issues.apache.org/jira/browse/RANGER-2923
>             Project: Ranger
>          Issue Type: Improvement
>          Components: Ranger
>    Affects Versions: 2.1.0
>            Reporter: Mahesh Hanumant Bandal
>            Assignee: Mahesh Hanumant Bandal
>            Priority: Major
>
> Insert values for the column "sync_source_info" under table "x_ugsync_audit_info" can go beyond the maximum length of column. (currently limit is VARCHAR 4000).
> Now changing data type to different db flavours as follows :
> mysql              : VARCHAR => MEDIUMTEXT
> oracle             : VARCHAR => CLOB
> postgres        : VARCHAR => TEXT
> sqlanywhere : VARCHAR => TEXT
> sqlserver        : VARCHAR => nvarchar(max)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)