You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Ajay Yadav (JIRA)" <ji...@apache.org> on 2014/09/01 15:41:21 UTC

[jira] [Comment Edited] (FALCON-145) Feed eviction be implemented in appropriate Storage implementation

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

Ajay Yadav edited comment on FALCON-145 at 9/1/14 1:40 PM:
-----------------------------------------------------------

[~shwethags]  Thanks for the review. I have updated the review board with new patch. 


was (Author: ajayyadava):
[~shwethags]  Thanks for the review. I have updated the review board with newer patch. 

> 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.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)