[
https://issues.apache.org/jira/browse/FALCON-761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152971#comment-14152971
]
Srikanth Sundarrajan commented on FALCON-761:
---------------------------------------------
>From an usage stand point, proposing the following.
*falcon instance -entity feed -listing -start <<>> -end <<>> -colo <<>>*
{noformat}
CLUSTER INSTANCE STATUS SIZE CREATION-TIME URI
========================================================================================================
cluster1 2014-09-10T00:00Z AVAILABLE 300000000 2014-09-10T01:20Z
/data/mydata/2014/09/10
cluster1 2014-09-11T00:00Z EMPTY 0 2014-09-11T01:20Z
/data/mydata/2014/09/11
cluster1 2014-09-12T00:00Z PARTIAL 50000000 2014-09-12T00:35Z
/data/mydata/2014/09/12
cluster1 2014-09-13T00:00Z MISSING - -
/data/mydata/2014/09/13
cluster2 2014-09-10T00:00Z AVAILABLE ? 2014-09-10T02:05Z
catalog:mydb:mydata?ds=2014-09-10
{noformat}
> Falcon to provide feed instance availability status
> ---------------------------------------------------
>
> Key: FALCON-761
> URL: https://issues.apache.org/jira/browse/FALCON-761
> Project: Falcon
> Issue Type: Improvement
> Components: client, feed
> Affects Versions: 0.5, 0.6
> Reporter: Srikanth Sundarrajan
> Assignee: Srikanth Sundarrajan
>
> Falcon processes or feed replication provides status on instances. When the
> instance status is WAITING for input, users have difficulty in identifying
> what feed is missing. In general it would very helpful to users to get feed
> availability status natively through falcon.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
