Mailing-List: contact dev-help@falcon.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@falcon.incubator.apache.org
Date: Tue, 16 Sep 2014 11:29:34 +0000 (UTC)
From: "Ajay Yadav (JIRA)" <jira@apache.org>
To: dev@falcon.incubator.apache.org
Message-ID: <JIRA.12673291.1381433149000.43518.1410866974258@Atlassian.JIRA>
In-Reply-To: <JIRA.12673291.1381433149000@Atlassian.JIRA>
References: <JIRA.12673291.1381433149000@Atlassian.JIRA>
 <JIRA.12673291.1381433149947@arcas>
Subject: [jira] [Updated] (FALCON-145) Feed eviction be implemented in
 appropriate Storage implementation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/FALCON-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ajay Yadav updated FALCON-145:
------------------------------
    Attachment: FALCON-145-v2.patch

Incorporated latest review comments. Updated the review board and uploading patch here as well. 

> Feed eviction be implemented in appropriate Storage implementation
> ------------------------------------------------------------------
>
>                 Key: FALCON-145
>                 URL: https://issues.apache.org/jira/browse/FALCON-145
>             Project: Falcon
>          Issue Type: Improvement
>            Reporter: Venkatesh Seetharam
>            Assignee: Ajay Yadav
>         Attachments: FALCON-145-v2.patch, falcon-145.patch
>
>
> Since the feed storage is abstracted in Storage class either as FileSystemStorage or CatalogStorage, moreover, behaviors for listing partitions and drop partitions are listed there, why do we need to hardcode the eviction behavior and instance deletion discovery for filesystem need to happen in FeedEvictor ? Why can't be implemented in appropriate Storage implementation. That way FeedEvictor would simpler and lot cleaner. 
> This can apply to table replication as well for import and export of partitions.


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