[jira] [Commented] (FALCON-256) Create new API for Process dependency graph DAG which captures process connected via feeds

["Srikanth Sundarrajan (JIRA)" <ji...@apache.org>]

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

Srikanth Sundarrajan commented on FALCON-256:
---------------------------------------------

> FalconCLI::validatePipeline is newly added, never used and it is private.

{code}
+    @GET
+    @Path("/entities")
+    @Produces({MediaType.APPLICATION_JSON})
+    public Response getEntityLineageGraph(@QueryParam("pipeline") final String pipeline) {
+        LOG.info("Get lineage Graph for pipeline:({})", pipeline);
{code}

might churn the graph and might be costly too. Would be useful to monitor the performance of this  (@Monitored ?)

> Create new API for Process dependency graph DAG which captures process connected via feeds
> ------------------------------------------------------------------------------------------
>
>                 Key: FALCON-256
>                 URL: https://issues.apache.org/jira/browse/FALCON-256
>             Project: Falcon
>          Issue Type: Improvement
>            Reporter: Shaik Idris Ali
>            Assignee: Ajay Yadav
>              Labels: API, REST, dependencies, graph
>         Attachments: FALCON-256.patch
>
>
> Currently Falcon has dependency APIs which lists the entity dependencies.
> i.e. A dependency of a process lists all the input and output feeds and corresponding clusters.
> With the new process DAG API, it should generate .DOT file which can be easily converted to visual graph.
> All the processes are linked by the configured feeds.
> EX: If process A generates feeds 1,2 and feed 1 is consumed by process B and 2 by process C respectively, then the .DOT file should generate adjacency matrix.
> Graph start{
> A -> B
> A -> C
> ..
> ..
> B->D
> D->E
> }
> Unless we build dashboard this API will be handy for users.



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