falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ajay Yadav (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (FALCON-301) Falcon allows multiple feed submission on a single path in hdfs
Date Sat, 13 Sep 2014 05:16:33 GMT

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

Ajay Yadav edited comment on FALCON-301 at 9/13/14 5:16 AM:
------------------------------------------------------------

[~svenkat]

The only use case is for the subpath to gate on individual colo data, as mentioned by Shaik
Idris above. I intend to allow sub paths and that will solve for that use case. 

In all other cases we have always found it to be problematic rather than helpful e.g. when
someone accidentally submits another feed for same path and with lesser retention than required.


1. One option is to disallow all - add/edit/reload of duplicate feeds. This will break existing
duplicate feeds and will need a migration strategy. However, advantage of this, apart from
being very neat, is that we can always safely assume that there are no feeds with duplicate
paths, in future. I am thinking more on this line as of now and need inputs on what will be
the most convenient migration strategy for this. 

2. Another option might be to disallow only addition of new feeds with duplicate paths but
allow edit and reload. This will not break any existing system but is not very neat IMHO.



was (Author: ajayyadava):
[~svenkat]

The only use case is for the subpath to gate on individual feeds, as mentioned by Shaik Idris
above. I intend to allow sub paths and that will solve for that use case. 

In all other cases we have always found it to be problematic rather than helpful e.g. when
someone accidentally submits another feed for same path and with lesser retention than required.


1. One option is to disallow all - add/edit/reload of duplicate feeds. This will break existing
duplicate feeds and will need a migration strategy. However, advantage of this, apart from
being very neat, is that we can always safely assume that there are no feeds with duplicate
paths, in future. I am thinking more on this line as of now and need inputs on what will be
the most convenient migration strategy for this. 

2. Another option might be to disallow only addition of new feeds with duplicate paths but
allow edit and reload. This will not break any existing system but is not very neat IMHO.


> Falcon allows multiple feed submission on a single path in hdfs
> ---------------------------------------------------------------
>
>                 Key: FALCON-301
>                 URL: https://issues.apache.org/jira/browse/FALCON-301
>             Project: Falcon
>          Issue Type: Bug
>          Components: client, feed
>    Affects Versions: 0.5
>            Reporter: Deepak Marathe
>            Assignee: Ajay Yadav
>            Priority: Minor
>         Attachments: diff.patch
>
>




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

Mime
View raw message