nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Payne (Jira)" <>
Subject [jira] [Reopened] (NIFI-6025) Track Enabled/Disabled State in Registry
Date Tue, 03 Sep 2019 15:19:00 GMT


Mark Payne reopened NIFI-6025:

Re-opening due to an issue that occurs when running against a version of Registry older than
0.5.0. While this works well against a 0.5.0 registry, if checking out a flow from an older
version of the registry, we see the flow immediately become "modified" or in a conflict state.
This is because the older version of the registry didn't store the Scheduled State, and so
a Flow Difference is erroneously created indicating that Processors were disabled when they
weren't (the flag was just null).

> Track Enabled/Disabled State in Registry
> ----------------------------------------
>                 Key: NIFI-6025
>                 URL:
>             Project: Apache NiFi
>          Issue Type: Improvement
>    Affects Versions: 1.8.0
>            Reporter: Alan Jackoway
>            Assignee: Mark Payne
>            Priority: Major
>              Labels: SDLC
>             Fix For: 1.10.0
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
> We often have little chunks of pipelines that are used for debugging/fixing things that
went wrong/etc. that we want to disable. I would love for disabled/enabled to be a thing that
gets committed to registry, but my little test says it isn't. It would be nice for disabled
state to be persisted in registry so that we can differentiate between things that should
usually be disabled and things that are just stopped.

This message was sent by Atlassian Jira

View raw message