[
https://issues.apache.org/jira/browse/TAJO-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377608#comment-14377608
]
Jinhang Choi commented on TAJO-1429:
------------------------------------
I agree with [~yongjin.choi] in some context. After trying catalog backup and
restore, I conclude that Tajo have to consider another support of different
catalog migration compared to existing mechanism. In other words, it needs to
support "catalog data" migration. This is because just restoring table DDL to
new catalog scheme cannot transport metadata such as the number of row in
tables, which are previously created by Tajo queries.
Providing forward compatibility update in some way is one of important issues
in the existing system. Even though the existing Tajo do not deal with diverse
types of metadata, those information can be seriously considered in future use
of Tajo functionality with enhancements of system, I think.
> 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)
