[jira] [Commented] (NIFI-2507) PutS3Object should support Canned ACLs

[James Wing (JIRA)]

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

James Wing commented on NIFI-2507:
--

Thanks, [~treardon], for this contribution!

> PutS3Object should support Canned ACLs
> --
>
> Key: NIFI-2507
> URL: https://issues.apache.org/jira/browse/NIFI-2507
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 0.7.0
>Reporter: Tim Reardon
>Assignee: James Wing
>Priority: Minor
> Fix For: 1.0.0, 0.7.1
>
>
> In order to support cross-account scenarios, PutS3Object should support 
> specifying canned ACL's such as "bucket-owner-full-control".
> See 
> http://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (NIFI-2537) Allow specification of Custom-MimeTypes.xml for IdentifyMimeTypes processor

[Rich Rademacher (JIRA)]

Rich Rademacher created NIFI-2537:
-

 Summary: Allow specification of Custom-MimeTypes.xml for 
IdentifyMimeTypes processor
 Key: NIFI-2537
 URL: https://issues.apache.org/jira/browse/NIFI-2537
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Extensions
Affects Versions: 0.7.0
Reporter: Rich Rademacher
Priority: Minor
 Fix For: 0.8.0


Add property in the IdentifyMimeType processor so the user can add his/her own 
Custom-MimeTypes.xml file into the Tika Engine.

This will allow the user to expand the known mime types when this processor is 
used e.g. to filter flowfiles from unknown sources



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2503) Backport PostHTTP SSL Protocol fix to 0.x branch

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2503:
--

Github user jskora commented on the issue:

https://github.com/apache/nifi/pull/811
  
Thanks @pvillard31 for committing this.

It looks like you put the "this closes..." comment on it, any idea why it 
didn't close automatically?


> Backport PostHTTP SSL Protocol fix to 0.x branch
> 
>
> Key: NIFI-2503
> URL: https://issues.apache.org/jira/browse/NIFI-2503
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core Framework
>Affects Versions: 0.7.0
>Reporter: Joe Skora
>Assignee: Joe Skora
>Priority: Critical
> Fix For: 0.8.0
>
>
> PostHTTP in the 0.x branch still has the hardcoded protocol version that 
> NIFI-1688 / [PR-624|https://github.com/apache/nifi/pull/624] fixed in the 1.0 
> branch.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2503) Backport PostHTTP SSL Protocol fix to 0.x branch

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2503:
--

Github user jskora closed the pull request at:

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


> Backport PostHTTP SSL Protocol fix to 0.x branch
> 
>
> Key: NIFI-2503
> URL: https://issues.apache.org/jira/browse/NIFI-2503
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core Framework
>Affects Versions: 0.7.0
>Reporter: Joe Skora
>Assignee: Joe Skora
>Priority: Critical
> Fix For: 0.8.0
>
>
> PostHTTP in the 0.x branch still has the hardcoded protocol version that 
> NIFI-1688 / [PR-624|https://github.com/apache/nifi/pull/624] fixed in the 1.0 
> branch.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi pull request #811: NIFI-2503 Backport PostHTTP SSL Protocol fix to 0.x ...

[jskora]

Github user jskora closed the pull request at:

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


---
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-2536) Update Documentation for Importing a Template

[James Wing (JIRA)]

James Wing created NIFI-2536:


 Summary: Update Documentation for Importing a Template
 Key: NIFI-2536
 URL: https://issues.apache.org/jira/browse/NIFI-2536
 Project: Apache NiFi
  Issue Type: Bug
  Components: Documentation & Website
Affects Versions: 1.0.0
Reporter: James Wing
Priority: Minor


The documentation for importing a template does not reflect recent UI changes 
for 1.0.  The current User Guide text reflects uploading templates from the 
Template Management dialog.  It should describe the new Upload Template button 
on the Actions Toolbar (or "Operate Palette"?).

{quote}
*Importing a Template*
After receiving a Template that has been exported from another NiFi, the first 
step needed to use the template is to import the template into this instance of 
NiFi. From the Template Management dialog (see Managing Templates), click the 
“Browse” button. This provides a File Selection dialog that allows the user to 
choose which template file to upload. Select the file and click Open. The 
“Browse” button is replaced by an “Import” button and a “Cancel” button. 
Clicking the “Import” button will attempt to import the Template into this 
instance of NiFi. If unable to import the Template, an error message will 
appear in red next to the “Browse” button. Otherwise, the Template will be 
added to the table and the “Browse” button will reappear.
{quote}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-1942) Create a processor to validate CSV against a user-supplied schema

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1942:
--

Github user pvillard31 commented on the issue:

https://github.com/apache/nifi/pull/476
  
Hey @JPercivall, I think I've addressed most of your comments:
- changed log level
- fixed decrementation (was not related to header but rather to 'finally' 
in 'while' loop)
- strategy naming and description
- fixed first line handling and added a unit test for that and to confirm 
Unique() behavior when validating line by line
- changed exception catching

It remains what you observed when displaying content of flow files after 
being processed by the processor. I've reproduced your observation but I didn't 
find any explanation. By any chance, do you know if there are some specific 
encoding related to the UI display? (I remember some discussions regarding how 
is processed the carriage return (shift + enter instead of \n) when used in a 
property in some processors) If you haves ideas, let me know!

Thanks.


> Create a processor to validate CSV against a user-supplied schema
> -
>
> Key: NIFI-1942
> URL: https://issues.apache.org/jira/browse/NIFI-1942
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Pierre Villard
>Assignee: Pierre Villard
>Priority: Minor
> Attachments: ValidateCSV.xml
>
>
> In order to extend the set of "quality control" processors, it would be 
> interesting to have a processor validating CSV formatted flow files against a 
> user-specified schema.
> Flow file validated against schema would be routed to "valid" relationship 
> although flow file not validated against schema would be routed to "invalid" 
> relationship.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi issue #476: NIFI-1942 Processor to validate CSV against user-supplied s...

[pvillard31]

Github user pvillard31 commented on the issue:

https://github.com/apache/nifi/pull/476
  
Hey @JPercivall, I think I've addressed most of your comments:
- changed log level
- fixed decrementation (was not related to header but rather to 'finally' 
in 'while' loop)
- strategy naming and description
- fixed first line handling and added a unit test for that and to confirm 
Unique() behavior when validating line by line
- changed exception catching

It remains what you observed when displaying content of flow files after 
being processed by the processor. I've reproduced your observation but I didn't 
find any explanation. By any chance, do you know if there are some specific 
encoding related to the UI display? (I remember some discussions regarding how 
is processed the carriage return (shift + enter instead of \n) when used in a 
property in some processors) If you haves ideas, let me know!

Thanks.


---
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-2508) Revert to using getKeyStorePassword() for key-password in AbstractKafkaProcessor

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2508:
--

Github user olegz closed the pull request at:

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


> Revert to using getKeyStorePassword() for key-password in 
> AbstractKafkaProcessor
> 
>
> Key: NIFI-2508
> URL: https://issues.apache.org/jira/browse/NIFI-2508
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Oleg Zhurakousky
>Assignee: Oleg Zhurakousky
>Priority: Blocker
> Fix For: 0.8.0
>
>
> Current NIFI build for 0.x is broken due to the SSL changes in Kafka 
> processors where it is using an _getKeyPassword()_ operation only available 
> in 1.0. We need to fall back on _getKeyStorePassword()_.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi pull request #804: NIFI-2508 fixed compilation errors in AbstractKafkaP...

[olegz]

Github user olegz closed the pull request at:

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


---
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-2503) Backport PostHTTP SSL Protocol fix to 0.x branch

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2503:
--

Github user pvillard31 commented on the issue:

https://github.com/apache/nifi/pull/811
  
@jskora I merged to 0.x, thanks. Could you close this PR manually?


> Backport PostHTTP SSL Protocol fix to 0.x branch
> 
>
> Key: NIFI-2503
> URL: https://issues.apache.org/jira/browse/NIFI-2503
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core Framework
>Affects Versions: 0.7.0
>Reporter: Joe Skora
>Assignee: Joe Skora
>Priority: Critical
> Fix For: 0.8.0
>
>
> PostHTTP in the 0.x branch still has the hardcoded protocol version that 
> NIFI-1688 / [PR-624|https://github.com/apache/nifi/pull/624] fixed in the 1.0 
> branch.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2503) Backport PostHTTP SSL Protocol fix to 0.x branch

[ASF subversion and git services (JIRA)]

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

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

Commit 24c0c111343d40188bf8b2de06ebeb39d1cccd88 in nifi's branch refs/heads/0.x 
from [~alopresto]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=24c0c11 ]

NIFI-2503 Backport PostHTTP SSL Protocol fix to 0.x branch

This closes #811.


> Backport PostHTTP SSL Protocol fix to 0.x branch
> 
>
> Key: NIFI-2503
> URL: https://issues.apache.org/jira/browse/NIFI-2503
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core Framework
>Affects Versions: 0.7.0
>Reporter: Joe Skora
>Assignee: Joe Skora
>Priority: Critical
> Fix For: 0.8.0
>
>
> PostHTTP in the 0.x branch still has the hardcoded protocol version that 
> NIFI-1688 / [PR-624|https://github.com/apache/nifi/pull/624] fixed in the 1.0 
> branch.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi pull request #753: NIFI-2299 Add standard services api access for scrip...

[joewitt]

Github user joewitt closed the pull request at:

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


---
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-2299) Add standard services API dependency to Scripting Processors

[Mark Payne (JIRA)]

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

Mark Payne commented on NIFI-2299:
--

This looks good. I've merged to master for 1.0.0. Thanks!

> Add standard services API dependency to Scripting Processors   
> ---
>
> Key: NIFI-2299
> URL: https://issues.apache.org/jira/browse/NIFI-2299
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.7.0, 0.6.1
>Reporter: sumanth chinthagunta
>Assignee: Joseph Witt
>  Labels: Scripts, groovy
> Fix For: 1.0.0
>
>
> Scripting Processors cannot used Controller Services such as 
> *DistributedMapCacheClientService* etc, as required dependencies are missing 
> for *ExecuteScript* Nar. By adding following dependencies we can open new 
> possibilities for Scripting Processors.  
> Add this dependency to 
> nifi/nifi-nar-bundles/nifi-scripting-bundle/nifi-scripting-nar/pom.xml
> {code}
> 
> org.apache.nifi
> nifi-standard-services-api-nar
> nar
> 
> {code}
> Add this dependency to 
> nifi/nifi-nar-bundles/nifi-scripting-bundle/nifi-scripting-processors/pom.xml
> {code}
> 
> org.apache.nifi
> nifi-distributed-cache-client-service-api
> 
> {code}
> Then we can create scripting processor like:
> {code}
> import org.apache.nifi.controller.ControllerService
> import com.crossbusiness.nifi.processors.StringSerDe
> final StringSerDe stringSerDe = new StringSerDe();
> def lookup = context.controllerServiceLookup
> def cacheServiceName = DistributedMapCacheClientServiceName.value
> log.error  "cacheServiceName: ${cacheServiceName}"
> def cacheServiceId = 
> lookup.getControllerServiceIdentifiers(ControllerService).find {
> cs -> lookup.getControllerServiceName(cs) == cacheServiceName
> }
> log.error  "cacheServiceId:  ${cacheServiceId}"
> def cache = lookup.getControllerService(cacheServiceId)
> log.error cache.get("aaa", stringSerDe, stringSerDe )
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-2299) Add standard services API dependency to Scripting Processors

[Mark Payne (JIRA)]

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

Mark Payne updated NIFI-2299:
-
Fix Version/s: (was: 1.1.0)
   1.0.0

> Add standard services API dependency to Scripting Processors   
> ---
>
> Key: NIFI-2299
> URL: https://issues.apache.org/jira/browse/NIFI-2299
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.7.0, 0.6.1
>Reporter: sumanth chinthagunta
>Assignee: Joseph Witt
>  Labels: Scripts, groovy
> Fix For: 1.0.0
>
>
> Scripting Processors cannot used Controller Services such as 
> *DistributedMapCacheClientService* etc, as required dependencies are missing 
> for *ExecuteScript* Nar. By adding following dependencies we can open new 
> possibilities for Scripting Processors.  
> Add this dependency to 
> nifi/nifi-nar-bundles/nifi-scripting-bundle/nifi-scripting-nar/pom.xml
> {code}
> 
> org.apache.nifi
> nifi-standard-services-api-nar
> nar
> 
> {code}
> Add this dependency to 
> nifi/nifi-nar-bundles/nifi-scripting-bundle/nifi-scripting-processors/pom.xml
> {code}
> 
> org.apache.nifi
> nifi-distributed-cache-client-service-api
> 
> {code}
> Then we can create scripting processor like:
> {code}
> import org.apache.nifi.controller.ControllerService
> import com.crossbusiness.nifi.processors.StringSerDe
> final StringSerDe stringSerDe = new StringSerDe();
> def lookup = context.controllerServiceLookup
> def cacheServiceName = DistributedMapCacheClientServiceName.value
> log.error  "cacheServiceName: ${cacheServiceName}"
> def cacheServiceId = 
> lookup.getControllerServiceIdentifiers(ControllerService).find {
> cs -> lookup.getControllerServiceName(cs) == cacheServiceName
> }
> log.error  "cacheServiceId:  ${cacheServiceId}"
> def cache = lookup.getControllerService(cacheServiceId)
> log.error cache.get("aaa", stringSerDe, stringSerDe )
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-2299) Add standard services API dependency to Scripting Processors

[Mark Payne (JIRA)]

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

Mark Payne updated NIFI-2299:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Add standard services API dependency to Scripting Processors   
> ---
>
> Key: NIFI-2299
> URL: https://issues.apache.org/jira/browse/NIFI-2299
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.7.0, 0.6.1
>Reporter: sumanth chinthagunta
>Assignee: Joseph Witt
>  Labels: Scripts, groovy
> Fix For: 1.0.0
>
>
> Scripting Processors cannot used Controller Services such as 
> *DistributedMapCacheClientService* etc, as required dependencies are missing 
> for *ExecuteScript* Nar. By adding following dependencies we can open new 
> possibilities for Scripting Processors.  
> Add this dependency to 
> nifi/nifi-nar-bundles/nifi-scripting-bundle/nifi-scripting-nar/pom.xml
> {code}
> 
> org.apache.nifi
> nifi-standard-services-api-nar
> nar
> 
> {code}
> Add this dependency to 
> nifi/nifi-nar-bundles/nifi-scripting-bundle/nifi-scripting-processors/pom.xml
> {code}
> 
> org.apache.nifi
> nifi-distributed-cache-client-service-api
> 
> {code}
> Then we can create scripting processor like:
> {code}
> import org.apache.nifi.controller.ControllerService
> import com.crossbusiness.nifi.processors.StringSerDe
> final StringSerDe stringSerDe = new StringSerDe();
> def lookup = context.controllerServiceLookup
> def cacheServiceName = DistributedMapCacheClientServiceName.value
> log.error  "cacheServiceName: ${cacheServiceName}"
> def cacheServiceId = 
> lookup.getControllerServiceIdentifiers(ControllerService).find {
> cs -> lookup.getControllerServiceName(cs) == cacheServiceName
> }
> log.error  "cacheServiceId:  ${cacheServiceId}"
> def cache = lookup.getControllerService(cacheServiceId)
> log.error cache.get("aaa", stringSerDe, stringSerDe )
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2535) SSL context service property in Publish/ConsumeKafka is causing clustering issue

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2535:
---

moved to 1.0.  This either needs to be triaged as not critical for 1.0 or 
addressed.

> SSL context service property in Publish/ConsumeKafka is causing clustering 
> issue 
> -
>
> Key: NIFI-2535
> URL: https://issues.apache.org/jira/browse/NIFI-2535
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Haimo Liu
>Priority: Critical
> Fix For: 1.0.0
>
>
> NIFI build Aug.9th
> I have a flow with the new kafka processors (publish, consume). it seems like 
> the newly added SSL context service property is causing clustering issue (one 
> of the nodes cannot join cluster), logs below (tried to copy the flow.xml.gz 
> file from node 1 to the other nodes so that they are completely identical, 
> doesn't fix the issue):
> 2016-08-09 16:52:38,893 INFO [Reconnect to Cluster] 
> o.a.n.c.c.node.NodeClusterCoordinator Resetting cluster node statuses from 
> {localhost:8893=NodeConnectionStatus[state=CONNECTED, roles=[Cluster 
> Coordinator], updateId=8], 
> localhost:8891=NodeConnectionStatus[state=CONNECTING, roles=[], updateId=33], 
> localhost:8892=NodeConnectionStatus[state=CONNECTED, roles=[Cluster 
> Coordinator], updateId=4]} to 
> {localhost:8893=NodeConnectionStatus[state=CONNECTED, roles=[Cluster 
> Coordinator], updateId=30], 
> localhost:8891=NodeConnectionStatus[state=CONNECTING, roles=[], updateId=33], 
> localhost:8892=NodeConnectionStatus[state=CONNECTED, roles=[Primary Node], 
> updateId=32]}
> 2016-08-09 16:52:40,071 ERROR [Reconnect to Cluster] 
> o.a.nifi.controller.StandardFlowService Handling reconnection request failed 
> due to: org.apache.nifi.controller.UninheritableFlowException: Failed to 
> connect node to cluster because local flow is different than cluster flow.
> org.apache.nifi.controller.UninheritableFlowException: Failed to connect node 
> to cluster because local flow is different than cluster flow.
>   at 
> org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:863)
>  [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
>   at 
> org.apache.nifi.controller.StandardFlowService.handleReconnectionRequest(StandardFlowService.java:589)
>  [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
>   at 
> org.apache.nifi.controller.StandardFlowService.access$300(StandardFlowService.java:97)
>  [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
>   at 
> org.apache.nifi.controller.StandardFlowService$2.run(StandardFlowService.java:401)
>  [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
>   at java.lang.Thread.run(Thread.java:745) [na:1.8.0_77]
> Caused by: org.apache.nifi.controller.UninheritableFlowException: Proposed 
> configuration is not inheritable by the flow controller because of flow 
> differences: Found difference in Flows:
> Local Fingerprint:   
> he.nifi.processors.kafka.pubsub.Partitioners$RoundRobinPartitionersasl.kerberos.service.nameNO_VALUEssl.context.serviceNO_VALUEtopicWARNINGsuccess04015ca0-0156-1000--4224fe88org.apache.nifi.pr
> Cluster Fingerprint: 
> he.nifi.processors.kafka.pubsub.Partitioners$RoundRobinPartitionersasl.kerberos.service.nameNO_VALUEtopicWARNINGsuccess04015ca0-0156-1000--4224fe88org.apache.nifi.processors.standard.GenerateF
>   at 
> org.apache.nifi.controller.StandardFlowSynchronizer.sync(StandardFlowSynchronizer.java:240)
>  ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
>   at 
> org.apache.nifi.controller.FlowController.synchronize(FlowController.java:1429)
>  ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
>   at 
> org.apache.nifi.persistence.StandardXMLFlowConfigurationDAO.load(StandardXMLFlowConfigurationDAO.java:81)
>  ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
>   at 
> org.apache.nifi.controller.StandardFlowService.loadFromBytes(StandardFlowService.java:668)
>  [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
>   at 
> org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:839)
>  [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
>   ... 4 common frames omitted
> 2016-08-09 16:52:40,071 INFO [Reconnect to Cluster] 
> o.a.n.c.c.node.NodeClusterCoordinator localhost:8891 requested disconnection 
> from cluster due to org.apache.nifi.controller.UninheritableFlowException: 
> Failed to connect node to cluster because local flow is different than 
> cluster flow.
> 2016-08-09 16:52:40,071 INFO [Reconnect to Cluster] 
> o.a.n.c.c.node.NodeClusterCoordinator Status of localhost:8891 changed from 
> 

[jira] [Commented] (NIFI-2299) Add standard services API dependency to Scripting Processors

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2299:
---

[~markap14] tested this and found that it was all working as expected.  

> Add standard services API dependency to Scripting Processors   
> ---
>
> Key: NIFI-2299
> URL: https://issues.apache.org/jira/browse/NIFI-2299
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.7.0, 0.6.1
>Reporter: sumanth chinthagunta
>Assignee: Joseph Witt
>  Labels: Scripts, groovy
> Fix For: 1.1.0
>
>
> Scripting Processors cannot used Controller Services such as 
> *DistributedMapCacheClientService* etc, as required dependencies are missing 
> for *ExecuteScript* Nar. By adding following dependencies we can open new 
> possibilities for Scripting Processors.  
> Add this dependency to 
> nifi/nifi-nar-bundles/nifi-scripting-bundle/nifi-scripting-nar/pom.xml
> {code}
> 
> org.apache.nifi
> nifi-standard-services-api-nar
> nar
> 
> {code}
> Add this dependency to 
> nifi/nifi-nar-bundles/nifi-scripting-bundle/nifi-scripting-processors/pom.xml
> {code}
> 
> org.apache.nifi
> nifi-distributed-cache-client-service-api
> 
> {code}
> Then we can create scripting processor like:
> {code}
> import org.apache.nifi.controller.ControllerService
> import com.crossbusiness.nifi.processors.StringSerDe
> final StringSerDe stringSerDe = new StringSerDe();
> def lookup = context.controllerServiceLookup
> def cacheServiceName = DistributedMapCacheClientServiceName.value
> log.error  "cacheServiceName: ${cacheServiceName}"
> def cacheServiceId = 
> lookup.getControllerServiceIdentifiers(ControllerService).find {
> cs -> lookup.getControllerServiceName(cs) == cacheServiceName
> }
> log.error  "cacheServiceId:  ${cacheServiceId}"
> def cache = lookup.getControllerService(cacheServiceId)
> log.error cache.get("aaa", stringSerDe, stringSerDe )
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (NIFI-2522) Controller Service scoping appears to make faulty assumption about parent identifier

[Joseph Witt (JIRA)]

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

Joseph Witt resolved NIFI-2522.
---
   Resolution: Not A Problem
Fix Version/s: (was: 1.0.0)

> Controller Service scoping appears to make faulty assumption about parent 
> identifier
> 
>
> Key: NIFI-2522
> URL: https://issues.apache.org/jira/browse/NIFI-2522
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Joseph Witt
>Assignee: Mark Payne
>Priority: Critical
>
> In testing the InvokeScriptedProcessor support for calling controller 
> services I found that the controller service scope was tied to the processor 
> the script was contained in rather than the process group.  Perhaps it is 
> pulling the wrong parent ID rather than ensuring it gets the parent process 
> group's id.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (NIFI-2535) SSL context service property in Pub/SubKafka processors is causing clustering issue

[Haimo Liu (JIRA)]

Haimo Liu created NIFI-2535:
---

 Summary: SSL context service property in Pub/SubKafka processors 
is causing clustering issue 
 Key: NIFI-2535
 URL: https://issues.apache.org/jira/browse/NIFI-2535
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core Framework
Reporter: Haimo Liu
Priority: Critical


NIFI build Aug.9th

I have a flow with the new kafka processors (publish, consume). it seems like 
the newly added SSL context service property is causing clustering issue (one 
of the nodes cannot join cluster), logs below (tried to copy the flow.xml.gz 
file from node 1 to the other nodes so that they are completely identical, 
doesn't fix the issue):

2016-08-09 16:52:38,893 INFO [Reconnect to Cluster] 
o.a.n.c.c.node.NodeClusterCoordinator Resetting cluster node statuses from 
{localhost:8893=NodeConnectionStatus[state=CONNECTED, roles=[Cluster 
Coordinator], updateId=8], 
localhost:8891=NodeConnectionStatus[state=CONNECTING, roles=[], updateId=33], 
localhost:8892=NodeConnectionStatus[state=CONNECTED, roles=[Cluster 
Coordinator], updateId=4]} to 
{localhost:8893=NodeConnectionStatus[state=CONNECTED, roles=[Cluster 
Coordinator], updateId=30], 
localhost:8891=NodeConnectionStatus[state=CONNECTING, roles=[], updateId=33], 
localhost:8892=NodeConnectionStatus[state=CONNECTED, roles=[Primary Node], 
updateId=32]}
2016-08-09 16:52:40,071 ERROR [Reconnect to Cluster] 
o.a.nifi.controller.StandardFlowService Handling reconnection request failed 
due to: org.apache.nifi.controller.UninheritableFlowException: Failed to 
connect node to cluster because local flow is different than cluster flow.
org.apache.nifi.controller.UninheritableFlowException: Failed to connect node 
to cluster because local flow is different than cluster flow.
at 
org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:863)
 [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at 
org.apache.nifi.controller.StandardFlowService.handleReconnectionRequest(StandardFlowService.java:589)
 [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at 
org.apache.nifi.controller.StandardFlowService.access$300(StandardFlowService.java:97)
 [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at 
org.apache.nifi.controller.StandardFlowService$2.run(StandardFlowService.java:401)
 [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_77]
Caused by: org.apache.nifi.controller.UninheritableFlowException: Proposed 
configuration is not inheritable by the flow controller because of flow 
differences: Found difference in Flows:
Local Fingerprint:   
he.nifi.processors.kafka.pubsub.Partitioners$RoundRobinPartitionersasl.kerberos.service.nameNO_VALUEssl.context.serviceNO_VALUEtopicWARNINGsuccess04015ca0-0156-1000--4224fe88org.apache.nifi.pr
Cluster Fingerprint: 
he.nifi.processors.kafka.pubsub.Partitioners$RoundRobinPartitionersasl.kerberos.service.nameNO_VALUEtopicWARNINGsuccess04015ca0-0156-1000--4224fe88org.apache.nifi.processors.standard.GenerateF
at 
org.apache.nifi.controller.StandardFlowSynchronizer.sync(StandardFlowSynchronizer.java:240)
 ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at 
org.apache.nifi.controller.FlowController.synchronize(FlowController.java:1429) 
~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at 
org.apache.nifi.persistence.StandardXMLFlowConfigurationDAO.load(StandardXMLFlowConfigurationDAO.java:81)
 ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at 
org.apache.nifi.controller.StandardFlowService.loadFromBytes(StandardFlowService.java:668)
 [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at 
org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:839)
 [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
... 4 common frames omitted
2016-08-09 16:52:40,071 INFO [Reconnect to Cluster] 
o.a.n.c.c.node.NodeClusterCoordinator localhost:8891 requested disconnection 
from cluster due to org.apache.nifi.controller.UninheritableFlowException: 
Failed to connect node to cluster because local flow is different than cluster 
flow.
2016-08-09 16:52:40,071 INFO [Reconnect to Cluster] 
o.a.n.c.c.node.NodeClusterCoordinator Status of localhost:8891 changed from 
NodeConnectionStatus[state=CONNECTING, roles=[], updateId=33] to 
NodeConnectionStatus[state=DISCONNECTED, Disconnect Code=Node's Flow did not 
Match Cluster Flow, Disconnect 
Reason=org.apache.nifi.controller.UninheritableFlowException: Failed to connect 
node to cluster because local flow is different than cluster flow., roles=[], 
updateId=33]
2016-08-09 16:52:40,072 INFO [Reconnect to Cluster] 
o.a.n.c.c.node.NodeClusterCoordinator Determined that Cluster Coordinator is 

[jira] [Updated] (NIFI-2535) SSL context service property in Publish/ConsumeKafka is causing clustering issue

[Haimo Liu (JIRA)]

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

Haimo Liu updated NIFI-2535:

Summary: SSL context service property in Publish/ConsumeKafka is causing 
clustering issue   (was: SSL context service property in Pub/SubKafka 
processors is causing clustering issue )

> SSL context service property in Publish/ConsumeKafka is causing clustering 
> issue 
> -
>
> Key: NIFI-2535
> URL: https://issues.apache.org/jira/browse/NIFI-2535
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Haimo Liu
>Priority: Critical
>
> NIFI build Aug.9th
> I have a flow with the new kafka processors (publish, consume). it seems like 
> the newly added SSL context service property is causing clustering issue (one 
> of the nodes cannot join cluster), logs below (tried to copy the flow.xml.gz 
> file from node 1 to the other nodes so that they are completely identical, 
> doesn't fix the issue):
> 2016-08-09 16:52:38,893 INFO [Reconnect to Cluster] 
> o.a.n.c.c.node.NodeClusterCoordinator Resetting cluster node statuses from 
> {localhost:8893=NodeConnectionStatus[state=CONNECTED, roles=[Cluster 
> Coordinator], updateId=8], 
> localhost:8891=NodeConnectionStatus[state=CONNECTING, roles=[], updateId=33], 
> localhost:8892=NodeConnectionStatus[state=CONNECTED, roles=[Cluster 
> Coordinator], updateId=4]} to 
> {localhost:8893=NodeConnectionStatus[state=CONNECTED, roles=[Cluster 
> Coordinator], updateId=30], 
> localhost:8891=NodeConnectionStatus[state=CONNECTING, roles=[], updateId=33], 
> localhost:8892=NodeConnectionStatus[state=CONNECTED, roles=[Primary Node], 
> updateId=32]}
> 2016-08-09 16:52:40,071 ERROR [Reconnect to Cluster] 
> o.a.nifi.controller.StandardFlowService Handling reconnection request failed 
> due to: org.apache.nifi.controller.UninheritableFlowException: Failed to 
> connect node to cluster because local flow is different than cluster flow.
> org.apache.nifi.controller.UninheritableFlowException: Failed to connect node 
> to cluster because local flow is different than cluster flow.
>   at 
> org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:863)
>  [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
>   at 
> org.apache.nifi.controller.StandardFlowService.handleReconnectionRequest(StandardFlowService.java:589)
>  [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
>   at 
> org.apache.nifi.controller.StandardFlowService.access$300(StandardFlowService.java:97)
>  [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
>   at 
> org.apache.nifi.controller.StandardFlowService$2.run(StandardFlowService.java:401)
>  [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
>   at java.lang.Thread.run(Thread.java:745) [na:1.8.0_77]
> Caused by: org.apache.nifi.controller.UninheritableFlowException: Proposed 
> configuration is not inheritable by the flow controller because of flow 
> differences: Found difference in Flows:
> Local Fingerprint:   
> he.nifi.processors.kafka.pubsub.Partitioners$RoundRobinPartitionersasl.kerberos.service.nameNO_VALUEssl.context.serviceNO_VALUEtopicWARNINGsuccess04015ca0-0156-1000--4224fe88org.apache.nifi.pr
> Cluster Fingerprint: 
> he.nifi.processors.kafka.pubsub.Partitioners$RoundRobinPartitionersasl.kerberos.service.nameNO_VALUEtopicWARNINGsuccess04015ca0-0156-1000--4224fe88org.apache.nifi.processors.standard.GenerateF
>   at 
> org.apache.nifi.controller.StandardFlowSynchronizer.sync(StandardFlowSynchronizer.java:240)
>  ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
>   at 
> org.apache.nifi.controller.FlowController.synchronize(FlowController.java:1429)
>  ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
>   at 
> org.apache.nifi.persistence.StandardXMLFlowConfigurationDAO.load(StandardXMLFlowConfigurationDAO.java:81)
>  ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
>   at 
> org.apache.nifi.controller.StandardFlowService.loadFromBytes(StandardFlowService.java:668)
>  [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
>   at 
> org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:839)
>  [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
>   ... 4 common frames omitted
> 2016-08-09 16:52:40,071 INFO [Reconnect to Cluster] 
> o.a.n.c.c.node.NodeClusterCoordinator localhost:8891 requested disconnection 
> from cluster due to org.apache.nifi.controller.UninheritableFlowException: 
> Failed to connect node to cluster because local flow is different than 
> cluster flow.
> 2016-08-09 16:52:40,071 INFO [Reconnect to Cluster] 
> o.a.n.c.c.node.NodeClusterCoordinator Status of 

[jira] [Resolved] (NIFI-2527) Update Apache NiFi Twitter profile

[Joseph Witt (JIRA)]

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

Joseph Witt resolved NIFI-2527.
---
Resolution: Fixed

> Update Apache NiFi Twitter profile
> --
>
> Key: NIFI-2527
> URL: https://issues.apache.org/jira/browse/NIFI-2527
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Documentation & Website
>Reporter: Rob Moran
>Assignee: Joseph Witt
>Priority: Minor
> Fix For: 1.0.0
>
> Attachments: large-format-sample.png, small-format-sample.png, 
> twitter-header.jpg, twitter-profile.png
>
>
> The attached graphics can be used to update the Apache NiFi Twitter profile 
> and header photos.
> The background imagery includes colors used in the UI redesign. I would like 
> to continue using this imagery in various parts of the UI and for other 
> Apache NiFi web presences to begin to establish a unique visual identity.
> Two samples are attached to show how the updated Twitter profile will look.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2516) Extract version info into parent pom, upgrade to commons-io 2.5

[ASF subversion and git services (JIRA)]

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

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

Commit 2dc094765d2b7393834ec649a5b35fb374b315fe in nifi's branch 
refs/heads/master from [~bryanrosan...@gmail.com]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=2dc0947 ]

NIFI-2516 - Extract version info into parent pom, upgrade to commons-io 2.5
NIFI-2516 - Removing slf4j-api, version from slf4j-log4j12

This closes #809.


> Extract version info into parent pom, upgrade to commons-io 2.5
> ---
>
> Key: NIFI-2516
> URL: https://issues.apache.org/jira/browse/NIFI-2516
> Project: Apache NiFi
>  Issue Type: Sub-task
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
>
> Parent pom at root of nifi project should contain the dependency versions.
> commons-io 2.5 is required for its BoundedReader which facilitates putting a 
> cap on the amount of bytes read during the payload deserialization.  This is 
> useful in avoiding an arbitrarily large payload sent by a malicious client.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi pull request #809: NIFI-2516 - Extract version info into parent pom, up...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2501) UI - Process Group configuration requires write permissions

[Matt Gilman (JIRA)]

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

Matt Gilman reassigned NIFI-2501:
-

Assignee: Matt Gilman

> UI - Process Group configuration requires write permissions
> ---
>
> Key: NIFI-2501
> URL: https://issues.apache.org/jira/browse/NIFI-2501
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Matt Gilman
> Fix For: 1.0.0
>
>
> Since Controller Services are accessed through the Process Group 
> configuration, we need to allow users without read/write permissions to 
> access that dialog in case they do have permissions to a controller service 
> in there. The Controller settings dialog is already updated to support this 
> case.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2516) Extract version info into parent pom, upgrade to commons-io 2.5

[Pierre Villard (JIRA)]

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

Pierre Villard commented on NIFI-2516:
--

Merged into master, thanks [~bryanrosan...@gmail.com]!

> Extract version info into parent pom, upgrade to commons-io 2.5
> ---
>
> Key: NIFI-2516
> URL: https://issues.apache.org/jira/browse/NIFI-2516
> Project: Apache NiFi
>  Issue Type: Sub-task
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
> Fix For: 1.0.0
>
>
> Parent pom at root of nifi project should contain the dependency versions.
> commons-io 2.5 is required for its BoundedReader which facilitates putting a 
> cap on the amount of bytes read during the payload deserialization.  This is 
> useful in avoiding an arbitrarily large payload sent by a malicious client.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (NIFI-2516) Extract version info into parent pom, upgrade to commons-io 2.5

[Pierre Villard (JIRA)]

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

Pierre Villard resolved NIFI-2516.
--
   Resolution: Fixed
Fix Version/s: 1.0.0

> Extract version info into parent pom, upgrade to commons-io 2.5
> ---
>
> Key: NIFI-2516
> URL: https://issues.apache.org/jira/browse/NIFI-2516
> Project: Apache NiFi
>  Issue Type: Sub-task
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
> Fix For: 1.0.0
>
>
> Parent pom at root of nifi project should contain the dependency versions.
> commons-io 2.5 is required for its BoundedReader which facilitates putting a 
> cap on the amount of bytes read during the payload deserialization.  This is 
> useful in avoiding an arbitrarily large payload sent by a malicious client.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2516) Extract version info into parent pom, upgrade to commons-io 2.5

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2516:
--

Github user asfgit closed the pull request at:

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


> Extract version info into parent pom, upgrade to commons-io 2.5
> ---
>
> Key: NIFI-2516
> URL: https://issues.apache.org/jira/browse/NIFI-2516
> Project: Apache NiFi
>  Issue Type: Sub-task
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
>
> Parent pom at root of nifi project should contain the dependency versions.
> commons-io 2.5 is required for its BoundedReader which facilitates putting a 
> cap on the amount of bytes read during the payload deserialization.  This is 
> useful in avoiding an arbitrarily large payload sent by a malicious client.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2527) Update Apache NiFi Twitter profile

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2527:
---

will go ahead and push these onto twitter.

> Update Apache NiFi Twitter profile
> --
>
> Key: NIFI-2527
> URL: https://issues.apache.org/jira/browse/NIFI-2527
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Documentation & Website
>Reporter: Rob Moran
>Assignee: Joseph Witt
>Priority: Minor
> Fix For: 1.0.0
>
> Attachments: large-format-sample.png, small-format-sample.png, 
> twitter-header.jpg, twitter-profile.png
>
>
> The attached graphics can be used to update the Apache NiFi Twitter profile 
> and header photos.
> The background imagery includes colors used in the UI redesign. I would like 
> to continue using this imagery in various parts of the UI and for other 
> Apache NiFi web presences to begin to establish a unique visual identity.
> Two samples are attached to show how the updated Twitter profile will look.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2516) Extract version info into parent pom, upgrade to commons-io 2.5

[ASF subversion and git services (JIRA)]

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

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

Commit 2dc094765d2b7393834ec649a5b35fb374b315fe in nifi's branch 
refs/heads/master from [~bryanrosan...@gmail.com]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=2dc0947 ]

NIFI-2516 - Extract version info into parent pom, upgrade to commons-io 2.5
NIFI-2516 - Removing slf4j-api, version from slf4j-log4j12

This closes #809.


> Extract version info into parent pom, upgrade to commons-io 2.5
> ---
>
> Key: NIFI-2516
> URL: https://issues.apache.org/jira/browse/NIFI-2516
> Project: Apache NiFi
>  Issue Type: Sub-task
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
>
> Parent pom at root of nifi project should contain the dependency versions.
> commons-io 2.5 is required for its BoundedReader which facilitates putting a 
> cap on the amount of bytes read during the payload deserialization.  This is 
> useful in avoiding an arbitrarily large payload sent by a malicious client.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2499) Update User Guide screenshots and text for new UI

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2499:
---

thanks for fixing up the PR.  I added the JIRA ref to commit message and edited 
the image paths to find all the great images you built.  Thanks!

+1 merged to master.

> Update User Guide screenshots and text for new UI
> -
>
> Key: NIFI-2499
> URL: https://issues.apache.org/jira/browse/NIFI-2499
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Sarah Olson
>Assignee: Sarah Olson
> Fix For: 1.0.0
>
>
> Update User Guide screenshots and text for new UI. 
> Added one or two additional screenshots as well. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (NIFI-2499) Update User Guide screenshots and text for new UI

[Joseph Witt (JIRA)]

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

Joseph Witt resolved NIFI-2499.
---
Resolution: Fixed

> Update User Guide screenshots and text for new UI
> -
>
> Key: NIFI-2499
> URL: https://issues.apache.org/jira/browse/NIFI-2499
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Sarah Olson
>Assignee: Sarah Olson
> Fix For: 1.0.0
>
>
> Update User Guide screenshots and text for new UI. 
> Added one or two additional screenshots as well. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2499) Update User Guide screenshots and text for new UI

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2499 This closes #825. Updated User Guide screen shots and text to reflect 
the new UI. Added two new screenshots as well.


> Update User Guide screenshots and text for new UI
> -
>
> Key: NIFI-2499
> URL: https://issues.apache.org/jira/browse/NIFI-2499
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Sarah Olson
>Assignee: Sarah Olson
> Fix For: 1.0.0
>
>
> Update User Guide screenshots and text for new UI. 
> Added one or two additional screenshots as well. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2499) Update User Guide screenshots and text for new UI

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2499 edited image paths in asciidoc


> Update User Guide screenshots and text for new UI
> -
>
> Key: NIFI-2499
> URL: https://issues.apache.org/jira/browse/NIFI-2499
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Sarah Olson
>Assignee: Sarah Olson
> Fix For: 1.0.0
>
>
> Update User Guide screenshots and text for new UI. 
> Added one or two additional screenshots as well. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi pull request #825: Updated User Guide

[asfgit]

Github user asfgit closed the pull request at:

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


---
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] [Resolved] (NIFI-2511) Bulletins do not seem to be working in a consistent manner

[Matt Gilman (JIRA)]

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

Matt Gilman resolved NIFI-2511.
---
Resolution: Fixed

> Bulletins do not seem to be working in a consistent manner
> --
>
> Key: NIFI-2511
> URL: https://issues.apache.org/jira/browse/NIFI-2511
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework, Core UI
>Affects Versions: 1.0.0-Beta
>Reporter: Aldrin Piri
>Assignee: Matt Gilman
> Fix For: 1.0.0
>
>
> Process Groups do not seem to have any indication that there are bulletins 
> contained within them.
> The top right bulletin indicator is seemingly only for system level events 
> but is different from the view that used to be provided with 0.x 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2511) Bulletins do not seem to be working in a consistent manner

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2511:
--

Github user asfgit closed the pull request at:

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


> Bulletins do not seem to be working in a consistent manner
> --
>
> Key: NIFI-2511
> URL: https://issues.apache.org/jira/browse/NIFI-2511
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework, Core UI
>Affects Versions: 1.0.0-Beta
>Reporter: Aldrin Piri
>Assignee: Matt Gilman
> Fix For: 1.0.0
>
>
> Process Groups do not seem to have any indication that there are bulletins 
> contained within them.
> The top right bulletin indicator is seemingly only for system level events 
> but is different from the view that used to be provided with 0.x 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2511) Bulletins do not seem to be working in a consistent manner

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2511: - Ensuring Process Group bulletins are bubbling up as expected.

This closes #822.

Signed-off-by: Bryan Bende 


> Bulletins do not seem to be working in a consistent manner
> --
>
> Key: NIFI-2511
> URL: https://issues.apache.org/jira/browse/NIFI-2511
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework, Core UI
>Affects Versions: 1.0.0-Beta
>Reporter: Aldrin Piri
>Assignee: Matt Gilman
> Fix For: 1.0.0
>
>
> Process Groups do not seem to have any indication that there are bulletins 
> contained within them.
> The top right bulletin indicator is seemingly only for system level events 
> but is different from the view that used to be provided with 0.x 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi pull request #822: Ensuring bulletins bubble up to ancestor Process Gro...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #825: Updated User Guide

[joewitt]

Github user joewitt commented on the issue:

https://github.com/apache/nifi/pull/825
  
@thesolson it looks great/quite close.  However, it appears all of the 
image:images/ refs are off.  I think they need to be just 'images:{imagename}' 
rather than the additional images/ path entry.


---
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-2507) PutS3Object should support Canned ACLs

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2507:
--

Github user asfgit closed the pull request at:

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


> PutS3Object should support Canned ACLs
> --
>
> Key: NIFI-2507
> URL: https://issues.apache.org/jira/browse/NIFI-2507
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 0.7.0
>Reporter: Tim Reardon
>Assignee: James Wing
>Priority: Minor
>
> In order to support cross-account scenarios, PutS3Object should support 
> specifying canned ACL's such as "bucket-owner-full-control".
> See 
> http://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2507) PutS3Object should support Canned ACLs

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2507 Added Canned ACL support to PutS3Object

This closes #801

Signed-off-by: James Wing 


> PutS3Object should support Canned ACLs
> --
>
> Key: NIFI-2507
> URL: https://issues.apache.org/jira/browse/NIFI-2507
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 0.7.0
>Reporter: Tim Reardon
>Assignee: James Wing
>Priority: Minor
>
> In order to support cross-account scenarios, PutS3Object should support 
> specifying canned ACL's such as "bucket-owner-full-control".
> See 
> http://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi pull request #801: NIFI-2507 Added Canned ACL support to PutS3Object

[asfgit]

Github user asfgit closed the pull request at:

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


---
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] [Comment Edited] (NIFI-2522) Controller Service scoping appears to make faulty assumption about parent identifier

[Mark Payne (JIRA)]

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

Mark Payne edited comment on NIFI-2522 at 8/9/16 8:21 PM:
--

[~joewitt] as far as I can tell, this is working properly. I was able to create 
a Controller Service as described in NIFI-2299, and it worked just as I 
expected.


was (Author: markap14):
[~joewitt] as far as I can tell, this is working properly. I was able to create 
a Controller Service as described in NIFI-2299, and it worked just as I 
expected it.

> Controller Service scoping appears to make faulty assumption about parent 
> identifier
> 
>
> Key: NIFI-2522
> URL: https://issues.apache.org/jira/browse/NIFI-2522
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Joseph Witt
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.0.0
>
>
> In testing the InvokeScriptedProcessor support for calling controller 
> services I found that the controller service scope was tied to the processor 
> the script was contained in rather than the process group.  Perhaps it is 
> pulling the wrong parent ID rather than ensuring it gets the parent process 
> group's id.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-2521) License and Notice - TestSNMPAgent classes appear to be copied from external sources

[Joseph Witt (JIRA)]

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

Joseph Witt updated NIFI-2521:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> License and Notice - TestSNMPAgent classes appear to be copied from external 
> sources
> 
>
> Key: NIFI-2521
> URL: https://issues.apache.org/jira/browse/NIFI-2521
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Witt
>Assignee: Joseph Witt
>Priority: Blocker
> Fix For: 1.0.0, 0.8.0
>
>
> TestSNMPAgentV1 and TestSNMPAgentV2c appear to be sourced at least in large 
> part from https://code.google.com/archive/p/springside-sub/
> TestSNMPAgentV3 appears to be sourced from  XYZ as found here 
> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-snmp-bundle/nifi-snmp-processors/src/test/java/org/apache/nifi/snmp/processors/TestSnmpAgentV3.java#L68.
> These classes should be completely removed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2521) License and Notice - TestSNMPAgent classes appear to be copied from external sources

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2521:
--

Github user asfgit closed the pull request at:

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


> License and Notice - TestSNMPAgent classes appear to be copied from external 
> sources
> 
>
> Key: NIFI-2521
> URL: https://issues.apache.org/jira/browse/NIFI-2521
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Witt
>Assignee: Joseph Witt
>Priority: Blocker
> Fix For: 1.0.0, 0.8.0
>
>
> TestSNMPAgentV1 and TestSNMPAgentV2c appear to be sourced at least in large 
> part from https://code.google.com/archive/p/springside-sub/
> TestSNMPAgentV3 appears to be sourced from  XYZ as found here 
> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-snmp-bundle/nifi-snmp-processors/src/test/java/org/apache/nifi/snmp/processors/TestSnmpAgentV3.java#L68.
> These classes should be completely removed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2521) License and Notice - TestSNMPAgent classes appear to be copied from external sources

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2521 This closes #815. removed test classes with questionable origin and 
licensing.


> License and Notice - TestSNMPAgent classes appear to be copied from external 
> sources
> 
>
> Key: NIFI-2521
> URL: https://issues.apache.org/jira/browse/NIFI-2521
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Witt
>Assignee: Joseph Witt
>Priority: Blocker
> Fix For: 1.0.0, 0.8.0
>
>
> TestSNMPAgentV1 and TestSNMPAgentV2c appear to be sourced at least in large 
> part from https://code.google.com/archive/p/springside-sub/
> TestSNMPAgentV3 appears to be sourced from  XYZ as found here 
> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-snmp-bundle/nifi-snmp-processors/src/test/java/org/apache/nifi/snmp/processors/TestSnmpAgentV3.java#L68.
> These classes should be completely removed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi pull request #815: NIFI-2521 removed test classes with questionable ori...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2521) License and Notice - TestSNMPAgent classes appear to be copied from external sources

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2521:
---

sounds good - i am comfortable with this.  Will merge to master and 0.x then 
close this JIRA.  Please make a new JIRA for 1.1 and 0.x to address providing 
new clean tests.  Thanks

> License and Notice - TestSNMPAgent classes appear to be copied from external 
> sources
> 
>
> Key: NIFI-2521
> URL: https://issues.apache.org/jira/browse/NIFI-2521
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Witt
>Assignee: Joseph Witt
>Priority: Blocker
> Fix For: 1.0.0, 0.8.0
>
>
> TestSNMPAgentV1 and TestSNMPAgentV2c appear to be sourced at least in large 
> part from https://code.google.com/archive/p/springside-sub/
> TestSNMPAgentV3 appears to be sourced from  XYZ as found here 
> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-snmp-bundle/nifi-snmp-processors/src/test/java/org/apache/nifi/snmp/processors/TestSnmpAgentV3.java#L68.
> These classes should be completely removed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (NIFI-2521) License and Notice - TestSNMPAgent classes appear to be copied from external sources

[Joseph Witt (JIRA)]

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

Joseph Witt reassigned NIFI-2521:
-

Assignee: Joseph Witt  (was: Pierre Villard)

> License and Notice - TestSNMPAgent classes appear to be copied from external 
> sources
> 
>
> Key: NIFI-2521
> URL: https://issues.apache.org/jira/browse/NIFI-2521
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Witt
>Assignee: Joseph Witt
>Priority: Blocker
> Fix For: 1.0.0, 0.8.0
>
>
> TestSNMPAgentV1 and TestSNMPAgentV2c appear to be sourced at least in large 
> part from https://code.google.com/archive/p/springside-sub/
> TestSNMPAgentV3 appears to be sourced from  XYZ as found here 
> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-snmp-bundle/nifi-snmp-processors/src/test/java/org/apache/nifi/snmp/processors/TestSnmpAgentV3.java#L68.
> These classes should be completely removed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2521) License and Notice - TestSNMPAgent classes appear to be copied from external sources

[Pierre Villard (JIRA)]

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

Pierre Villard commented on NIFI-2521:
--

[~joewitt] it clearly seems that there is more digging required from me to 
ensure we are safe here. Besides there is a unit test failing time to time. At 
this point, with releases coming, the safest way to move forward is to remove 
the tests. I'll submit a new PR shortly to address the tests of this bundle. In 
the meantime, the PR you submitted LGTM. +1

> License and Notice - TestSNMPAgent classes appear to be copied from external 
> sources
> 
>
> Key: NIFI-2521
> URL: https://issues.apache.org/jira/browse/NIFI-2521
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Witt
>Assignee: Pierre Villard
>Priority: Blocker
> Fix For: 1.0.0, 0.8.0
>
>
> TestSNMPAgentV1 and TestSNMPAgentV2c appear to be sourced at least in large 
> part from https://code.google.com/archive/p/springside-sub/
> TestSNMPAgentV3 appears to be sourced from  XYZ as found here 
> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-snmp-bundle/nifi-snmp-processors/src/test/java/org/apache/nifi/snmp/processors/TestSnmpAgentV3.java#L68.
> These classes should be completely removed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (NIFI-2526) Fix DN order, allow multiple standalone runs, standalone generate client certificates,

[Bryan Rosander (JIRA)]

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

Bryan Rosander reassigned NIFI-2526:


Assignee: Bryan Rosander

> Fix DN order, allow multiple standalone runs, standalone generate client 
> certificates, 
> ---
>
> Key: NIFI-2526
> URL: https://issues.apache.org/jira/browse/NIFI-2526
> Project: Apache NiFi
>  Issue Type: Sub-task
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
>
> NiFi authorization framework currently expects OU to come before CN, the tool 
> should reflect that by default.
> Standalone tool would be much more useful if you could keep running and 
> refining in the same directory with the same CA certificate.
> Standalone tool would be much more useful if it could also generate client 
> certificates.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-2475) UI - Update Policy page for adminstrators

[Matt Burgess (JIRA)]

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

Matt Burgess updated NIFI-2475:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> UI - Update Policy page for adminstrators
> -
>
> Key: NIFI-2475
> URL: https://issues.apache.org/jira/browse/NIFI-2475
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>Priority: Blocker
> Fix For: 1.0.0
>
>
> We need to update the Policy page to make it more clear that when updating 
> the list of users who can view or modify the policies of a component, we are 
> appending to the list of administrators not overriding it.
> This needs to be made obvious as it is different behavior then updating the 
> list of users who can view or modify a component as these policies override 
> the otherwise inherited policies.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2475) UI - Update Policy page for adminstrators

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2475: - Updating UI to better suggest that component specific 
administrators do not override higher level administrators.

This closes #813


> UI - Update Policy page for adminstrators
> -
>
> Key: NIFI-2475
> URL: https://issues.apache.org/jira/browse/NIFI-2475
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>Priority: Blocker
> Fix For: 1.0.0
>
>
> We need to update the Policy page to make it more clear that when updating 
> the list of users who can view or modify the policies of a component, we are 
> appending to the list of administrators not overriding it.
> This needs to be made obvious as it is different behavior then updating the 
> list of users who can view or modify a component as these policies override 
> the otherwise inherited policies.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi pull request #813: Updating UI to reflect administrator policies do not...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2475) UI - Update Policy page for adminstrators

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2475:
--

Github user asfgit closed the pull request at:

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


> UI - Update Policy page for adminstrators
> -
>
> Key: NIFI-2475
> URL: https://issues.apache.org/jira/browse/NIFI-2475
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>Priority: Blocker
> Fix For: 1.0.0
>
>
> We need to update the Policy page to make it more clear that when updating 
> the list of users who can view or modify the policies of a component, we are 
> appending to the list of administrators not overriding it.
> This needs to be made obvious as it is different behavior then updating the 
> list of users who can view or modify a component as these policies override 
> the otherwise inherited policies.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (NIFI-2530) Template authorization - Fall back to Process Group

[Matt Gilman (JIRA)]

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

Matt Gilman reassigned NIFI-2530:
-

Assignee: Matt Gilman

> Template authorization - Fall back to Process Group
> ---
>
> Key: NIFI-2530
> URL: https://issues.apache.org/jira/browse/NIFI-2530
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>Priority: Blocker
> Fix For: 1.0.0
>
>
> Template authorization strategy in order:
> 1 - Explicit policy on template
> 2 - Authorize based on permissions of underlying components
> 3 - Authorize based on parent Process Group
> Currently, only 1 and 2 are checked. Need to fall back to parent Process 
> Group.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi issue #813: Updating UI to reflect administrator policies do not overri...

[mattyb149]

Github user mattyb149 commented on the issue:

https://github.com/apache/nifi/pull/813
  
+1 LGTM, merging



---
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 pull request #824: Nifi 2526

[brosander]

GitHub user brosander opened a pull request:

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

Nifi 2526



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

$ git pull https://github.com/brosander/nifi NIFI-2526

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

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


commit 690c7efcfa64e967be113733d9ca89f5d7b2a27c
Author: Bryan Rosander 
Date:   2016-08-09T15:11:21Z

NIFI-2526 - DN order, multiple standalone runs, client certificates

commit bd7229c8ed622d9813028f661095d23fb60a99e8
Author: Bryan Rosander 
Date:   2016-08-09T19:36:21Z

NIFI-2526 - Logic for sorting DN, reversing X500Names before using them to 
generate certificate




---
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-2507) PutS3Object should support Canned ACLs

[James Wing (JIRA)]

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

James Wing commented on NIFI-2507:
--

Agreed, I will also merge into master.

> PutS3Object should support Canned ACLs
> --
>
> Key: NIFI-2507
> URL: https://issues.apache.org/jira/browse/NIFI-2507
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 0.7.0
>Reporter: Tim Reardon
>Assignee: James Wing
>Priority: Minor
>
> In order to support cross-account scenarios, PutS3Object should support 
> specifying canned ACL's such as "bucket-owner-full-control".
> See 
> http://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (NIFI-2534) Error when stopping a process group the user doesn't have any permission for

[Bryan Bende (JIRA)]

Bryan Bende created NIFI-2534:
-

 Summary: Error when stopping a process group the user doesn't have 
any permission for
 Key: NIFI-2534
 URL: https://issues.apache.org/jira/browse/NIFI-2534
 Project: Apache NiFi
  Issue Type: Bug
Affects Versions: 1.0.0
Reporter: Bryan Bende
Priority: Minor
 Fix For: 1.0.0


I created a process group in a secure instance, then overrode the policy for 
"view component" such that no user had view component for the group (left the 
modify component inheriting from parent). Then right-clicked the process group 
and chose stop, and the circle in the header stayed spinning.

In Chrome Dev tools the error showed on line 1090 of nf-process-group.js 

if (processGroupMap.has(processGroup.id)) {

Saying "id" is undefined.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2520) License/Notice for nifi-hive module not rolled up and not citing storm-hive

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2520:
--

Github user asfgit closed the pull request at:

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


> License/Notice for nifi-hive module not rolled up and not citing storm-hive
> ---
>
> Key: NIFI-2520
> URL: https://issues.apache.org/jira/browse/NIFI-2520
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Joseph Witt
>Assignee: Matt Burgess
>Priority: Blocker
> Fix For: 1.0.0
>
>
> In reviewing licensing and notice for the nifi-hive module it was discovered 
> that the NOTICE information in nifi-hive-nar is not rolled up for the 
> dependencies it pulls into our nifi-assembly.  I recommend we either avoid 
> pulling this nar into the assembly (since it is so big anyway) or we pull it 
> in and make sure to roll up L considerations.
> Also, the HiveOptions and HiveWriter classes appear to be sourced from 
> storm-hive and we need to cite the storm-hive CopyRight if applicable in our 
> nifi.git/NOTICE



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-2520) License/Notice for nifi-hive module not rolled up and not citing storm-hive

[Joseph Witt (JIRA)]

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

Joseph Witt updated NIFI-2520:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

cool - looks good.  +1 merged to master

> License/Notice for nifi-hive module not rolled up and not citing storm-hive
> ---
>
> Key: NIFI-2520
> URL: https://issues.apache.org/jira/browse/NIFI-2520
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Joseph Witt
>Assignee: Matt Burgess
>Priority: Blocker
> Fix For: 1.0.0
>
>
> In reviewing licensing and notice for the nifi-hive module it was discovered 
> that the NOTICE information in nifi-hive-nar is not rolled up for the 
> dependencies it pulls into our nifi-assembly.  I recommend we either avoid 
> pulling this nar into the assembly (since it is so big anyway) or we pull it 
> in and make sure to roll up L considerations.
> Also, the HiveOptions and HiveWriter classes appear to be sourced from 
> storm-hive and we need to cite the storm-hive CopyRight if applicable in our 
> nifi.git/NOTICE



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2520) License/Notice for nifi-hive module not rolled up and not citing storm-hive

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2520 This closes #818. Added attribution for storm-hive and other Hive 
dependencies to NOTICEs


> License/Notice for nifi-hive module not rolled up and not citing storm-hive
> ---
>
> Key: NIFI-2520
> URL: https://issues.apache.org/jira/browse/NIFI-2520
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Joseph Witt
>Assignee: Matt Burgess
>Priority: Blocker
> Fix For: 1.0.0
>
>
> In reviewing licensing and notice for the nifi-hive module it was discovered 
> that the NOTICE information in nifi-hive-nar is not rolled up for the 
> dependencies it pulls into our nifi-assembly.  I recommend we either avoid 
> pulling this nar into the assembly (since it is so big anyway) or we pull it 
> in and make sure to roll up L considerations.
> Also, the HiveOptions and HiveWriter classes appear to be sourced from 
> storm-hive and we need to cite the storm-hive CopyRight if applicable in our 
> nifi.git/NOTICE



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi pull request #818: NIFI-2520: Added attribution for storm-hive and othe...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2507) PutS3Object should support Canned ACLs

[ASF subversion and git services (JIRA)]

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

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

Commit 13262d2f7b1ab0cda81c6c982fc70c1bd62ddcca in nifi's branch refs/heads/0.x 
from [~treardon]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=13262d2 ]

NIFI-2507 Added Canned ACL support to PutS3Object

This closes #801

Signed-off-by: James Wing 


> PutS3Object should support Canned ACLs
> --
>
> Key: NIFI-2507
> URL: https://issues.apache.org/jira/browse/NIFI-2507
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 0.7.0
>Reporter: Tim Reardon
>Assignee: James Wing
>Priority: Minor
>
> In order to support cross-account scenarios, PutS3Object should support 
> specifying canned ACL's such as "bucket-owner-full-control".
> See 
> http://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2507) PutS3Object should support Canned ACLs

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2507:
---

[~jameswing] and [~treardon] Please make sure that if merged it goes to master 
and not just 0.x as the pR is currently aligned

> PutS3Object should support Canned ACLs
> --
>
> Key: NIFI-2507
> URL: https://issues.apache.org/jira/browse/NIFI-2507
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 0.7.0
>Reporter: Tim Reardon
>Assignee: James Wing
>Priority: Minor
>
> In order to support cross-account scenarios, PutS3Object should support 
> specifying canned ACL's such as "bucket-owner-full-control".
> See 
> http://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-2406) Rare start-up problems resulting in all nodes disconnected

[Joseph Witt (JIRA)]

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

Joseph Witt updated NIFI-2406:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

+1.  full clean build w/contrib-check good.  Tested various kill/graceful 
scenarios with leader/non-leader.  All behavior now as expected

merged to master

> Rare start-up problems resulting in all nodes disconnected
> --
>
> Key: NIFI-2406
> URL: https://issues.apache.org/jira/browse/NIFI-2406
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Percivall
>Assignee: Mark Payne
> Fix For: 1.0.0
>
> Attachments: logs.tar.gz
>
>
> While testing PR 678[1], I came across a time where all the nodes were in a 
> disconnected state and each were in a weird state of heartbeating but not 
> connected.
> Also in the logs there were ~1000 lines of:
> 2016-07-26 11:38:07,841 INFO [Leader Election Notification Thread-1] 
> o.a.n.c.l.e.CuratorLeaderElectionManager 
> org.apache.nifi.controller.leader.election.CuratorLeaderElectionManager$ElectionListener@24fae8c6
>  This node has been elected Leader for Role 'Cluster Coordinator'
> This message only gets called here[2] which is a call back for ZK. Also there 
> were many log messages of:
> 2016-07-26 11:54:07,910 WARN [Clustering Tasks Thread-1] 
> o.a.n.c.c.node.NodeClusterCoordinator Failed to determine which node is 
> elected active Cluster Coordinator: ZooKeeper reports the address as 
> localhost:6001, but there is no node with this address
> I believe this is a problem with ZK/NiFi that existed before this PR and not 
> directly related to the PR being reviewed. I will attach a tar of the 3 
> node's logs.
> [1] https://github.com/apache/nifi/pull/678
> [2] 
> https://github.com/apache/nifi/blame/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/leader/election/CuratorLeaderElectionManager.java#L220-L220



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2406) Rare start-up problems resulting in all nodes disconnected

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2406 This closes #820. Addressed regression introduced in NIFI-2406 where 
the cluster does not recognize a new Cluster Coordinator when the coordinator 
is shutdown


> Rare start-up problems resulting in all nodes disconnected
> --
>
> Key: NIFI-2406
> URL: https://issues.apache.org/jira/browse/NIFI-2406
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Percivall
>Assignee: Mark Payne
> Fix For: 1.0.0
>
> Attachments: logs.tar.gz
>
>
> While testing PR 678[1], I came across a time where all the nodes were in a 
> disconnected state and each were in a weird state of heartbeating but not 
> connected.
> Also in the logs there were ~1000 lines of:
> 2016-07-26 11:38:07,841 INFO [Leader Election Notification Thread-1] 
> o.a.n.c.l.e.CuratorLeaderElectionManager 
> org.apache.nifi.controller.leader.election.CuratorLeaderElectionManager$ElectionListener@24fae8c6
>  This node has been elected Leader for Role 'Cluster Coordinator'
> This message only gets called here[2] which is a call back for ZK. Also there 
> were many log messages of:
> 2016-07-26 11:54:07,910 WARN [Clustering Tasks Thread-1] 
> o.a.n.c.c.node.NodeClusterCoordinator Failed to determine which node is 
> elected active Cluster Coordinator: ZooKeeper reports the address as 
> localhost:6001, but there is no node with this address
> I believe this is a problem with ZK/NiFi that existed before this PR and not 
> directly related to the PR being reviewed. I will attach a tar of the 3 
> node's logs.
> [1] https://github.com/apache/nifi/pull/678
> [2] 
> https://github.com/apache/nifi/blame/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/leader/election/CuratorLeaderElectionManager.java#L220-L220



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2406) Rare start-up problems resulting in all nodes disconnected

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2406:
--

Github user asfgit closed the pull request at:

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


> Rare start-up problems resulting in all nodes disconnected
> --
>
> Key: NIFI-2406
> URL: https://issues.apache.org/jira/browse/NIFI-2406
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Percivall
>Assignee: Mark Payne
> Fix For: 1.0.0
>
> Attachments: logs.tar.gz
>
>
> While testing PR 678[1], I came across a time where all the nodes were in a 
> disconnected state and each were in a weird state of heartbeating but not 
> connected.
> Also in the logs there were ~1000 lines of:
> 2016-07-26 11:38:07,841 INFO [Leader Election Notification Thread-1] 
> o.a.n.c.l.e.CuratorLeaderElectionManager 
> org.apache.nifi.controller.leader.election.CuratorLeaderElectionManager$ElectionListener@24fae8c6
>  This node has been elected Leader for Role 'Cluster Coordinator'
> This message only gets called here[2] which is a call back for ZK. Also there 
> were many log messages of:
> 2016-07-26 11:54:07,910 WARN [Clustering Tasks Thread-1] 
> o.a.n.c.c.node.NodeClusterCoordinator Failed to determine which node is 
> elected active Cluster Coordinator: ZooKeeper reports the address as 
> localhost:6001, but there is no node with this address
> I believe this is a problem with ZK/NiFi that existed before this PR and not 
> directly related to the PR being reviewed. I will attach a tar of the 3 
> node's logs.
> [1] https://github.com/apache/nifi/pull/678
> [2] 
> https://github.com/apache/nifi/blame/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/leader/election/CuratorLeaderElectionManager.java#L220-L220



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2406) Rare start-up problems resulting in all nodes disconnected

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2406 This closes #820. Addressed regression introduced in NIFI-2406 where 
the cluster does not recognize a new Cluster Coordinator when the coordinator 
is shutdown


> Rare start-up problems resulting in all nodes disconnected
> --
>
> Key: NIFI-2406
> URL: https://issues.apache.org/jira/browse/NIFI-2406
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Percivall
>Assignee: Mark Payne
> Fix For: 1.0.0
>
> Attachments: logs.tar.gz
>
>
> While testing PR 678[1], I came across a time where all the nodes were in a 
> disconnected state and each were in a weird state of heartbeating but not 
> connected.
> Also in the logs there were ~1000 lines of:
> 2016-07-26 11:38:07,841 INFO [Leader Election Notification Thread-1] 
> o.a.n.c.l.e.CuratorLeaderElectionManager 
> org.apache.nifi.controller.leader.election.CuratorLeaderElectionManager$ElectionListener@24fae8c6
>  This node has been elected Leader for Role 'Cluster Coordinator'
> This message only gets called here[2] which is a call back for ZK. Also there 
> were many log messages of:
> 2016-07-26 11:54:07,910 WARN [Clustering Tasks Thread-1] 
> o.a.n.c.c.node.NodeClusterCoordinator Failed to determine which node is 
> elected active Cluster Coordinator: ZooKeeper reports the address as 
> localhost:6001, but there is no node with this address
> I believe this is a problem with ZK/NiFi that existed before this PR and not 
> directly related to the PR being reviewed. I will attach a tar of the 3 
> node's logs.
> [1] https://github.com/apache/nifi/pull/678
> [2] 
> https://github.com/apache/nifi/blame/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/leader/election/CuratorLeaderElectionManager.java#L220-L220



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi pull request #820: NIFI-2406: Addressed regression introduced in NIFI-2...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2507) PutS3Object should support Canned ACLs

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2507:
--

Github user jvwing commented on the issue:

https://github.com/apache/nifi/pull/801
  
Thanks for the update, @tequalsme, I verified:
* Property descriptor name/displayName updated
* Reformated createCannedACL is appreciated, thanks
* Exception error message from bad canned ACL names is reasonably 
intelligible
* Updated integration test ITPutS3Object.testGetPropertyDescriptors is 
passing
* Comments are a nice enhancement, and the generated Javadoc looks good

I will squash, rebase, and merge shortly.


> PutS3Object should support Canned ACLs
> --
>
> Key: NIFI-2507
> URL: https://issues.apache.org/jira/browse/NIFI-2507
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 0.7.0
>Reporter: Tim Reardon
>Assignee: James Wing
>Priority: Minor
>
> In order to support cross-account scenarios, PutS3Object should support 
> specifying canned ACL's such as "bucket-owner-full-control".
> See 
> http://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi issue #801: NIFI-2507 Added Canned ACL support to PutS3Object

[jvwing]

Github user jvwing commented on the issue:

https://github.com/apache/nifi/pull/801
  
Thanks for the update, @tequalsme, I verified:
* Property descriptor name/displayName updated
* Reformated createCannedACL is appreciated, thanks
* Exception error message from bad canned ACL names is reasonably 
intelligible
* Updated integration test ITPutS3Object.testGetPropertyDescriptors is 
passing
* Comments are a nice enhancement, and the generated Javadoc looks good

I will squash, rebase, and merge shortly.


---
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-1781) Update UI to reflect component level authorization

[James Wing (JIRA)]

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

James Wing commented on NIFI-1781:
--

Thanks, [~mcgilman], I _think_ I understand.  I will reply on Joe Witt's dev 
mailing list thread.

> Update UI to reflect component level authorization
> --
>
> Key: NIFI-1781
> URL: https://issues.apache.org/jira/browse/NIFI-1781
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Matt Gilman
> Fix For: 1.0.0, 1.0.0-Beta
>
> Attachments: 0001-NIFI-1781.patch, nifi-component-samples.png, 
> nifi-sample-flow.png
>
>
> - Update to UI to visual access level per component



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-2533) When searching for users to add to a policy, should filter out users that are already on the policy

[Andrew Lim (JIRA)]

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

Andrew Lim updated NIFI-2533:
-
Attachment: NIFI-2533.png

> When searching for users to add to a policy, should filter out users that are 
> already on the policy
> ---
>
> Key: NIFI-2533
> URL: https://issues.apache.org/jira/browse/NIFI-2533
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Priority: Minor
> Attachments: NIFI-2533.png
>
>
> As shown in the attached screenshot.  User1 is already on the policy.  When 
> adding additional users to the policy, the "Search users" window should 
> filter out User1 from the list.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (NIFI-2533) When searching for users to add to a policy, should filter out users that are already on the policy

[Andrew Lim (JIRA)]

Andrew Lim created NIFI-2533:


 Summary: When searching for users to add to a policy, should 
filter out users that are already on the policy
 Key: NIFI-2533
 URL: https://issues.apache.org/jira/browse/NIFI-2533
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Core UI
Affects Versions: 1.0.0
Reporter: Andrew Lim
Priority: Minor


As shown in the attached screenshot.  User1 is already on the policy.  When 
adding additional users to the policy, the "Search users" window should filter 
out User1 from the list.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-2520) License/Notice for nifi-hive module not rolled up and not citing storm-hive

[Matt Burgess (JIRA)]

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

Matt Burgess updated NIFI-2520:
---
Status: Patch Available  (was: In Progress)

> License/Notice for nifi-hive module not rolled up and not citing storm-hive
> ---
>
> Key: NIFI-2520
> URL: https://issues.apache.org/jira/browse/NIFI-2520
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Joseph Witt
>Assignee: Matt Burgess
>Priority: Blocker
> Fix For: 1.0.0
>
>
> In reviewing licensing and notice for the nifi-hive module it was discovered 
> that the NOTICE information in nifi-hive-nar is not rolled up for the 
> dependencies it pulls into our nifi-assembly.  I recommend we either avoid 
> pulling this nar into the assembly (since it is so big anyway) or we pull it 
> in and make sure to roll up L considerations.
> Also, the HiveOptions and HiveWriter classes appear to be sourced from 
> storm-hive and we need to cite the storm-hive CopyRight if applicable in our 
> nifi.git/NOTICE



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2406) Rare start-up problems resulting in all nodes disconnected

[Mark Payne (JIRA)]

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

Mark Payne commented on NIFI-2406:
--

[~joewitt] - I just pushed an update to the PR (separate commit so you can see 
what changed). I was able to reproduce this easily when doing a kill -9, or a 
nice restart, but it depends on whether or not the node becomes the cluster 
coordinator when it starts up. The issue was that FlowController started the 
heartbeat monitor, which in turn announced the node as the Cluster Coordinator 
- even when it wasn't. This overwrote the true Cluster Coordinator's address, 
so the nodes were confused. Fixed it so that it publishes the address only when 
the node is truly elected Cluster Coordinator.

> Rare start-up problems resulting in all nodes disconnected
> --
>
> Key: NIFI-2406
> URL: https://issues.apache.org/jira/browse/NIFI-2406
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Percivall
>Assignee: Mark Payne
> Fix For: 1.0.0
>
> Attachments: logs.tar.gz
>
>
> While testing PR 678[1], I came across a time where all the nodes were in a 
> disconnected state and each were in a weird state of heartbeating but not 
> connected.
> Also in the logs there were ~1000 lines of:
> 2016-07-26 11:38:07,841 INFO [Leader Election Notification Thread-1] 
> o.a.n.c.l.e.CuratorLeaderElectionManager 
> org.apache.nifi.controller.leader.election.CuratorLeaderElectionManager$ElectionListener@24fae8c6
>  This node has been elected Leader for Role 'Cluster Coordinator'
> This message only gets called here[2] which is a call back for ZK. Also there 
> were many log messages of:
> 2016-07-26 11:54:07,910 WARN [Clustering Tasks Thread-1] 
> o.a.n.c.c.node.NodeClusterCoordinator Failed to determine which node is 
> elected active Cluster Coordinator: ZooKeeper reports the address as 
> localhost:6001, but there is no node with this address
> I believe this is a problem with ZK/NiFi that existed before this PR and not 
> directly related to the PR being reviewed. I will attach a tar of the 3 
> node's logs.
> [1] https://github.com/apache/nifi/pull/678
> [2] 
> https://github.com/apache/nifi/blame/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/leader/election/CuratorLeaderElectionManager.java#L220-L220



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-2520) License/Notice for nifi-hive module not rolled up and not citing storm-hive

[Joseph Witt (JIRA)]

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

Joseph Witt updated NIFI-2520:
--
Status: Open  (was: Patch Available)

feedback provided to [~mattyb149] and then patch can be resubmitted

> License/Notice for nifi-hive module not rolled up and not citing storm-hive
> ---
>
> Key: NIFI-2520
> URL: https://issues.apache.org/jira/browse/NIFI-2520
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Joseph Witt
>Assignee: Matt Burgess
>Priority: Blocker
> Fix For: 1.0.0
>
>
> In reviewing licensing and notice for the nifi-hive module it was discovered 
> that the NOTICE information in nifi-hive-nar is not rolled up for the 
> dependencies it pulls into our nifi-assembly.  I recommend we either avoid 
> pulling this nar into the assembly (since it is so big anyway) or we pull it 
> in and make sure to roll up L considerations.
> Also, the HiveOptions and HiveWriter classes appear to be sourced from 
> storm-hive and we need to cite the storm-hive CopyRight if applicable in our 
> nifi.git/NOTICE



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2520) License/Notice for nifi-hive module not rolled up and not citing storm-hive

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2520:
---

[~mattyb149] since we dont have a binary dependency to Storm we don't need to 
call it out as we are in the assembly/NOTICE and hive-nar/NOTICE.  But since 
you used a couple of their class files as source you DO need to call that out 
in the top level nifi source NOTICE and the assembly/NOTICE and the 
hive-nar/NOTICE. The entry basically shoudl say we're including derived works 
of the Copyright Storm... and list the two files that were copied from/derived 
from.

Make those edits and I think we're in good shape.

Thanks!
Joe

> License/Notice for nifi-hive module not rolled up and not citing storm-hive
> ---
>
> Key: NIFI-2520
> URL: https://issues.apache.org/jira/browse/NIFI-2520
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Joseph Witt
>Assignee: Matt Burgess
>Priority: Blocker
> Fix For: 1.0.0
>
>
> In reviewing licensing and notice for the nifi-hive module it was discovered 
> that the NOTICE information in nifi-hive-nar is not rolled up for the 
> dependencies it pulls into our nifi-assembly.  I recommend we either avoid 
> pulling this nar into the assembly (since it is so big anyway) or we pull it 
> in and make sure to roll up L considerations.
> Also, the HiveOptions and HiveWriter classes appear to be sourced from 
> storm-hive and we need to cite the storm-hive CopyRight if applicable in our 
> nifi.git/NOTICE



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-2406) Rare start-up problems resulting in all nodes disconnected

[Mark Payne (JIRA)]

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

Mark Payne updated NIFI-2406:
-
Status: Patch Available  (was: Open)

> Rare start-up problems resulting in all nodes disconnected
> --
>
> Key: NIFI-2406
> URL: https://issues.apache.org/jira/browse/NIFI-2406
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Percivall
>Assignee: Mark Payne
> Fix For: 1.0.0
>
> Attachments: logs.tar.gz
>
>
> While testing PR 678[1], I came across a time where all the nodes were in a 
> disconnected state and each were in a weird state of heartbeating but not 
> connected.
> Also in the logs there were ~1000 lines of:
> 2016-07-26 11:38:07,841 INFO [Leader Election Notification Thread-1] 
> o.a.n.c.l.e.CuratorLeaderElectionManager 
> org.apache.nifi.controller.leader.election.CuratorLeaderElectionManager$ElectionListener@24fae8c6
>  This node has been elected Leader for Role 'Cluster Coordinator'
> This message only gets called here[2] which is a call back for ZK. Also there 
> were many log messages of:
> 2016-07-26 11:54:07,910 WARN [Clustering Tasks Thread-1] 
> o.a.n.c.c.node.NodeClusterCoordinator Failed to determine which node is 
> elected active Cluster Coordinator: ZooKeeper reports the address as 
> localhost:6001, but there is no node with this address
> I believe this is a problem with ZK/NiFi that existed before this PR and not 
> directly related to the PR being reviewed. I will attach a tar of the 3 
> node's logs.
> [1] https://github.com/apache/nifi/pull/678
> [2] 
> https://github.com/apache/nifi/blame/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/leader/election/CuratorLeaderElectionManager.java#L220-L220



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-2286) Policies: "Add user to policy" and "Remove" icons do not have hover help text

[Andrew Lim (JIRA)]

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

Andrew Lim updated NIFI-2286:
-
Issue Type: Improvement  (was: Bug)

> Policies:  "Add user to policy" and "Remove" icons do not have hover help text
> --
>
> Key: NIFI-2286
> URL: https://issues.apache.org/jira/browse/NIFI-2286
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Priority: Minor
>  Labels: UI
>
> The "Add user to policy" and "Remove" buttons in the Access Policies window 
> do not have any help text displayed when the user hovers over them.
> This will be really helpful especially to new users of the Authorization API.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2286) Policies: "Add user to policy" and "Remove" icons do not have hover help text

[Andrew Lim (JIRA)]

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

Andrew Lim commented on NIFI-2286:
--

The NiFi Users window also has the same "Add User " icon.  That one needs hover 
text as well.  Something like "Add User/Group"

> Policies:  "Add user to policy" and "Remove" icons do not have hover help text
> --
>
> Key: NIFI-2286
> URL: https://issues.apache.org/jira/browse/NIFI-2286
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Priority: Minor
>  Labels: UI
>
> The "Add user to policy" and "Remove" buttons in the Access Policies window 
> do not have any help text displayed when the user hovers over them.
> This will be really helpful especially to new users of the Authorization API.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-2286) Policies: "Add user to policy" and "Remove" icons do not have hover help text

[Andrew Lim (JIRA)]

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

Andrew Lim updated NIFI-2286:
-
Affects Version/s: (was: 1.1.0)
   1.0.0

> Policies:  "Add user to policy" and "Remove" icons do not have hover help text
> --
>
> Key: NIFI-2286
> URL: https://issues.apache.org/jira/browse/NIFI-2286
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Priority: Minor
>  Labels: UI
>
> The "Add user to policy" and "Remove" buttons in the Access Policies window 
> do not have any help text displayed when the user hovers over them.
> This will be really helpful especially to new users of the Authorization API.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (NIFI-2532) Should add hover text to "Add User" and "Remove" icons

[Andrew Lim (JIRA)]

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

Andrew Lim resolved NIFI-2532.
--
Resolution: Duplicate

Dupe of NIFI-2286

> Should add hover text to "Add User" and "Remove" icons
> --
>
> Key: NIFI-2532
> URL: https://issues.apache.org/jira/browse/NIFI-2532
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Priority: Minor
>
> The "Add User" icon is used when adding users/groups and when adding users to 
> policies.
> The "Remove" icon (trashcan) is used to remove policies.
> Both of these icons should have hover text so users will have a better idea 
> of the action performed if clicked.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-2515) Setting key.serializer in publish kafka leads to org.apache.kafka.common.errors.SerializationException

[Joseph Witt (JIRA)]

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

Joseph Witt updated NIFI-2515:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

+1 merged to master and 0.x

> Setting key.serializer in publish kafka leads to 
> org.apache.kafka.common.errors.SerializationException
> --
>
> Key: NIFI-2515
> URL: https://issues.apache.org/jira/browse/NIFI-2515
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0-Beta
>Reporter: Arpit Gupta
>Assignee: Oleg Zhurakousky
>Priority: Minor
> Fix For: 1.0.0, 0.8.0
>
>
> If one sets key.serializer in the publish kafka processor we see error
> {code}
> 4895-9b14-9e8b1d88755e}, body={topics=[putMessages-83cf2948-b110-2016-08-07 
> 17:11:56,191 ERROR [Timer-Driven Process Thread-7] 
> o.a.n.p.kafka.pubsub.PublishKafka 
> PublishKafka[id=65fd2baf-0156-1000--f6bf89be] 
> PublishKafka[id=65fd2baf-0156-1000--f6bf89be] failed to process due 
> to org.apache.kafka.common.errors.SerializationException: Can't convert key 
> of class [B to class org.apache.kafka.common.serialization.IntegerSerializer 
> specified in key.serializer; rolling back session: 
> org.apache.kafka.common.errors.SerializationException: Can't convert key of 
> class [B to class org.apache.kafka.common.serialization.IntegerSerializer 
> specified in key.serializer
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2515) Setting key.serializer in publish kafka leads to org.apache.kafka.common.errors.SerializationException

[ASF subversion and git services (JIRA)]

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

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

Commit fcf85ecdae114745e92c59d06073b7eb6cb8e4a0 in nifi's branch refs/heads/0.x 
from [~ozhurakousky]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=fcf85ec ]

NIFI-2515 fixed Kafka serialization/deserialization settings


> Setting key.serializer in publish kafka leads to 
> org.apache.kafka.common.errors.SerializationException
> --
>
> Key: NIFI-2515
> URL: https://issues.apache.org/jira/browse/NIFI-2515
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0-Beta
>Reporter: Arpit Gupta
>Assignee: Oleg Zhurakousky
>Priority: Minor
> Fix For: 1.0.0, 0.8.0
>
>
> If one sets key.serializer in the publish kafka processor we see error
> {code}
> 4895-9b14-9e8b1d88755e}, body={topics=[putMessages-83cf2948-b110-2016-08-07 
> 17:11:56,191 ERROR [Timer-Driven Process Thread-7] 
> o.a.n.p.kafka.pubsub.PublishKafka 
> PublishKafka[id=65fd2baf-0156-1000--f6bf89be] 
> PublishKafka[id=65fd2baf-0156-1000--f6bf89be] failed to process due 
> to org.apache.kafka.common.errors.SerializationException: Can't convert key 
> of class [B to class org.apache.kafka.common.serialization.IntegerSerializer 
> specified in key.serializer; rolling back session: 
> org.apache.kafka.common.errors.SerializationException: Can't convert key of 
> class [B to class org.apache.kafka.common.serialization.IntegerSerializer 
> specified in key.serializer
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (NIFI-2532) Should add hover text to "Add User" and "Remove" icon

[Andrew Lim (JIRA)]

Andrew Lim created NIFI-2532:


 Summary: Should add hover text to "Add User" and "Remove" icon
 Key: NIFI-2532
 URL: https://issues.apache.org/jira/browse/NIFI-2532
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Core UI
Affects Versions: 1.0.0
Reporter: Andrew Lim
Priority: Minor


The "Add User" icon is used when adding users/groups and when adding users to 
policies.

The "Remove" icon (trashcan) is used to remove policies.

Both of these icons should have hover text so users will have a better idea of 
the action performed if clicked.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-2532) Should add hover text to "Add User" and "Remove" icons

[Andrew Lim (JIRA)]

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

Andrew Lim updated NIFI-2532:
-
Summary: Should add hover text to "Add User" and "Remove" icons  (was: 
Should add hover text to "Add User" and "Remove" icon)

> Should add hover text to "Add User" and "Remove" icons
> --
>
> Key: NIFI-2532
> URL: https://issues.apache.org/jira/browse/NIFI-2532
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Priority: Minor
>
> The "Add User" icon is used when adding users/groups and when adding users to 
> policies.
> The "Remove" icon (trashcan) is used to remove policies.
> Both of these icons should have hover text so users will have a better idea 
> of the action performed if clicked.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2515) Setting key.serializer in publish kafka leads to org.apache.kafka.common.errors.SerializationException

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2515:
--

Github user asfgit closed the pull request at:

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


> Setting key.serializer in publish kafka leads to 
> org.apache.kafka.common.errors.SerializationException
> --
>
> Key: NIFI-2515
> URL: https://issues.apache.org/jira/browse/NIFI-2515
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0-Beta
>Reporter: Arpit Gupta
>Assignee: Oleg Zhurakousky
>Priority: Minor
> Fix For: 1.0.0, 0.8.0
>
>
> If one sets key.serializer in the publish kafka processor we see error
> {code}
> 4895-9b14-9e8b1d88755e}, body={topics=[putMessages-83cf2948-b110-2016-08-07 
> 17:11:56,191 ERROR [Timer-Driven Process Thread-7] 
> o.a.n.p.kafka.pubsub.PublishKafka 
> PublishKafka[id=65fd2baf-0156-1000--f6bf89be] 
> PublishKafka[id=65fd2baf-0156-1000--f6bf89be] failed to process due 
> to org.apache.kafka.common.errors.SerializationException: Can't convert key 
> of class [B to class org.apache.kafka.common.serialization.IntegerSerializer 
> specified in key.serializer; rolling back session: 
> org.apache.kafka.common.errors.SerializationException: Can't convert key of 
> class [B to class org.apache.kafka.common.serialization.IntegerSerializer 
> specified in key.serializer
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-2406) Rare start-up problems resulting in all nodes disconnected

[Joseph Witt (JIRA)]

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

Joseph Witt updated NIFI-2406:
--
Status: Open  (was: Patch Available)

reported issues with previous patch testing

> Rare start-up problems resulting in all nodes disconnected
> --
>
> Key: NIFI-2406
> URL: https://issues.apache.org/jira/browse/NIFI-2406
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Percivall
>Assignee: Mark Payne
> Fix For: 1.0.0
>
> Attachments: logs.tar.gz
>
>
> While testing PR 678[1], I came across a time where all the nodes were in a 
> disconnected state and each were in a weird state of heartbeating but not 
> connected.
> Also in the logs there were ~1000 lines of:
> 2016-07-26 11:38:07,841 INFO [Leader Election Notification Thread-1] 
> o.a.n.c.l.e.CuratorLeaderElectionManager 
> org.apache.nifi.controller.leader.election.CuratorLeaderElectionManager$ElectionListener@24fae8c6
>  This node has been elected Leader for Role 'Cluster Coordinator'
> This message only gets called here[2] which is a call back for ZK. Also there 
> were many log messages of:
> 2016-07-26 11:54:07,910 WARN [Clustering Tasks Thread-1] 
> o.a.n.c.c.node.NodeClusterCoordinator Failed to determine which node is 
> elected active Cluster Coordinator: ZooKeeper reports the address as 
> localhost:6001, but there is no node with this address
> I believe this is a problem with ZK/NiFi that existed before this PR and not 
> directly related to the PR being reviewed. I will attach a tar of the 3 
> node's logs.
> [1] https://github.com/apache/nifi/pull/678
> [2] 
> https://github.com/apache/nifi/blame/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/leader/election/CuratorLeaderElectionManager.java#L220-L220



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi pull request #814: NIFI-2515 fixed Kafka serialization/deserialization ...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2515) Setting key.serializer in publish kafka leads to org.apache.kafka.common.errors.SerializationException

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2515 This closes #814. fixed Kafka serialization/deserialization settings


> Setting key.serializer in publish kafka leads to 
> org.apache.kafka.common.errors.SerializationException
> --
>
> Key: NIFI-2515
> URL: https://issues.apache.org/jira/browse/NIFI-2515
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0-Beta
>Reporter: Arpit Gupta
>Assignee: Oleg Zhurakousky
>Priority: Minor
> Fix For: 1.0.0, 0.8.0
>
>
> If one sets key.serializer in the publish kafka processor we see error
> {code}
> 4895-9b14-9e8b1d88755e}, body={topics=[putMessages-83cf2948-b110-2016-08-07 
> 17:11:56,191 ERROR [Timer-Driven Process Thread-7] 
> o.a.n.p.kafka.pubsub.PublishKafka 
> PublishKafka[id=65fd2baf-0156-1000--f6bf89be] 
> PublishKafka[id=65fd2baf-0156-1000--f6bf89be] failed to process due 
> to org.apache.kafka.common.errors.SerializationException: Can't convert key 
> of class [B to class org.apache.kafka.common.serialization.IntegerSerializer 
> specified in key.serializer; rolling back session: 
> org.apache.kafka.common.errors.SerializationException: Can't convert key of 
> class [B to class org.apache.kafka.common.serialization.IntegerSerializer 
> specified in key.serializer
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (NIFI-1965) Create a QueryDNS processor

[Joseph Witt (JIRA)]

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

Joseph Witt resolved NIFI-1965.
---
Resolution: Fixed

+1. full clean build w/contrib check.  Merged to master.

> Create a QueryDNS processor
> ---
>
> Key: NIFI-1965
> URL: https://issues.apache.org/jira/browse/NIFI-1965
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Andre
>Assignee: Andre
> Fix For: 1.0.0
>
>
> As part of a data pipeline security teams frequently must enrich data using 
> DNS enabled APIs such as:
> ShadowServer BGP and ASN lookup via DNS
> https://www.shadowserver.org/wiki/pmwiki.php/Services/IP-BGP#toc7 
> Team Cymru Malware Hash Registry
> http://www.team-cymru.org/MHR.html
> Spamhaus (SBL, XBL, etc)
> and others
> QueryDNS will use an expression language enabled property to run a query 
> against DNS and add the raw result to an attribute (for later processing if 
> necessary). 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-1965) Create a QueryDNS processor

[ASF subversion and git services (JIRA)]

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

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

Commit f6ba92229224504d0bbd1126bd8428a010bb4c45 in nifi's branch 
refs/heads/master from Andre F de Miranda
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=f6ba922 ]

NIFI-1965  This closes #819. COnvert DNS_TIMEOUT property to TIME_PERIOD


> Create a QueryDNS processor
> ---
>
> Key: NIFI-1965
> URL: https://issues.apache.org/jira/browse/NIFI-1965
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Andre
>Assignee: Andre
> Fix For: 1.0.0
>
>
> As part of a data pipeline security teams frequently must enrich data using 
> DNS enabled APIs such as:
> ShadowServer BGP and ASN lookup via DNS
> https://www.shadowserver.org/wiki/pmwiki.php/Services/IP-BGP#toc7 
> Team Cymru Malware Hash Registry
> http://www.team-cymru.org/MHR.html
> Spamhaus (SBL, XBL, etc)
> and others
> QueryDNS will use an expression language enabled property to run a query 
> against DNS and add the raw result to an attribute (for later processing if 
> necessary). 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-1965) Create a QueryDNS processor

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1965:
--

Github user asfgit closed the pull request at:

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


> Create a QueryDNS processor
> ---
>
> Key: NIFI-1965
> URL: https://issues.apache.org/jira/browse/NIFI-1965
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Andre
>Assignee: Andre
> Fix For: 1.0.0
>
>
> As part of a data pipeline security teams frequently must enrich data using 
> DNS enabled APIs such as:
> ShadowServer BGP and ASN lookup via DNS
> https://www.shadowserver.org/wiki/pmwiki.php/Services/IP-BGP#toc7 
> Team Cymru Malware Hash Registry
> http://www.team-cymru.org/MHR.html
> Spamhaus (SBL, XBL, etc)
> and others
> QueryDNS will use an expression language enabled property to run a query 
> against DNS and add the raw result to an attribute (for later processing if 
> necessary). 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi pull request #819: NIFI-1965 - Convert DNS_TIMEOUT property to TIME_PER...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2499) Update User Guide screenshots and text for new UI

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2499:
--

Github user thesolson closed the pull request at:

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


> Update User Guide screenshots and text for new UI
> -
>
> Key: NIFI-2499
> URL: https://issues.apache.org/jira/browse/NIFI-2499
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Sarah Olson
>Assignee: Sarah Olson
> Fix For: 1.0.0
>
>
> Update User Guide screenshots and text for new UI. 
> Added one or two additional screenshots as well. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2499) Update User Guide screenshots and text for new UI

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2499:
---

[~solson75] Hello - went to merge and evaluate and finding there are now merge 
conflicts.  Can you resolve those?

> Update User Guide screenshots and text for new UI
> -
>
> Key: NIFI-2499
> URL: https://issues.apache.org/jira/browse/NIFI-2499
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Sarah Olson
>Assignee: Sarah Olson
> Fix For: 1.0.0
>
>
> Update User Guide screenshots and text for new UI. 
> Added one or two additional screenshots as well. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)