mirror of https://github.com/apache/nifi.git
6a58d780d7
- Initial checkpoint: able ot start version control and detect changes, in standalone mode, still 'crude' implementation - Checkpoint: Can place flow under version control and can determine if modified - Checkpoint: Change version working in some cases. Does not work if processor removed because COMPONENT_REMOVED type has ComponentA whose ID is the VersionedComponentID but we are trying to call ProcessorDAO.get() with this ID - Checkpoint: Able to change flow from Version 1 to Version 2 and back. Not yet tested with controller services. Have not tried changing/removing connections. Not cluster-friendly yet. All inline, not in background. Have not taken into account ports, funnels, remote ports, etc. Have not tested with Labels yet - Checkpoint after implementing ClusterReplicationComponentLifecycle instead of JerseyClientComponentLifecycle - Checkpoint: Updated to allow starting version control and updating version in clustered mode - Checkpoint: Updated versioning endpoint so that when version of a flow is updated, the bundle information is populated and the snapshot is replicated to the cluster. - Checkpoint: Implemented endpoint for reverting to previously sync'ed version of a flow and updated version control endpoint so that Process Group can be pushed as a new version to existing flow instead of only creating a new flow - Checkpoint: Updated so that if a Process Group is under Version Control and it has a child Process Group, which is also under Version Control, we can handle that gracefully. Not yet tested because it depends on updates to the nifi-registry module, which can't be compiled due to maven dependency conflicts |
||
|---|---|---|
| .. | ||
| nifi-custom-ui-utilities | ||
| nifi-jetty | ||
| nifi-ui-extension | ||
| nifi-web-api | ||
| nifi-web-content-access | ||
| nifi-web-content-viewer | ||
| nifi-web-docs | ||
| nifi-web-error | ||
| nifi-web-optimistic-locking | ||
| nifi-web-security | ||
| nifi-web-ui | ||
| pom.xml | ||