[jira] [Updated] (RANGER-1817) Audit to Solr fails to log when the number of columns are in large number

["Fatima Amjad Khan (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/RANGER-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fatima Amjad Khan updated RANGER-1817:
--------------------------------------
    Attachment: 0001-RANGER-1817.patch

> Audit to Solr fails to log when the number of columns are in large number
> -------------------------------------------------------------------------
>
>                 Key: RANGER-1817
>                 URL: https://issues.apache.org/jira/browse/RANGER-1817
>             Project: Ranger
>          Issue Type: Bug
>          Components: Ranger
>    Affects Versions: master, 0.7.1
>            Reporter: Fatima Amjad Khan
>            Assignee: Fatima Amjad Khan
>             Fix For: master, 0.7.1
>
>         Attachments: 0001-RANGER-1817.patch
>
>
> Audit to Solr fails to log when the number of columns are in large number. This is due to Solr has a hard limit on solr.StrField and if this string is exceeding max length 32766, it throws exception which causes the audit to fail. To overcome this we need to trip this in Audit records and the best place to do it is in solr schema for ranger-audits.
> For this we need to change the file managed_schema in ranger and commit it to zookeeper.
> Change required in the managed_schema file is, find the following in the managed_schema file and add this param to limit the length to 2500 max. 
> {noformat}
> <filter class="solr.LengthFilterFactory" min="0" max="2500”/>
> {noformat}
> Final changes:
> {noformat}
> <fieldType name="key_lower_case" class="solr.TextField" sortMissingLast="true" omitNorms="true">
> <analyzer>
> <tokenizer class="solr.KeywordTokenizerFactory"/>
> <filter class="solr.LowerCaseFilterFactory"/>
> <filter class="solr.LengthFilterFactory" min="0" max="2500"/>
> </analyzer>
> </fieldType>
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)