Kishor Gollapalliwar created RANGER-3385:
--------------------------------------------
Summary: Duplicate SQL prefix should not be allowed
Key: RANGER-3385
URL: https://issues.apache.org/jira/browse/RANGER-3385
Project: Ranger
Issue Type: Bug
Components: Ranger
Reporter: Kishor Gollapalliwar
Assignee: Kishor Gollapalliwar
Duplicate SQL prefix 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 DB changes.
# Assume user1 needs to update table1 and user2 needs to update table2.
# Both Checked latest DB patch prefix (say it is *056-*). And used prefix
*057-* for their SQL files
If case is not taken and both commits ends up merging. The setup script will
apply ONLY one of the both SQL files (prefixed *057-*) randomly.
Reproduce Steps:
# cd <ranger-repo>/security-admin/db/mysql/patches
# Update prefix of last 2 patches such that both contains same prefix
# mvn clean compile package install -U #build ranger
# setup ranger
To avoid this, we need to fail maven build itself if there are duplicate prefix.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
