[
https://issues.apache.org/jira/browse/FALCON-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861351#comment-13861351
]
Srikanth Sundarrajan commented on FALCON-240:
---------------------------------------------
The issue with this approach is while process & replication returns status of
the specific instance of the data, retention gives status of a "run" which is
not tied to any specific data instance (time partition). Perhaps the way to
look at instance status for retention is to allow the last status to be stored
and retrieved and not consider inputs such as start time or end time. Since a
successful retention removes all data that are outside the allowed time window,
it is sufficient to know if the last instance was successful or a failure.
> Instance status from CLI on a feed doesn't give the retention details
> ---------------------------------------------------------------------
>
> Key: FALCON-240
> URL: https://issues.apache.org/jira/browse/FALCON-240
> Project: Falcon
> Issue Type: Bug
> Reporter: Suhas Vasu
> Assignee: Suhas Vasu
> Attachments: FALCON-240.patch
>
>
> Doing a instance status for a feed doesn't show details for retention.
> Ex:
> Running the following command -
> falcon instance -type feed -name X -status -start 2013-12-28T00:00Z -end
> 2013-12-30T12:00Z
> gives -
> Consolidated Status: SUCCEEDED
> Instances:
> Instance Cluster SourceCluster Status
> Start End Details Log
> -----------------------------------------------------------------------------------------------
> Additional Information:
> Response: STATUSRequest Id: f2f48373-44d7-4b9b-afc8-b2c6e8c68827
> It would be helpful to know the retention details of a feed.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
