[jira] [Commented] (FALCON-2104) Loss of data in GraphDB when upgrading Falcon from 0.9 to 0.10.

["Srikanth Sundarrajan (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FALCON-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15400418#comment-15400418 ] 

Srikanth Sundarrajan commented on FALCON-2104:
----------------------------------------------

You might want to shutdown the falcon server when you are copying the state to JSON, as you dont want any dirty writes to the db after having backed up an entry. 

Does shift from 0.4.2 to 0.5.4 of titan introduce any other incompatibility that one should be aware of?

> Loss of data in GraphDB when upgrading Falcon from 0.9 to 0.10. 
> ----------------------------------------------------------------
>
>                 Key: FALCON-2104
>                 URL: https://issues.apache.org/jira/browse/FALCON-2104
>             Project: Falcon
>          Issue Type: Bug
>    Affects Versions: 0.10
>            Reporter: Balu Vellanki
>            Assignee: Balu Vellanki
>            Priority: Critical
>             Fix For: trunk, 0.10
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> FALCON-1333 (Instance Search feature) requires Falcon to use titan-berkeleyje version 0.5.4 to support indexing. Up until version 0.9 - Falcon used   titan-berkeleyje-jre6 version 0.4.2.  GraphDB created by version 0.4.2 cannot be read by version 0.5.4. When attempting an upgrade, I realized that entity and instance lineage data created in 0.9 version could not be read by Falcon in 0.10 version. 
> The only solution seems to provide a tool to do the following
> - Use 0.4.2 version of titan-berkeleyje-jre6 to read the berkeleyDB based graphDB and create a JSON file with all data.
> - shutdown falcon-0.9, upgrade Falcon.
> - use 0.5.4 version of titan-berkeleyje to read JSON file and repopulate berkeleyDB based graphDB.
> - restart falcon-0.10
> I will work on the tool, and update release-notes, upgrade instructions accordingly. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)