You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Ramesh Mani (Jira)" <ji...@apache.org> on 2022/04/16 06:25:00 UTC

[jira] [Updated] (RANGER-3638) Solr Ranger document level security breaks solr if collection is reloaded

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

Ramesh Mani updated RANGER-3638:
--------------------------------
    Fix Version/s: 2.3.0

> Solr Ranger document level security breaks solr if collection is reloaded
> -------------------------------------------------------------------------
>
>                 Key: RANGER-3638
>                 URL: https://issues.apache.org/jira/browse/RANGER-3638
>             Project: Ranger
>          Issue Type: Bug
>          Components: Ranger
>    Affects Versions: 2.2.0
>            Reporter: Sailaja Polavarapu
>            Assignee: Sailaja Polavarapu
>            Priority: Major
>             Fix For: 3.0.0, 2.3.0
>
>         Attachments: 0001-RANGER-3638-Avoid-calling-rangerSolrAuthorizerImpl-c.patch
>
>
> Solr stops working if using a collection with document level security enabled when:
> adding fields to collection schema
> making changes to collection config
> reloading collection
> This does not happens if the reload is done to the non document level security collection, with other collection with document level security.
> -solr can no longer send ranger audits to solr-infra showing 403 errror from solr-infra
> -solr can no longer save audits to hdfs showing issue with the hdfs sink.
> -solr answer 403 to any query to the collection with document level security and other collections, admin commands too
> -zookeeper znodes warnings are seen on the logs.
> After solr restart all collections with and without document level security are available again and answer queries.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)