[
https://issues.apache.org/jira/browse/FALCON-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15401474#comment-15401474
]
Balu Vellanki commented on FALCON-2104:
---------------------------------------
Thank you [~venkatnrangan] for helping, The patch looks good and I will test it
again tonight. I realized we only need 0.9 patch if we are downgrading from
0.10 to 0.9. When we are upgrading from 0.9 or lower version to 0.10, we can
use the serialize API https://falcon.apache.org/restapi/Graph.html to create
the JSON output. I tested that the output of serialize api can be used to read
into 0.10 and it works. We can document this in the release notes.
I will create a pull request once I finish testing, let me know if that is ok.
> 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: Venkat Ranganathan
> Priority: Critical
> Fix For: trunk, 0.10
>
> Attachments: FALCON-2104.patch-v0.10, FALCON-2104.patch-v0.9
>
> 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)
