You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Ajay Yadav (JIRA)" <ji...@apache.org> on 2014/09/28 07:10:34 UTC

[jira] [Commented] (FALCON-265) reverse lookup for falcon entity definition

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

Ajay Yadav commented on FALCON-265:
-----------------------------------

I am considering to choose between one of the following options for CLI command and REST API URL.

# *falcon entity -type feed -lookup /projects/data/2014/09/10* and API URL on lines of *api/entities/:entity-type?path=/projects/data/2014/09/10*

# *falcon feed -lookup /projects/data/2014/09/10* and API URL on lines of *api/feed?path=/projects/data/2014/09/10*

IMHO, basic difference between the two is the entity type option and since this option is of no use on entities other than feed, the second option being more concise should be used.

Thoughts?
CC [~svenkat] [~sriksun] 

> reverse lookup for falcon entity definition
> -------------------------------------------
>
>                 Key: FALCON-265
>                 URL: https://issues.apache.org/jira/browse/FALCON-265
>             Project: Falcon
>          Issue Type: Improvement
>          Components: general
>            Reporter: Binish A.R
>            Assignee: Ajay Yadav
>
> Can we have an option to reverse lookup an entityspecification?
> For instance, 
> 1. Given a path find the corresponding feed definition.
> 2. Given an input feed name, list the corresponding processes.
> Note that [2] is not the same as -dependency option, since depedency option list all dependencies, including both input and output.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)