nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (Jira)" <>
Subject [jira] [Commented] (NIFI-6025) Track Enabled/Disabled State in Registry
Date Thu, 29 Aug 2019 14:36:00 GMT


ASF subversion and git services commented on NIFI-6025:

Commit 4ae1fec78a77be5b9b06bd79fa22ae020f3365bc in nifi's branch refs/heads/master from Mark
[;h=4ae1fec ]

NIFI-6025: Include Processor 'scheduled state' (i.e., Enabled or Disabled) in the VersionedProcessor
when pushing to Flow Registry and take into account when updating flows on the NiFi side

NIFI-6025: Include difference in Scheduled State as a Local Flow Difference

This closes #3546.

Signed-off-by: Bryan Bende <>

> 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 10m
>  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