Return-Path: X-Original-To: apmail-falcon-dev-archive@minotaur.apache.org Delivered-To: apmail-falcon-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7C8B318B43 for ; Wed, 17 Jun 2015 06:29:03 +0000 (UTC) Received: (qmail 93551 invoked by uid 500); 17 Jun 2015 06:29:03 -0000 Delivered-To: apmail-falcon-dev-archive@falcon.apache.org Received: (qmail 93506 invoked by uid 500); 17 Jun 2015 06:29:03 -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 93481 invoked by uid 99); 17 Jun 2015 06:29:03 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Jun 2015 06:29:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id E2D51CE5C5 for ; Wed, 17 Jun 2015 06:29:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.332 X-Spam-Level: X-Spam-Status: No, score=0.332 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.648] autolearn=disabled Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id pOewPsYNjzmG for ; Wed, 17 Jun 2015 06:29:02 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with SMTP id 70383214DE for ; Wed, 17 Jun 2015 06:29:01 +0000 (UTC) Received: (qmail 93463 invoked by uid 99); 17 Jun 2015 06:29:00 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Jun 2015 06:29:00 +0000 Date: Wed, 17 Jun 2015 06:29:00 +0000 (UTC) From: "Ajay Yadava (JIRA)" To: dev@falcon.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (FALCON-335) Clean up historical data periodically MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/FALCON-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajay Yadava updated FALCON-335: ------------------------------- Labels: lineage newbie (was: lineage) > Clean up historical data periodically > ------------------------------------- > > Key: FALCON-335 > URL: https://issues.apache.org/jira/browse/FALCON-335 > Project: Falcon > Issue Type: Sub-task > Affects Versions: 0.5 > Reporter: Venkatesh Seetharam > Labels: lineage, newbie > > It is reasonable to leave behind graph elements after an entity is deleted to allow historical queries. However there has to be some cleanup based on time limit that ought to be available. This is required even for active ones. Also it might be worth considering to make an option available to the user to delete an entity along with its historical data. -- This message was sent by Atlassian JIRA (v6.3.4#6332)