You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Bryan Bende (JIRA)" <ji...@apache.org> on 2018/02/15 17:38:00 UTC

[jira] [Commented] (NIFI-4884) Failed to import flow from registry when processor has CRON schedule

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

Bryan Bende commented on NIFI-4884:
-----------------------------------

I believe the issue is that when we apply values from the versioned processor to the actual processor, we are setting the schedule duration before the schedule strategy.

Testing a change and will submit a PR if it works.

> Failed to import flow from registry when processor has CRON schedule
> --------------------------------------------------------------------
>
>                 Key: NIFI-4884
>                 URL: https://issues.apache.org/jira/browse/NIFI-4884
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 1.5.0
>            Reporter: Bryan Bende
>            Assignee: Bryan Bende
>            Priority: Major
>
> Steps to reproduce:
>  * Make a new process group
>  * Go into new PG
>  * Create a GenerateFlowFile processor
>  * Set scheduling strategy to CRON
>  * Start Version Control
>  * Create a new PG by importing V1 that was saved in previous step
> This will produce a modal pop up saying that the cron expression is not a valid scheduling strategy and will result in an empty PG.
> Tested on a large PG with 50+ processors where only one had CRON, and still results in empty PG with nothing imported.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)