[
https://issues.apache.org/jira/browse/FALCON-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15334259#comment-15334259
]
Ajay Yadava commented on FALCON-2030:
-------------------------------------
I understand the motivation to help users but I think the fix in FALCON-2023 is
correct, sufficient and forward looking approach. We should fix any issues
which are caused by relying on the feeds locations to conform a particular
pattern. The date pattern should be to facilitate certain use cases but not to
block any other use cases.
Let me give another practical benefit of *not* enforcing the pattern. Falcon
users can now write their own custom retention policy, so one can now write a
custom policy which treats a folder as the feed location and deletes only the
sub folders or files with creation time older than a certain date. In fact this
was the use case for a certain user on the mailing list.
> Enforce time partition pattern in the data location path in feed definition
> ----------------------------------------------------------------------------
>
> Key: FALCON-2030
> URL: https://issues.apache.org/jira/browse/FALCON-2030
> Project: Falcon
> Issue Type: Improvement
> Components: feed
> Reporter: Venkatesan Ramachandran
> Assignee: Venkatesan Ramachandran
>
> In feed definition, data location can be specified without time series
> pattern like below:
> <locations>
> <location type="data"
> path="/tmp/falcon-regression/RetentionTest/testFolders/"/>
> <location type="stats" path="/projects/falcon/clicksStats"/>
> <location type="meta" path="/projects/falcon/clicksMetaData"/>
> </locations>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
