falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srikanth Sundarrajan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-949) Force update feature
Date Thu, 29 Jan 2015 09:50:35 GMT

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

Srikanth Sundarrajan commented on FALCON-949:
---------------------------------------------

Minor nit, looks good otherwise.

Might improve readability if updateInternal was in an independent statement.
{noformat}
+            result.append(updateInternal(entity, entity, clusterEntity, bundle,
+                    CurrentUser.getUser())).append("\n");
{noformat}

> Force update feature
> --------------------
>
>                 Key: FALCON-949
>                 URL: https://issues.apache.org/jira/browse/FALCON-949
>             Project: Falcon
>          Issue Type: Improvement
>            Reporter: Shwetha G S
>            Assignee: pavan kumar kolamuri
>         Attachments: FALCON-949-v1.patch, FALCON-949.patch
>
>
> Falcon does update only if the entity is changed. Sometimes, there is a need to force
an update for updating the workflow definition for parent workflow. Users do this currently
by adding a dummy property. Instead, we should add a force option



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

Mime
View raw message