[
https://issues.apache.org/jira/browse/NIFI-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15940512#comment-15940512
]
ASF subversion and git services commented on NIFI-3380:
-------------------------------------------------------
Commit d90cf846b9dcd49acdeac7bb5fcd13ee80dcdba6 in nifi's branch
refs/heads/master from [~bbende]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=d90cf84 ]
NIFI-3380 Bumping NAR plugin to 1.2.0-SNAPSHOT development to leverage changes
from master, adding buildnumber-maven-plugin to nifi-nar-bundles to properly
set build info in MANIFEST of NARs
- Refactoring NarDetails to include all info from MANIFEST
- Adding the concept of a Bundle and refactoring NarClassLoaders to pass
Bundles to ExtensionManager
- Adding logic to fail start-up when multiple NARs with same coordinates exist,
moving Bundle classes to framework API
- Refactoring bundle API to classes and creating BundleCoordinate
- Updating FlowController to use BundleCoordinate
- Updating the UI and DTO model to support showing bundle details that loaded
an extension type.
- Adding bundle details for processor canvas node, processor dialogs,
controller service dialogs, and reporting task dialogs.
- Updating the formating of the bundle coordinates.
- Addressing text overflow in the configuration/details dialog.
- Fixing self referencing functions.
- Updating extension UI mapping to incorporate bundle coordinates.
- Discovering custom UIs through the supplied bundles.
- Adding verification methods for creating extensions through the rest api.
- Only returning extensions that are common amongst all nodes.
- Rendering the ghost processors using a dotted border.
- Adding bundle details to the flow.xml.
- Loading NiFi build and version details from the framework NAR.
- Removing properties for build and version details.
- Wiring together front end and back end changes.
- Including bundle coordinates in the component data model.
- Wiring together component data model and flow.xml.
- Addressing issue when resolve unvesioned dependent NARs.
Updating unit tests to pass based on framework changes
- Fixing logging of extension types during start up
- Allowing the application to start if there is a compatible bundle found. -
Reporting missing bundle when the a compatible bundle is not found. - Fixing
table height in new component dialogs.
Fixing chechstyle error and increasing test timeout for
TestStandardControllerServiceProvider
- Adding ability to change processor type at runtime
- Adding backend code to change type for controller services
- Cleaning up instance classloaders for temp components.
- Creating a dialog for changing the version of a component.
- Updating the formatting of the component type and bundle throughout.
- Updating the new component dialogs to support selecting source group.
- Cleaning up new component dialogs.
- Cleaning up documentation in the cluster node endpoint.
Adding missing include in nifi-web-ui pom compressor plugin
- Refactoring so ConfigurableComponent provides getLogger() and so the nodes
provide the ConfigurableComponent
- Creating LoggableComponent to pass around the component, logger, and
coordinate with in the framework
- Finishing clean up following rebase.
Calling lifecycle methods for add and remove when changing versions of a
component
- Introducing verifyCanUpdateBundle(coordinate) to ConfiguredComponent, and
adding unit tests
- Ensuring documentation is available for all components. Including those of
the same type that are loaded from different bundles.
Adding lookup from ClassLoader to Bundle, adding fix for instance class loading
to include all parent NARs, and adding additional unit tests for FlowController
- Adding validation to ensure referenced controller services implement the
required API
- Fixing template instantiation to look up compatible bundle
- Requiring services/reporting tasks to be disabled/stopped.
- Only supporting a change version option when the item has multiple versions
available.
- Limiting the possible new controller services to the applicable API version.
- Showing the implemented API versions for Controller Services.
- Updating the property descriptor tooltip to indicate the required service
requirements.
- Introducing version based sorting in the new component dialog, change version
dialog, and new controller service dialog.
- Addressing remainder of the issues from recent rebase.
Ensuring bundles have been added to the flow before proposing a flow, and
incorporating bundle information into flow fingerprinting
- Refactoring the way missing bundles work to retain the desired bundle if
available
- Fixing logger.isDebugEnabled to be logger.isTraceEnabled
- Auditing when user changes the bundle. - Ensuring bundle details are present
in templates.
Moving standard prioritizers to framework NAR and refactoring ExtensionManager
logic to handle cases where an extension is in a JAR directly in the lib
directory
- Ensuring all nodes attempt to instantiate the same template instance when the
available bundles may differ. - Fixing the auditing of copy/paste and template
instantiation. - Running addtional verification methods when running standalone.
Refactoring controller service invocation handler to allow updating the node
used by the invocation handler
- Ensuring the bundles in a proposed flow are compatible with the current
instance when the current instance has no flow is going to accept the proposed
flow
- Merging whether multiple versions of the component are available
- Setting NAR plugin back to current released version
- Cleaning up DocGenerator to not process multiple times
Addressing incorrect usage of nf.Common. - Using formatType in the new
component type dialogs.
Improving error messages when looking for bundles
Addressing comments from PR. - Fixing references to global nf namespace. -
Fixing injection of nfProcessGroupConfiguration in nfComponentVersion. - Fixing
web api integration tests.
Not rendering unversioned in help documentation. - Ensuring the
isExtentionMissing flag is correct after changing the component type.
Adding synchronization in node classes to ensure changing component can't occur
when component is running, introducing MissingBundleException for better
reporting when a node can't join cluster due to a missing bundle, and bumping
NAR plugin to released version 1.2.0
Adding concept of missing components to fingerprinting to ensure nodes agree on
missing components when joining a cluster
NIFI-3380: NIFI-3520: - Fixing hive nar dependency. - Marking DBCPService as
provided. - Skipping services that require instance classloading and are
cobundled with their service API. - Skipping components that require instance
classloading and reference service APIs that are cobundled. - Addressing UI
issues in the new component dialogs when re-opening with a filter applied.
Fixing checkstyles issue and adding back assume checks to distributed cache
server test
Ensuring new component types are sorted correctly when shown initially.
This closes #1585.
> Multiple Versions of the Same Component
> ---------------------------------------
>
> Key: NIFI-3380
> URL: https://issues.apache.org/jira/browse/NIFI-3380
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Fix For: 1.2.0
>
> Attachments: nifi-example-processors-nar-1.0.nar,
> nifi-example-processors-nar-2.0.nar, nifi-example-service-api-nar-1.0.nar,
> nifi-example-service-api-nar-2.0.nar, nifi-example-service-nar-1.0.nar,
> nifi-example-service-nar-1.1.nar, nifi-example-service-nar-2.0.nar
>
>
> This ticket is to track the work for supporting multiple versions of the same
> component within NiFi. The overall design for this feature is described in
> detail at the following wiki page:
> https://cwiki.apache.org/confluence/display/NIFI/Multiple+Versions+of+the+Same+Extension
> This ticket will track only the core NiFi work, and a separate ticket will be
> created to track enhancements for the NAR Maven Plugin.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
