[
https://issues.apache.org/jira/browse/FALCON-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804494#comment-13804494
]
Venkatesh Seetharam commented on FALCON-156:
--------------------------------------------
Falcon introduces a higher-layer of abstraction and exposing internals of a
workflow engine/scheduler to the end user will beat that purpose. The end user
of Falcon need not know about Oozie nor DistCp. Falcon would have returned
error if it had not materialized an update successfully barring some use cases
where Oozie is not synchronous.
Also, architecturally, Oozie is one of the implementations for Falcon to
materialize schedules and orchestrate workflows. There can be more in the
future.
> falcon should return oozie coord status
> ---------------------------------------
>
> Key: FALCON-156
> URL: https://issues.apache.org/jira/browse/FALCON-156
> Project: Falcon
> Issue Type: Improvement
> Components: general
> Reporter: Sanjeev T
> Priority: Trivial
>
> falcon submit/update/delete for feed/process, should return with the oozie
> coord.
> It would be easy to debug, if it runs into issue
--
This message was sent by Atlassian JIRA
(v6.1#6144)
