falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srikanth Sundarrajan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-240) Instance status from CLI on a feed doesn't give the retention details
Date Thu, 09 Jan 2014 05:47:58 GMT

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

Srikanth Sundarrajan commented on FALCON-240:

[~sepreece], JMS messages are published when feed instances are removed, also when the feed
is mapped to hcatalog table, the partition is dropped. Both these should provide information
on when an instance was removed. Even with instance status on retention lifecycle, it would
be hard to figure out which execution actually removed what instances, unless we browse through
each of the instances and search for the requisite instance time.

> 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

View raw message