[jira] [Updated] (HIVE-10635) Redo HIVE-7018 in a schematool compatible manner

2015-05-06 Thread Hari Sankar Sivarama Subramaniyan (JIRA)

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

Hari Sankar Sivarama Subramaniyan updated HIVE-10635:
-
Description: In HIVE-10614, we had to revert HIVE-7018 because it was not 
schematool compatible and it would prevent upgrade from 0.14.0 to 1.3.0 when 
run via schematool. We need to redo HIVE-7018 work once the script introduced 
for HIVE-7018 is schematool compliant.  (was: In HIVE-10614, we had to revert 
HIVE-7018 because it was not schematool compatible and it would prevent upgrade 
from 0.14.0 to 1.3.0 when run via schematool.)

 Redo HIVE-7018 in a schematool compatible manner
 

 Key: HIVE-10635
 URL: https://issues.apache.org/jira/browse/HIVE-10635
 Project: Hive
  Issue Type: Bug
  Components: Metastore
Reporter: Hari Sankar Sivarama Subramaniyan

 In HIVE-10614, we had to revert HIVE-7018 because it was not schematool 
 compatible and it would prevent upgrade from 0.14.0 to 1.3.0 when run via 
 schematool. We need to redo HIVE-7018 work once the script introduced for 
 HIVE-7018 is schematool compliant.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HIVE-10635) Redo HIVE-7018 in a schematool compatible manner

2015-05-06 Thread Hari Sankar Sivarama Subramaniyan (JIRA)

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

Hari Sankar Sivarama Subramaniyan updated HIVE-10635:
-
Component/s: Metastore

 Redo HIVE-7018 in a schematool compatible manner
 

 Key: HIVE-10635
 URL: https://issues.apache.org/jira/browse/HIVE-10635
 Project: Hive
  Issue Type: Bug
  Components: Metastore
Reporter: Hari Sankar Sivarama Subramaniyan

 In HIVE-10614, we had to revert HIVE-7018 because it was not schematool 
 compatible and it would prevent upgrade from 0.14.0 to 1.3.0 when run via 
 schematool.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)