svn commit: r1880080 [3/4] - in /nifi/site/trunk/docs/nifi-registry-docs: html/ html/images/ rest-api/
Modified: nifi/site/trunk/docs/nifi-registry-docs/html/user-guide.html URL: http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-registry-docs/html/user-guide.html?rev=1880080=1880079=1880080=diff == --- nifi/site/trunk/docs/nifi-registry-docs/html/user-guide.html (original) +++ nifi/site/trunk/docs/nifi-registry-docs/html/user-guide.html Mon Jul 20 16:49:17 2020 @@ -478,7 +478,9 @@ body.book #toc,body.book #preamble,body. Delete a Bucket Delete Multiple Buckets Edit a Bucket Name -Bucket Policies +Make a Bucket Publicly Visible +Allow Bundles in a Bucket to be Overwritten +Bucket Policies Manage Users Groups @@ -500,7 +502,7 @@ body.book #toc,body.book #preamble,body. Other Group Level Actions -Manage Bundles +Manage Bundles Upload Bundle Download Bundle @@ -831,6 +833,18 @@ It is possible to delete a flow that is +Check "Make publicly available" to allow read access to items in the bucket by unauthenticated users. This will override any specific bucket policies granting read access. + + + + + + + + + + + To quickly create multiple buckets, check "Keep this dialog open after creating bucket". @@ -915,7 +929,38 @@ To quickly create multiple buckets, chec -Bucket Policies +Make a Bucket Publicly Visible + +To allow read access to items in a bucket by unauthenticated users, select the "Make publicly visible" checkbox. + + + + + + + +This setting will override any specific policies granting read access to the bucket. + + + +Allow Bundles in a Bucket to be Overwritten + +To allow released bundles in a bucket to be overwritten, select the "Allow bundle overwrite" checkbox. + + + + + + + +Currently, the only supported bundle type is a https://nifi.apache.org/docs/nifi-docs/html/developer-guide.html#nars;>NiFi Archive (NAR). By default, buckets do not allow the re-release of released NARs. This setting explicitly allows the same version of a NAR to be uploaded to a bucket. + + +For more information on bundles, see the Manage Bundles section. + + + +Bucket Policies Bucket policies define user privileges on buckets/flows in the Registry and in NiFi. The available permissions are: @@ -1212,7 +1257,7 @@ Some users cannot have their names edite Can manage policies - Allow a user to grant all registry users read, write, and delete permission to a bucket. -Can proxy user requests - Allow a connected system (e.g., NiFi) to process requests of authorized users of that system. +Can proxy user requests - Allow a connected system (e.g., NiFi) to process requests of authorized users of that system. For example, if dev and prod NiFi clusters are connected to the same NiFi Registry instance, privileges can be set to allow the dev NiFi cluster to only update versioned flows while limiting the prod NiFi to only download flows. @@ -1411,7 +1456,7 @@ Groups cannot contain other groups. -Manage Bundles +Manage Bundles Bundles can be managed through the REST API. @@ -1517,7 +1562,7 @@ In order to upload a NAR to NiFi Registr -Last updated 2019-08-21 12:14:43 -04:00 +Last updated 2020-07-15 11:04:45 -04:00
svn commit: r1880080 [4/4] - in /nifi/site/trunk/docs/nifi-registry-docs: html/ html/images/ rest-api/
Modified: nifi/site/trunk/docs/nifi-registry-docs/rest-api/rest-api.html URL: http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-registry-docs/rest-api/rest-api.html?rev=1880080=1880079=1880080=diff == --- nifi/site/trunk/docs/nifi-registry-docs/rest-api/rest-api.html (original) +++ nifi/site/trunk/docs/nifi-registry-docs/rest-api/rest-api.html Mon Jul 20 16:49:17 2020 @@ -434,7 +434,7 @@ body.book #toc,body.book #preamble,body. Apache NiFi Registry REST API -version 0.5.0 +version 0.7.0 Table of Contents @@ -459,12 +459,13 @@ body.book #toc,body.book #preamble,body. 3.1. Access 3.1.1. Get access status -3.1.2. Create token trying all providers -3.1.3. Create token using identity provider -3.1.4. Test identity provider -3.1.5. Get identity provider usage -3.1.6. Create token using kerberos -3.1.7. Create token using basic auth +3.1.2. Performs a logout for other providers that have been issued a JWT. +3.1.3. Create token trying all providers +3.1.4. Create token using identity provider +3.1.5. Test identity provider +3.1.6. Get identity provider usage +3.1.7. Create token using kerberos +3.1.8. Create token using basic auth 3.2. Bucket Bundles @@ -633,29 +634,30 @@ body.book #toc,body.book #preamble,body. 4.43. ResourcePermissions 4.44. Restricted 4.45. Restriction -4.46. Stateful -4.47. SystemResourceConsideration -4.48. TagCount -4.49. Tenant -4.50. User -4.51. UserGroup -4.52. VersionedConnection -4.53. VersionedControllerService -4.54. VersionedFlow -4.55. VersionedFlowCoordinates -4.56. VersionedFlowDifference -4.57. VersionedFlowSnapshot -4.58. VersionedFlowSnapshotMetadata -4.59. VersionedFunnel -4.60. VersionedLabel -4.61. VersionedParameter -4.62. VersionedParameterContext -4.63. VersionedPort -4.64. VersionedProcessGroup -4.65. VersionedProcessor -4.66. VersionedPropertyDescriptor -4.67. VersionedRemoteGroupPort -4.68. VersionedRemoteProcessGroup +4.46. RevisionInfo +4.47. Stateful +4.48. SystemResourceConsideration +4.49. TagCount +4.50. Tenant +4.51. User +4.52. UserGroup +4.53. VersionedConnection +4.54. VersionedControllerService +4.55. VersionedFlow +4.56. VersionedFlowCoordinates +4.57. VersionedFlowDifference +4.58. VersionedFlowSnapshot +4.59. VersionedFlowSnapshotMetadata +4.60. VersionedFunnel +4.61. VersionedLabel +4.62. VersionedParameter +4.63. VersionedParameterContext +4.64. VersionedPort +4.65. VersionedProcessGroup +4.66. VersionedProcessor +4.67. VersionedPropertyDescriptor +4.68. VersionedRemoteGroupPort +4.69. VersionedRemoteProcessGroup @@ -671,7 +673,7 @@ body.book #toc,body.book #preamble,body. 1.1. Version information -Version : 0.5.0 +Version : 0.7.0 @@ -909,20 +911,108 @@ body.book #toc,body.book #preamble,body. -3.1.2. Create token trying all providers +3.1.2. Performs a logout for other providers that have been issued a JWT. -POST /access/token +DELETE /access/logout Description + + + + +Note + + +This endpoint is subject to change as NiFi Registry and its REST API evolve. + + + + + + +Responses + + + + + + + + +HTTP Code +Description +Schema + + + + +200 +User was logged out successfully. +No Content + + +401 +Authentication token provided was empty or not in the correct JWT format. +No Content + + +500 +Client failed to log out. +No Content + + + + + +Consumes + + + +/ + + + + + +Produces + + + +/ + + + + + +Example HTTP request + +Request path + + +/access/logout + + + + + + +3.1.3. Create token trying all providers + + +POST /access/token + + + +Description Creates a token for accessing the REST API via auto-detected method of verifying client identity claim credentials. The token returned is formatted as a JSON Web Token (JWT). The token is base64 encoded and comprised of three parts. The header, the body, and the signature. The expiration of the token is a contained within the body. The token can be used in the Authorization header in the format 'Authorization: Bearer token'. -Responses +Responses @@ -966,7 +1056,7 @@ body.book #toc,body.book #preamble,body. -Consumes +Consumes @@ -976,7 +1066,7 @@ body.book #toc,body.book #preamble,body. -Produces +Produces @@ -986,9 +1076,9 @@ body.book #toc,body.book #preamble,body. -Example HTTP request +Example HTTP request -Request path +Request path /access/token @@ -1009,20 +1099,20 @@ body.book #toc,body.book #preamble,body. -3.1.3. Create token using identity provider +3.1.4. Create token using identity provider POST /access/token/identity-provider -Description +Description Creates a token for accessing the REST API via a custom identity provider. The user credentials must be passed in a format understood by the custom identity provider, e.g., a third-party auth token in an HTTP header. The exact format of the user credentials expected by the custom
svn commit: r1880080 [1/4] - in /nifi/site/trunk/docs/nifi-registry-docs: html/ html/images/ rest-api/
Author: bbende Date: Mon Jul 20 16:49:17 2020 New Revision: 1880080 URL: http://svn.apache.org/viewvc?rev=1880080=rev Log: Added latest NiFi Registry 0.7.0 docs Added: nifi/site/trunk/docs/nifi-registry-docs/html/images/bucket_nav_allow_bundle_overwrite.png (with props) nifi/site/trunk/docs/nifi-registry-docs/html/images/bucket_nav_make_public.png (with props) Modified: nifi/site/trunk/docs/nifi-registry-docs/html/administration-guide.html nifi/site/trunk/docs/nifi-registry-docs/html/getting-started.html nifi/site/trunk/docs/nifi-registry-docs/html/images/bucket_nav_name_edit.png nifi/site/trunk/docs/nifi-registry-docs/html/images/delete_bucket_policy.png nifi/site/trunk/docs/nifi-registry-docs/html/images/group_added.png nifi/site/trunk/docs/nifi-registry-docs/html/images/new_bucket_dialog.png nifi/site/trunk/docs/nifi-registry-docs/html/images/new_bucket_policy_added.png nifi/site/trunk/docs/nifi-registry-docs/html/images/new_bucket_policy_create.png nifi/site/trunk/docs/nifi-registry-docs/html/images/remove_group_from_user.png nifi/site/trunk/docs/nifi-registry-docs/html/images/remove_user_from_group.png nifi/site/trunk/docs/nifi-registry-docs/html/images/select_users_new_group_added.png nifi/site/trunk/docs/nifi-registry-docs/html/images/test_bucket_dialog.png nifi/site/trunk/docs/nifi-registry-docs/html/images/user_nav_add_to_group.png nifi/site/trunk/docs/nifi-registry-docs/html/images/user_nav_name_edit.png nifi/site/trunk/docs/nifi-registry-docs/html/images/user_special_privileges.png nifi/site/trunk/docs/nifi-registry-docs/html/rest-api.html nifi/site/trunk/docs/nifi-registry-docs/html/user-guide.html nifi/site/trunk/docs/nifi-registry-docs/rest-api/rest-api.html Modified: nifi/site/trunk/docs/nifi-registry-docs/html/administration-guide.html URL: http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-registry-docs/html/administration-guide.html?rev=1880080=1880079=1880080=diff == --- nifi/site/trunk/docs/nifi-registry-docs/html/administration-guide.html (original) +++ nifi/site/trunk/docs/nifi-registry-docs/html/administration-guide.html Mon Jul 20 16:49:17 2020 @@ -457,6 +457,7 @@ body.book #toc,body.book #preamble,body. System Requirements How to install and start NiFi Registry +Recommended Antivirus Exclusions Security Configuration User Authentication @@ -678,6 +679,42 @@ When running Registry with only a JRE yo +Recommended Antivirus Exclusions + + +Antivirus software can take a long time to scan large directories and the numerous files within them. Additionally, if the antivirus software locks files or directories during a scan, those resources are unavailable to NiFi Registry processes, causing latency or unavailability of these resources in a NiFi Registry instance. To prevent these performance and reliability issues from occurring, it is highly recommended to configure your antivirus software to skip scans on the following NiFi Registry directories: + + + + +database + + +extension_bundles + + +flow_storage + + +logs + + + + + + + + + + +The directories listed are generated at startup for a default NiFi Registry installation. Consider your configuration when determining directories to exclude during antivirus scans. For example, if an external database has been setup or if a different flow storage directory is specified in your configuration. + + + + + + + Security Configuration @@ -1354,8 +1391,8 @@ This will sync users and groups from a d -NiFi Identity -The identity of a NiFi instance/node that will be accessing this registry. Each NiFi Identity will be granted permission to proxy user requests, as well as read any bucket to perform synchronization status checks. +NiFi Group Name +The name of the group, whose members are NiFi instance/node identities, that will be accessing this registry. The members of this group will be granted permission to proxy user requests, as well as read any bucket to perform synchronization checks. @@ -1371,6 +1408,10 @@ This will sync users and groups from a d Initial Admin Identity The identity of an initial admin user that will be granted access to the UI and given the ability to create additional users, groups, and policies. For example, a certificate DN, LDAP identity, or Kerberos principal. + +NiFi Identity +The identity of a NiFi instance/node that will be accessing this registry. Each NiFi Identity will be granted permission to proxy user requests, as well as read any bucket to perform synchronization status checks. + @@ -2610,7 +2651,7 @@ providing 2 total locations, including < The metadata database maintains the knowledge of which buckets exist, which versioned items belong to which buckets, as well as the version history for each item. -Currently, NiFi Registry supports using H2, Postgres
svn commit: r1880080 [2/4] - in /nifi/site/trunk/docs/nifi-registry-docs: html/ html/images/ rest-api/
Modified: nifi/site/trunk/docs/nifi-registry-docs/html/rest-api.html URL: http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-registry-docs/html/rest-api.html?rev=1880080=1880079=1880080=diff == --- nifi/site/trunk/docs/nifi-registry-docs/html/rest-api.html (original) +++ nifi/site/trunk/docs/nifi-registry-docs/html/rest-api.html Mon Jul 20 16:49:17 2020 @@ -450,7 +450,7 @@ body.book #toc,body.book #preamble,body. Apache NiFi Registry REST API -version 0.5.0 +version 0.7.0 Table of Contents @@ -475,12 +475,13 @@ body.book #toc,body.book #preamble,body. 3.1. Access 3.1.1. Get access status -3.1.2. Create token trying all providers -3.1.3. Create token using identity provider -3.1.4. Test identity provider -3.1.5. Get identity provider usage -3.1.6. Create token using kerberos -3.1.7. Create token using basic auth +3.1.2. Performs a logout for other providers that have been issued a JWT. +3.1.3. Create token trying all providers +3.1.4. Create token using identity provider +3.1.5. Test identity provider +3.1.6. Get identity provider usage +3.1.7. Create token using kerberos +3.1.8. Create token using basic auth 3.2. Bucket Bundles @@ -649,29 +650,30 @@ body.book #toc,body.book #preamble,body. 4.43. ResourcePermissions 4.44. Restricted 4.45. Restriction -4.46. Stateful -4.47. SystemResourceConsideration -4.48. TagCount -4.49. Tenant -4.50. User -4.51. UserGroup -4.52. VersionedConnection -4.53. VersionedControllerService -4.54. VersionedFlow -4.55. VersionedFlowCoordinates -4.56. VersionedFlowDifference -4.57. VersionedFlowSnapshot -4.58. VersionedFlowSnapshotMetadata -4.59. VersionedFunnel -4.60. VersionedLabel -4.61. VersionedParameter -4.62. VersionedParameterContext -4.63. VersionedPort -4.64. VersionedProcessGroup -4.65. VersionedProcessor -4.66. VersionedPropertyDescriptor -4.67. VersionedRemoteGroupPort -4.68. VersionedRemoteProcessGroup +4.46. RevisionInfo +4.47. Stateful +4.48. SystemResourceConsideration +4.49. TagCount +4.50. Tenant +4.51. User +4.52. UserGroup +4.53. VersionedConnection +4.54. VersionedControllerService +4.55. VersionedFlow +4.56. VersionedFlowCoordinates +4.57. VersionedFlowDifference +4.58. VersionedFlowSnapshot +4.59. VersionedFlowSnapshotMetadata +4.60. VersionedFunnel +4.61. VersionedLabel +4.62. VersionedParameter +4.63. VersionedParameterContext +4.64. VersionedPort +4.65. VersionedProcessGroup +4.66. VersionedProcessor +4.67. VersionedPropertyDescriptor +4.68. VersionedRemoteGroupPort +4.69. VersionedRemoteProcessGroup @@ -687,7 +689,7 @@ body.book #toc,body.book #preamble,body. 1.1. Version information -Version : 0.5.0 +Version : 0.7.0 @@ -925,20 +927,108 @@ body.book #toc,body.book #preamble,body. -3.1.2. Create token trying all providers +3.1.2. Performs a logout for other providers that have been issued a JWT. -POST /access/token +DELETE /access/logout Description + + + + +Note + + +This endpoint is subject to change as NiFi Registry and its REST API evolve. + + + + + + +Responses + + + + + + + + +HTTP Code +Description +Schema + + + + +200 +User was logged out successfully. +No Content + + +401 +Authentication token provided was empty or not in the correct JWT format. +No Content + + +500 +Client failed to log out. +No Content + + + + + +Consumes + + + +/ + + + + + +Produces + + + +/ + + + + + +Example HTTP request + +Request path + + +/access/logout + + + + + + +3.1.3. Create token trying all providers + + +POST /access/token + + + +Description Creates a token for accessing the REST API via auto-detected method of verifying client identity claim credentials. The token returned is formatted as a JSON Web Token (JWT). The token is base64 encoded and comprised of three parts. The header, the body, and the signature. The expiration of the token is a contained within the body. The token can be used in the Authorization header in the format 'Authorization: Bearer token'. -Responses +Responses @@ -982,7 +1072,7 @@ body.book #toc,body.book #preamble,body. -Consumes +Consumes @@ -992,7 +1082,7 @@ body.book #toc,body.book #preamble,body. -Produces +Produces @@ -1002,9 +1092,9 @@ body.book #toc,body.book #preamble,body. -Example HTTP request +Example HTTP request -Request path +Request path /access/token @@ -1025,20 +1115,20 @@ body.book #toc,body.book #preamble,body. -3.1.3. Create token using identity provider +3.1.4. Create token using identity provider POST /access/token/identity-provider -Description +Description Creates a token for accessing the REST API via a custom identity provider. The user credentials must be passed in a format understood by the custom identity provider, e.g., a third-party auth token in an HTTP header. The exact format of the user credentials expected by the custom identity provider
svn commit: r40576 - /release/nifi/nifi-registry/nifi-registry-0.5.0/
Author: bbende Date: Mon Jul 20 15:11:29 2020 New Revision: 40576 Log: Deleting NiFi Registy 0.5.0 now that 0.7.0 and 0.6.0 are on the website Removed: release/nifi/nifi-registry/nifi-registry-0.5.0/
[nifi-site] branch main updated: NIFIREG-404 Updating site for NiFi Registry 0.7.0 release
This is an automated email from the ASF dual-hosted git repository. bbende pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/nifi-site.git The following commit(s) were added to refs/heads/main by this push: new 1de9d52 NIFIREG-404 Updating site for NiFi Registry 0.7.0 release 1de9d52 is described below commit 1de9d5281e96c3e9c2f36a487350a6405507c0ea Author: Bryan Bende AuthorDate: Mon Jul 20 11:03:15 2020 -0400 NIFIREG-404 Updating site for NiFi Registry 0.7.0 release --- src/pages/html/registry.hbs | 58 ++--- 1 file changed, 29 insertions(+), 29 deletions(-) diff --git a/src/pages/html/registry.hbs b/src/pages/html/registry.hbs index c376898..a0b0fd1 100644 --- a/src/pages/html/registry.hbs +++ b/src/pages/html/registry.hbs @@ -66,6 +66,35 @@ title: Apache NiFi - Registry + 0.7.0 + + + Sources + + https://www.apache.org/dyn/closer.lua?path=/nifi/nifi-registry/nifi-registry-0.7.0/nifi-registry-0.7.0-source-release.zip;>nifi-registry-0.7.0-source-release.zip ( + https://downloads.apache.org/nifi/nifi-registry/nifi-registry-0.7.0/nifi-registry-0.7.0-source-release.zip.asc;>asc, + https://downloads.apache.org/nifi/nifi-registry/nifi-registry-0.7.0/nifi-registry-0.7.0-source-release.zip.sha256;>sha256, + https://downloads.apache.org/nifi/nifi-registry/nifi-registry-0.7.0/nifi-registry-0.7.0-source-release.zip.sha512;>sha512 ) + + + + Binaries + + https://www.apache.org/dyn/closer.lua?path=/nifi/nifi-registry/nifi-registry-0.7.0/nifi-registry-0.7.0-bin.tar.gz;>nifi-registry-0.7.0-bin.tar.gz ( + https://downloads.apache.org/nifi/nifi-registry/nifi-registry-0.7.0/nifi-registry-0.7.0-bin.tar.gz.asc;>asc, + https://downloads.apache.org/nifi/nifi-registry/nifi-registry-0.7.0/nifi-registry-0.7.0-bin.tar.gz.sha256;>sha256, + https://downloads.apache.org/nifi/nifi-registry/nifi-registry-0.7.0/nifi-registry-0.7.0-bin.tar.gz.sha512;>sha512 ) + + https://www.apache.org/dyn/closer.lua?path=/nifi/nifi-registry/nifi-registry-0.7.0/nifi-registry-0.7.0-bin.zip;>nifi-registry-0.7.0-bin.zip ( + https://downloads.apache.org/nifi/nifi-registry/nifi-registry-0.7.0/nifi-registry-0.7.0-bin.zip.asc;>asc, + https://downloads.apache.org/nifi/nifi-registry/nifi-registry-0.7.0/nifi-registry-0.7.0-bin.zip.sha256;>sha256, + https://downloads.apache.org/nifi/nifi-registry/nifi-registry-0.7.0/nifi-registry-0.7.0-bin.zip.sha512;>sha512 ) + + + https://cwiki.apache.org/confluence/display/NIFIREG/Release+Notes#ReleaseNotes-NiFiRegistry0.7.0;>Release Notes + + + 0.6.0 @@ -94,35 +123,6 @@ title: Apache NiFi - Registry https://cwiki.apache.org/confluence/display/NIFIREG/Release+Notes#ReleaseNotes-NiFiRegistry0.6.0;>Release Notes - -0.5.0 - - -Sources - -https://archive.apache.org/dist/nifi/nifi-registry/nifi-registry-0.5.0/nifi-registry-0.5.0-source-release.zip;>nifi-registry-0.5.0-source-release.zip ( - https://archive.apache.org/dist/nifi/nifi-registry/nifi-registry-0.5.0/nifi-registry-0.5.0-source-release.zip.asc;>asc, - https://archive.apache.org/dist/nifi/nifi-registry/nifi-registry-0.5.0/nifi-registry-0.5.0-source-release.zip.sha256;>sha256, - https://archive.apache.org/dist/nifi/nifi-registry/nifi-registry-0.5.0/nifi-registry-0.5.0-source-release.zip.sha512;>sha512 ) - - - -Binaries - -https://archive.apache.org/dist/nifi/nifi-registry/nifi-registry-0.5.0/nifi-registry-0.5.0-bin.tar.gz;>nifi-registry-0.5.0-bin.tar.gz ( -
svn commit: r1880078 - /nifi/site/trunk/registry.html
Author: bbende Date: Mon Jul 20 15:02:53 2020 New Revision: 1880078 URL: http://svn.apache.org/viewvc?rev=1880078=rev Log: NIFIREG-404 Updating site for NiFi Registry 0.7.0 release Modified: nifi/site/trunk/registry.html Modified: nifi/site/trunk/registry.html URL: http://svn.apache.org/viewvc/nifi/site/trunk/registry.html?rev=1880078=1880077=1880078=diff == --- nifi/site/trunk/registry.html (original) +++ nifi/site/trunk/registry.html Mon Jul 20 15:02:53 2020 @@ -171,6 +171,35 @@ + 0.7.0 + + + Sources + + https://www.apache.org/dyn/closer.lua?path=/nifi/nifi-registry/nifi-registry-0.7.0/nifi-registry-0.7.0-source-release.zip;>nifi-registry-0.7.0-source-release.zip ( + https://downloads.apache.org/nifi/nifi-registry/nifi-registry-0.7.0/nifi-registry-0.7.0-source-release.zip.asc;>asc, + https://downloads.apache.org/nifi/nifi-registry/nifi-registry-0.7.0/nifi-registry-0.7.0-source-release.zip.sha256;>sha256, + https://downloads.apache.org/nifi/nifi-registry/nifi-registry-0.7.0/nifi-registry-0.7.0-source-release.zip.sha512;>sha512 ) + + + + Binaries + + https://www.apache.org/dyn/closer.lua?path=/nifi/nifi-registry/nifi-registry-0.7.0/nifi-registry-0.7.0-bin.tar.gz;>nifi-registry-0.7.0-bin.tar.gz ( + https://downloads.apache.org/nifi/nifi-registry/nifi-registry-0.7.0/nifi-registry-0.7.0-bin.tar.gz.asc;>asc, + https://downloads.apache.org/nifi/nifi-registry/nifi-registry-0.7.0/nifi-registry-0.7.0-bin.tar.gz.sha256;>sha256, + https://downloads.apache.org/nifi/nifi-registry/nifi-registry-0.7.0/nifi-registry-0.7.0-bin.tar.gz.sha512;>sha512 ) + + https://www.apache.org/dyn/closer.lua?path=/nifi/nifi-registry/nifi-registry-0.7.0/nifi-registry-0.7.0-bin.zip;>nifi-registry-0.7.0-bin.zip ( + https://downloads.apache.org/nifi/nifi-registry/nifi-registry-0.7.0/nifi-registry-0.7.0-bin.zip.asc;>asc, + https://downloads.apache.org/nifi/nifi-registry/nifi-registry-0.7.0/nifi-registry-0.7.0-bin.zip.sha256;>sha256, + https://downloads.apache.org/nifi/nifi-registry/nifi-registry-0.7.0/nifi-registry-0.7.0-bin.zip.sha512;>sha512 ) + + + https://cwiki.apache.org/confluence/display/NIFIREG/Release+Notes#ReleaseNotes-NiFiRegistry0.7.0;>Release Notes + + + 0.6.0 @@ -199,35 +228,6 @@ https://cwiki.apache.org/confluence/display/NIFIREG/Release+Notes#ReleaseNotes-NiFiRegistry0.6.0;>Release Notes - -0.5.0 - - -Sources - -https://archive.apache.org/dist/nifi/nifi-registry/nifi-registry-0.5.0/nifi-registry-0.5.0-source-release.zip;>nifi-registry-0.5.0-source-release.zip ( - https://archive.apache.org/dist/nifi/nifi-registry/nifi-registry-0.5.0/nifi-registry-0.5.0-source-release.zip.asc;>asc, - https://archive.apache.org/dist/nifi/nifi-registry/nifi-registry-0.5.0/nifi-registry-0.5.0-source-release.zip.sha256;>sha256, - https://archive.apache.org/dist/nifi/nifi-registry/nifi-registry-0.5.0/nifi-registry-0.5.0-source-release.zip.sha512;>sha512 ) - - - -Binaries - -https://archive.apache.org/dist/nifi/nifi-registry/nifi-registry-0.5.0/nifi-registry-0.5.0-bin.tar.gz;>nifi-registry-0.5.0-bin.tar.gz ( - https://archive.apache.org/dist/nifi/nifi-registry/nifi-registry-0.5.0/nifi-registry-0.5.0-bin.tar.gz.asc;>asc, - https://archive.apache.org/dist/nifi/nifi-registry/nifi-registry-0.5.0/nifi-registry-0.5.0-bin.tar.gz.sha256;>sha256, - https://archive.apache.org/dist/nifi/nifi-registry/nifi-registry-0.5.0/nifi-registry-0.5.0-bin.tar.gz.sha512;>sha512 ) - -
[jira] [Assigned] (MINIFI-498) C2 Server Error - Too Many Open Files
[ https://issues.apache.org/jira/browse/MINIFI-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri reassigned MINIFI-498: -- Assignee: Corinne Jukes (was: Aldrin Piri) > C2 Server Error - Too Many Open Files > - > > Key: MINIFI-498 > URL: https://issues.apache.org/jira/browse/MINIFI-498 > Project: Apache NiFi MiNiFi > Issue Type: Bug > Components: Command and Control >Affects Versions: 0.5.0 > Environment: OS: Amazon Linux 2 (4.14.77-86.82.amzn2.x86_64) > Java: 1.8.0_191-b12 > ulimits: > core file size (blocks, -c) 0 > data seg size (kbytes, -d) unlimited > scheduling priority (-e) 0 > file size (blocks, -f) unlimited > pending signals (-i) 31769 > max locked memory (kbytes, -l) 64 > max memory size (kbytes, -m) unlimited > open files (-n) 5 > pipe size (512 bytes, -p) 8 > POSIX message queues (bytes, -q) 819200 > real-time priority (-r) 0 > stack size (kbytes, -s) 8192 > cpu time (seconds, -t) unlimited > max user processes (-u) 1 > virtual memory (kbytes, -v) unlimited > file locks (-x) unlimited >Reporter: Michael >Assignee: Corinne Jukes >Priority: Blocker > Fix For: 0.6.0 > > > After several days of running C2 the errors are being logged about having > "Too Many Open Files". At this point, C2 is not responsive to clients trying > to check for new configurations. > _33e79e: Too many open files_ > _Apr 29 14:33:22 ec2.internal c2.sh[20851]: Caused by: > java.nio.file.FileSystemException: > /opt/minifi-c2/./files/5233730D-AC58-4853-9C0E-273D0E_ > > Running _lsof_ shows an increasingly larger number of open files. Our MiNiFi > instances are checking for new files every few seconds (probably too short), > but it seems like maybe some file handles are not being cleaned up. > Restarting C2 clears up this condition and C2 becomes responsive again. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MINIFI-498) C2 Server Error - Too Many Open Files
[ https://issues.apache.org/jira/browse/MINIFI-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17161297#comment-17161297 ] Aldrin Piri commented on MINIFI-498: [~Jukes] I was not able to get it easily reproduced at the time. I've added you to the contributors and will make you the assignee on this ticket. Thanks for digging in! > C2 Server Error - Too Many Open Files > - > > Key: MINIFI-498 > URL: https://issues.apache.org/jira/browse/MINIFI-498 > Project: Apache NiFi MiNiFi > Issue Type: Bug > Components: Command and Control >Affects Versions: 0.5.0 > Environment: OS: Amazon Linux 2 (4.14.77-86.82.amzn2.x86_64) > Java: 1.8.0_191-b12 > ulimits: > core file size (blocks, -c) 0 > data seg size (kbytes, -d) unlimited > scheduling priority (-e) 0 > file size (blocks, -f) unlimited > pending signals (-i) 31769 > max locked memory (kbytes, -l) 64 > max memory size (kbytes, -m) unlimited > open files (-n) 5 > pipe size (512 bytes, -p) 8 > POSIX message queues (bytes, -q) 819200 > real-time priority (-r) 0 > stack size (kbytes, -s) 8192 > cpu time (seconds, -t) unlimited > max user processes (-u) 1 > virtual memory (kbytes, -v) unlimited > file locks (-x) unlimited >Reporter: Michael >Assignee: Aldrin Piri >Priority: Blocker > Fix For: 0.6.0 > > > After several days of running C2 the errors are being logged about having > "Too Many Open Files". At this point, C2 is not responsive to clients trying > to check for new configurations. > _33e79e: Too many open files_ > _Apr 29 14:33:22 ec2.internal c2.sh[20851]: Caused by: > java.nio.file.FileSystemException: > /opt/minifi-c2/./files/5233730D-AC58-4853-9C0E-273D0E_ > > Running _lsof_ shows an increasingly larger number of open files. Our MiNiFi > instances are checking for new files every few seconds (probably too short), > but it seems like maybe some file handles are not being cleaned up. > Restarting C2 clears up this condition and C2 becomes responsive again. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[nifi-registry] branch main updated: NIFIREG-404 Updating docker files for next release
This is an automated email from the ASF dual-hosted git repository.
bbende pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/nifi-registry.git
The following commit(s) were added to refs/heads/main by this push:
new 2243782 NIFIREG-404 Updating docker files for next release
2243782 is described below
commit 22437820f4a2e964974d77101e60a684b33a9d6a
Author: Bryan Bende
AuthorDate: Mon Jul 20 09:35:12 2020 -0400
NIFIREG-404 Updating docker files for next release
---
nifi-registry-core/nifi-registry-docker/dockerhub/DockerImage.txt | 2 +-
nifi-registry-core/nifi-registry-docker/dockerhub/Dockerfile | 2 +-
nifi-registry-docker-maven/dockermaven/Dockerfile | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/nifi-registry-core/nifi-registry-docker/dockerhub/DockerImage.txt
b/nifi-registry-core/nifi-registry-docker/dockerhub/DockerImage.txt
index 6af15fc..3f8a258 100644
--- a/nifi-registry-core/nifi-registry-docker/dockerhub/DockerImage.txt
+++ b/nifi-registry-core/nifi-registry-docker/dockerhub/DockerImage.txt
@@ -13,4 +13,4 @@
# See the License for the specific language governing permissions and
# limitations under the License.
-apache/nifi-registry:0.6.0
+apache/nifi-registry:0.8.0
diff --git a/nifi-registry-core/nifi-registry-docker/dockerhub/Dockerfile
b/nifi-registry-core/nifi-registry-docker/dockerhub/Dockerfile
index 623c613..d0cd3ab 100644
--- a/nifi-registry-core/nifi-registry-docker/dockerhub/Dockerfile
+++ b/nifi-registry-core/nifi-registry-docker/dockerhub/Dockerfile
@@ -22,7 +22,7 @@ LABEL site="https://nifi.apache.org;
ARG UID=1000
ARG GID=1000
-ARG NIFI_REGISTRY_VERSION=0.7.0
+ARG NIFI_REGISTRY_VERSION=0.8.0
ARG MIRROR=https://archive.apache.org/dist
ENV NIFI_REGISTRY_BASE_DIR /opt/nifi-registry
diff --git a/nifi-registry-docker-maven/dockermaven/Dockerfile
b/nifi-registry-docker-maven/dockermaven/Dockerfile
index 945cb80..ba3e9b0 100644
--- a/nifi-registry-docker-maven/dockermaven/Dockerfile
+++ b/nifi-registry-docker-maven/dockermaven/Dockerfile
@@ -20,7 +20,7 @@ FROM openjdk:8-jre AS artifactbase
LABEL maintainer="Apache NiFi "
ARG NIFI_REGISTRY_BINARY
-ARG NIFI_REGISTRY_VERSION=1.0.0
+ARG NIFI_REGISTRY_VERSION=0.8.0
ENV NIFI_REGISTRY_BASE_DIR /opt/nifi-registry
ENV NIFI_REGISTRY_HOME ${NIFI_REGISTRY_BASE_DIR}/nifi-registry-current
[nifi-registry] branch main updated (9b93397 -> 016479e)
This is an automated email from the ASF dual-hosted git repository. bbende pushed a change to branch main in repository https://gitbox.apache.org/repos/asf/nifi-registry.git. from 9b93397 NIFIREG-394 call onConfigured with the same classloader - checkstyle violation - call onConfigured with the same classloader add c8f2603 NIFIREG-404-RC1 prepare release nifi-registry-0.7.0-RC1 add 42cdfed NIFIREG-404-RC1 prepare for next development iteration new 016479e Merge branch 'NIFIREG-404-RC1' into main The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: nifi-registry-assembly/pom.xml | 10 +- nifi-registry-core/nifi-registry-bootstrap/pom.xml | 4 ++-- .../nifi-registry-bundle-utils/pom.xml | 4 ++-- nifi-registry-core/nifi-registry-client/pom.xml| 6 +++--- .../nifi-registry-data-model/pom.xml | 4 ++-- nifi-registry-core/nifi-registry-docker/pom.xml| 2 +- nifi-registry-core/nifi-registry-docs/pom.xml | 4 ++-- nifi-registry-core/nifi-registry-flow-diff/pom.xml | 4 ++-- nifi-registry-core/nifi-registry-framework/pom.xml | 18 +- nifi-registry-core/nifi-registry-jetty/pom.xml | 4 ++-- .../nifi-registry-properties/pom.xml | 2 +- .../nifi-registry-provider-api/pom.xml | 2 +- nifi-registry-core/nifi-registry-resources/pom.xml | 2 +- .../nifi-registry-revision-api/pom.xml | 2 +- .../nifi-registry-revision-common/pom.xml | 4 ++-- .../nifi-registry-revision-entity-model/pom.xml| 2 +- .../nifi-registry-revision-entity-service/pom.xml | 6 +++--- .../nifi-registry-revision-spring-jdbc/pom.xml | 6 +++--- nifi-registry-core/nifi-registry-revision/pom.xml | 2 +- nifi-registry-core/nifi-registry-runtime/pom.xml | 8 .../nifi-registry-security-api/pom.xml | 2 +- .../nifi-registry-security-utils/pom.xml | 2 +- nifi-registry-core/nifi-registry-test/pom.xml | 2 +- nifi-registry-core/nifi-registry-utils/pom.xml | 2 +- nifi-registry-core/nifi-registry-web-api/pom.xml | 22 +++--- nifi-registry-core/nifi-registry-web-docs/pom.xml | 4 ++-- nifi-registry-core/nifi-registry-web-ui/pom.xml| 4 ++-- nifi-registry-core/pom.xml | 4 ++-- nifi-registry-docker-maven/dockermaven/pom.xml | 4 ++-- nifi-registry-docker-maven/pom.xml | 4 ++-- .../nifi-registry-aws-assembly/pom.xml | 4 ++-- .../nifi-registry-aws-extensions/pom.xml | 2 +- nifi-registry-extensions/nifi-registry-aws/pom.xml | 2 +- .../nifi-registry-ranger-assembly/pom.xml | 4 ++-- .../nifi-registry-ranger-jersey-bundle/pom.xml | 2 +- .../nifi-registry-ranger-plugin/pom.xml| 10 +- .../nifi-registry-ranger/pom.xml | 2 +- nifi-registry-extensions/pom.xml | 2 +- .../nifi-registry-toolkit-assembly/pom.xml | 4 ++-- .../nifi-registry-toolkit-persistence/pom.xml | 10 +- nifi-registry-toolkit/pom.xml | 2 +- pom.xml| 18 +- 42 files changed, 104 insertions(+), 104 deletions(-)
[nifi-registry] 01/01: Merge branch 'NIFIREG-404-RC1' into main
This is an automated email from the ASF dual-hosted git repository. bbende pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/nifi-registry.git commit 016479e9207f2ea09ac3ad4a100eb78f328409bc Merge: 9b93397 42cdfed Author: Bryan Bende AuthorDate: Mon Jul 20 09:30:30 2020 -0400 Merge branch 'NIFIREG-404-RC1' into main nifi-registry-assembly/pom.xml | 10 +- nifi-registry-core/nifi-registry-bootstrap/pom.xml | 4 ++-- .../nifi-registry-bundle-utils/pom.xml | 4 ++-- nifi-registry-core/nifi-registry-client/pom.xml| 6 +++--- .../nifi-registry-data-model/pom.xml | 4 ++-- nifi-registry-core/nifi-registry-docker/pom.xml| 2 +- nifi-registry-core/nifi-registry-docs/pom.xml | 4 ++-- nifi-registry-core/nifi-registry-flow-diff/pom.xml | 4 ++-- nifi-registry-core/nifi-registry-framework/pom.xml | 18 +- nifi-registry-core/nifi-registry-jetty/pom.xml | 4 ++-- .../nifi-registry-properties/pom.xml | 2 +- .../nifi-registry-provider-api/pom.xml | 2 +- nifi-registry-core/nifi-registry-resources/pom.xml | 2 +- .../nifi-registry-revision-api/pom.xml | 2 +- .../nifi-registry-revision-common/pom.xml | 4 ++-- .../nifi-registry-revision-entity-model/pom.xml| 2 +- .../nifi-registry-revision-entity-service/pom.xml | 6 +++--- .../nifi-registry-revision-spring-jdbc/pom.xml | 6 +++--- nifi-registry-core/nifi-registry-revision/pom.xml | 2 +- nifi-registry-core/nifi-registry-runtime/pom.xml | 8 .../nifi-registry-security-api/pom.xml | 2 +- .../nifi-registry-security-utils/pom.xml | 2 +- nifi-registry-core/nifi-registry-test/pom.xml | 2 +- nifi-registry-core/nifi-registry-utils/pom.xml | 2 +- nifi-registry-core/nifi-registry-web-api/pom.xml | 22 +++--- nifi-registry-core/nifi-registry-web-docs/pom.xml | 4 ++-- nifi-registry-core/nifi-registry-web-ui/pom.xml| 4 ++-- nifi-registry-core/pom.xml | 4 ++-- nifi-registry-docker-maven/dockermaven/pom.xml | 4 ++-- nifi-registry-docker-maven/pom.xml | 4 ++-- .../nifi-registry-aws-assembly/pom.xml | 4 ++-- .../nifi-registry-aws-extensions/pom.xml | 2 +- nifi-registry-extensions/nifi-registry-aws/pom.xml | 2 +- .../nifi-registry-ranger-assembly/pom.xml | 4 ++-- .../nifi-registry-ranger-jersey-bundle/pom.xml | 2 +- .../nifi-registry-ranger-plugin/pom.xml| 10 +- .../nifi-registry-ranger/pom.xml | 2 +- nifi-registry-extensions/pom.xml | 2 +- .../nifi-registry-toolkit-assembly/pom.xml | 4 ++-- .../nifi-registry-toolkit-persistence/pom.xml | 10 +- nifi-registry-toolkit/pom.xml | 2 +- pom.xml| 18 +- 42 files changed, 104 insertions(+), 104 deletions(-)
svn commit: r40575 - /dev/nifi/nifi-registry/nifi-registry-0.7.0/ /release/nifi/nifi-registry/nifi-registry-0.7.0/
Author: bbende Date: Mon Jul 20 13:15:53 2020 New Revision: 40575 Log: NIFIREG-404 Added: release/nifi/nifi-registry/nifi-registry-0.7.0/ - copied from r40574, dev/nifi/nifi-registry/nifi-registry-0.7.0/ Removed: dev/nifi/nifi-registry/nifi-registry-0.7.0/
[nifi-minifi-cpp] branch main updated: MINIFICPP-1297 - TestSuite called "Tests" should have a more talkative name
This is an automated email from the ASF dual-hosted git repository.
aboda pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/nifi-minifi-cpp.git
The following commit(s) were added to refs/heads/main by this push:
new 13403fb MINIFICPP-1297 - TestSuite called "Tests" should have a more
talkative name
13403fb is described below
commit 13403fb5a920c451081fcbc3050249d0ba0a462b
Author: Arpad Boda
AuthorDate: Fri Jul 17 09:07:20 2020 +0200
MINIFICPP-1297 - TestSuite called "Tests" should have a more talkative name
Signed-off-by: Arpad Boda
This closes #841
Approved by multiple contributors on GH
---
libminifi/test/unit/Tests.cpp | 25 -
libminifi/test/unit/TimeUtilTests.cpp | 4
2 files changed, 4 insertions(+), 25 deletions(-)
diff --git a/libminifi/test/unit/Tests.cpp b/libminifi/test/unit/Tests.cpp
deleted file mode 100644
index 705665d..000
--- a/libminifi/test/unit/Tests.cpp
+++ /dev/null
@@ -1,25 +0,0 @@
-/**
- *
- * Licensed to the Apache Software Foundation (ASF) under one or more
- * contributor license agreements. See the NOTICE file distributed with
- * this work for additional information regarding copyright ownership.
- * The ASF licenses this file to You under the Apache License, Version 2.0
- * (the "License"); you may not use this file except in compliance with
- * the License. You may obtain a copy of the License at
- *
- * http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
- * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- * See the License for the specific language governing permissions and
- * limitations under the License.
- */
-
-
-#include "utils/TimeUtil.h"
-#include "../TestBase.h"
-
-TEST_CASE("Test time conversion", "[testtimeconversion]") {
- REQUIRE("2017-02-16 20:14:56.196" == getTimeStr(1487276096196, true));
-}
diff --git a/libminifi/test/unit/TimeUtilTests.cpp
b/libminifi/test/unit/TimeUtilTests.cpp
index 94832db..d52535e 100644
--- a/libminifi/test/unit/TimeUtilTests.cpp
+++ b/libminifi/test/unit/TimeUtilTests.cpp
@@ -85,3 +85,7 @@ TEST_CASE("parseDateTimeStr() works correctly",
"[parseDateTimeStr]") {
REQUIRE(parseDateTimeStr("2024-01-30T23:01:15Z") == 1706655675);
REQUIRE(parseDateTimeStr("2087-07-31T01:33:50Z") == 3710453630);
}
+
+TEST_CASE("Test time conversion", "[testtimeconversion]") {
+ REQUIRE("2017-02-16 20:14:56.196" == getTimeStr(1487276096196, true));
+}
[nifi-maven] branch main updated: NIFI-7415: Add .asf.yaml to configure GitHub integrations
This is an automated email from the ASF dual-hosted git repository. pvillard pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/nifi-maven.git The following commit(s) were added to refs/heads/main by this push: new bfbcd40 NIFI-7415: Add .asf.yaml to configure GitHub integrations new c80bc25 Merge pull request #12 from mattyb149/NIFI-7415 bfbcd40 is described below commit bfbcd401fda73edac567e35c7a6e4d6b8919193d Author: Matthew Burgess AuthorDate: Fri May 1 11:45:22 2020 -0400 NIFI-7415: Add .asf.yaml to configure GitHub integrations --- .asf.yaml | 35 +++ 1 file changed, 35 insertions(+) diff --git a/.asf.yaml b/.asf.yaml new file mode 100644 index 000..f413a53 --- /dev/null +++ b/.asf.yaml @@ -0,0 +1,35 @@ +# Licensed to the Apache Software Foundation (ASF) under one +# or more contributor license agreements. See the NOTICE file +# distributed with this work for additional information +# regarding copyright ownership. The ASF licenses this file +# to you under the Apache License, Version 2.0 (the +# "License"); you may not use this file except in compliance +# with the License. You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, software +# distributed under the License is distributed on an "AS IS" BASIS, +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +# See the License for the specific language governing permissions and +# limitations under the License. +github: + description: "Apache NiFi NAR Maven Plugin" + homepage: https://nifi.apache.org/ + labels: +- nifi +- maven +- java + features: +wiki: false +issues: false +projects: false + enabled_merge_buttons: +squash: true +merge: true +rebase: true +notifications: +commits: commits@nifi.apache.org +issues: iss...@nifi.apache.org +pullrequests: iss...@nifi.apache.org +jira_options: link label worklog \ No newline at end of file
[nifi-site] branch main updated: NIFI-7415: Add .asf.yaml to configure GitHub integrations
This is an automated email from the ASF dual-hosted git repository. pvillard pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/nifi-site.git The following commit(s) were added to refs/heads/main by this push: new 704ae99 NIFI-7415: Add .asf.yaml to configure GitHub integrations new 105fffa Merge pull request #38 from mattyb149/NIFI-7415 704ae99 is described below commit 704ae998415a126665c50c88ee1510371fea026b Author: Matthew Burgess AuthorDate: Fri May 1 11:51:03 2020 -0400 NIFI-7415: Add .asf.yaml to configure GitHub integrations --- .asf.yaml | 34 ++ 1 file changed, 34 insertions(+) diff --git a/.asf.yaml b/.asf.yaml new file mode 100644 index 000..ada1418 --- /dev/null +++ b/.asf.yaml @@ -0,0 +1,34 @@ +# Licensed to the Apache Software Foundation (ASF) under one +# or more contributor license agreements. See the NOTICE file +# distributed with this work for additional information +# regarding copyright ownership. The ASF licenses this file +# to you under the Apache License, Version 2.0 (the +# "License"); you may not use this file except in compliance +# with the License. You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, software +# distributed under the License is distributed on an "AS IS" BASIS, +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +# See the License for the specific language governing permissions and +# limitations under the License. +github: + description: "Apache NiFi website" + homepage: https://nifi.apache.org/ + labels: +- nifi +- java + features: +wiki: false +issues: false +projects: false + enabled_merge_buttons: +squash: true +merge: true +rebase: true +notifications: +commits: commits@nifi.apache.org +issues: iss...@nifi.apache.org +pullrequests: iss...@nifi.apache.org +jira_options: link label worklog \ No newline at end of file
[nifi] branch main updated: NIFI-7633: Added FlowFileConcurrency of SINGLE_BATCH_PER_NODE to allow data to be pulled into a ProcessGroup as a batch
This is an automated email from the ASF dual-hosted git repository.
pvillard pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/nifi.git
The following commit(s) were added to refs/heads/main by this push:
new a473fc0 NIFI-7633: Added FlowFileConcurrency of SINGLE_BATCH_PER_NODE
to allow data to be pulled into a ProcessGroup as a batch
a473fc0 is described below
commit a473fc037385a3da68a3a0a305db6489f89aef67
Author: Mark Payne
AuthorDate: Wed Jul 8 11:50:12 2020 -0400
NIFI-7633: Added FlowFileConcurrency of SINGLE_BATCH_PER_NODE to allow data
to be pulled into a ProcessGroup as a batch
Signed-off-by: Pierre Villard
This closes #4405.
---
nifi-docs/src/main/asciidoc/user-guide.adoc| 38 ++-
.../java/org/apache/nifi/groups/DataValve.java | 87 ++
...eConcurrency.java => DataValveDiagnostics.java} | 31 +-
.../{FlowFileGate.java => DataflowDirection.java} | 12 +-
.../apache/nifi/groups/FlowFileConcurrency.java| 15 +
.../java/org/apache/nifi/groups/FlowFileGate.java | 6 +-
.../java/org/apache/nifi/groups/ProcessGroup.java | 10 +
.../org/apache/nifi/connectable/LocalPort.java | 45 ++-
.../bootstrap/BootstrapDiagnosticsFactory.java | 2 +
.../bootstrap/tasks/DataValveDiagnosticsTask.java | 69 +
...wFileGate.java => SingleBatchFlowFileGate.java} | 16 +-
.../nifi/groups/SingleConcurrencyFlowFileGate.java | 13 +-
.../org/apache/nifi/groups/StandardDataValve.java | 329 +
.../apache/nifi/groups/StandardProcessGroup.java | 19 +-
.../apache/nifi/groups/UnboundedFlowFileGate.java | 6 +-
.../TestStandardControllerServiceProvider.java | 18 +-
.../controller/service/mock/MockProcessGroup.java | 14 +-
.../js/nf/canvas/nf-process-group-configuration.js | 19 +-
.../nifi/processors/tests/system/Duplicate.java| 75 +
.../processors/tests/system/GenerateFlowFile.java | 2 +
.../services/org.apache.nifi.processor.Processor | 1 +
.../apache/nifi/tests/system/NiFiClientUtil.java | 24 +-
.../org/apache/nifi/tests/system/NiFiSystemIT.java | 21 +-
.../tests/system/pg/BatchFlowBetweenGroupsIT.java | 137 +
.../resources/conf/clustered/node1/logback.xml | 3 +-
.../resources/conf/clustered/node2/logback.xml | 3 +-
.../src/test/resources/conf/default/logback.xml| 3 +-
27 files changed, 959 insertions(+), 59 deletions(-)
diff --git a/nifi-docs/src/main/asciidoc/user-guide.adoc
b/nifi-docs/src/main/asciidoc/user-guide.adoc
index 958d4d2..4894c63 100644
--- a/nifi-docs/src/main/asciidoc/user-guide.adoc
+++ b/nifi-docs/src/main/asciidoc/user-guide.adoc
@@ -744,25 +744,30 @@ information or context about the Process Group.
[[Flowfile_Concurrency]]
=== FlowFile Concurrency
-FlowFile Concurrency is used to control how data is brought into the Process
Group. There are two options available: Unbounded (which is the default)
-and Single FlowFile Per Node. When the concurrency is set to "Unbounded," the
Input Ports in the Process Group will ingest data as quickly as they
+FlowFile Concurrency is used to control how data is brought into the Process
Group. There are three options available: Unbounded (which is the default),
+Single FlowFile Per Node, and Single Batch Per Node. When the concurrency is
set to "Unbounded," the Input Ports in the Process Group will ingest data as
quickly as they
are able, provided that backpressure does not prevent them from doing so.
-When the FlowFile Concurrency is configured to "Single FlowFile Per Node," the
Input Ports will only allow through a single FlowFile at at time.
+When the FlowFile Concurrency is configured to "Single FlowFile Per Node", the
Input Ports will only allow through a single FlowFile at at time.
Once that FlowFile enters the Process Group, no additional FlowFiles will be
brought in until all FlowFiles have left the Process Group (either by
being removed from the system / auto-terminated, or by exiting through an
Output Port). This will often result in slower performance, as it reduces
the parallelization that NiFi uses to process the data. However, there are
several reasons that a user may want to use this approach. A common use case
is one in which each incoming FlowFile contains references to several other
data items, such as a list of files in a directory. The user may want to
process the entire listing before allowing any other data to enter the Process
Group.
+When the FlowFile Concurrency is configured to "Single Batch Per Node", the
Input Ports will behave similarly to the way that they behave in the
+"Single FlowFile Per Node" mode, but when a FlowFile is ingested, the Input
Ports will continue to ingest all data until all of the queues feeding
+the Input Ports have been emptied. At that point, they will not bring any more
data into the Process Group until all data has finished processing and
+has left the Process Group (see note on <>
