[
https://issues.apache.org/jira/browse/TAJO-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14370896#comment-14370896
]
Seungun Choe commented on TAJO-1429:
------------------------------------
Thanks for your opinion, Jihoon.
But, I think it's not comfortable at operating cluster.
When tajo cluster is upraded, operator can know to show error about 'catalog
schema information was changed' at log files.
Using tajo-dump, it follows the next step. (it's inconvenient.)
1) upgrade tajo cluster.
2) check error messages.
3) down-grade tajo master.
4) bin/tajo-dump db_name > file_name
6) upgrade tajo master
7) bin/tsql -f file_name
So, I suggest that I make migration tool.
> 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)
