[
https://issues.apache.org/jira/browse/FALCON-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13737213#comment-13737213
]
Venkatesh Seetharam commented on FALCON-72:
-------------------------------------------
bq. 2. Can we add a method to AbstractWorkflowEngine to validate the Workflow
URL validity and not have to implement any specific validation here. If we
apply security patch and the version api, is rejected due to missing ticket,
this might break.
I did think about this but cannot be done. The implementation for the
AbstractWorkflowEngine in common module is present in oozie module which
depends on common module. It'll become a circular dependency. May be a better
solution is to just open the connection to the URL specified in the interface
and see if its reachable.
> Feeds with invalid oozie URI in cluster cannot be deleted
> ---------------------------------------------------------
>
> Key: FALCON-72
> URL: https://issues.apache.org/jira/browse/FALCON-72
> Project: Falcon
> Issue Type: Bug
> Components: general
> Affects Versions: 0.3
> Reporter: Venkatesh Seetharam
> Assignee: Venkatesh Seetharam
> Attachments: FALCON-72.patch, FALCON-72.r1.patch
>
>
> User submits a cluster dsl with a bad oozie uri. He then submits a feed with
> this cluster. User will never be able to remove the feed from Falcon.
> I'd suggest we add validations for all the interfaces:
> * Execute - create a JobClient object
> * Workflow - This is initialized quite late
> * Messaging - not sure if we need to validate this? Will Falcon work without
> this?
> * Read - Why not validate this as well?
> Thanks Grant Liu for bringing this to my attention.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
