[jira] Commented: (HIVE-1427) Provide metastore schema migration scripts (0.5 -> 0.6)

["John Sichi (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HIVE-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903547#action_12903547 ] 

John Sichi commented on HIVE-1427:
----------------------------------

Also need script corresponding to this change from HIVE-675.

-      <field name="description">  
-        <column name="DESC" length="767" jdbc-type="VARCHAR"/>  
-      </field>  
+      <field name="description">
+        <column name="DESC" length="4000" jdbc-type="VARCHAR" allows-null="true"/>
+      </field>
+      <field name="locationUri">
+        <column name="DB_LOCATION_URI" length="4000" jdbc-type="VARCHAR" allows-null="false"/>
+      </field>


> Provide metastore schema migration scripts (0.5 -> 0.6)
> -------------------------------------------------------
>
>                 Key: HIVE-1427
>                 URL: https://issues.apache.org/jira/browse/HIVE-1427
>             Project: Hadoop Hive
>          Issue Type: Task
>          Components: Metastore
>            Reporter: Carl Steinbach
>            Assignee: Carl Steinbach
>             Fix For: 0.6.0
>
>
> At a minimum this ticket covers packaging up example MySQL migration scripts (cumulative across all schema changes from 0.5 to 0.6) and explaining what to do with them in the release notes.
> This is also probably a good point at which to decide and clearly state which Metastore DBs we officially support in production, e.g. do we need to provide migration scripts for Derby?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.