[
https://issues.apache.org/jira/browse/RANGER-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16722802#comment-16722802
]
Pradeep Agrawal commented on RANGER-2295:
-----------------------------------------
Committed to master branch :
https://github.com/apache/ranger/commit/f80ee0e76f492686a219d7712db2a3a6e34bc7ef
> Set specific Ranger version in patches status entry table
> ----------------------------------------------------------
>
> Key: RANGER-2295
> URL: https://issues.apache.org/jira/browse/RANGER-2295
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
> Affects Versions: 1.0.0, 1.1.0, 1.2.0
> Reporter: Pradeep Agrawal
> Assignee: Pradeep Agrawal
> Priority: Major
> Fix For: 1.0.1, 2.0.0, 1.1.1, 1.2.1
>
> Attachments:
> 0002-RANGER-2295-Set-specific-Ranger-version-in-patches-s.patch
>
>
> DB setup script looks for a specific version (Ranger 2.0.0-SNAPSHOT) to
> decide if patches need to be applied:
> {code:java}
> select version from x_db_version_h where version = 'DB_PATCHES' and inst_by =
> 'Ranger 2.0.0-SNAPSHOT' and active = 'Y';
> select version from x_db_version_h where version = 'JAVA_PATCHES' and inst_by
> = 'Ranger 2.0.0-SNAPSHOT' and active = 'Y';
> {code}
> However, the optimized schema creation script comes with a generic version
> (Ranger 1.0.0):
> {code:java}
> INSERT INTO x_db_version_h
> (version,inst_at,inst_by,updated_at,updated_by,active) VALUES
> ('DB_PATCHES',CURRENT_TIMESTAMP,'Ranger
> 1.0.0',CURRENT_TIMESTAMP,'localhost','Y');
> INSERT INTO x_db_version_h
> (version,inst_at,inst_by,updated_at,updated_by,active) VALUES
> ('JAVA_PATCHES',CURRENT_TIMESTAMP,'Ranger
> 1.0.0',CURRENT_TIMESTAMP,'localhost','Y');
> {code}
> The result is that a separate check is executed for each patch, which takes
> time. It will be good if the status entries have the exact ranger version
> rather a base version.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
