[
https://issues.apache.org/jira/browse/FALCON-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15334247#comment-15334247
]
Ajay Yadava commented on FALCON-2030:
-------------------------------------
Thanks [~me.venkatr]!
Metadatas do change but it is not necessary to maintain their versions as it is
not practically useful to maintain old versions. Only the latest and one source
of truth is required and maintained.
Also, as you said that users might use a version number, a unique id like epoch
etc., or just use the english version like /mydata-june. How will we enforce
the pattern in those cases?
> 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)
