[jira] [Commented] (NIFI-4255) Add support for providing ACLs for paths in Zookeeper Migration tool

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16139034#comment-16139034
 ] 

ASF GitHub Bot commented on NIFI-4255:
--

Github user YolandaMDavis commented on the issue:

https://github.com/apache/nifi/pull/2065
  
thank you @jtstorck !


> Add support for providing ACLs for paths in Zookeeper Migration tool
> 
>
> Key: NIFI-4255
> URL: https://issues.apache.org/jira/browse/NIFI-4255
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Tools and Build
>Affects Versions: 1.3.0
>Reporter: Yolanda M. Davis
>Assignee: Yolanda M. Davis
>
> Currently in the Zookeeper migration utility there is support for applying 
> acls when importing zookeeper data (Znodes).  However this support only 
> applies default ACLs values (either Open or Creator specific), and the value 
> used depends on if security is enabled or disabled in the destination 
> Zookeeper instance. This may become problematic if the user/identity used to 
> import zookeeper data does not align with the users/identities that require 
> read/modify rights on the imported Znodes. This also doesn't provide users 
> flexibility in defining specific rights or applying additional authorizations 
> on paths.
> Enhancing the existing utility to support providing ACL information would 
> offer users more flexibility in defining permissions and authentication 
> schemes on znodes. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi issue #2065: NIFI-4255 - added flag to allow migration of existing (sou...

[YolandaMDavis]

Github user YolandaMDavis commented on the issue:

https://github.com/apache/nifi/pull/2065
  
thank you @jtstorck !


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-4255) Add support for providing ACLs for paths in Zookeeper Migration tool

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16138944#comment-16138944
 ] 

ASF subversion and git services commented on NIFI-4255:
---

Commit acee2627ca562a4dc94adfe9836ecd32a4666902 in nifi's branch 
refs/heads/master from [~YolandaMDavis]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=acee262 ]

NIFI-4255 - Added flag to allow migration of existing (source) acls to 
destination, update to documentation
Added build-helper-maven-plugin to nifi-toolkit-zookeeper-migrator pom to build 
groovy test code
Moved spock spec from src/test/java to src/test/groovy
Minor code formatting updates to ZooKeeperMigrator.java

This closes #2065


> Add support for providing ACLs for paths in Zookeeper Migration tool
> 
>
> Key: NIFI-4255
> URL: https://issues.apache.org/jira/browse/NIFI-4255
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Tools and Build
>Affects Versions: 1.3.0
>Reporter: Yolanda M. Davis
>Assignee: Yolanda M. Davis
>
> Currently in the Zookeeper migration utility there is support for applying 
> acls when importing zookeeper data (Znodes).  However this support only 
> applies default ACLs values (either Open or Creator specific), and the value 
> used depends on if security is enabled or disabled in the destination 
> Zookeeper instance. This may become problematic if the user/identity used to 
> import zookeeper data does not align with the users/identities that require 
> read/modify rights on the imported Znodes. This also doesn't provide users 
> flexibility in defining specific rights or applying additional authorizations 
> on paths.
> Enhancing the existing utility to support providing ACL information would 
> offer users more flexibility in defining permissions and authentication 
> schemes on znodes. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (NIFI-4255) Add support for providing ACLs for paths in Zookeeper Migration tool

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16138945#comment-16138945
 ] 

ASF GitHub Bot commented on NIFI-4255:
--

Github user asfgit closed the pull request at:

https://github.com/apache/nifi/pull/2065


> Add support for providing ACLs for paths in Zookeeper Migration tool
> 
>
> Key: NIFI-4255
> URL: https://issues.apache.org/jira/browse/NIFI-4255
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Tools and Build
>Affects Versions: 1.3.0
>Reporter: Yolanda M. Davis
>Assignee: Yolanda M. Davis
>
> Currently in the Zookeeper migration utility there is support for applying 
> acls when importing zookeeper data (Znodes).  However this support only 
> applies default ACLs values (either Open or Creator specific), and the value 
> used depends on if security is enabled or disabled in the destination 
> Zookeeper instance. This may become problematic if the user/identity used to 
> import zookeeper data does not align with the users/identities that require 
> read/modify rights on the imported Znodes. This also doesn't provide users 
> flexibility in defining specific rights or applying additional authorizations 
> on paths.
> Enhancing the existing utility to support providing ACL information would 
> offer users more flexibility in defining permissions and authentication 
> schemes on znodes. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi pull request #2065: NIFI-4255 - added flag to allow migration of existi...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/nifi/pull/2065


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-4255) Add support for providing ACLs for paths in Zookeeper Migration tool

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16138936#comment-16138936
 ] 

ASF GitHub Bot commented on NIFI-4255:
--

Github user jtstorck commented on the issue:

https://github.com/apache/nifi/pull/2065
  
+1 LGTM

Made a few minor formatting changes, and moved the spock spec from 
src/test/java to src/test/groovy.

To test this, I ran a KDC and ZK server in a docker container with two 
principals.  I created a node using principal1 that was sasl-secured via 
principal1, and used the zk migrator to export it to a json file.  Then, I 
manually modified the json file to change the ACL on the node I created to set 
the owner to principal2.  I then used the zk migrator to send the updated json 
to ZK, using the --ignore-source and --use-existing-acl options.  After 
attempting to access the node as principal1 (which failed as expected), I was 
able to access the node as princopal2 (as expected).


> Add support for providing ACLs for paths in Zookeeper Migration tool
> 
>
> Key: NIFI-4255
> URL: https://issues.apache.org/jira/browse/NIFI-4255
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Tools and Build
>Affects Versions: 1.3.0
>Reporter: Yolanda M. Davis
>Assignee: Yolanda M. Davis
>
> Currently in the Zookeeper migration utility there is support for applying 
> acls when importing zookeeper data (Znodes).  However this support only 
> applies default ACLs values (either Open or Creator specific), and the value 
> used depends on if security is enabled or disabled in the destination 
> Zookeeper instance. This may become problematic if the user/identity used to 
> import zookeeper data does not align with the users/identities that require 
> read/modify rights on the imported Znodes. This also doesn't provide users 
> flexibility in defining specific rights or applying additional authorizations 
> on paths.
> Enhancing the existing utility to support providing ACL information would 
> offer users more flexibility in defining permissions and authentication 
> schemes on znodes. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi issue #2065: NIFI-4255 - added flag to allow migration of existing (sou...

[jtstorck]

Github user jtstorck commented on the issue:

https://github.com/apache/nifi/pull/2065
  
+1 LGTM

Made a few minor formatting changes, and moved the spock spec from 
src/test/java to src/test/groovy.

To test this, I ran a KDC and ZK server in a docker container with two 
principals.  I created a node using principal1 that was sasl-secured via 
principal1, and used the zk migrator to export it to a json file.  Then, I 
manually modified the json file to change the ACL on the node I created to set 
the owner to principal2.  I then used the zk migrator to send the updated json 
to ZK, using the --ignore-source and --use-existing-acl options.  After 
attempting to access the node as principal1 (which failed as expected), I was 
able to access the node as princopal2 (as expected).


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (NIFI-4318) PutHiveQL processor cannot be stopped

[Pierre Villard (JIRA)]

Pierre Villard created NIFI-4318:


 Summary: PutHiveQL processor cannot be stopped
 Key: NIFI-4318
 URL: https://issues.apache.org/jira/browse/NIFI-4318
 Project: Apache NiFi
  Issue Type: Bug
  Components: Extensions
Affects Versions: 1.3.0
 Environment: 3-nodes cluster
Reporter: Pierre Villard
 Attachments: image001.png, thread-2.txt, thread.txt

I tried to stop PutHiveQL processor after experiencing some cookie/kerberos 
issues while sending requests to Hive, but the processor could not be stopped 
and showed running threads (it remained in this situation at least for half an 
hour). I had to restart NiFi to solve the situation.

Attached: a screenshot and two thread dumps at about 5 minutes interval.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (NIFI-4313) Stream has already been closed PutDataBaseRecord

[Pierre Villard (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-4313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Villard resolved NIFI-4313.
--
Resolution: Duplicate

> Stream has already been closed PutDataBaseRecord
> 
>
> Key: NIFI-4313
> URL: https://issues.apache.org/jira/browse/NIFI-4313
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.3.0
> Environment: rhel 7.0 
> nifi 1.3.0 
> Oracle Database 11.2.0.2 
> ojdbc7.jar for the driver
>Reporter: peter parker
>  Labels: features
> Attachments: attachment (1).jpg, attachment (2).jpg, attachment.jpg
>
>
> while trying to insert a record whether its a csv or an avro record i get a 
> Stream has already been closed Exception. when i have a default sysdate 
> column in the table
> the stack traces are also in the picture attached to this issue
> i have tried to do a validation query in the DBConnectionPool and it didn't 
> work



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi-minifi-cpp pull request #131: MINIFI-388 symlink versioned libcrypto/li...

[achristianson]

Github user achristianson commented on a diff in the pull request:

https://github.com/apache/nifi-minifi-cpp/pull/131#discussion_r134803404
  
--- Diff: thirdparty/civetweb-1.9.1/src/civetweb.c ---
@@ -11856,7 +11859,24 @@ ssl_get_client_cert_info(struct mg_connection 
*conn)
 
/* Calculate SHA1 fingerprint and store as a hex string */
ulen = 0;
-   ASN1_digest((int (*)())i2d_X509, digest, (char *)cert, buf, 
);
+
+   /* ASN1_digest is deprecated. Do the calculation manually,
--- End diff --


https://github.com/civetweb/civetweb/commit/fb9ef36bb295cf489aecd79c8bb9c6eac11e896e
 is where it comes from.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi-minifi-cpp pull request #131: MINIFI-388 symlink versioned libcrypto/li...

[achristianson]

Github user achristianson commented on a diff in the pull request:

https://github.com/apache/nifi-minifi-cpp/pull/131#discussion_r134803190
  
--- Diff: thirdparty/civetweb-1.9.1/src/civetweb.c ---
@@ -11856,7 +11859,24 @@ ssl_get_client_cert_info(struct mg_connection 
*conn)
 
/* Calculate SHA1 fingerprint and store as a hex string */
ulen = 0;
-   ASN1_digest((int (*)())i2d_X509, digest, (char *)cert, buf, 
);
+
+   /* ASN1_digest is deprecated. Do the calculation manually,
--- End diff --

Yes.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-2715) When performing a Queue Listing, if FlowFile has no content, UI does not indicate this fact

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-2715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16138592#comment-16138592
 ] 

ASF GitHub Bot commented on NIFI-2715:
--

Github user yuri1969 commented on the issue:

https://github.com/apache/nifi/pull/2100
  
@scottyaslan The text's style should match the one used on detail values 
now.


> When performing a Queue Listing, if FlowFile has no content, UI does not 
> indicate this fact
> ---
>
> Key: NIFI-2715
> URL: https://issues.apache.org/jira/browse/NIFI-2715
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Mark Payne
>Priority: Minor
>
> I have a queue that has FlowFiles with no content (this is the result of 
> running GetHTMLElement with the destination set to attribute and sending the 
> matching FlowFiles to this queue). When I view the queue listing, the 
> FlowFiles have no Content Claim, but there is no indicator that there is no 
> Content Claim. The UI should specifically indicate this, as it leaves the 
> user confused as to why they are unable to view the content.
> Also, while looking at this, when I view the details of a FlowFile, I found 
> that the File Size was listed as 'no previous value set' because the FlowFile 
> had no content claim.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi-minifi-cpp pull request #131: MINIFI-388 symlink versioned libcrypto/li...

[phrocker]

Github user phrocker commented on a diff in the pull request:

https://github.com/apache/nifi-minifi-cpp/pull/131#discussion_r134802972
  
--- Diff: thirdparty/civetweb-1.9.1/src/civetweb.c ---
@@ -11856,7 +11859,24 @@ ssl_get_client_cert_info(struct mg_connection 
*conn)
 
/* Calculate SHA1 fingerprint and store as a hex string */
ulen = 0;
-   ASN1_digest((int (*)())i2d_X509, digest, (char *)cert, buf, 
);
+
+   /* ASN1_digest is deprecated. Do the calculation manually,
--- End diff --

is this also a backport? 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi issue #2100: NIFI-2715 - When performing a Queue Listing, if...

[yuri1969]

Github user yuri1969 commented on the issue:

https://github.com/apache/nifi/pull/2100
  
@scottyaslan The text's style should match the one used on detail values 
now.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi-minifi-cpp issue #131: MINIFI-388 symlink versioned libcrypto/libssl to...

[achristianson]

Github user achristianson commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/131
  
Issue was addressed by an upstream commit in civetweb: 
https://github.com/civetweb/civetweb/commit/e849ce4b54c09d5b4441e371f17cf13368ac2234.
 Backported that commit which should fix the travis/ubuntu trusty issue.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Assigned] (NIFI-170) nar-maven-plugin does not have any kind of tests (unit- nor integration tests)

[Arun Manivannan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arun Manivannan reassigned NIFI-170:


Assignee: Arun Manivannan

> nar-maven-plugin does not have any kind of tests (unit- nor integration tests)
> --
>
> Key: NIFI-170
> URL: https://issues.apache.org/jira/browse/NIFI-170
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Tools and Build
>Affects Versions: 0.0.1
>Reporter: Karl Heinz Marbaise
>Assignee: Arun Manivannan
>  Labels: beginner
>
> There should be some kind of unit and/or integration tests for the plugin to 
> check if the plugin does what it should and of course make changes easier.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (NIFI-4317) Document logback logging considerations for Windows environments

[Aldrin Piri (JIRA)]

Aldrin Piri created NIFI-4317:
-

 Summary: Document logback logging considerations for Windows 
environments
 Key: NIFI-4317
 URL: https://issues.apache.org/jira/browse/NIFI-4317
 Project: Apache NiFi
  Issue Type: Task
  Components: Documentation & Website
Reporter: Aldrin Piri


Logback can have some issues with file renaming in some Windows environments 
and can lead to files not rolling over due to failing to rename a file in that 
process.

This can lead to a singular log file growing unbounded.

http://logback.qos.ch/codes.html#renamingError



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (NIFI-4316) Upgrade to newer version of logback

[Aldrin Piri (JIRA)]

Aldrin Piri created NIFI-4316:
-

 Summary: Upgrade to newer version of logback
 Key: NIFI-4316
 URL: https://issues.apache.org/jira/browse/NIFI-4316
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Core Framework
Affects Versions: 1.3.0
Reporter: Aldrin Piri


There are some bugs outstanding with logback that can cause compression to fail 
in some environments (was able to recreate in Windows and OS X), seemingly 
related to the current outstanding issue: 
https://jira.qos.ch/browse/LOGBACK-1162

This will also cause the given set of files to grow beyond their bounds of a 
specified totalSizeCap if one is provided.

Steps I used to create this comprised:
* Using a simple flow that generates flow files and terminates them at an 
update attribute is sufficient.
* Adjust logback to have DEBUG level for the root logger.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (NIFI-4315) Upgrade to newer version of logback

[Aldrin Piri (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16138353#comment-16138353
 ] 

Aldrin Piri commented on NIFI-4315:
---

Current version of logback used is 1.2.3.

> Upgrade to newer version of logback
> ---
>
> Key: NIFI-4315
> URL: https://issues.apache.org/jira/browse/NIFI-4315
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Affects Versions: 1.3.0
>Reporter: Aldrin Piri
>
> There are some bugs outstanding with logback that can cause compression to 
> fail in some environments (was able to recreate in Windows and OS X), 
> seemingly related to the current outstanding issue: 
> https://jira.qos.ch/browse/LOGBACK-1162
> This will also cause the given set of files to grow beyond their bounds of a 
> specified totalSizeCap if one is provided.
> Steps I used to create this comprised:
> * Using a simple flow that generates flow files and terminates them at an 
> update attribute is sufficient.
> * Adjust logback to have DEBUG level for the root logger.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (NIFI-4315) Upgrade to newer version of logback

[Aldrin Piri (JIRA)]

Aldrin Piri created NIFI-4315:
-

 Summary: Upgrade to newer version of logback
 Key: NIFI-4315
 URL: https://issues.apache.org/jira/browse/NIFI-4315
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Core Framework
Affects Versions: 1.3.0
Reporter: Aldrin Piri


There are some bugs outstanding with logback that can cause compression to fail 
in some environments (was able to recreate in Windows and OS X), seemingly 
related to the current outstanding issue: 
https://jira.qos.ch/browse/LOGBACK-1162

This will also cause the given set of files to grow beyond their bounds of a 
specified totalSizeCap if one is provided.

Steps I used to create this comprised:
* Using a simple flow that generates flow files and terminates them at an 
update attribute is sufficient.
* Adjust logback to have DEBUG level for the root logger.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (NIFI-4314) Document logback logging considerations for Windows environments

[Aldrin Piri (JIRA)]

Aldrin Piri created NIFI-4314:
-

 Summary: Document logback logging considerations for Windows 
environments
 Key: NIFI-4314
 URL: https://issues.apache.org/jira/browse/NIFI-4314
 Project: Apache NiFi
  Issue Type: Task
  Components: Documentation & Website
Reporter: Aldrin Piri


Logback can have some issues with file renaming in some Windows environments 
and can lead to files not rolling over due to failing to rename a file in that 
process.

This can lead to a singular log file growing unbounded.

http://logback.qos.ch/codes.html#renamingError



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi issue #2063: NIFI-4269 Added the ability to serialize Mongo documents t...

[MikeThomsen]

Github user MikeThomsen commented on the issue:

https://github.com/apache/nifi/pull/2063
  
@mattyb149 Ok, changes committed and at least the French build ran to 
completion.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-4269) GetMongo should be able to provide pure JSON as well as "extended JSON"

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16138325#comment-16138325
 ] 

ASF GitHub Bot commented on NIFI-4269:
--

Github user MikeThomsen commented on the issue:

https://github.com/apache/nifi/pull/2063
  
@mattyb149 Ok, changes committed and at least the French build ran to 
completion.


> GetMongo should be able to provide pure JSON as well as "extended JSON"
> ---
>
> Key: NIFI-4269
> URL: https://issues.apache.org/jira/browse/NIFI-4269
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Mike Thomsen
>
> GetMongo currently only supports "extended JSON." That results in ugly JSON 
> like this:
> {
> "timestamp": {
> "$date": LONG_TIMESTAMP
> }
> }
> instead of something cleaner like this:
> {
> "timestamp": "2017-08-07T00:00:00Z"
> }
> GetMongo should be refactored to support both modes of JSON serialization.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (NIFI-4313) Stream has already been closed PutDataBaseRecord

[peter parker (JIRA)]

peter parker created NIFI-4313:
--

 Summary: Stream has already been closed PutDataBaseRecord
 Key: NIFI-4313
 URL: https://issues.apache.org/jira/browse/NIFI-4313
 Project: Apache NiFi
  Issue Type: Bug
  Components: Extensions
Affects Versions: 1.3.0
 Environment: rhel 7.0 
nifi 1.3.0 
Oracle Database 11.2.0.2 
ojdbc7.jar for the driver
Reporter: peter parker
 Attachments: attachment (1).jpg, attachment (2).jpg, attachment.jpg

while trying to insert a record whether its a csv or an avro record i get a 
Stream has already been closed Exception. when i have a default sysdate column 
in the table
the stack traces are also in the picture attached to this issue
i have tried to do a validation query in the DBConnectionPool and it didn't work



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (NIFI-4312) PutDataBaseRecord when column is default sysdate Stream has already been closed Excepotion pops up

[peter parker (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-4312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

peter parker updated NIFI-4312:
---
Summary: PutDataBaseRecord when column is default sysdate Stream has 
already been closed Excepotion pops up  (was: PutDataBaseRecord when column is 
default sysdate)

> PutDataBaseRecord when column is default sysdate Stream has already been 
> closed Excepotion pops up
> --
>
> Key: NIFI-4312
> URL: https://issues.apache.org/jira/browse/NIFI-4312
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Affects Versions: 1.3.0
> Environment: rhel 7.0 
> nifi 1.3.0
> Oracle Database 11.2.0.2
> ojdbc7.jar for the driver
>Reporter: peter parker
>  Labels: features
> Fix For: 1.4.0
>
> Attachments: attachment.jpg
>
>
> while trying to insert a record whether its a csv or an avro record i get a 
> Stream has already been closed Exception. when i have a default sysdate 
> column in the table
> full stack trace:
> PutDatabaseRecord[id=32a9f123-4cb5-3994-1669-d305c4dfd8db] Failed to
> process 
> StandardFlowFileRecord[uuid=650de48a-7f08=4655=9f07-b0f1d6086044,claim=StandardContentClaim
> [resourceClaim-StandardResourceClaim[id=1503482458485-452,
> container=default, section-452], offset=435424,
> length=1535],offset=0,name=3083066194824986,size=1535] due to
> java.sql.SQLException Stream has already been closed:
> the stack traces are also in the picture attached to this issue
> i have tried to do a validation query in the DBConnectionPool and it didn't 
> work



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (NIFI-4312) PutDataBaseRecord when column is default sysdate Stream has already been closed Exception pops up

[peter parker (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16138073#comment-16138073
 ] 

peter parker commented on NIFI-4312:


do i need to add any extra details ?

> PutDataBaseRecord when column is default sysdate Stream has already been 
> closed Exception pops up
> -
>
> Key: NIFI-4312
> URL: https://issues.apache.org/jira/browse/NIFI-4312
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.3.0
> Environment: rhel 7.0 
> nifi 1.3.0
> Oracle Database 11.2.0.2
> ojdbc7.jar for the driver
>Reporter: peter parker
>  Labels: features
> Attachments: attachment (1).jpg, attachment (2).jpg, attachment.jpg
>
>
> while trying to insert a record whether its a csv or an avro record i get a 
> Stream has already been closed Exception. when i have a default sysdate 
> column in the table
> the stack traces are also in the picture attached to this issue
> i have tried to do a validation query in the DBConnectionPool and it didn't 
> work



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (NIFI-4312) PutDataBaseRecord when column is default sysdate Stream has already been closed Exception pops up

[peter parker (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-4312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

peter parker updated NIFI-4312:
---
Summary: PutDataBaseRecord when column is default sysdate Stream has 
already been closed Exception pops up  (was: PutDataBaseRecord when column is 
default sysdate Stream has already been closed Excepotion pops up)

> PutDataBaseRecord when column is default sysdate Stream has already been 
> closed Exception pops up
> -
>
> Key: NIFI-4312
> URL: https://issues.apache.org/jira/browse/NIFI-4312
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.3.0
> Environment: rhel 7.0 
> nifi 1.3.0
> Oracle Database 11.2.0.2
> ojdbc7.jar for the driver
>Reporter: peter parker
>  Labels: features
> Attachments: attachment (1).jpg, attachment (2).jpg, attachment.jpg
>
>
> while trying to insert a record whether its a csv or an avro record i get a 
> Stream has already been closed Exception. when i have a default sysdate 
> column in the table
> the stack traces are also in the picture attached to this issue
> i have tried to do a validation query in the DBConnectionPool and it didn't 
> work



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (NIFI-4312) PutDataBaseRecord when column is default sysdate Stream has already been closed Excepotion pops up

[peter parker (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-4312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

peter parker updated NIFI-4312:
---
Attachment: attachment (2).jpg

stack trace

> PutDataBaseRecord when column is default sysdate Stream has already been 
> closed Excepotion pops up
> --
>
> Key: NIFI-4312
> URL: https://issues.apache.org/jira/browse/NIFI-4312
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.3.0
> Environment: rhel 7.0 
> nifi 1.3.0
> Oracle Database 11.2.0.2
> ojdbc7.jar for the driver
>Reporter: peter parker
>  Labels: features
> Attachments: attachment (1).jpg, attachment (2).jpg, attachment.jpg
>
>
> while trying to insert a record whether its a csv or an avro record i get a 
> Stream has already been closed Exception. when i have a default sysdate 
> column in the table
> full stack trace:
> PutDatabaseRecord[id=32a9f123-4cb5-3994-1669-d305c4dfd8db] Failed to
> process 
> StandardFlowFileRecord[uuid=650de48a-7f08=4655=9f07-b0f1d6086044,claim=StandardContentClaim
> [resourceClaim-StandardResourceClaim[id=1503482458485-452,
> container=default, section-452], offset=435424,
> length=1535],offset=0,name=3083066194824986,size=1535] due to
> java.sql.SQLException Stream has already been closed:
> the stack traces are also in the picture attached to this issue
> i have tried to do a validation query in the DBConnectionPool and it didn't 
> work



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (NIFI-4312) PutDataBaseRecord when column is default sysdate Stream has already been closed Excepotion pops up

[peter parker (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-4312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

peter parker updated NIFI-4312:
---
Description: 
while trying to insert a record whether its a csv or an avro record i get a 
Stream has already been closed Exception. when i have a default sysdate column 
in the table

the stack traces are also in the picture attached to this issue
i have tried to do a validation query in the DBConnectionPool and it didn't work


  was:
while trying to insert a record whether its a csv or an avro record i get a 
Stream has already been closed Exception. when i have a default sysdate column 
in the table

full stack trace:

PutDatabaseRecord[id=32a9f123-4cb5-3994-1669-d305c4dfd8db] Failed to
process 
StandardFlowFileRecord[uuid=650de48a-7f08=4655=9f07-b0f1d6086044,claim=StandardContentClaim
[resourceClaim-StandardResourceClaim[id=1503482458485-452,
container=default, section-452], offset=435424,
length=1535],offset=0,name=3083066194824986,size=1535] due to
java.sql.SQLException Stream has already been closed:

the stack traces are also in the picture attached to this issue
i have tried to do a validation query in the DBConnectionPool and it didn't work



> PutDataBaseRecord when column is default sysdate Stream has already been 
> closed Excepotion pops up
> --
>
> Key: NIFI-4312
> URL: https://issues.apache.org/jira/browse/NIFI-4312
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.3.0
> Environment: rhel 7.0 
> nifi 1.3.0
> Oracle Database 11.2.0.2
> ojdbc7.jar for the driver
>Reporter: peter parker
>  Labels: features
> Attachments: attachment (1).jpg, attachment (2).jpg, attachment.jpg
>
>
> while trying to insert a record whether its a csv or an avro record i get a 
> Stream has already been closed Exception. when i have a default sysdate 
> column in the table
> the stack traces are also in the picture attached to this issue
> i have tried to do a validation query in the DBConnectionPool and it didn't 
> work



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (NIFI-4312) PutDataBaseRecord when column is default sysdate Stream has already been closed Excepotion pops up

[peter parker (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-4312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

peter parker updated NIFI-4312:
---
Attachment: attachment (1).jpg

> PutDataBaseRecord when column is default sysdate Stream has already been 
> closed Excepotion pops up
> --
>
> Key: NIFI-4312
> URL: https://issues.apache.org/jira/browse/NIFI-4312
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.3.0
> Environment: rhel 7.0 
> nifi 1.3.0
> Oracle Database 11.2.0.2
> ojdbc7.jar for the driver
>Reporter: peter parker
>  Labels: features
> Attachments: attachment (1).jpg, attachment.jpg
>
>
> while trying to insert a record whether its a csv or an avro record i get a 
> Stream has already been closed Exception. when i have a default sysdate 
> column in the table
> full stack trace:
> PutDatabaseRecord[id=32a9f123-4cb5-3994-1669-d305c4dfd8db] Failed to
> process 
> StandardFlowFileRecord[uuid=650de48a-7f08=4655=9f07-b0f1d6086044,claim=StandardContentClaim
> [resourceClaim-StandardResourceClaim[id=1503482458485-452,
> container=default, section-452], offset=435424,
> length=1535],offset=0,name=3083066194824986,size=1535] due to
> java.sql.SQLException Stream has already been closed:
> the stack traces are also in the picture attached to this issue
> i have tried to do a validation query in the DBConnectionPool and it didn't 
> work



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (NIFI-4312) PutDataBaseRecord when column is default sysdate Stream has already been closed Excepotion pops up

[peter parker (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16138049#comment-16138049
 ] 

peter parker commented on NIFI-4312:


i have added the full stack trace from the log file

> PutDataBaseRecord when column is default sysdate Stream has already been 
> closed Excepotion pops up
> --
>
> Key: NIFI-4312
> URL: https://issues.apache.org/jira/browse/NIFI-4312
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.3.0
> Environment: rhel 7.0 
> nifi 1.3.0
> Oracle Database 11.2.0.2
> ojdbc7.jar for the driver
>Reporter: peter parker
>  Labels: features
> Attachments: attachment (1).jpg, attachment.jpg
>
>
> while trying to insert a record whether its a csv or an avro record i get a 
> Stream has already been closed Exception. when i have a default sysdate 
> column in the table
> full stack trace:
> PutDatabaseRecord[id=32a9f123-4cb5-3994-1669-d305c4dfd8db] Failed to
> process 
> StandardFlowFileRecord[uuid=650de48a-7f08=4655=9f07-b0f1d6086044,claim=StandardContentClaim
> [resourceClaim-StandardResourceClaim[id=1503482458485-452,
> container=default, section-452], offset=435424,
> length=1535],offset=0,name=3083066194824986,size=1535] due to
> java.sql.SQLException Stream has already been closed:
> the stack traces are also in the picture attached to this issue
> i have tried to do a validation query in the DBConnectionPool and it didn't 
> work



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (NIFI-4312) PutDataBaseRecord when column is default sysdate Stream has already been closed Excepotion pops up

[Pierre Villard (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16138031#comment-16138031
 ] 

Pierre Villard commented on NIFI-4312:
--

Hi Peter,

You should have a complete stack trace in the nifi-app.log file that would give 
very important information to debug this issue. Could you add this information 
here? (what you joined is the bulletin info that contains only the message part 
of the exception without the full stack trace).

> PutDataBaseRecord when column is default sysdate Stream has already been 
> closed Excepotion pops up
> --
>
> Key: NIFI-4312
> URL: https://issues.apache.org/jira/browse/NIFI-4312
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.3.0
> Environment: rhel 7.0 
> nifi 1.3.0
> Oracle Database 11.2.0.2
> ojdbc7.jar for the driver
>Reporter: peter parker
>  Labels: features
> Attachments: attachment.jpg
>
>
> while trying to insert a record whether its a csv or an avro record i get a 
> Stream has already been closed Exception. when i have a default sysdate 
> column in the table
> full stack trace:
> PutDatabaseRecord[id=32a9f123-4cb5-3994-1669-d305c4dfd8db] Failed to
> process 
> StandardFlowFileRecord[uuid=650de48a-7f08=4655=9f07-b0f1d6086044,claim=StandardContentClaim
> [resourceClaim-StandardResourceClaim[id=1503482458485-452,
> container=default, section-452], offset=435424,
> length=1535],offset=0,name=3083066194824986,size=1535] due to
> java.sql.SQLException Stream has already been closed:
> the stack traces are also in the picture attached to this issue
> i have tried to do a validation query in the DBConnectionPool and it didn't 
> work



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (NIFI-4312) PutDataBaseRecord when column is default sysdate Stream has already been closed Excepotion pops up

[Pierre Villard (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-4312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Villard updated NIFI-4312:
-
Fix Version/s: (was: 1.4.0)

> PutDataBaseRecord when column is default sysdate Stream has already been 
> closed Excepotion pops up
> --
>
> Key: NIFI-4312
> URL: https://issues.apache.org/jira/browse/NIFI-4312
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.3.0
> Environment: rhel 7.0 
> nifi 1.3.0
> Oracle Database 11.2.0.2
> ojdbc7.jar for the driver
>Reporter: peter parker
>  Labels: features
> Attachments: attachment.jpg
>
>
> while trying to insert a record whether its a csv or an avro record i get a 
> Stream has already been closed Exception. when i have a default sysdate 
> column in the table
> full stack trace:
> PutDatabaseRecord[id=32a9f123-4cb5-3994-1669-d305c4dfd8db] Failed to
> process 
> StandardFlowFileRecord[uuid=650de48a-7f08=4655=9f07-b0f1d6086044,claim=StandardContentClaim
> [resourceClaim-StandardResourceClaim[id=1503482458485-452,
> container=default, section-452], offset=435424,
> length=1535],offset=0,name=3083066194824986,size=1535] due to
> java.sql.SQLException Stream has already been closed:
> the stack traces are also in the picture attached to this issue
> i have tried to do a validation query in the DBConnectionPool and it didn't 
> work



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (NIFI-4312) PutDataBaseRecord when column is default sysdate Stream has already been closed Excepotion pops up

[Pierre Villard (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-4312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Villard updated NIFI-4312:
-
Issue Type: Bug  (was: New Feature)

> PutDataBaseRecord when column is default sysdate Stream has already been 
> closed Excepotion pops up
> --
>
> Key: NIFI-4312
> URL: https://issues.apache.org/jira/browse/NIFI-4312
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.3.0
> Environment: rhel 7.0 
> nifi 1.3.0
> Oracle Database 11.2.0.2
> ojdbc7.jar for the driver
>Reporter: peter parker
>  Labels: features
> Attachments: attachment.jpg
>
>
> while trying to insert a record whether its a csv or an avro record i get a 
> Stream has already been closed Exception. when i have a default sysdate 
> column in the table
> full stack trace:
> PutDatabaseRecord[id=32a9f123-4cb5-3994-1669-d305c4dfd8db] Failed to
> process 
> StandardFlowFileRecord[uuid=650de48a-7f08=4655=9f07-b0f1d6086044,claim=StandardContentClaim
> [resourceClaim-StandardResourceClaim[id=1503482458485-452,
> container=default, section-452], offset=435424,
> length=1535],offset=0,name=3083066194824986,size=1535] due to
> java.sql.SQLException Stream has already been closed:
> the stack traces are also in the picture attached to this issue
> i have tried to do a validation query in the DBConnectionPool and it didn't 
> work



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (NIFI-4312) PutDataBaseRecord when column is default sysdate

[peter parker (JIRA)]

peter parker created NIFI-4312:
--

 Summary: PutDataBaseRecord when column is default sysdate
 Key: NIFI-4312
 URL: https://issues.apache.org/jira/browse/NIFI-4312
 Project: Apache NiFi
  Issue Type: New Feature
  Components: Extensions
Affects Versions: 1.3.0
 Environment: rhel 7.0 
nifi 1.3.0
Oracle Database 11.2.0.2
ojdbc7.jar for the driver

Reporter: peter parker
 Fix For: 1.4.0
 Attachments: attachment.jpg

while trying to insert a record whether its a csv or an avro record i get a 
Stream has already been closed Exception. when i have a default sysdate column 
in the table

full stack trace:

PutDatabaseRecord[id=32a9f123-4cb5-3994-1669-d305c4dfd8db] Failed to
process 
StandardFlowFileRecord[uuid=650de48a-7f08=4655=9f07-b0f1d6086044,claim=StandardContentClaim
[resourceClaim-StandardResourceClaim[id=1503482458485-452,
container=default, section-452], offset=435424,
length=1535],offset=0,name=3083066194824986,size=1535] due to
java.sql.SQLException Stream has already been closed:

the stack traces are also in the picture attached to this issue
i have tried to do a validation query in the DBConnectionPool and it didn't work




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (NIFI-4310) Certain flow configurations are improperly identified as empty during flow election

[Yolanda M. Davis (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-4310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yolanda M. Davis updated NIFI-4310:
---
Status: Patch Available  (was: In Progress)

PR available here: https://github.com/apache/nifi/pull/2107

> Certain flow configurations are improperly identified as empty during flow 
> election
> ---
>
> Key: NIFI-4310
> URL: https://issues.apache.org/jira/browse/NIFI-4310
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.3.0
>Reporter: Yolanda M. Davis
>Assignee: Yolanda M. Davis
>
> While testing a cluster containing nodes with two different flows on initial 
> startup, I discovered that one flow, with an empty root processor group but 
> containing reporting tasks, would lose a flow election against flows that 
> also had empty root processor groups yet with no reporting tasks or 
> controller tasks. This caused an issue downstream during startup where it 
> attempted to replace the non-empty flow with an empty flow on certain nodes, 
> which led to UninheritableFlowExceptions. Further investigation revealed that 
> during election there is a check to determine if the flow is empty however 
> the check does not account for the existence of a reporting task or 
> controller services. This should be repaired to ensure that flows are 
> properly identified as non-empty for election.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (NIFI-4310) Certain flow configurations are improperly identified as empty during flow election

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16137951#comment-16137951
 ] 

ASF GitHub Bot commented on NIFI-4310:
--

GitHub user YolandaMDavis opened a pull request:

https://github.com/apache/nifi/pull/2107

NIFI-4310 - added changes to support detection of reporting tasks and…

… controller services during isEmpty flow check. Added testing scenarios

Recommend the following tests scenarios are included:

- Confirm cluster starts after flow election with empty flows on all nodes
- Confirm start after election initiated for cluster having all but one 
node containing empty flows (one remaining node contains flow populated with 
root process group) 
- Confirm start after election initiated for cluster containing 1/2 nodes 
with empty flows (remaining halves would contain flows with only controller 
services).
- Confirm start after election initiated for cluster containing 1/2 nodes 
with empty flows (remaining halves would contain flows with only reporting 
tasks).

Thank you for submitting a contribution to Apache NiFi.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [x] Is there a JIRA ticket associated with this PR? Is it referenced 
 in the commit message?

- [x] Does your PR title start with NIFI- where  is the JIRA number 
you are trying to resolve? Pay particular attention to the hyphen "-" character.

- [ ] Has your PR been rebased against the latest commit within the target 
branch (typically master)?

- [ x] Is your initial contribution a single, squashed commit?

### For code changes:
- [x ] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?
- [x] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
- [ ] If applicable, have you updated the LICENSE file, including the main 
LICENSE file under nifi-assembly?
- [ ] If applicable, have you updated the NOTICE file, including the main 
NOTICE file found under nifi-assembly?
- [ ] If adding new Properties, have you added .displayName in addition to 
.name (programmatic access) for each of the new properties?

### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in 
which it is rendered?

### Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/YolandaMDavis/nifi NIFI-4310

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/2107.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 #2107


commit 028e381e281d982cc6683c9a0949a3dc820b55d7
Author: Yolanda M. Davis 
Date:   2017-08-23T05:53:49Z

NIFI-4310 - added changes to support detection of reporting tasks and 
controller services during isEmpty flow check. Added testing scenarios




> Certain flow configurations are improperly identified as empty during flow 
> election
> ---
>
> Key: NIFI-4310
> URL: https://issues.apache.org/jira/browse/NIFI-4310
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.3.0
>Reporter: Yolanda M. Davis
>Assignee: Yolanda M. Davis
>
> While testing a cluster containing nodes with two different flows on initial 
> startup, I discovered that one flow, with an empty root processor group but 
> containing reporting tasks, would lose a flow election against flows that 
> also had empty root processor groups yet with no reporting tasks or 
> controller tasks. This caused an issue downstream during startup where it 
> attempted to replace the non-empty flow with an empty flow on certain nodes, 
> which led to UninheritableFlowExceptions. Further investigation revealed that 
> during election there is a check to determine if the flow is empty however 
> the check does not account for the existence of a reporting task or 
> controller services. This should be repaired to ensure that flows are 
> properly identified as non-empty for election.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi pull request #2107: NIFI-4310 - added changes to support detection of r...

[YolandaMDavis]

GitHub user YolandaMDavis opened a pull request:

https://github.com/apache/nifi/pull/2107

NIFI-4310 - added changes to support detection of reporting tasks and…

… controller services during isEmpty flow check. Added testing scenarios

Recommend the following tests scenarios are included:

- Confirm cluster starts after flow election with empty flows on all nodes
- Confirm start after election initiated for cluster having all but one 
node containing empty flows (one remaining node contains flow populated with 
root process group) 
- Confirm start after election initiated for cluster containing 1/2 nodes 
with empty flows (remaining halves would contain flows with only controller 
services).
- Confirm start after election initiated for cluster containing 1/2 nodes 
with empty flows (remaining halves would contain flows with only reporting 
tasks).

Thank you for submitting a contribution to Apache NiFi.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [x] Is there a JIRA ticket associated with this PR? Is it referenced 
 in the commit message?

- [x] Does your PR title start with NIFI- where  is the JIRA number 
you are trying to resolve? Pay particular attention to the hyphen "-" character.

- [ ] Has your PR been rebased against the latest commit within the target 
branch (typically master)?

- [ x] Is your initial contribution a single, squashed commit?

### For code changes:
- [x ] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?
- [x] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
- [ ] If applicable, have you updated the LICENSE file, including the main 
LICENSE file under nifi-assembly?
- [ ] If applicable, have you updated the NOTICE file, including the main 
NOTICE file found under nifi-assembly?
- [ ] If adding new Properties, have you added .displayName in addition to 
.name (programmatic access) for each of the new properties?

### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in 
which it is rendered?

### Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/YolandaMDavis/nifi NIFI-4310

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/2107.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 #2107


commit 028e381e281d982cc6683c9a0949a3dc820b55d7
Author: Yolanda M. Davis 
Date:   2017-08-23T05:53:49Z

NIFI-4310 - added changes to support detection of reporting tasks and 
controller services during isEmpty flow check. Added testing scenarios




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---