Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 10A2F200B60 for ; Sun, 31 Jul 2016 04:17:25 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 0F484160A8B; Sun, 31 Jul 2016 02:17:25 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 575DD160A8A for ; Sun, 31 Jul 2016 04:17:24 +0200 (CEST) Received: (qmail 60698 invoked by uid 500); 31 Jul 2016 02:17:23 -0000 Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@falcon.apache.org Delivered-To: mailing list dev@falcon.apache.org Received: (qmail 60683 invoked by uid 99); 31 Jul 2016 02:17:23 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 31 Jul 2016 02:17:23 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 2448E1804F0 for ; Sun, 31 Jul 2016 02:17:23 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -4.646 X-Spam-Level: X-Spam-Status: No, score=-4.646 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id M7YtTl-xFHRc for ; Sun, 31 Jul 2016 02:17:22 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with SMTP id 8F83A5F39B for ; Sun, 31 Jul 2016 02:17:21 +0000 (UTC) Received: (qmail 60544 invoked by uid 99); 31 Jul 2016 02:17:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 31 Jul 2016 02:17:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 92EA82C0D5D for ; Sun, 31 Jul 2016 02:17:20 +0000 (UTC) Date: Sun, 31 Jul 2016 02:17:20 +0000 (UTC) From: "Srikanth Sundarrajan (JIRA)" To: dev@falcon.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (FALCON-2104) Loss of data in GraphDB when upgrading Falcon from 0.9 to 0.10. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sun, 31 Jul 2016 02:17:25 -0000 [ https://issues.apache.org/jira/browse/FALCON-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15400913#comment-15400913 ] Srikanth Sundarrajan commented on FALCON-2104: ---------------------------------------------- I dont know of a way to distribute this outside a release. I would think it is best shipped as a part of 0.10 release. > 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)