[
https://issues.apache.org/jira/browse/NIFI-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15377048#comment-15377048
]
ASF GitHub Bot commented on NIFI-1896:
--------------------------------------
GitHub user apiri opened a pull request:
https://github.com/apache/nifi/pull/650
NIFI-1896 Refactoring nifi-api module to only be those items needed for
implementing extensions
NIFI-1896 Refactoring nifi-api module to only be those items needed for
implementing extensions.
This PR consists of multiple commits to show the process and discrete steps
in the overall effort. Can squash when reviewed and validated.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apiri/incubator-nifi nifi-1896
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/650.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #650
----
commit 0a232ee40b79e571aa15d40ecc7570b145d8e989
Author: Aldrin Piri <[email protected]>
Date: 2016-07-13T13:28:19Z
Initial refactoring of ProvenanceEventRepository and introduction of
ProvenanceRepository as service loaded component.
commit 8b78205279de6896bccad32e23d9066ab2bb3c84
Author: Aldrin Piri <[email protected]>
Date: 2016-07-13T18:41:02Z
Refactoring authorization and user interfaces to be located in the
nifi-framework-api module. Updating associated modules to make use of this
dependency. Performing general cleanup.
commit 4fffd33d356dc4919263fd1a79d49864aab7ffce
Author: Aldrin Piri <[email protected]>
Date: 2016-07-13T21:26:40Z
Removed deprecated OnConfigured and associated references.
commit 9d55f534f1de562899d18c37f111980eb0340076
Author: Aldrin Piri <[email protected]>
Date: 2016-07-13T21:31:12Z
Moving repository and queue interfacves to nifi-framework-api.
commit d1e166a1405ac41a29e65bf2c9a3b92a5be652c2
Author: Aldrin Piri <[email protected]>
Date: 2016-07-13T21:43:10Z
Migrating history components to nifi-framework-api.
commit 5d1d3b3698daccffec1cdd02f7c497cc9dda3a02
Author: Aldrin Piri <[email protected]>
Date: 2016-07-13T21:45:56Z
Marking FlowFilePrioritizer as deprecated.
commit 437f010279c1352891c1051b78f2384a6cab51ad
Author: Aldrin Piri <[email protected]>
Date: 2016-07-14T13:38:07Z
removing deprecated annotations.
commit 65ef9a29e58f6747bd97b77ca08d29148bf55260
Author: Aldrin Piri <[email protected]>
Date: 2016-07-14T13:46:20Z
Migrating EventReporter to nifi-framework-api.
commit c7e50fe32cdfc29f33ef6dc27e7cbb16d9dbdc75
Author: Aldrin Piri <[email protected]>
Date: 2016-07-14T13:57:12Z
Migrating provenance search items to nifi-framework-api.
commit e0e9410f065c37eeba7828fe257dd5b7e299815f
Author: Aldrin Piri <[email protected]>
Date: 2016-07-14T14:11:56Z
Migrating web package out of nifi-api. Removing ResourceNotFoundException
from Javadoc of getEvent in ProvenanceEventRepository. No impls seem to throw
this and seems like provenance event repo should not share this web exception.
If exception is needed, would prefer to provide that from event repo that is
then wrapped by RNFE at controller level.
----
> Extract Extension API into separate module
> ------------------------------------------
>
> Key: NIFI-1896
> URL: https://issues.apache.org/jira/browse/NIFI-1896
> Project: Apache NiFi
> Issue Type: Task
> Components: Core Framework
> Reporter: Aldrin Piri
> Assignee: Aldrin Piri
> Fix For: 1.0.0
>
>
> As discussed on the mailing list, the original contents of which are below:
> {quote}
> I would like to propose a refactoring of the nifi-api for our master/1.0
> branch. In summary, a lightweight and concise view of this module allows for
> reduced footprint of the NIFI API for components and minimizes the creep of
> those items that authoring components do not need to use.
> In a broader context there is a core set of interfaces that users will
> interface with in their generation of new extensions for NiFi. Summarily,
> these components have comprised Processors, Controller Services, Reporting
> Tasks, & Prioritizers (the last of which is currently under discussion to
> potentially be removed from this forward facing status).
> What I would like to suggest is the refactoring of the nifi-api module to be
> broken down into to two components: the nifi-api and the nifi-framework-api.
> nifi-api will encompass all things developers would need to provide
> extensions tailored toward interacting with dataflow. nifi-framework-api
> would address the more internal items that are also extensible, but not
> something that is typically implemented and would consist of the remainder of
> those items not in nifi-api.
> This enables a core set of APIs that extensions can implement with a broader
> perspective of providing API compatibility between both NiFi and MiNiFi.
> This enables some nice reuse of work with the goal ultimately amounting to,
> write for NiFi, run on MiNiFi and the reverse.
> Logistically, for NiFi extension writers, at first glance, not much would
> change with their efforts. The core dependency would remain the same, but
> would be curtailed in its scope to only what is required. Framework
> components of course, would need to be updated to include a dependency on
> nifi-framework-api.
> Given that the new structure would not yet be released, and to allow MiNiFi
> to continue on its development path, a Git submodule or subtree would be
> introduced into MiNiFi and supporting documentation on how to make use of
> this for those not familiar.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
