falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suhas Vasu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-145) Feed eviction be implemented in appropriate Storage implementation
Date Wed, 01 Oct 2014 13:23:34 GMT

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

Suhas Vasu commented on FALCON-145:

EvictionHelper class and its corresponding usage was removed as part of FALCON-731. So, I
don't see why it has to be re-introduced here. 

> 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-v3.patch, FALCON-145-v4.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

View raw message