[jira] [Commented] (HIVE-3999) Mysql metastore upgrade script will end up with different schema than the full schema load

2013-02-17 Thread caofangkun (JIRA)
[ https://issues.apache.org/jira/browse/HIVE-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13580452#comment-13580452 ] caofangkun commented on HIVE-3999: -- We'd better set a default value for column

[jira] [Commented] (HIVE-3999) Mysql metastore upgrade script will end up with different schema than the full schema load

2013-02-17 Thread Jarek Jarcec Cecho (JIRA)
[ https://issues.apache.org/jira/browse/HIVE-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13580457#comment-13580457 ] Jarek Jarcec Cecho commented on HIVE-3999: -- Hi sir, setting the default value was

Re: [jira] [Commented] (HIVE-3999) Mysql metastore upgrade script will end up with different schema than the full schema load

2013-02-17 Thread FangKun Cao
Hi Jarek Jarcec Cecho, I agree with you now. Your solution is the most suitable way. 2013/2/18 Jarek Jarcec Cecho (JIRA) j...@apache.org [

[jira] [Commented] (HIVE-3999) Mysql metastore upgrade script will end up with different schema than the full schema load

2013-02-17 Thread caofangkun (JIRA)
[ https://issues.apache.org/jira/browse/HIVE-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13580469#comment-13580469 ] caofangkun commented on HIVE-3999: -- Hi Jarek Jarcec Cecho, I agree with you now. Your

[jira] [Commented] (HIVE-3999) Mysql metastore upgrade script will end up with different schema than the full schema load

2013-02-08 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/HIVE-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13574474#comment-13574474 ] Hudson commented on HIVE-3999: -- Integrated in hive-trunk-hadoop1 #73 (See

[jira] [Commented] (HIVE-3999) Mysql metastore upgrade script will end up with different schema than the full schema load

2013-02-08 Thread Mark Grover (JIRA)
[ https://issues.apache.org/jira/browse/HIVE-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13574505#comment-13574505 ] Mark Grover commented on HIVE-3999: --- Thanks Namit! Mysql metastore

[jira] [Commented] (HIVE-3999) Mysql metastore upgrade script will end up with different schema than the full schema load

2013-02-08 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/HIVE-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13574918#comment-13574918 ] Hudson commented on HIVE-3999: -- Integrated in Hive-trunk-hadoop2 #112 (See

[jira] [Commented] (HIVE-3999) Mysql metastore upgrade script will end up with different schema than the full schema load

2013-02-08 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/HIVE-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13574956#comment-13574956 ] Hudson commented on HIVE-3999: -- Integrated in Hive-trunk-h0.21 #1961 (See

[jira] [Commented] (HIVE-3999) Mysql metastore upgrade script will end up with different schema than the full schema load

2013-02-07 Thread Mark Grover (JIRA)
[ https://issues.apache.org/jira/browse/HIVE-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13574253#comment-13574253 ] Mark Grover commented on HIVE-3999: --- +1 (non-committer) Mysql metastore