[
https://issues.apache.org/jira/browse/TAJO-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14370960#comment-14370960
]
Hyunsik Choi commented on TAJO-1429:
------------------------------------
I don't think that this is a problem. You aways consider the migration of
catalog when you try major version upgrades. Most of database systems including
Hive also should do.
Also, your practice seems to be inconvenient. Upgrade practice is as follow:
1) bin/tajo-dump all > backup.sql
2) change catalog-site.xml to use another database in RDBMS (keep old database
for recovery)
3) launch new upgraded Tajo binary
4) bin/tajo -f backup.sql
> Old version catalog databases dose not work on tajo-0.11.0-SNAPSHOT.
> ---------------------------------------------------------------------
>
> Key: TAJO-1429
> URL: https://issues.apache.org/jira/browse/TAJO-1429
> Project: Tajo
> Issue Type: Bug
> Reporter: Seungun Choe
> Assignee: Seungun Choe
> Priority: Minor
>
> In my case, make catalog database set on tajo-0.9.0-SNAPSHOT.
> This catalog worked on tajo-0.9.1-SNAPSHOT and tajo-0.10.0-SNAPSHOT.
> But, it does not work on tajo-0.11.0-SNAPSHOT.
> So, I change META table's value at catalog database. ( 2 -> 3 )
> But, it does not working.
> I think old version catalog database can use any time, any version tajo.
> (My catalog databases is on mysql.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
