alopresto commented on issue #3335: NIFI-5018 URL: https://github.com/apache/nifi/pull/3335#issuecomment-467267426 The four components altered are the ones most frequently displayed on the canvas, and therefore likely to cause changes in versioned flows based on position changes. Can I ask what reasoning led to not applying this snap feature to labels, funnels, or queue description panels/bend points? It seems like this would lead to an inconsistent experience for a user adding/modifying components on the canvas. My concern is that having the canvas change those dimensions/positioning will report back to the server that the component position has changed via the API, which will mark each component state as modified when flow versioning is enabled. This means that the version control features provided through the integration with NiFi Registry will be invoked and the flow will be marked as modified locally. It may also cause problems with nodes re-joining a cluster where two nodes may report the state changes in a non-deterministic manner and cause a conflict in the flow fingerprinting.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
