+1 from me, this sounds like the right direction. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free.www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Wed, Aug 28, 2024 at 2:48 AM Isha Lamboo <[email protected]> wrote: > Hi Bryan, > > From the perspective of an admin maintaining clusters with many different > teams working on them, this sounds like a valuable improvement. > I think it will be especially useful for develop and test environments > where different versions of flows tend to be left on the canvas "just in > case we need more testing". > > Regards, > > Isha > > -----Oorspronkelijk bericht----- > Van: Bryan Bende <[email protected]> > Verzonden: dinsdag 27 augustus 2024 17:40 > Aan: [email protected] > Onderwerp: [DISCUSS] Removal of MissingComponentsCheck from Flow > Synchronization > > All, > > I'd like to propose a change to the flow synchronization behavior and > since we are still defining the new NIP process, I created a proposal under > the existing Feature Proposal page: > > > https://cwiki.apache.org/confluence/display/NIFI/Remove+MissingComponentsCheck+from+Flow+Synchronization > > This is more of a change in behavior, rather than a new feature. > Please provide any feedback or concerns. If there are no objections, I can > proceed with creating a JIRA and PR, the code changes should be very narrow. > > Thanks, > > Bryan >
