You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Kishor Gollapalliwar (Jira)" <ji...@apache.org> on 2021/09/06 07:38:00 UTC

[jira] [Updated] (RANGER-3398) Duplicate JAVA patch suffix should not be allowed

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

Kishor Gollapalliwar updated RANGER-3398:
-----------------------------------------
    Fix Version/s:     (was: 2.2.0)
                       (was: 3.0.0)

> Duplicate JAVA patch suffix should not be allowed
> -------------------------------------------------
>
>                 Key: RANGER-3398
>                 URL: https://issues.apache.org/jira/browse/RANGER-3398
>             Project: Ranger
>          Issue Type: Bug
>          Components: Ranger
>            Reporter: Kishor Gollapalliwar
>            Assignee: Kishor Gollapalliwar
>            Priority: Major
>
> Duplicate JAVA suffix is allowed. Currently we need a manual human intervention to find and correct. Use case in details as follows.
> Use-Case:
>  # Say user1 & user2 working on a fix in Ranger and they both need JAVA patch changes.
>  # Assume user1 needs to update table1 and user2 needs to update table2 using java.
>  # Both Checked latest JAVA patch suffix (say it is *_J10050*). And used suffix *_J10051* for their JAVA files
> If both commits ends up merging. The setup script will apply ONLY one of the both JAVA files (suffixed *_J10051*) randomly.
> Reproduce Steps:
>  # cd <ranger-repo>/security-admin/src/main/java/org/apache/ranger/patch/
>  # Update suffix of last 2 patches such that both contains same suffix
>  # mvn clean compile package install -U #build ranger
>  # setup ranger
> To avoid this, we need to fail maven build itself if there are duplicate suffix.



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