[
https://issues.apache.org/jira/browse/FALCON-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13810011#comment-13810011
]
Shaik Idris Ali commented on FALCON-161:
----------------------------------------
Hi Venkatesh,
Is this issue common across non Hcat based feeds?
Let me know if my understanding is correct based on your the bug description:
Say, I have feed whose frequency is hours(1) and late cut-off is defined as
hours(24) and retention as
1. case(1): retention= hours(36). (>late cut-off)
Here, the feed ensures that data is present for atleast last 36 hours and data
can change till 24 hours.
2. case(2): retention = hours(18) (<late cut-off)
Here, the feed ensures data is present for last 18 hours but it can change till
24 hours, so the feed definition iteself is invalid here and I think this
validation is present.
Is this the scenario related to case(2)?
> Feed evictor evicts instances not eligible when pattern has dash
> ----------------------------------------------------------------
>
> Key: FALCON-161
> URL: https://issues.apache.org/jira/browse/FALCON-161
> Project: Falcon
> Issue Type: Sub-task
> Affects Versions: 0.3
> Reporter: Venkatesh Seetharam
> Assignee: Venkatesh Seetharam
> Attachments: FALCON_161.patch
>
>
> I encountered this bug accidentally when testing replication. The desired
> instance for replication was always evicted when it was not eligible and
> replication fails all the time in late data saying the partition does not
> exist. After looking at this for some time, figured out that a partition
> containing "-" in the pattern did not work since I had reused much of
> existing code that ignores it in FileSystem storage.
> {code} ${YEAR}-${MONTH}-${DAY} {code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
