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

Posted to dev@ranger.apache.org by "Pradeep Agrawal (Jira)" <ji...@apache.org> on 2022/06/17 05:21:00 UTC

[jira] [Updated] (RANGER-3795) Fix java patch J10033 and J10046 failure

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

Pradeep Agrawal updated RANGER-3795:
------------------------------------
    Summary: Fix java patch J10033 and J10046 failure  (was: Fix PatchForMigratingOldRegimePolicyJson_J10046 failure)

> Fix java patch J10033 and J10046 failure
> ----------------------------------------
>
>                 Key: RANGER-3795
>                 URL: https://issues.apache.org/jira/browse/RANGER-3795
>             Project: Ranger
>          Issue Type: Bug
>          Components: Ranger
>    Affects Versions: 3.0.0
>            Reporter: Pradeep Agrawal
>            Assignee: Pradeep Agrawal
>            Priority: Major
>             Fix For: 3.0.0
>
>
> During kafka policy porting to new db schema via java patch PatchForMigratingOldRegimePolicyJson_J10046,  it finds a kafka default policy which has user kafka and rangerlookup in it. If these users does not exist in ranger then policy porting to new schema may fail. 
> Also The issue is observed only when older version of ranger installation does not have PatchForMigratingOldRegimePolicyJson_J10046 applied in it 



--
This message was sent by Atlassian Jira
(v8.20.7#820007)