Review - Draft : Board Report for Ranger - period Ending 02/28/2017
FYI: draft board report for Apache Ranger – Feb 2017. == # Description: The Ranger project is a framework to enable, monitor and manage comprehensive data security across the Hadoop platform. # Issues: * There are no issues requiring board attention at this time. # Activity: * Ranger 0.7.0 release is done and Community is working on 1.0.0 release activities * Jira: 105 total, +72(added) -58(resolved) over last 28 days (Feb-2017) * Git (Source): 83 commits over last 28 days (Feb-2017) * SVN (Site & Docs): 2 commits over last 28 days (Feb-2017) # Health report: * Added five more committers and Expecting more adaption to Apache Ranger * Scoping for next release is in progress, which may include integration with other Apache projects ## PMC changes: - Currently 17 PMC members. - Last PMC members were added as part of Ranger Graduation on Jan 18, 2017. - No new PMC members added in the last 1 months # Committer base changes: * Currently 22 committers. * New commmitters: - Abhay Kulkarni was added as a committer on Mon Feb 13 2017 - Ankita Sinha was added as a committer on Thu Feb 09 2017 - Mehul Parikh was added as a committer on Sun Feb 26 2017 - Pradeep Agrawal was added as a committer on Thu Feb 09 2017 - Sailaja Polavarapu was added as a committer on Mon Feb 13 2017 # Releases: * 0.7.0 was released on Sun Feb 26 2017 # Mailing list activity: * dev@ranger.apache.org: - 856 emails sent to list (in the month of Feb 2017) * u...@ranger.apache.org: - 48 emails sent to list (in the month of Feb 2017) * comm...@ranger.apache.org: - 125 emails sent to list (in the month of Feb 2017) # JIRA activity: * 72 JIRA tickets created in the month of Feb 2017 * 58 JIRA tickets closed/resolved in the month of Feb 2017 == Thanks, Selva-
[jira] [Reopened] (RANGER-1378) There is Page not found (404) error when clicking Admin tab in Audit.
[ https://issues.apache.org/jira/browse/RANGER-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reopened RANGER-1378: - > There is Page not found (404) error when clicking Admin tab in Audit. > - > > Key: RANGER-1378 > URL: https://issues.apache.org/jira/browse/RANGER-1378 > Project: Ranger > Issue Type: Bug > Components: admin >Reporter: Qiang Zhang >Assignee: Pradeep Agrawal > Labels: patch > Attachments: > 0001-RANGER-1378-There-is-Page-not-found-404-error-when-c.patch, > Audit-Admin-error.png > > > There is Page not found (404) error when clicking Admin tab in Audit. > Wrong reason: There is no vx_trx_log table in ranger database. > Exception [EclipseLink-4002] (Eclipse Persistence Services - > 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException > Internal Exception: > com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Expression #1 of > SELECT list is not in GROUP BY clause and contains nonaggregated column > 'ranger.x_trx_log.id' which is not functionally dependent on columns in GROUP > BY clause; this is incompatible with sql_mode=only_full_group_by > Error Code: 1055 > Call: SELECT ID AS a1, ACTION AS a2, ADDED_BY_ID AS a3, ATTR_NAME AS a4, > CREATE_TIME AS a5, NEW_VAL AS a6, CLASS_TYPE AS a7, OBJECT_ID AS a8, > OBJECT_NAME AS a9, PARENT_OBJECT_CLASS_TYPE AS a10, PARENT_OBJECT_ID AS a11, > PARENT_OBJECT_NAME AS a12, PREV_VAL AS a13, REQ_ID AS a14, SESS_ID AS a15, > SESS_TYPE AS a16, TRX_ID AS a17, UPDATE_TIME AS a18, UPD_BY_ID AS a19 FROM > vx_trx_log ORDER BY CREATE_TIME DESC LIMIT ?, ? > bind => [2 parameters bound] > Query: ReadAllQuery(referenceClass=VXXTrxLog sql="SELECT ID AS a1, ACTION AS > a2, ADDED_BY_ID AS a3, ATTR_NAME AS a4, CREATE_TIME AS a5, NEW_VAL AS a6, > CLASS_TYPE AS a7, OBJECT_ID AS a8, OBJECT_NAME AS a9, > PARENT_OBJECT_CLASS_TYPE AS a10, PARENT_OBJECT_ID AS a11, PARENT_OBJECT_NAME > AS a12, PREV_VAL AS a13, REQ_ID AS a14, SESS_ID AS a15, SESS_TYPE AS a16, > TRX_ID AS a17, UPDATE_TIME AS a18, UPD_BY_ID AS a19 FROM vx_trx_log ORDER BY > CREATE_TIME DESC LIMIT ?, ?") -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (RANGER-1378) There is Page not found (404) error when clicking Admin tab in Audit.
[ https://issues.apache.org/jira/browse/RANGER-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reassigned RANGER-1378: --- Assignee: Pradeep Agrawal (was: Qiang Zhang) > There is Page not found (404) error when clicking Admin tab in Audit. > - > > Key: RANGER-1378 > URL: https://issues.apache.org/jira/browse/RANGER-1378 > Project: Ranger > Issue Type: Bug > Components: admin >Reporter: Qiang Zhang >Assignee: Pradeep Agrawal > Labels: patch > Attachments: > 0001-RANGER-1378-There-is-Page-not-found-404-error-when-c.patch, > Audit-Admin-error.png > > > There is Page not found (404) error when clicking Admin tab in Audit. > Wrong reason: There is no vx_trx_log table in ranger database. > Exception [EclipseLink-4002] (Eclipse Persistence Services - > 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException > Internal Exception: > com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Expression #1 of > SELECT list is not in GROUP BY clause and contains nonaggregated column > 'ranger.x_trx_log.id' which is not functionally dependent on columns in GROUP > BY clause; this is incompatible with sql_mode=only_full_group_by > Error Code: 1055 > Call: SELECT ID AS a1, ACTION AS a2, ADDED_BY_ID AS a3, ATTR_NAME AS a4, > CREATE_TIME AS a5, NEW_VAL AS a6, CLASS_TYPE AS a7, OBJECT_ID AS a8, > OBJECT_NAME AS a9, PARENT_OBJECT_CLASS_TYPE AS a10, PARENT_OBJECT_ID AS a11, > PARENT_OBJECT_NAME AS a12, PREV_VAL AS a13, REQ_ID AS a14, SESS_ID AS a15, > SESS_TYPE AS a16, TRX_ID AS a17, UPDATE_TIME AS a18, UPD_BY_ID AS a19 FROM > vx_trx_log ORDER BY CREATE_TIME DESC LIMIT ?, ? > bind => [2 parameters bound] > Query: ReadAllQuery(referenceClass=VXXTrxLog sql="SELECT ID AS a1, ACTION AS > a2, ADDED_BY_ID AS a3, ATTR_NAME AS a4, CREATE_TIME AS a5, NEW_VAL AS a6, > CLASS_TYPE AS a7, OBJECT_ID AS a8, OBJECT_NAME AS a9, > PARENT_OBJECT_CLASS_TYPE AS a10, PARENT_OBJECT_ID AS a11, PARENT_OBJECT_NAME > AS a12, PREV_VAL AS a13, REQ_ID AS a14, SESS_ID AS a15, SESS_TYPE AS a16, > TRX_ID AS a17, UPDATE_TIME AS a18, UPD_BY_ID AS a19 FROM vx_trx_log ORDER BY > CREATE_TIME DESC LIMIT ?, ?") -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1294) Ranger Kms support default key ACLs and whitelist key ACLs
[ https://issues.apache.org/jira/browse/RANGER-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15896725#comment-15896725 ] Qiang Zhang commented on RANGER-1294: - Currently,the Hadoop Kms has supported default key ACLs and whitelist key ACLs. Ranger don't support related functions. Corresponding to the blacklist function, these functions can be more accurate, more direct, and more detailed control of data security. So Ranger should support these functions. The reference link: https://issues.apache.org/jira/browse/HADOOP-11341 > Ranger Kms support default key ACLs and whitelist key ACLs > -- > > Key: RANGER-1294 > URL: https://issues.apache.org/jira/browse/RANGER-1294 > Project: Ranger > Issue Type: New Feature >Reporter: Qiang Zhang >Assignee: Qiang Zhang > Labels: patch > > Currently,the Hadoop Kms has supported default key ACLs and whitelist key > ACLs.So the Ranger Kms should also support similar function. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Re: Review Request 56487: Ranger Kms support default key ACLs and whitelist key ACLs
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/56487/ --- (Updated 三月 6, 2017, 4:03 a.m.) Review request for ranger, Don Bosco Durai, Colm O hEigeartaigh, Ramesh Mani, Selvamohan Neethiraj, and Velmurugan Periasamy. Bugs: RANGER-1294 https://issues.apache.org/jira/browse/RANGER-1294 Repository: ranger Description (updated) --- Currently,the Hadoop Kms has supported default key ACLs and whitelist key ACLs. Ranger don't support related functions. Corresponding to the blacklist function, these functions can be more accurate, more direct, and more detailed control of data security. So Ranger should support these functions. The reference link: https://issues.apache.org/jira/browse/HADOOP-11341 Diffs - kms/config/kms-webapp/dbks-site.xml a098db1 kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/KMSConfiguration.java 4bf2886 plugin-kms/src/main/java/org/apache/ranger/authorization/kms/authorizer/RangerKmsAuthorizer.java 9bebafa Diff: https://reviews.apache.org/r/56487/diff/1/ Testing --- steps: 1.add policy to give permission for user xiehh in ranger-admin WebUI 2.create zone [xiehh@zdh41 ~]$ hdfs dfs -mkdir /keyZone [xiehh@zdh41 ~]$ hdfs crypto -createZone -keyName key0 -path /keyZone [xiehh@zdh41 ~]$ hdfs dfs -put a.txt /keyZone test: 1.configure as following in dbks-site.xml default.key.acl.DECRYPT_EEK * whitelist.key.acl.DECRYPT_EEK * -->test with user xiehh [xiehh@zdh41 ~]$ hdfs dfs -cat /keyZone/a.txt dasdads asdasd 2.configure as follows in dbks-site.xml default.key.acl.DECRYPT_EEK mysql whitelist.key.acl.DECRYPT_EEK mysql -->test with user xiehh [xiehh@zdh41 ~]$ hdfs dfs -cat /keyZone/a.txt cat: User [xiehh] is not authorized to perform [DECRYPT_EEK] on key with ACL name [key0]!! 3. configure as follows in dbks-site.xml default.key.acl.DECRYPT_EEK * whitelist.key.acl.DECRYPT_EEK mysql --> test with user xiehh [xiehh@zdh41 ~]$ hdfs dfs -cat /keyZone/a.txt dasdads asdasd 4.configure as follows in dbks-site.xml default.key.acl.DECRYPT_EEK mysql whitelist.key.acl.DECRYPT_EEK * -->test with user xiehh [xiehh@zdh41 ~]$ hdfs dfs -cat /keyZone/a.txt dasdads asdasd ... Thanks, Qiang Zhang
[jira] [Updated] (RANGER-1294) Ranger Kms support default key ACLs and whitelist key ACLs
[ https://issues.apache.org/jira/browse/RANGER-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-1294: Description: Currently,the Hadoop Kms has supported default key ACLs and whitelist key ACLs. Ranger doesn't support related functions. Corresponding to the blacklist function, these functions can be more accurate, more direct, and more detailed control of data security. So Ranger should support these functions. The reference link: https://issues.apache.org/jira/browse/HADOOP-11341 (was: Currently,the Hadoop Kms has supported default key ACLs and whitelist key ACLs.So the Ranger Kms should also support similar function.) > Ranger Kms support default key ACLs and whitelist key ACLs > -- > > Key: RANGER-1294 > URL: https://issues.apache.org/jira/browse/RANGER-1294 > Project: Ranger > Issue Type: New Feature >Reporter: Qiang Zhang >Assignee: Qiang Zhang > Labels: patch > > Currently,the Hadoop Kms has supported default key ACLs and whitelist key > ACLs. Ranger doesn't support related functions. Corresponding to the > blacklist function, these functions can be more accurate, more direct, and > more detailed control of data security. So Ranger should support these > functions. The reference link: > https://issues.apache.org/jira/browse/HADOOP-11341 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Re: Review Request 56487: Ranger Kms support default key ACLs and whitelist key ACLs
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/56487/ --- (Updated 三月 6, 2017, 4:41 a.m.) Review request for ranger, Don Bosco Durai, Colm O hEigeartaigh, Ramesh Mani, Selvamohan Neethiraj, and Velmurugan Periasamy. Bugs: RANGER-1294 https://issues.apache.org/jira/browse/RANGER-1294 Repository: ranger Description (updated) --- Currently,the Hadoop Kms has supported default key ACLs and whitelist key ACLs. Ranger doesn't support related functions. Corresponding to the blacklist function, these functions can be more accurate, more direct, and more detailed control of data security. So Ranger should support these functions. The reference link: https://issues.apache.org/jira/browse/HADOOP-11341 Diffs - kms/config/kms-webapp/dbks-site.xml a098db1 kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/KMSConfiguration.java 4bf2886 plugin-kms/src/main/java/org/apache/ranger/authorization/kms/authorizer/RangerKmsAuthorizer.java 9bebafa Diff: https://reviews.apache.org/r/56487/diff/1/ Testing --- steps: 1.add policy to give permission for user xiehh in ranger-admin WebUI 2.create zone [xiehh@zdh41 ~]$ hdfs dfs -mkdir /keyZone [xiehh@zdh41 ~]$ hdfs crypto -createZone -keyName key0 -path /keyZone [xiehh@zdh41 ~]$ hdfs dfs -put a.txt /keyZone test: 1.configure as following in dbks-site.xml default.key.acl.DECRYPT_EEK * whitelist.key.acl.DECRYPT_EEK * -->test with user xiehh [xiehh@zdh41 ~]$ hdfs dfs -cat /keyZone/a.txt dasdads asdasd 2.configure as follows in dbks-site.xml default.key.acl.DECRYPT_EEK mysql whitelist.key.acl.DECRYPT_EEK mysql -->test with user xiehh [xiehh@zdh41 ~]$ hdfs dfs -cat /keyZone/a.txt cat: User [xiehh] is not authorized to perform [DECRYPT_EEK] on key with ACL name [key0]!! 3. configure as follows in dbks-site.xml default.key.acl.DECRYPT_EEK * whitelist.key.acl.DECRYPT_EEK mysql --> test with user xiehh [xiehh@zdh41 ~]$ hdfs dfs -cat /keyZone/a.txt dasdads asdasd 4.configure as follows in dbks-site.xml default.key.acl.DECRYPT_EEK mysql whitelist.key.acl.DECRYPT_EEK * -->test with user xiehh [xiehh@zdh41 ~]$ hdfs dfs -cat /keyZone/a.txt dasdads asdasd ... Thanks, Qiang Zhang
Review Request 57276: RANGER-1417 : Ranger Upgrade is failing for Oracle DB flavor
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/57276/ --- Review request for ranger, Ankita Sinha, Don Bosco Durai, Gautam Borad, Abhay Kulkarni, Madhan Neethiraj, Mehul Parikh, Ramesh Mani, Selvamohan Neethiraj, Sailaja Polavarapu, and Velmurugan Periasamy. Bugs: RANGER-1417 https://issues.apache.org/jira/browse/RANGER-1417 Repository: ranger Description --- **Problem Statement:** Ranger Upgrade(0.6 to 0.7) is failing for Oracle DB flavor as the java patches are not marked applied in x_db_version_h table by db_setup.py script in 0.6 version. **Proposed Solution :** db_setup.py can identify java patches that are marked as 'N' but NOT installed by current version of Ranger Admin; and marked such entries status to 'Y'. Diffs - security-admin/scripts/db_setup.py 4112e05 Diff: https://reviews.apache.org/r/57276/diff/1/ Testing --- **Use Case: Ranger upgrade case(0.6 to 0.7)** Steps performed(with patch) : 1. Installed and started 0.6 version of Ranger admin for Oracle DB flavor. 2. From installation log messages it was observed that java patches have been executed. 3. Logged into ranger Oracle DB and executed below command to check whether executed java patches entries status has been marked 'Y' or not. SELECT * FROM X_DB_VERSION_H WHERE VERSION LIKE 'J%'; >From output of above sql statement it was observed that though patches have >been applied their active status is not set to ='Y'. 4. Stop Ranger admin. 5. Took Ranger latest code from master; applied patch and created build. Unzipped the generated tar file and in install.properties provided Ranger db configuration which were used in 0.6 version of Ranger installation. 6. Logged into ranger Oracle DB and executed below command to check whether executed java patches entries status has been marked 'Y' or not. SELECT * FROM X_DB_VERSION_H WHERE VERSION LIKE 'J%'; **Expected Behaviour:** output of above sql statement should state that all java patches have been applied, this can be determine by referring active column of output where active column value must be 'Y'. **Actual Behaviour:** >From output of above sql statement it was observed that active column value >was set to 'Y' and additional java patches have also been applied successfully. Thanks, Pradeep Agrawal
[jira] [Created] (RANGER-1423) CLONE - Ranger Upgrade is failing for Oracle DB flavor
Pradeep Agrawal created RANGER-1423: --- Summary: CLONE - Ranger Upgrade is failing for Oracle DB flavor Key: RANGER-1423 URL: https://issues.apache.org/jira/browse/RANGER-1423 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 0.7.0 Reporter: Pradeep Agrawal Assignee: Pradeep Agrawal Fix For: 0.7.1 *Problem Statement :* Ranger Upgrade(0.6 to 0.7) is failing for Oracle DB flavor as the java patches are not marked applied in x_db_version_h table by db_setup.py script in 0.6 version. *Proposed Solution for 0.6 :* db_setup.py script need to be fix so that patches are marked applied after execution of each java patch. *Proposed Solution for 0.7 or later :* From db_setup.py Identify java patches that are marked as 'N' but NOT installed by current Ranger version; marked such entries to 'Y'. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1423) CLONE - Ranger Upgrade is failing for Oracle DB flavor
[ https://issues.apache.org/jira/browse/RANGER-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1423: Description: *Problem Statement :* Ranger Upgrade(0.6 to 0.7) is failing for Oracle DB flavor as the java patches are not marked applied in x_db_version_h table by db_setup.py script in 0.6 version. *Proposed Solution for 0.6 :* db_setup.py script need to be fix so that patches are marked applied after execution of each java patch. was: *Problem Statement :* Ranger Upgrade(0.6 to 0.7) is failing for Oracle DB flavor as the java patches are not marked applied in x_db_version_h table by db_setup.py script in 0.6 version. *Proposed Solution for 0.6 :* db_setup.py script need to be fix so that patches are marked applied after execution of each java patch. *Proposed Solution for 0.7 or later :* From db_setup.py Identify java patches that are marked as 'N' but NOT installed by current Ranger version; marked such entries to 'Y'. > CLONE - Ranger Upgrade is failing for Oracle DB flavor > -- > > Key: RANGER-1423 > URL: https://issues.apache.org/jira/browse/RANGER-1423 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.6.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 0.6.4 > > > *Problem Statement :* Ranger Upgrade(0.6 to 0.7) is failing for Oracle DB > flavor as the java patches are not marked applied in x_db_version_h table by > db_setup.py script in 0.6 version. > *Proposed Solution for 0.6 :* db_setup.py script need to be fix so that > patches are marked applied after execution of each java patch. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1423) CLONE - Ranger Upgrade is failing for Oracle DB flavor
[ https://issues.apache.org/jira/browse/RANGER-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1423: Fix Version/s: (was: 0.7.1) 0.6.4 > CLONE - Ranger Upgrade is failing for Oracle DB flavor > -- > > Key: RANGER-1423 > URL: https://issues.apache.org/jira/browse/RANGER-1423 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.6.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 0.6.4 > > > *Problem Statement :* Ranger Upgrade(0.6 to 0.7) is failing for Oracle DB > flavor as the java patches are not marked applied in x_db_version_h table by > db_setup.py script in 0.6 version. > *Proposed Solution for 0.6 :* db_setup.py script need to be fix so that > patches are marked applied after execution of each java patch. > *Proposed Solution for 0.7 or later :* From db_setup.py Identify java patches > that are marked as 'N' but NOT installed by current Ranger version; marked > such entries to 'Y'. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1423) CLONE - Ranger Upgrade is failing for Oracle DB flavor
[ https://issues.apache.org/jira/browse/RANGER-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1423: Affects Version/s: (was: 0.7.0) 0.6.0 > CLONE - Ranger Upgrade is failing for Oracle DB flavor > -- > > Key: RANGER-1423 > URL: https://issues.apache.org/jira/browse/RANGER-1423 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.6.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 0.6.4 > > > *Problem Statement :* Ranger Upgrade(0.6 to 0.7) is failing for Oracle DB > flavor as the java patches are not marked applied in x_db_version_h table by > db_setup.py script in 0.6 version. > *Proposed Solution for 0.6 :* db_setup.py script need to be fix so that > patches are marked applied after execution of each java patch. > *Proposed Solution for 0.7 or later :* From db_setup.py Identify java patches > that are marked as 'N' but NOT installed by current Ranger version; marked > such entries to 'Y'. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1423) CLONE - Ranger Upgrade is failing for Oracle DB flavor
[ https://issues.apache.org/jira/browse/RANGER-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-1423: Attachment: RANGER-1423-1.patch > CLONE - Ranger Upgrade is failing for Oracle DB flavor > -- > > Key: RANGER-1423 > URL: https://issues.apache.org/jira/browse/RANGER-1423 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.6.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 0.6.4 > > Attachments: RANGER-1423-1.patch > > > *Problem Statement :* Ranger Upgrade(0.6 to 0.7) is failing for Oracle DB > flavor as the java patches are not marked applied in x_db_version_h table by > db_setup.py script in 0.6 version. > *Proposed Solution for 0.6 :* db_setup.py script need to be fix so that > patches are marked applied after execution of each java patch. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
