[GitHub] nifi-minifi-cpp pull request #18: MINIFI-34 - attempt to progress the CMake ...

[trixpan]

GitHub user trixpan opened a pull request:

https://github.com/apache/nifi-minifi-cpp/pull/18

MINIFI-34 - attempt to progress the CMake environment



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

$ git pull https://github.com/trixpan/nifi-minifi-cpp cmake_woes

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

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


commit 9cb84cf65e16d55a8652259159ae4785eabc925a
Author: Aldrin Piri 
Date:   2016-05-05T21:32:57Z

MINIFI-34 Establishing CMake build system to provide build functionality 
equivalent to pre-existing Makefile.

commit 253c7c42ba94f11720f276b024630af4765bbf44
Author: Aldrin Piri 
Date:   2016-10-06T14:52:34Z

Updating .travis.yml to support CMake build system.

commit 2251ecce3833d3ac134d7004bee1e07f67f9cbdd
Author: Aldrin Piri 
Date:   2016-10-06T20:41:34Z

Adjusting travis build.

commit df11017e4ddd67e86271d67cd141eab610555355
Author: Andre F de Miranda 
Date:   2016-10-07T04:40:20Z

MINIFI-34 - Adjust CMake files to succeed in RHEL6 and Ubuntu




---
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-2799) AWS Credentials for Assume Role Need Proxy

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2799:
--

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

https://github.com/apache/nifi/pull/1112#discussion_r82326521
  
--- Diff: 
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/credentials/provider/factory/CredentialPropertyDescriptors.java
 ---
@@ -18,6 +18,7 @@
 
 import org.apache.nifi.components.PropertyDescriptor;
 import org.apache.nifi.processor.util.StandardValidators;
+import org.joda.time.DateTime;
--- End diff --

This import does not appear to be used, can it be removed?


> AWS Credentials for Assume Role Need Proxy
> --
>
> Key: NIFI-2799
> URL: https://issues.apache.org/jira/browse/NIFI-2799
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Keren Tseytlin
>Assignee: James Wing
>Priority: Minor
> Fix For: 1.1.0
>
>
> As a user of Nifi, when I want to enable cross account fetching of S3 objects 
> I need the proxy variables to be set in order to generate temporary AWS 
> tokens for STS:AssumeRole.
> Within some enterprise environments, it is necessary to set the proxy 
> variables prior to running AssumeRole methods. Without this being set, the 
> machine in VPC A times out on generating temporary keys and is unable to 
> assume a role as a machine in VPC B. 
> This ticket arose from this conversation: 
> http://apache-nifi-developer-list.39713.n7.nabble.com/Nifi-Cross-Account-Download-With-A-Profile-Flag-td13232.html#a13252
> Goal: There are files stored in an S3 bucket in VPC B. My Nifi machines are 
> in VPC A. I want Nifi to be able to get those files from VPC B. VPC A and VPC 
> B need to be communicating in the FetchS3Object component.



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

[jira] [Commented] (NIFI-2799) AWS Credentials for Assume Role Need Proxy

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2799:
--

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

https://github.com/apache/nifi/pull/1112#discussion_r82327829
  
--- Diff: 
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/credentials/provider/factory/strategies/AssumeRoleCredentialsStrategy.java
 ---
@@ -113,16 +134,34 @@ public AWSCredentialsProvider 
getDerivedCredentialsProvider(Map AWS Credentials for Assume Role Need Proxy
> --
>
> Key: NIFI-2799
> URL: https://issues.apache.org/jira/browse/NIFI-2799
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Keren Tseytlin
>Assignee: James Wing
>Priority: Minor
> Fix For: 1.1.0
>
>
> As a user of Nifi, when I want to enable cross account fetching of S3 objects 
> I need the proxy variables to be set in order to generate temporary AWS 
> tokens for STS:AssumeRole.
> Within some enterprise environments, it is necessary to set the proxy 
> variables prior to running AssumeRole methods. Without this being set, the 
> machine in VPC A times out on generating temporary keys and is unable to 
> assume a role as a machine in VPC B. 
> This ticket arose from this conversation: 
> http://apache-nifi-developer-list.39713.n7.nabble.com/Nifi-Cross-Account-Download-With-A-Profile-Flag-td13232.html#a13252
> Goal: There are files stored in an S3 bucket in VPC B. My Nifi machines are 
> in VPC A. I want Nifi to be able to get those files from VPC B. VPC A and VPC 
> B need to be communicating in the FetchS3Object component.



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

[GitHub] nifi pull request #1112: NIFI-2799: AWS Credentials for Assume Role Need Pro...

[jvwing]

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

https://github.com/apache/nifi/pull/1112#discussion_r82326547
  
--- Diff: 
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/credentials/provider/factory/CredentialPropertyDescriptors.java
 ---
@@ -44,7 +45,7 @@
 .allowableValues("true", "false")
 .defaultValue("false")
 .description("If true, uses the Default Credential chain, 
including EC2 instance profiles or roles, " +
-"environment variables, default user credentials, etc.")
+"environment variables, default user credentials, 
etc.")
--- End diff --

Is this a purposeful whitespace change?


---
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-2799) AWS Credentials for Assume Role Need Proxy

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2799:
--

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

https://github.com/apache/nifi/pull/1112#discussion_r82326589
  
--- Diff: 
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/credentials/provider/factory/CredentialPropertyDescriptors.java
 ---
@@ -153,6 +154,29 @@
 .addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
 .sensitive(false)
 .description("External ID for cross-account access. This is 
used in conjunction with role arn, " +
-"role name, and optional session time out")
+"role name, and optional session time out")
--- End diff --

Same question on the indentation change.


> AWS Credentials for Assume Role Need Proxy
> --
>
> Key: NIFI-2799
> URL: https://issues.apache.org/jira/browse/NIFI-2799
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Keren Tseytlin
>Assignee: James Wing
>Priority: Minor
> Fix For: 1.1.0
>
>
> As a user of Nifi, when I want to enable cross account fetching of S3 objects 
> I need the proxy variables to be set in order to generate temporary AWS 
> tokens for STS:AssumeRole.
> Within some enterprise environments, it is necessary to set the proxy 
> variables prior to running AssumeRole methods. Without this being set, the 
> machine in VPC A times out on generating temporary keys and is unable to 
> assume a role as a machine in VPC B. 
> This ticket arose from this conversation: 
> http://apache-nifi-developer-list.39713.n7.nabble.com/Nifi-Cross-Account-Download-With-A-Profile-Flag-td13232.html#a13252
> Goal: There are files stored in an S3 bucket in VPC B. My Nifi machines are 
> in VPC A. I want Nifi to be able to get those files from VPC B. VPC A and VPC 
> B need to be communicating in the FetchS3Object component.



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

[GitHub] nifi pull request #1112: NIFI-2799: AWS Credentials for Assume Role Need Pro...

[jvwing]

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

https://github.com/apache/nifi/pull/1112#discussion_r82326589
  
--- Diff: 
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/credentials/provider/factory/CredentialPropertyDescriptors.java
 ---
@@ -153,6 +154,29 @@
 .addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
 .sensitive(false)
 .description("External ID for cross-account access. This is 
used in conjunction with role arn, " +
-"role name, and optional session time out")
+"role name, and optional session time out")
--- End diff --

Same question on the indentation change.


---
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 #1112: NIFI-2799: AWS Credentials for Assume Role Need Pro...

[jvwing]

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

https://github.com/apache/nifi/pull/1112#discussion_r82327829
  
--- Diff: 
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/credentials/provider/factory/strategies/AssumeRoleCredentialsStrategy.java
 ---
@@ -113,16 +134,34 @@ public AWSCredentialsProvider 
getDerivedCredentialsProvider(Map

[jira] [Comment Edited] (NIFI-2870) Allow to set replication factor in Kafka Consume Processor

[Stephane Maarek (JIRA)]

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

Stephane Maarek edited comment on NIFI-2870 at 10/7/16 4:16 AM:


you're right, somehow I messed that up. Things are working for me now! please 
close the issue.. 


was (Author: stephane.maa...@gmail.com):
you're right, somehow I messed that up. Things are working for me now!

> Allow to set replication factor in Kafka Consume Processor
> --
>
> Key: NIFI-2870
> URL: https://issues.apache.org/jira/browse/NIFI-2870
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
> Environment: standard installation
>Reporter: Stephane Maarek
>
> I deployed a Kafka cluster with one broker only (I know it's bad), but then 
> when trying to read from the ConsumeKafka0.10, I came across this error:
> replication factor: 3 larger than available brokers: 1
> I believe the replication factor should be a parameter in the processor?



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

[jira] [Commented] (NIFI-2870) Allow to set replication factor in Kafka Consume Processor

[Stephane Maarek (JIRA)]

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

Stephane Maarek commented on NIFI-2870:
---

you're right, somehow I messed that up. Things are working for me now!

> Allow to set replication factor in Kafka Consume Processor
> --
>
> Key: NIFI-2870
> URL: https://issues.apache.org/jira/browse/NIFI-2870
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
> Environment: standard installation
>Reporter: Stephane Maarek
>
> I deployed a Kafka cluster with one broker only (I know it's bad), but then 
> when trying to read from the ConsumeKafka0.10, I came across this error:
> replication factor: 3 larger than available brokers: 1
> I believe the replication factor should be a parameter in the processor?



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

[jira] [Commented] (NIFI-2873) Nifi throws UnknownHostException with HA NameNode

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2873:
--

GitHub user baank opened a pull request:

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

NIFI-2873: Nifi throws UnknownHostException with HA NameNode

Thank you for submitting a contribution to Apache NiFi.

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

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

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

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

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

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

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

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



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

$ git pull https://github.com/baank/nifi upstream

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

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


commit bf2e4c9d6cbaccf8e1b01c774f92c2c99676716f
Author: d810146 
Date:   2016-10-07T02:27:30Z

NIFI-2873: Nifi throws UnknownHostException with HA NameNode




> Nifi throws UnknownHostException with HA NameNode
> -
>
> Key: NIFI-2873
> URL: https://issues.apache.org/jira/browse/NIFI-2873
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0
>Reporter: Franco
> Fix For: 1.1.0
>
>
> This is the same issue that previously affected Spark:
> https://github.com/Jianfeng-chs/spark/commit/9f2b2bf001262215742be418f24d5093c92ff10f
> We are experiencing this issue consistently when trying to use 
> PutHiveStreaming. In theory this should be a problem with GetHDFS but for 
> whatever reason it is not.
> The fix is identical namely preloading the Hadoop configuration during the 
> processor setup phase. Pull request forthcoming.
> {code:title=Stack Trace|borderStyle=solid}
> 2016-10-06 16:07:59,225 ERROR [Timer-Driven Process Thread-9] 
> o.a.n.processors.hive.PutHiveStreaming
> java.lang.IllegalArgumentException: java.net.UnknownHostException: tdcdv2
> at 
> org.apache.hadoop.security.SecurityUtil.buildTokenService(SecurityUtil.java:374)
>  ~[hadoop-common-2.6.2.jar:na]
> at 
> org.apache.hadoop.hdfs.NameNodeProxies.createNonHAProxy(NameNodeProxies.java:310)
>  ~[hadoop-hdfs-2.6.2.jar:na]
> at 
> org.apache.hadoop.hdfs.NameNodeProxies.createProxy(NameNodeProxies.java:176) 
> ~[hadoop-hdfs-2.6.2.jar:na]
> at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:668) 
> ~[hadoop-hdfs-2.6.2.jar:na]
> at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:604) 
> ~[hadoop-hdfs-2.6.2.jar:na]
> at 
> org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:148)
>  ~[hadoop-hdfs-2.6.2.jar:na]
> at 
> org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2596) 
> ~[hadoop-common-2.6.2.jar:na]
> at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:91) 
> ~[hadoop-common-2.6.2.jar:na]
> at 
> org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2630) 
> ~[hadoop-common-2.6.2.jar:na]
> at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2612) 

[jira] [Updated] (NIFI-2873) Nifi throws UnknownHostException with HA NameNode

[Franco (JIRA)]

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

Franco updated NIFI-2873:
-
Description: 
This is the same issue that previously affected Spark:
https://github.com/Jianfeng-chs/spark/commit/9f2b2bf001262215742be418f24d5093c92ff10f

We are experiencing this issue consistently when trying to use 
PutHiveStreaming. In theory this should be a problem with GetHDFS but for 
whatever reason it is not.

The fix is identical namely preloading the Hadoop configuration during the 
processor setup phase. Pull request forthcoming.

{code:title=Stack Trace|borderStyle=solid}
2016-10-06 16:07:59,225 ERROR [Timer-Driven Process Thread-9] 
o.a.n.processors.hive.PutHiveStreaming
java.lang.IllegalArgumentException: java.net.UnknownHostException: tdcdv2
at 
org.apache.hadoop.security.SecurityUtil.buildTokenService(SecurityUtil.java:374)
 ~[hadoop-common-2.6.2.jar:na]
at 
org.apache.hadoop.hdfs.NameNodeProxies.createNonHAProxy(NameNodeProxies.java:310)
 ~[hadoop-hdfs-2.6.2.jar:na]
at 
org.apache.hadoop.hdfs.NameNodeProxies.createProxy(NameNodeProxies.java:176) 
~[hadoop-hdfs-2.6.2.jar:na]
at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:668) 
~[hadoop-hdfs-2.6.2.jar:na]
at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:604) 
~[hadoop-hdfs-2.6.2.jar:na]
at 
org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:148)
 ~[hadoop-hdfs-2.6.2.jar:na]
at 
org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2596) 
~[hadoop-common-2.6.2.jar:na]
at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:91) 
~[hadoop-common-2.6.2.jar:na]
at 
org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2630) 
~[hadoop-common-2.6.2.jar:na]
at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2612) 
~[hadoop-common-2.6.2.jar:na]
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:370) 
~[hadoop-common-2.6.2.jar:na]
at org.apache.hadoop.fs.Path.getFileSystem(Path.java:296) 
~[hadoop-common-2.6.2.jar:na]
at 
org.apache.hadoop.hive.ql.io.orc.OrcRecordUpdater.(OrcRecordUpdater.java:221)
 ~[hive-exec-1.2.1.jar:1.2.1]
at 
org.apache.hadoop.hive.ql.io.orc.OrcOutputFormat.getRecordUpdater(OrcOutputFormat.java:292)
 ~[hive-exec-1.2.1.jar:1.2.1]
at 
org.apache.hive.hcatalog.streaming.AbstractRecordWriter.createRecordUpdater(AbstractRecordWriter.java:141)
 ~[hive-hcatalog-streaming-1.2.1.jar:1.2.1]
at 
org.apache.hive.hcatalog.streaming.AbstractRecordWriter.newBatch(AbstractRecordWriter.java:121)
 ~[hive-hcatalog-streaming-1.2.1.jar:1.2.1]
at 
org.apache.hive.hcatalog.streaming.StrictJsonWriter.newBatch(StrictJsonWriter.java:37)
 ~[hive-hcatalog-streaming-1.2.1.jar:1.2.1]
at 
org.apache.hive.hcatalog.streaming.HiveEndPoint$TransactionBatchImpl.(HiveEndPoint.java:509)
 ~[hive-hcatalog-streaming-1.2.1.jar:1.2.1]
at 
org.apache.hive.hcatalog.streaming.HiveEndPoint$TransactionBatchImpl.(HiveEndPoint.java:461)
 ~[hive-hcatalog-streaming-1.2.1.jar:1.2.1]
at 
org.apache.hive.hcatalog.streaming.HiveEndPoint$ConnectionImpl.fetchTransactionBatchImpl(HiveEndPoint.java:345)
 ~[hive-hcatalog-streaming-1.2.1.jar:1.2.1]
at 
org.apache.hive.hcatalog.streaming.HiveEndPoint$ConnectionImpl.fetchTransactionBatch(HiveEndPoint.java:325)
 ~[hive-hcatalog-streaming-1.2.1.jar:1.2.1]
at 
org.apache.nifi.util.hive.HiveWriter.lambda$nextTxnBatch$1(HiveWriter.java:250) 
~[nifi-hive-processors-1.0.0.jar:1.0.0]
{code}

  was:
This is the same issue that previously affected Spark:
https://github.com/Jianfeng-chs/spark/commit/9f2b2bf001262215742be418f24d5093c92ff10f

We are experiencing this issue consistently when trying to use PutHiveStreaming.

The fix is identical namely preloading the Hadoop configuration during the 
processor setup phase. Pull request forthcoming.

{code:title=Stack Trace|borderStyle=solid}
2016-10-06 16:07:59,225 ERROR [Timer-Driven Process Thread-9] 
o.a.n.processors.hive.PutHiveStreaming
java.lang.IllegalArgumentException: java.net.UnknownHostException: tdcdv2
at 
org.apache.hadoop.security.SecurityUtil.buildTokenService(SecurityUtil.java:374)
 ~[hadoop-common-2.6.2.jar:na]
at 
org.apache.hadoop.hdfs.NameNodeProxies.createNonHAProxy(NameNodeProxies.java:310)
 ~[hadoop-hdfs-2.6.2.jar:na]
at 
org.apache.hadoop.hdfs.NameNodeProxies.createProxy(NameNodeProxies.java:176) 
~[hadoop-hdfs-2.6.2.jar:na]
at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:668) 
~[hadoop-hdfs-2.6.2.jar:na]
at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:604) 
~[hadoop-hdfs-2.6.2.jar:na]
at 
org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:148)
 ~[hadoop-hdfs-2.6.2.jar:na]
at 
org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2596) 

[jira] [Updated] (NIFI-2873) Nifi throws UnknownHostException with HA NameNode

[Franco (JIRA)]

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

Franco updated NIFI-2873:
-
Description: 
This is the same issue that previously affected Spark:
https://github.com/Jianfeng-chs/spark/commit/9f2b2bf001262215742be418f24d5093c92ff10f

We are experiencing this issue consistently when trying to use PutHiveStreaming.

The fix is identical namely preloading the Hadoop configuration during the 
processor setup phase. Pull request forthcoming.

{code:title=Stack Trace|borderStyle=solid}
2016-10-06 16:07:59,225 ERROR [Timer-Driven Process Thread-9] 
o.a.n.processors.hive.PutHiveStreaming
java.lang.IllegalArgumentException: java.net.UnknownHostException: tdcdv2
at 
org.apache.hadoop.security.SecurityUtil.buildTokenService(SecurityUtil.java:374)
 ~[hadoop-common-2.6.2.jar:na]
at 
org.apache.hadoop.hdfs.NameNodeProxies.createNonHAProxy(NameNodeProxies.java:310)
 ~[hadoop-hdfs-2.6.2.jar:na]
at 
org.apache.hadoop.hdfs.NameNodeProxies.createProxy(NameNodeProxies.java:176) 
~[hadoop-hdfs-2.6.2.jar:na]
at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:668) 
~[hadoop-hdfs-2.6.2.jar:na]
at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:604) 
~[hadoop-hdfs-2.6.2.jar:na]
at 
org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:148)
 ~[hadoop-hdfs-2.6.2.jar:na]
at 
org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2596) 
~[hadoop-common-2.6.2.jar:na]
at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:91) 
~[hadoop-common-2.6.2.jar:na]
at 
org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2630) 
~[hadoop-common-2.6.2.jar:na]
at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2612) 
~[hadoop-common-2.6.2.jar:na]
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:370) 
~[hadoop-common-2.6.2.jar:na]
at org.apache.hadoop.fs.Path.getFileSystem(Path.java:296) 
~[hadoop-common-2.6.2.jar:na]
at 
org.apache.hadoop.hive.ql.io.orc.OrcRecordUpdater.(OrcRecordUpdater.java:221)
 ~[hive-exec-1.2.1.jar:1.2.1]
at 
org.apache.hadoop.hive.ql.io.orc.OrcOutputFormat.getRecordUpdater(OrcOutputFormat.java:292)
 ~[hive-exec-1.2.1.jar:1.2.1]
at 
org.apache.hive.hcatalog.streaming.AbstractRecordWriter.createRecordUpdater(AbstractRecordWriter.java:141)
 ~[hive-hcatalog-streaming-1.2.1.jar:1.2.1]
at 
org.apache.hive.hcatalog.streaming.AbstractRecordWriter.newBatch(AbstractRecordWriter.java:121)
 ~[hive-hcatalog-streaming-1.2.1.jar:1.2.1]
at 
org.apache.hive.hcatalog.streaming.StrictJsonWriter.newBatch(StrictJsonWriter.java:37)
 ~[hive-hcatalog-streaming-1.2.1.jar:1.2.1]
at 
org.apache.hive.hcatalog.streaming.HiveEndPoint$TransactionBatchImpl.(HiveEndPoint.java:509)
 ~[hive-hcatalog-streaming-1.2.1.jar:1.2.1]
at 
org.apache.hive.hcatalog.streaming.HiveEndPoint$TransactionBatchImpl.(HiveEndPoint.java:461)
 ~[hive-hcatalog-streaming-1.2.1.jar:1.2.1]
at 
org.apache.hive.hcatalog.streaming.HiveEndPoint$ConnectionImpl.fetchTransactionBatchImpl(HiveEndPoint.java:345)
 ~[hive-hcatalog-streaming-1.2.1.jar:1.2.1]
at 
org.apache.hive.hcatalog.streaming.HiveEndPoint$ConnectionImpl.fetchTransactionBatch(HiveEndPoint.java:325)
 ~[hive-hcatalog-streaming-1.2.1.jar:1.2.1]
at 
org.apache.nifi.util.hive.HiveWriter.lambda$nextTxnBatch$1(HiveWriter.java:250) 
~[nifi-hive-processors-1.0.0.jar:1.0.0]
{code}

  was:
This is the same issue that previously affected Spark:
https://github.com/Jianfeng-chs/spark/commit/9f2b2bf001262215742be418f24d5093c92ff10f

We are experiencing this issue consistently when trying to use PutHiveStreaming 
and likely would affect PutHiveQL.

The fix is identical namely preloading the Hadoop configuration during the 
processor setup phase. Pull request forthcoming.

{code:title=Stack Trace|borderStyle=solid}
2016-10-06 16:07:59,225 ERROR [Timer-Driven Process Thread-9] 
o.a.n.processors.hive.PutHiveStreaming
java.lang.IllegalArgumentException: java.net.UnknownHostException: tdcdv2
at 
org.apache.hadoop.security.SecurityUtil.buildTokenService(SecurityUtil.java:374)
 ~[hadoop-common-2.6.2.jar:na]
at 
org.apache.hadoop.hdfs.NameNodeProxies.createNonHAProxy(NameNodeProxies.java:310)
 ~[hadoop-hdfs-2.6.2.jar:na]
at 
org.apache.hadoop.hdfs.NameNodeProxies.createProxy(NameNodeProxies.java:176) 
~[hadoop-hdfs-2.6.2.jar:na]
at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:668) 
~[hadoop-hdfs-2.6.2.jar:na]
at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:604) 
~[hadoop-hdfs-2.6.2.jar:na]
at 
org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:148)
 ~[hadoop-hdfs-2.6.2.jar:na]
at 
org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2596) 
~[hadoop-common-2.6.2.jar:na]
at 

[jira] [Updated] (NIFI-2873) Nifi throws UnknownHostException with HA NameNode

[Franco (JIRA)]

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

Franco updated NIFI-2873:
-
Description: 
This is the same issue that previously affected Spark:
https://github.com/Jianfeng-chs/spark/commit/9f2b2bf001262215742be418f24d5093c92ff10f

We are experiencing this issue consistently when trying to use PutHiveStreaming 
and likely would affect PutHiveQL.

The fix is identical namely preloading the Hadoop configuration during the 
processor setup phase. Pull request forthcoming.

{code:title=Stack Trace|borderStyle=solid}
2016-10-06 16:07:59,225 ERROR [Timer-Driven Process Thread-9] 
o.a.n.processors.hive.PutHiveStreaming
java.lang.IllegalArgumentException: java.net.UnknownHostException: tdcdv2
at 
org.apache.hadoop.security.SecurityUtil.buildTokenService(SecurityUtil.java:374)
 ~[hadoop-common-2.6.2.jar:na]
at 
org.apache.hadoop.hdfs.NameNodeProxies.createNonHAProxy(NameNodeProxies.java:310)
 ~[hadoop-hdfs-2.6.2.jar:na]
at 
org.apache.hadoop.hdfs.NameNodeProxies.createProxy(NameNodeProxies.java:176) 
~[hadoop-hdfs-2.6.2.jar:na]
at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:668) 
~[hadoop-hdfs-2.6.2.jar:na]
at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:604) 
~[hadoop-hdfs-2.6.2.jar:na]
at 
org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:148)
 ~[hadoop-hdfs-2.6.2.jar:na]
at 
org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2596) 
~[hadoop-common-2.6.2.jar:na]
at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:91) 
~[hadoop-common-2.6.2.jar:na]
at 
org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2630) 
~[hadoop-common-2.6.2.jar:na]
at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2612) 
~[hadoop-common-2.6.2.jar:na]
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:370) 
~[hadoop-common-2.6.2.jar:na]
at org.apache.hadoop.fs.Path.getFileSystem(Path.java:296) 
~[hadoop-common-2.6.2.jar:na]
at 
org.apache.hadoop.hive.ql.io.orc.OrcRecordUpdater.(OrcRecordUpdater.java:221)
 ~[hive-exec-1.2.1.jar:1.2.1]
at 
org.apache.hadoop.hive.ql.io.orc.OrcOutputFormat.getRecordUpdater(OrcOutputFormat.java:292)
 ~[hive-exec-1.2.1.jar:1.2.1]
at 
org.apache.hive.hcatalog.streaming.AbstractRecordWriter.createRecordUpdater(AbstractRecordWriter.java:141)
 ~[hive-hcatalog-streaming-1.2.1.jar:1.2.1]
at 
org.apache.hive.hcatalog.streaming.AbstractRecordWriter.newBatch(AbstractRecordWriter.java:121)
 ~[hive-hcatalog-streaming-1.2.1.jar:1.2.1]
at 
org.apache.hive.hcatalog.streaming.StrictJsonWriter.newBatch(StrictJsonWriter.java:37)
 ~[hive-hcatalog-streaming-1.2.1.jar:1.2.1]
at 
org.apache.hive.hcatalog.streaming.HiveEndPoint$TransactionBatchImpl.(HiveEndPoint.java:509)
 ~[hive-hcatalog-streaming-1.2.1.jar:1.2.1]
at 
org.apache.hive.hcatalog.streaming.HiveEndPoint$TransactionBatchImpl.(HiveEndPoint.java:461)
 ~[hive-hcatalog-streaming-1.2.1.jar:1.2.1]
at 
org.apache.hive.hcatalog.streaming.HiveEndPoint$ConnectionImpl.fetchTransactionBatchImpl(HiveEndPoint.java:345)
 ~[hive-hcatalog-streaming-1.2.1.jar:1.2.1]
at 
org.apache.hive.hcatalog.streaming.HiveEndPoint$ConnectionImpl.fetchTransactionBatch(HiveEndPoint.java:325)
 ~[hive-hcatalog-streaming-1.2.1.jar:1.2.1]
at 
org.apache.nifi.util.hive.HiveWriter.lambda$nextTxnBatch$1(HiveWriter.java:250) 
~[nifi-hive-processors-1.0.0.jar:1.0.0]
{code}

  was:
This is the same issue that previously affected Spark:
https://github.com/Jianfeng-chs/spark/commit/9f2b2bf001262215742be418f24d5093c92ff10f

We are experiencing this issue consistently when trying to use PutHiveStreaming 
and likely would affect PutHiveQL.

The fix is identical namely preloading the Hadoop configuration during the 
processor setup phase. Pull request forthcoming.

{code:title=Bar.java|borderStyle=solid}
2016-10-06 16:07:59,225 ERROR [Timer-Driven Process Thread-9] 
o.a.n.processors.hive.PutHiveStreaming
java.lang.IllegalArgumentException: java.net.UnknownHostException: tdcdv2
at 
org.apache.hadoop.security.SecurityUtil.buildTokenService(SecurityUtil.java:374)
 ~[hadoop-common-2.6.2.jar:na]
at 
org.apache.hadoop.hdfs.NameNodeProxies.createNonHAProxy(NameNodeProxies.java:310)
 ~[hadoop-hdfs-2.6.2.jar:na]
at 
org.apache.hadoop.hdfs.NameNodeProxies.createProxy(NameNodeProxies.java:176) 
~[hadoop-hdfs-2.6.2.jar:na]
at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:668) 
~[hadoop-hdfs-2.6.2.jar:na]
at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:604) 
~[hadoop-hdfs-2.6.2.jar:na]
at 
org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:148)
 ~[hadoop-hdfs-2.6.2.jar:na]
at 
org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2596) 

[jira] [Updated] (NIFI-2873) Nifi throws UnknownHostException with HA NameNode

[Franco (JIRA)]

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

Franco updated NIFI-2873:
-
Description: 
This is the same issue that previously affected Spark:
https://github.com/Jianfeng-chs/spark/commit/9f2b2bf001262215742be418f24d5093c92ff10f

We are experiencing this issue consistently when trying to use PutHiveStreaming 
and likely would affect PutHiveQL.

The fix is identical namely preloading the Hadoop configuration during the 
processor setup phase. Pull request forthcoming.

{code:title=Bar.java|borderStyle=solid}
2016-10-06 16:07:59,225 ERROR [Timer-Driven Process Thread-9] 
o.a.n.processors.hive.PutHiveStreaming
java.lang.IllegalArgumentException: java.net.UnknownHostException: tdcdv2
at 
org.apache.hadoop.security.SecurityUtil.buildTokenService(SecurityUtil.java:374)
 ~[hadoop-common-2.6.2.jar:na]
at 
org.apache.hadoop.hdfs.NameNodeProxies.createNonHAProxy(NameNodeProxies.java:310)
 ~[hadoop-hdfs-2.6.2.jar:na]
at 
org.apache.hadoop.hdfs.NameNodeProxies.createProxy(NameNodeProxies.java:176) 
~[hadoop-hdfs-2.6.2.jar:na]
at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:668) 
~[hadoop-hdfs-2.6.2.jar:na]
at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:604) 
~[hadoop-hdfs-2.6.2.jar:na]
at 
org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:148)
 ~[hadoop-hdfs-2.6.2.jar:na]
at 
org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2596) 
~[hadoop-common-2.6.2.jar:na]
at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:91) 
~[hadoop-common-2.6.2.jar:na]
at 
org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2630) 
~[hadoop-common-2.6.2.jar:na]
at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2612) 
~[hadoop-common-2.6.2.jar:na]
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:370) 
~[hadoop-common-2.6.2.jar:na]
at org.apache.hadoop.fs.Path.getFileSystem(Path.java:296) 
~[hadoop-common-2.6.2.jar:na]
at 
org.apache.hadoop.hive.ql.io.orc.OrcRecordUpdater.(OrcRecordUpdater.java:221)
 ~[hive-exec-1.2.1.jar:1.2.1]
at 
org.apache.hadoop.hive.ql.io.orc.OrcOutputFormat.getRecordUpdater(OrcOutputFormat.java:292)
 ~[hive-exec-1.2.1.jar:1.2.1]
at 
org.apache.hive.hcatalog.streaming.AbstractRecordWriter.createRecordUpdater(AbstractRecordWriter.java:141)
 ~[hive-hcatalog-streaming-1.2.1.jar:1.2.1]
at 
org.apache.hive.hcatalog.streaming.AbstractRecordWriter.newBatch(AbstractRecordWriter.java:121)
 ~[hive-hcatalog-streaming-1.2.1.jar:1.2.1]
at 
org.apache.hive.hcatalog.streaming.StrictJsonWriter.newBatch(StrictJsonWriter.java:37)
 ~[hive-hcatalog-streaming-1.2.1.jar:1.2.1]
at 
org.apache.hive.hcatalog.streaming.HiveEndPoint$TransactionBatchImpl.(HiveEndPoint.java:509)
 ~[hive-hcatalog-streaming-1.2.1.jar:1.2.1]
at 
org.apache.hive.hcatalog.streaming.HiveEndPoint$TransactionBatchImpl.(HiveEndPoint.java:461)
 ~[hive-hcatalog-streaming-1.2.1.jar:1.2.1]
at 
org.apache.hive.hcatalog.streaming.HiveEndPoint$ConnectionImpl.fetchTransactionBatchImpl(HiveEndPoint.java:345)
 ~[hive-hcatalog-streaming-1.2.1.jar:1.2.1]
at 
org.apache.hive.hcatalog.streaming.HiveEndPoint$ConnectionImpl.fetchTransactionBatch(HiveEndPoint.java:325)
 ~[hive-hcatalog-streaming-1.2.1.jar:1.2.1]
at 
org.apache.nifi.util.hive.HiveWriter.lambda$nextTxnBatch$1(HiveWriter.java:250) 
~[nifi-hive-processors-1.0.0.jar:1.0.0]
{code}

  was:
This is the same issue that previously affected Spark:
https://github.com/Jianfeng-chs/spark/commit/9f2b2bf001262215742be418f24d5093c92ff10f

We are experiencing this issue consistently when trying to use PutHiveStreaming 
and likely would affect PutHiveQL.

The fix is identical namely preloading the Hadoop configuration during the 
processor setup phase. Pull request forthcoming.


---
2016-10-06 16:07:59,225 ERROR [Timer-Driven Process Thread-9] 
o.a.n.processors.hive.PutHiveStreaming
java.lang.IllegalArgumentException: java.net.UnknownHostException: tdcdv2
at 
org.apache.hadoop.security.SecurityUtil.buildTokenService(SecurityUtil.java:374)
 ~[hadoop-common-2.6.2.jar:na]
at 
org.apache.hadoop.hdfs.NameNodeProxies.createNonHAProxy(NameNodeProxies.java:310)
 ~[hadoop-hdfs-2.6.2.jar:na]
at 
org.apache.hadoop.hdfs.NameNodeProxies.createProxy(NameNodeProxies.java:176) 
~[hadoop-hdfs-2.6.2.jar:na]
at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:668) 
~[hadoop-hdfs-2.6.2.jar:na]
at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:604) 
~[hadoop-hdfs-2.6.2.jar:na]
at 
org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:148)
 ~[hadoop-hdfs-2.6.2.jar:na]
at 
org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2596) 
~[hadoop-common-2.6.2.jar:na]
   

[jira] [Updated] (NIFI-2873) Nifi throws UnknownHostException with HA NameNode

[Franco (JIRA)]

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

Franco updated NIFI-2873:
-
Description: 
This is the same issue that previously affected Spark:
https://github.com/Jianfeng-chs/spark/commit/9f2b2bf001262215742be418f24d5093c92ff10f

We are experiencing this issue consistently when trying to use PutHiveStreaming 
and likely would affect PutHiveQL.

The fix is identical namely preloading the Hadoop configuration during the 
processor setup phase. Pull request forthcoming.


---
2016-10-06 16:07:59,225 ERROR [Timer-Driven Process Thread-9] 
o.a.n.processors.hive.PutHiveStreaming
java.lang.IllegalArgumentException: java.net.UnknownHostException: tdcdv2
at 
org.apache.hadoop.security.SecurityUtil.buildTokenService(SecurityUtil.java:374)
 ~[hadoop-common-2.6.2.jar:na]
at 
org.apache.hadoop.hdfs.NameNodeProxies.createNonHAProxy(NameNodeProxies.java:310)
 ~[hadoop-hdfs-2.6.2.jar:na]
at 
org.apache.hadoop.hdfs.NameNodeProxies.createProxy(NameNodeProxies.java:176) 
~[hadoop-hdfs-2.6.2.jar:na]
at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:668) 
~[hadoop-hdfs-2.6.2.jar:na]
at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:604) 
~[hadoop-hdfs-2.6.2.jar:na]
at 
org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:148)
 ~[hadoop-hdfs-2.6.2.jar:na]
at 
org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2596) 
~[hadoop-common-2.6.2.jar:na]
at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:91) 
~[hadoop-common-2.6.2.jar:na]
at 
org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2630) 
~[hadoop-common-2.6.2.jar:na]
at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2612) 
~[hadoop-common-2.6.2.jar:na]
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:370) 
~[hadoop-common-2.6.2.jar:na]
at org.apache.hadoop.fs.Path.getFileSystem(Path.java:296) 
~[hadoop-common-2.6.2.jar:na]
at 
org.apache.hadoop.hive.ql.io.orc.OrcRecordUpdater.(OrcRecordUpdater.java:221)
 ~[hive-exec-1.2.1.jar:1.2.1]
at 
org.apache.hadoop.hive.ql.io.orc.OrcOutputFormat.getRecordUpdater(OrcOutputFormat.java:292)
 ~[hive-exec-1.2.1.jar:1.2.1]
at 
org.apache.hive.hcatalog.streaming.AbstractRecordWriter.createRecordUpdater(AbstractRecordWriter.java:141)
 ~[hive-hcatalog-streaming-1.2.1.jar:1.2.1]
at 
org.apache.hive.hcatalog.streaming.AbstractRecordWriter.newBatch(AbstractRecordWriter.java:121)
 ~[hive-hcatalog-streaming-1.2.1.jar:1.2.1]
at 
org.apache.hive.hcatalog.streaming.StrictJsonWriter.newBatch(StrictJsonWriter.java:37)
 ~[hive-hcatalog-streaming-1.2.1.jar:1.2.1]
at 
org.apache.hive.hcatalog.streaming.HiveEndPoint$TransactionBatchImpl.(HiveEndPoint.java:509)
 ~[hive-hcatalog-streaming-1.2.1.jar:1.2.1]
at 
org.apache.hive.hcatalog.streaming.HiveEndPoint$TransactionBatchImpl.(HiveEndPoint.java:461)
 ~[hive-hcatalog-streaming-1.2.1.jar:1.2.1]
at 
org.apache.hive.hcatalog.streaming.HiveEndPoint$ConnectionImpl.fetchTransactionBatchImpl(HiveEndPoint.java:345)
 ~[hive-hcatalog-streaming-1.2.1.jar:1.2.1]
at 
org.apache.hive.hcatalog.streaming.HiveEndPoint$ConnectionImpl.fetchTransactionBatch(HiveEndPoint.java:325)
 ~[hive-hcatalog-streaming-1.2.1.jar:1.2.1]
at 
org.apache.nifi.util.hive.HiveWriter.lambda$nextTxnBatch$1(HiveWriter.java:250) 
~[nifi-hive-processors-1.0.0.jar:1.0.0]

  was:
This is the same issue that previously affected Spark:
https://github.com/Jianfeng-chs/spark/commit/9f2b2bf001262215742be418f24d5093c92ff10f

We are experiencing this issue consistently when trying to use PutHiveStreaming 
and likely would affect PutHiveQL.

The fix is identical namely preloading the Hadoop configuration during the 
processor setup phase. Pull request forthcoming.


> Nifi throws UnknownHostException with HA NameNode
> -
>
> Key: NIFI-2873
> URL: https://issues.apache.org/jira/browse/NIFI-2873
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0
>Reporter: Franco
> Fix For: 1.1.0
>
>
> This is the same issue that previously affected Spark:
> https://github.com/Jianfeng-chs/spark/commit/9f2b2bf001262215742be418f24d5093c92ff10f
> We are experiencing this issue consistently when trying to use 
> PutHiveStreaming and likely would affect PutHiveQL.
> The fix is identical namely preloading the Hadoop configuration during the 
> processor setup phase. Pull request forthcoming.
> ---
> 2016-10-06 16:07:59,225 ERROR [Timer-Driven Process Thread-9] 
> o.a.n.processors.hive.PutHiveStreaming
> java.lang.IllegalArgumentException: java.net.UnknownHostException: tdcdv2
> at 
> 

[jira] [Created] (NIFI-2872) Create PutCloudwatchMetric Processor

[Edgardo Vega (JIRA)]

Edgardo Vega created NIFI-2872:
--

 Summary: Create PutCloudwatchMetric Processor
 Key: NIFI-2872
 URL: https://issues.apache.org/jira/browse/NIFI-2872
 Project: Apache NiFi
  Issue Type: Task
  Components: Core Framework
Affects Versions: 1.1.0
Reporter: Edgardo Vega
Priority: Minor


Create a processor for put metrics into aws cloudwatch.



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

[GitHub] nifi issue #1108: NIFI-2565: add Grok parser

[trixpan]

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/1108
  
By the way, most of these modifications are already available here: 

https://github.com/trixpan/nifi/commits/NIFI-2565


---
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-2565) NiFi processor to parse logs using Grok patterns

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2565:
--

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/1108
  
By the way, most of these modifications are already available here: 

https://github.com/trixpan/nifi/commits/NIFI-2565


> NiFi processor to parse logs using Grok patterns
> 
>
> Key: NIFI-2565
> URL: https://issues.apache.org/jira/browse/NIFI-2565
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Andre
> Fix For: 1.1.0
>
>
> Following up on Ryan Ward to create a Grok capable parser
> https://mail-archives.apache.org/mod_mbox/nifi-dev/201606.mbox/%3CCADD=rnPa8nHkJbeM280=PTQ=wurtwhstm5u+7btoo9pcym2...@mail.gmail.com%3E



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

[jira] [Commented] (NIFI-2565) NiFi processor to parse logs using Grok patterns

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2565:
--

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/1108
  
You can certainly include a file with the default patterns, however you 
should not hardcode them. By hardcoding them you prevent the user from 
optimising for speed by removing unused patterns from the pattern files (I 
realise they can remove from the default packaged patterns but that means they 
would be changing packaged files after an install, something you should always 
avoid) 


> NiFi processor to parse logs using Grok patterns
> 
>
> Key: NIFI-2565
> URL: https://issues.apache.org/jira/browse/NIFI-2565
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Andre
> Fix For: 1.1.0
>
>
> Following up on Ryan Ward to create a Grok capable parser
> https://mail-archives.apache.org/mod_mbox/nifi-dev/201606.mbox/%3CCADD=rnPa8nHkJbeM280=PTQ=wurtwhstm5u+7btoo9pcym2...@mail.gmail.com%3E



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

[GitHub] nifi issue #1108: NIFI-2565: add Grok parser

[trixpan]

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/1108
  
You can certainly include a file with the default patterns, however you 
should not hardcode them. By hardcoding them you prevent the user from 
optimising for speed by removing unused patterns from the pattern files (I 
realise they can remove from the default packaged patterns but that means they 
would be changing packaged files after an install, something you should always 
avoid) 


---
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-2565) NiFi processor to parse logs using Grok patterns

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2565:
--

Github user selim-namsi commented on the issue:

https://github.com/apache/nifi/pull/1108
  
@trixpan Thank you for all this useful feedback, I'll start working on 
these modifications.
For the patterns, I hard coded the patterns because I was thinking about 
adding by default some useful patterns and also let the user add his custom 
pattern. What do you think about it ?

Thanks


> NiFi processor to parse logs using Grok patterns
> 
>
> Key: NIFI-2565
> URL: https://issues.apache.org/jira/browse/NIFI-2565
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Andre
> Fix For: 1.1.0
>
>
> Following up on Ryan Ward to create a Grok capable parser
> https://mail-archives.apache.org/mod_mbox/nifi-dev/201606.mbox/%3CCADD=rnPa8nHkJbeM280=PTQ=wurtwhstm5u+7btoo9pcym2...@mail.gmail.com%3E



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

[GitHub] nifi issue #1108: NIFI-2565: add Grok parser

[selim-namsi]

Github user selim-namsi commented on the issue:

https://github.com/apache/nifi/pull/1108
  
@trixpan Thank you for all this useful feedback, I'll start working on 
these modifications.
For the patterns, I hard coded the patterns because I was thinking about 
adding by default some useful patterns and also let the user add his custom 
pattern. What do you think about it ?

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-2799) AWS Credentials for Assume Role Need Proxy

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2799:
--

GitHub user ktseytlin opened a pull request:

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

NIFI-2799: AWS Credentials for Assume Role Need Proxy

Thank you for submitting a contribution to Apache NiFi.

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

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

https://issues.apache.org/jira/browse/NIFI-2799

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

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

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

### For code changes:
- [X] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?

Full tests have been run, and unit tests for additional functionality pass. 
This build has also been tested on AWS and it is confirmed that the way the 
proxy is configured using these changes allow for the AssumeRole tokens to be 
properly generated.

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

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

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

@jvwing 


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

$ git pull https://github.com/ktseytlin/nifi NIFI-2799

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

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


commit e20bb67d94f2bc636ffed6c205a2cebfad5ddab6
Author: Keren Tseytlin 
Date:   2016-10-06T20:44:51Z

Merge pull request #1 from apache/master

Bringing in Nifi master into local

commit 8c6d0c81a2ff5e417ee7b676a0db5d773a6c7679
Author: Keren Tseytlin 
Date:   2016-10-06T21:04:12Z

Updated AssumeAWSCredentials to allow for Assume Role to create and use 
proxy credentials in order to get temprorary access keys when traversing VPCs

commit a980194e9b3ceca0cc8fdd2ad17b996c4c1d19b7
Author: speddy93 
Date:   2016-10-06T21:10:41Z

Added tests: testAssumeRoleInvalidProxyPort




> AWS Credentials for Assume Role Need Proxy
> --
>
> Key: NIFI-2799
> URL: https://issues.apache.org/jira/browse/NIFI-2799
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Keren Tseytlin
>Assignee: James Wing
>Priority: Minor
> Fix For: 1.1.0
>
>
> As a user of Nifi, when I want to enable cross account fetching of S3 objects 
> I need the proxy variables to be set in order to generate temporary AWS 
> tokens for STS:AssumeRole.
> Within some enterprise environments, it is necessary to set the proxy 
> variables prior to running AssumeRole methods. Without this being set, the 
> machine in VPC A times out on generating temporary keys and is unable to 
> assume a role as a machine in VPC B. 
> This ticket arose from this conversation: 
> http://apache-nifi-developer-list.39713.n7.nabble.com/Nifi-Cross-Account-Download-With-A-Profile-Flag-td13232.html#a13252
> Goal: There are files stored in an S3 bucket in VPC B. My Nifi machines are 
> in VPC A. I want Nifi to be able to get those files from VPC B. VPC A and VPC 
> B need to be communicating in the FetchS3Object component.



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

[GitHub] nifi pull request #1112: NIFI-2799: AWS Credentials for Assume Role Need Pro...

[ktseytlin]

GitHub user ktseytlin opened a pull request:

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

NIFI-2799: AWS Credentials for Assume Role Need Proxy

Thank you for submitting a contribution to Apache NiFi.

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

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

https://issues.apache.org/jira/browse/NIFI-2799

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

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

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

### For code changes:
- [X] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?

Full tests have been run, and unit tests for additional functionality pass. 
This build has also been tested on AWS and it is confirmed that the way the 
proxy is configured using these changes allow for the AssumeRole tokens to be 
properly generated.

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

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

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

@jvwing 


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

$ git pull https://github.com/ktseytlin/nifi NIFI-2799

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

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


commit e20bb67d94f2bc636ffed6c205a2cebfad5ddab6
Author: Keren Tseytlin 
Date:   2016-10-06T20:44:51Z

Merge pull request #1 from apache/master

Bringing in Nifi master into local

commit 8c6d0c81a2ff5e417ee7b676a0db5d773a6c7679
Author: Keren Tseytlin 
Date:   2016-10-06T21:04:12Z

Updated AssumeAWSCredentials to allow for Assume Role to create and use 
proxy credentials in order to get temprorary access keys when traversing VPCs

commit a980194e9b3ceca0cc8fdd2ad17b996c4c1d19b7
Author: speddy93 
Date:   2016-10-06T21:10:41Z

Added tests: testAssumeRoleInvalidProxyPort




---
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-2836) Cluster - Request Replication

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2836:
- Ensure that we wait until a request is completed before unlocking the lock 
for request replication
- Ensure that failures do not trigger request completion logic unless the 
failure is the last node to report its status
- This closes #1109


> Cluster - Request Replication
> -
>
> Key: NIFI-2836
> URL: https://issues.apache.org/jira/browse/NIFI-2836
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.1.0
>
>
> When a request is replicated throughout the cluster, the cluster coordinator 
> needs to ensure that request completes (including both parts of the two-phase 
> commit if applicable) prior to replicating the next request.
> Looks like a write lock is obtained while submitted a background task. The 
> actually work completes outside the locks scope.



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

[jira] [Commented] (NIFI-2836) Cluster - Request Replication

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2836:
--

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1109
  
Thanks @markap14! This has been merged to master.


> Cluster - Request Replication
> -
>
> Key: NIFI-2836
> URL: https://issues.apache.org/jira/browse/NIFI-2836
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.1.0
>
>
> When a request is replicated throughout the cluster, the cluster coordinator 
> needs to ensure that request completes (including both parts of the two-phase 
> commit if applicable) prior to replicating the next request.
> Looks like a write lock is obtained while submitted a background task. The 
> actually work completes outside the locks scope.



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

[jira] [Commented] (NIFI-2836) Cluster - Request Replication

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2836:
--

Github user asfgit closed the pull request at:

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


> Cluster - Request Replication
> -
>
> Key: NIFI-2836
> URL: https://issues.apache.org/jira/browse/NIFI-2836
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.1.0
>
>
> When a request is replicated throughout the cluster, the cluster coordinator 
> needs to ensure that request completes (including both parts of the two-phase 
> commit if applicable) prior to replicating the next request.
> Looks like a write lock is obtained while submitted a background task. The 
> actually work completes outside the locks scope.



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

[GitHub] nifi pull request #1109: NIFI-2836: Ensure that we wait until a request is c...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1109: NIFI-2836: Ensure that we wait until a request is complete...

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1109
  
Thanks @markap14! This has been merged to master.


---
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 #1073: Nifi 2829

[paulgibeault]

Github user paulgibeault commented on the issue:

https://github.com/apache/nifi/pull/1073
  
Yes I can squash this, as soon as I learn how.  I am new to this.


---
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-2777) Provenance Events' Node Identifier not set when querying only 1 node in cluster

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2777:
NIFI-2856:
- Only performing response merging when the node is the cluster cooridinator 
even if there is a single response.
- Fixing PropertyDescriptor merging to ensure the 'choosen' descriptor is 
included in map of all responses.

This closes #1095.


> Provenance Events' Node Identifier not set when querying only 1 node in 
> cluster
> ---
>
> Key: NIFI-2777
> URL: https://issues.apache.org/jira/browse/NIFI-2777
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Matt Gilman
> Fix For: 1.1.0
>
>
> If I open the Provenance page and search for a FlowFile UUID and restrict the 
> search to a specific node, the Node Identifier is not populated in the events 
> that are returned. As a result, I cannot view the lineage.



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

[jira] [Created] (NIFI-2871) nifi-app.log disappears after being tailed by "TailFile" for a while

[Haimo Liu (JIRA)]

Haimo Liu created NIFI-2871:
---

 Summary: nifi-app.log disappears after being tailed by "TailFile" 
for a while
 Key: NIFI-2871
 URL: https://issues.apache.org/jira/browse/NIFI-2871
 Project: Apache NiFi
  Issue Type: Bug
  Components: Extensions
Affects Versions: 1.0.0
Reporter: Haimo Liu


If NIFI tries to roll “nifi-app.log” into “nifi-app-timestamp.log”, while the 
log file is being tailed, nifi-app.log will be gone…not sure if this happens 
100% of time, but I am able to reproduce the issue consistently.



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

[jira] [Updated] (NIFI-2848) Queues aren't fairly drained when leading to a single component

[Pierre Villard (JIRA)]

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

Pierre Villard updated NIFI-2848:
-
Status: Patch Available  (was: Open)

> Queues aren't fairly drained when leading to a single component
> ---
>
> Key: NIFI-2848
> URL: https://issues.apache.org/jira/browse/NIFI-2848
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Affects Versions: 0.7.0, 1.0.0
>Reporter: Joseph Gresock
>Assignee: Pierre Villard
> Attachments: Backpressure_prioritization_test.xml, dominate_1.png, 
> dominate_2.png, queue_drain.png
>
>
> Consider the scenario where multiple queues lead to a single component and 
> all of them are full due to back pressure.  With the attached template, it is 
> easily observable that once a single queue starts to drain due to relieved 
> back pressure, it will continue to drain as long as it has incoming flow 
> files.  This means that if there's a constant flow of incoming flow files to 
> this queue, the other queues will never be drained (at least, that's my 
> theory based on several hours of observation).
> To reproduce this: 
> # Load the template into NiFi 1.0.0
> # Play all three GenerateFlowFile processors, but not the UpdateAttribute 
> processor (this simulates backpressure).  Wait until each queue has 1,000 
> flow files (max backpressure)
> # Stop the GenerateFlowFile processors, and play the UpdateAttribute 
> processor (this relieves the backpressure)
> # Observe which queue has started to drain, and start its GenerateFlowFile 
> processor
> # Observe that the other two queues remain full indefinitely, while the 
> draining queue continues to replenish and be drained indefinitely



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

[jira] [Commented] (NIFI-2777) Provenance Events' Node Identifier not set when querying only 1 node in cluster

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2777:
--

Github user asfgit closed the pull request at:

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


> Provenance Events' Node Identifier not set when querying only 1 node in 
> cluster
> ---
>
> Key: NIFI-2777
> URL: https://issues.apache.org/jira/browse/NIFI-2777
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Matt Gilman
> Fix For: 1.1.0
>
>
> If I open the Provenance page and search for a FlowFile UUID and restrict the 
> search to a specific node, the Node Identifier is not populated in the events 
> that are returned. As a result, I cannot view the lineage.



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

[jira] [Updated] (NIFI-2777) Provenance Events' Node Identifier not set when querying only 1 node in cluster

[Mark Payne (JIRA)]

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

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

> Provenance Events' Node Identifier not set when querying only 1 node in 
> cluster
> ---
>
> Key: NIFI-2777
> URL: https://issues.apache.org/jira/browse/NIFI-2777
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Matt Gilman
> Fix For: 1.1.0
>
>
> If I open the Provenance page and search for a FlowFile UUID and restrict the 
> search to a specific node, the Node Identifier is not populated in the events 
> that are returned. As a result, I cannot view the lineage.



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

[jira] [Commented] (NIFI-2856) Queue Listing - Cluster node id is missing

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2777:
NIFI-2856:
- Only performing response merging when the node is the cluster cooridinator 
even if there is a single response.
- Fixing PropertyDescriptor merging to ensure the 'choosen' descriptor is 
included in map of all responses.

This closes #1095.


> Queue Listing - Cluster node id is missing
> --
>
> Key: NIFI-2856
> URL: https://issues.apache.org/jira/browse/NIFI-2856
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework, Core UI
>Reporter: Matt Gilman
>Assignee: Matt Gilman
> Fix For: 1.1.0
>
>
> The cluster node id appears to be missing when performing a queue listing in 
> clustered mode. As a result, subsequent attempts to directly access that 
> flowfile fail with a message indicating that
> {noformat}The id of the node in the cluster is required{noformat}



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

[jira] [Updated] (NIFI-2856) Queue Listing - Cluster node id is missing

[Mark Payne (JIRA)]

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

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

> Queue Listing - Cluster node id is missing
> --
>
> Key: NIFI-2856
> URL: https://issues.apache.org/jira/browse/NIFI-2856
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework, Core UI
>Reporter: Matt Gilman
>Assignee: Matt Gilman
> Fix For: 1.1.0
>
>
> The cluster node id appears to be missing when performing a queue listing in 
> clustered mode. As a result, subsequent attempts to directly access that 
> flowfile fail with a message indicating that
> {noformat}The id of the node in the cluster is required{noformat}



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

[GitHub] nifi issue #1095: Cluster - Merging response when the node is the Cluster Co...

[markap14]

Github user markap14 commented on the issue:

https://github.com/apache/nifi/pull/1095
  
Code changes look good. Appears to have addressed the known issues. +1 will 
merge to master.


---
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-2865) Address issues of PublishKafka blocking when having trouble communicating with Kafka broker and improve performance

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2865: Refactored PublishKafka and PublishKafka_0_10 to allow batching of 
FlowFiles within a single publish and to let messages timeout if not 
acknowledged

Signed-off-by: Bryan Bende 


> Address issues of PublishKafka blocking when having trouble communicating 
> with Kafka broker and improve performance
> ---
>
> Key: NIFI-2865
> URL: https://issues.apache.org/jira/browse/NIFI-2865
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.1.0
>
>
> When NiFi is unable to communicate properly with the Kafka broker, we see the 
> NiFi threads occasionally block. This should be resolvable by calling the 
> wakeup() method of the client. Additionally, if Kafka takes too long to 
> respond, we should be able to route the FlowFile to failure and move on.
> PublishKafka has a nice feature that allows a demarcated stream to be sent as 
> separate messages, so that a large number of messages can be sent as a single 
> FlowFile. However, in the case of individual messages per FlowFile, the 
> performance could be improved by batching together multiple FlowFiles per 
> session



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

[GitHub] nifi pull request #1110: Nifi 2865

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2865) Address issues of PublishKafka blocking when having trouble communicating with Kafka broker and improve performance

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2865: Fixed bug in StreamDemarcator that is exposed when the final bit of 
data in a stream is smaller than the previous and the previous demarcation 
ended on a buffer length boundary

This closes #1110.

Signed-off-by: Bryan Bende 


> Address issues of PublishKafka blocking when having trouble communicating 
> with Kafka broker and improve performance
> ---
>
> Key: NIFI-2865
> URL: https://issues.apache.org/jira/browse/NIFI-2865
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.1.0
>
>
> When NiFi is unable to communicate properly with the Kafka broker, we see the 
> NiFi threads occasionally block. This should be resolvable by calling the 
> wakeup() method of the client. Additionally, if Kafka takes too long to 
> respond, we should be able to route the FlowFile to failure and move on.
> PublishKafka has a nice feature that allows a demarcated stream to be sent as 
> separate messages, so that a large number of messages can be sent as a single 
> FlowFile. However, in the case of individual messages per FlowFile, the 
> performance could be improved by batching together multiple FlowFiles per 
> session



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

[GitHub] nifi pull request #1110: Nifi 2865

[markap14]

GitHub user markap14 opened a pull request:

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

Nifi 2865

Thank you for submitting a contribution to Apache NiFi.

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

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

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

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

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

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

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

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


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

$ git pull https://github.com/markap14/nifi NIFI-2865

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

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


commit 3ebc18d434908685b88d7ab0d74fd40631fa0243
Author: Mark Payne 
Date:   2016-09-08T23:37:35Z

NIFI-2865: Refactored PublishKafka and PublishKafka_0_10 to allow batching 
of FlowFiles within a single publish and to let messages timeout if not 
acknowledged

commit 022370e188c625cc0fe133f2ff314c9639c95724
Author: Mark Payne 
Date:   2016-10-06T19:39:24Z

NIFI-2865: Fixed bug in StreamDemarcator that is exposed when the final bit 
of data in a stream is smaller than the previous and the previous demarcation 
ended on a buffer length boundary




---
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-2865) Address issues of PublishKafka blocking when having trouble communicating with Kafka broker and improve performance

[Bryan Bende (JIRA)]

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

Bryan Bende commented on NIFI-2865:
---

Reverted this commit on master due to a failing test with stream demarcator 
that exposed a bug that needs to be resolved.

> Address issues of PublishKafka blocking when having trouble communicating 
> with Kafka broker and improve performance
> ---
>
> Key: NIFI-2865
> URL: https://issues.apache.org/jira/browse/NIFI-2865
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.1.0
>
>
> When NiFi is unable to communicate properly with the Kafka broker, we see the 
> NiFi threads occasionally block. This should be resolvable by calling the 
> wakeup() method of the client. Additionally, if Kafka takes too long to 
> respond, we should be able to route the FlowFile to failure and move on.
> PublishKafka has a nice feature that allows a demarcated stream to be sent as 
> separate messages, so that a large number of messages can be sent as a single 
> FlowFile. However, in the case of individual messages per FlowFile, the 
> performance could be improved by batching together multiple FlowFiles per 
> session



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

[jira] [Commented] (NIFI-2865) Address issues of PublishKafka blocking when having trouble communicating with Kafka broker and improve performance

[ASF subversion and git services (JIRA)]

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

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

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

Revert "NIFI-2865: Refactored PublishKafka and PublishKafka_0_10 to allow 
batching of FlowFiles within a single publish and to let messages timeout if 
not acknowledged"

This reverts commit 92cca96d49042f9898f93b3a2d2210b924708e52.


> Address issues of PublishKafka blocking when having trouble communicating 
> with Kafka broker and improve performance
> ---
>
> Key: NIFI-2865
> URL: https://issues.apache.org/jira/browse/NIFI-2865
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.1.0
>
>
> When NiFi is unable to communicate properly with the Kafka broker, we see the 
> NiFi threads occasionally block. This should be resolvable by calling the 
> wakeup() method of the client. Additionally, if Kafka takes too long to 
> respond, we should be able to route the FlowFile to failure and move on.
> PublishKafka has a nice feature that allows a demarcated stream to be sent as 
> separate messages, so that a large number of messages can be sent as a single 
> FlowFile. However, in the case of individual messages per FlowFile, the 
> performance could be improved by batching together multiple FlowFiles per 
> session



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

[jira] [Reopened] (NIFI-2865) Address issues of PublishKafka blocking when having trouble communicating with Kafka broker and improve performance

[Bryan Bende (JIRA)]

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

Bryan Bende reopened NIFI-2865:
---

> Address issues of PublishKafka blocking when having trouble communicating 
> with Kafka broker and improve performance
> ---
>
> Key: NIFI-2865
> URL: https://issues.apache.org/jira/browse/NIFI-2865
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.1.0
>
>
> When NiFi is unable to communicate properly with the Kafka broker, we see the 
> NiFi threads occasionally block. This should be resolvable by calling the 
> wakeup() method of the client. Additionally, if Kafka takes too long to 
> respond, we should be able to route the FlowFile to failure and move on.
> PublishKafka has a nice feature that allows a demarcated stream to be sent as 
> separate messages, so that a large number of messages can be sent as a single 
> FlowFile. However, in the case of individual messages per FlowFile, the 
> performance could be improved by batching together multiple FlowFiles per 
> session



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

[GitHub] nifi-minifi-cpp issue #14: MINIFI-34 Establishing CMake build system to prov...

[apiri]

Github user apiri commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/14
  
Yep, sounds fair.  From the reading and research I've done, CMake certainly 
feels like it makes things possible.  Travis is being a little odd with CMake.  
Will work to flush out those issues so that those changes are also included 
with this PR.


---
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 #675: LSB Adherence

[PuspenduBanerjee]

Github user PuspenduBanerjee commented on the issue:

https://github.com/apache/nifi/pull/675
  
taking care of a personal emergency at my native place in India and will
not be available till 17th Oct. Sorry for any inconvenience.


Thanks & Regards,
Puspendu Banerjee

On Thu, Oct 6, 2016 at 9:07 AM, trixpan  wrote:

> @apiri  have a look on
>
> #1092 
>
> and
>
> #1093 
>
> Which are essentially addressing a number of the issues discussed here.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> , or mute
> the thread
> 

> .
>



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

[GitHub] nifi-minifi pull request #41: Adding Travis CI build badge.

[apiri]

GitHub user apiri opened a pull request:

https://github.com/apache/nifi-minifi/pull/41

Adding Travis CI build badge.

Adding Travis CI build badge.

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

$ git pull https://github.com/apiri/nifi-minifi add-travis-badge

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

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


commit 9784d49bea0e8d9026e5f564b0ffb77d6b951f02
Author: Aldrin Piri 
Date:   2016-10-06T18:25:02Z

Adding Travis CI build badge.

Signed-off-by: Aldrin Piri 




---
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 #1090: UI - Policy Management Improvements

[alopresto]

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/1090
  
Reviewing...


---
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-2429) Persistent provenance repo should continue despite indexing failures 0.x branch improvement

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2429:
--

Github user mosermw closed the pull request at:

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


> Persistent provenance repo should continue despite indexing failures 0.x 
> branch improvement
> ---
>
> Key: NIFI-2429
> URL: https://issues.apache.org/jira/browse/NIFI-2429
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core Framework
>Affects Versions: 0.7.0
>Reporter: Joseph Witt
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 0.8.0
>
>
> [~markap14] created this subtask for just the 0.x line so we can get the 1.x 
> ticket addressed.



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

[GitHub] nifi pull request #1072: NIFI-2429 PersistentProvenanceRepository bug fixes

[mosermw]

Github user mosermw closed the pull request at:

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


---
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-1280) Create FilterCSVColumns Processor

[Toivo Adams (JIRA)]

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

Toivo Adams edited comment on NIFI-1280 at 10/6/16 5:30 PM:


[~markap14]

Roughly same way as databases use indexes.
For example 
select * from emp join emp as mgr on emp.mgr = mgr.id where emp.salary > 
mgr.salary

We can create index on salary column.
Of course indexing itself is expensive operation.
But maybe we can find a way how to create index reasonably cheap.
I have crazy idea to create index in previous step during writing to FlowFile.
Of course creating index should optional and should be used with care.
But sometimes it might improve performance considerably.

Maybe indexing is not worth of trouble.

Glad you have new version almost ready.
Certainly I am interested to see it.
I have a feeling this greatly improves user experience.

Thanks
Toivo


was (Author: toivo adams):
@markap14

Roughly same way as databases use indexes.
For example 
select * from emp join emp as mgr on emp.mgr = mgr.id where emp.salary > 
mgr.salary

We can create index on salary column.
Of course indexing itself is expensive operation.
But maybe we can find a way how to create index reasonably cheap.
I have crazy idea to create index in previous step during writing to FlowFile.
Of course creating index should optional and should be used with care.
But sometimes it might improve performance considerably.

Maybe indexing is not worth of trouble.

Glad you have new version almost ready.
Certainly I am interested to see it.
I have a feeling this greatly improves user experience.

Thanks
Toivo

> Create FilterCSVColumns Processor
> -
>
> Key: NIFI-1280
> URL: https://issues.apache.org/jira/browse/NIFI-1280
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Extensions
>Reporter: Mark Payne
>Assignee: Toivo Adams
>
> We should have a Processor that allows users to easily filter out specific 
> columns from CSV data. For instance, a user would configure two different 
> properties: "Columns of Interest" (a comma-separated list of column indexes) 
> and "Filtering Strategy" (Keep Only These Columns, Remove Only These Columns).
> We can do this today with ReplaceText, but it is far more difficult than it 
> would be with this Processor, as the user has to use Regular Expressions, 
> etc. with ReplaceText.
> Eventually a Custom UI could even be built that allows a user to upload a 
> Sample CSV and choose which columns from there, similar to the way that Excel 
> works when importing CSV by dragging and selecting the desired columns? That 
> would certainly be a larger undertaking and would not need to be done for an 
> initial implementation.



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

[jira] [Commented] (NIFI-1280) Create FilterCSVColumns Processor

[Toivo Adams (JIRA)]

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

Toivo Adams commented on NIFI-1280:
---

@markap14

Roughly same way as databases use indexes.
For example 
select * from emp join emp as mgr on emp.mgr = mgr.id where emp.salary > 
mgr.salary

We can create index on salary column.
Of course indexing itself is expensive operation.
But maybe we can find a way how to create index reasonably cheap.
I have crazy idea to create index in previous step during writing to FlowFile.
Of course creating index should optional and should be used with care.
But sometimes it might improve performance considerably.

Maybe indexing is not worth of trouble.

Glad you have new version almost ready.
Certainly I am interested to see it.
I have a feeling this greatly improves user experience.

Thanks
Toivo

> Create FilterCSVColumns Processor
> -
>
> Key: NIFI-1280
> URL: https://issues.apache.org/jira/browse/NIFI-1280
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Extensions
>Reporter: Mark Payne
>Assignee: Toivo Adams
>
> We should have a Processor that allows users to easily filter out specific 
> columns from CSV data. For instance, a user would configure two different 
> properties: "Columns of Interest" (a comma-separated list of column indexes) 
> and "Filtering Strategy" (Keep Only These Columns, Remove Only These Columns).
> We can do this today with ReplaceText, but it is far more difficult than it 
> would be with this Processor, as the user has to use Regular Expressions, 
> etc. with ReplaceText.
> Eventually a Custom UI could even be built that allows a user to upload a 
> Sample CSV and choose which columns from there, similar to the way that Excel 
> works when importing CSV by dragging and selecting the desired columns? That 
> would certainly be a larger undertaking and would not need to be done for an 
> initial implementation.



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

[jira] [Commented] (NIFI-2429) Persistent provenance repo should continue despite indexing failures 0.x branch improvement

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2429:
--

Github user jskora commented on the issue:

https://github.com/apache/nifi/pull/1072
  
Reviewed and committed.

Thanks @mosermw 


> Persistent provenance repo should continue despite indexing failures 0.x 
> branch improvement
> ---
>
> Key: NIFI-2429
> URL: https://issues.apache.org/jira/browse/NIFI-2429
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core Framework
>Affects Versions: 0.7.0
>Reporter: Joseph Witt
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 0.8.0
>
>
> [~markap14] created this subtask for just the 0.x line so we can get the 1.x 
> ticket addressed.



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

[GitHub] nifi issue #1072: NIFI-2429 PersistentProvenanceRepository bug fixes

[jskora]

Github user jskora commented on the issue:

https://github.com/apache/nifi/pull/1072
  
Reviewed and committed.

Thanks @mosermw 


---
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-2395) PersistentProvenanceRepository Deadlocks caused by a blocked journal merge

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2395 This closes #734. Ensure that if we fail to index provenance events 
we do not prevent the repo from continuing to merge journals


> PersistentProvenanceRepository Deadlocks caused by a blocked journal merge
> --
>
> Key: NIFI-2395
> URL: https://issues.apache.org/jira/browse/NIFI-2395
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 0.6.0, 0.7.0
>Reporter: Brian Davis
>Assignee: Joseph Witt
>Priority: Blocker
> Fix For: 1.0.0, 1.0.0-Beta
>
>
> I have a nifi instance that I have been running for about a week and has 
> deadlocked at least 3 times during this time.  When I say deadlock the whole 
> nifi instance stops doing any progress on flowfiles.  I looked at the stack 
> trace and there are a lot of threads stuck doing tasks in the 
> PersistentProvenanceRepository.  Looking at the code I think this is what is 
> happening:
> There is a ReadWriteLock that all the reads are waiting for a write.  The 
> write is in the loop:
> {code}
> while (journalFileCount > journalCountThreshold || repoSize > 
> sizeThreshold) {
> // if a shutdown happens while we are in this loop, kill 
> the rollover thread and break
> if (this.closed.get()) {
> if (future != null) {
> future.cancel(true);
> }
> break;
> }
> if (repoSize > sizeThreshold) {
> logger.debug("Provenance Repository has exceeded its 
> size threshold; will trigger purging of oldest events");
> purgeOldEvents();
> journalFileCount = getJournalCount();
> repoSize = getSize(getLogFiles(), 0L);
> continue;
> } else {
> // if we are constrained by the number of journal 
> files rather than the size of the repo,
> // then we will just sleep a bit because another 
> thread is already actively merging the journals,
> // due to the runnable that we scheduled above
> try {
> Thread.sleep(100L);
> } catch (final InterruptedException ie) {
> }
> }
> logger.debug("Provenance Repository is still behind. 
> Keeping flow slowed down "
> + "to accommodate. Currently, there are {} 
> journal files ({} bytes) and "
> + "threshold for blocking is {} ({} bytes)", 
> journalFileCount, repoSize, journalCountThreshold, sizeThreshold);
> journalFileCount = getJournalCount();
> repoSize = getSize(getLogFiles(), 0L);
> }
> logger.info("Provenance Repository has now caught up with 
> rolling over journal files. Current number of "
> + "journal files to be rolled over is {}", 
> journalFileCount);
> }
> {code}
> My nifi is at the sleep indefinitely.  The reason my nifi cannot move forward 
> is because of the thread doing the merge is stopped.  The thread doing the 
> merge is at:
> {code}
> accepted = eventQueue.offer(new Tuple<>(record, blockIndex), 10, 
> TimeUnit.MILLISECONDS);
> {code}
> so the queue is full.  
> What I believe happened is that the callables created here:
> {code}
> final Callable callable = new 
> Callable() {
> @Override
> public Object call() throws IOException {
> while (!eventQueue.isEmpty() || 
> !finishedAdding.get()) {
> final 
> Tuple tuple;
> try {
> tuple = eventQueue.poll(10, 
> TimeUnit.MILLISECONDS);
> } catch (final InterruptedException 
> ie) {
> continue;
> }
> if (tuple == null) {
> continue;
>   

[jira] [Commented] (NIFI-2429) Persistent provenance repo should continue despite indexing failures 0.x branch improvement

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2429 changes needed after cherry-picking NIFI-2395 from master


> Persistent provenance repo should continue despite indexing failures 0.x 
> branch improvement
> ---
>
> Key: NIFI-2429
> URL: https://issues.apache.org/jira/browse/NIFI-2429
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core Framework
>Affects Versions: 0.7.0
>Reporter: Joseph Witt
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 0.8.0
>
>
> [~markap14] created this subtask for just the 0.x line so we can get the 1.x 
> ticket addressed.



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

[GitHub] nifi-minifi-cpp issue #17: MINIFI-34 - Add Travis badge to README.md

[apiri]

Github user apiri commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/17
  
Eegads!  😱 

Indeed.  Looks good here.  I'll merge it in, because you should likely be 
sleeping at this point!  Thanks for catching this.


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

[GitHub] nifi-minifi-cpp issue #14: MINIFI-34 Establishing CMake build system to prov...

[trixpan]

Github user trixpan commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/14
  
@apiri another note: Seems like CMake is a must before we get Windows build 
in shape:

According to 
[this](http://help.appveyor.com/discussions/problems/1467-building-with-makefile)
 and 
[this](http://stackoverflow.com/questions/12881854/how-to-use-gnu-make-on-windows),
 using gnu make on appveyor is sort of a funny endeavour.


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

[GitHub] nifi-minifi-cpp issue #17: MINIFI-34 - Add Travis badge to README.md

[trixpan]

Github user trixpan commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/17
  
@apiri we forgot this. :fearful: 


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

[GitHub] nifi-minifi-cpp pull request #17: MINIFI-34 - Add Travis badge to README.md

[trixpan]

GitHub user trixpan opened a pull request:

https://github.com/apache/nifi-minifi-cpp/pull/17

MINIFI-34 - Add Travis badge to README.md



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

$ git pull https://github.com/trixpan/nifi-minifi-cpp MINIFI-34

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

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


commit 7595ccee9e64fd9266925fcfb55070fa2c2f78d5
Author: Your Name 
Date:   2016-10-06T14:58:45Z

MINIFI-34 - Add Travis badge to README.md




---
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-1712) HBaseClientService unable to connect when Phoenix is installed

[Bryan Bende (JIRA)]

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

Bryan Bende reassigned NIFI-1712:
-

Assignee: Bryan Bende

> HBaseClientService unable to connect when Phoenix is installed
> --
>
> Key: NIFI-1712
> URL: https://issues.apache.org/jira/browse/NIFI-1712
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Bryan Bende
>Assignee: Bryan Bende
>Priority: Minor
>
> A user reported running HDP 2.3.2 with Phoenix installed, and NiFi 0.6.0, 
> with the following error:
>   
> 2016-03-31 13:24:23,916 INFO [StandardProcessScheduler Thread-5] 
> o.a.nifi.hbase.HBase_1_1_2_ClientService 
> HBase_1_1_2_ClientService[id=e7e9b2ed-d336-34be-acb4-6c8b60c735c2] HBase 
> Security Enabled, logging in as principal n...@hdp.supergrp.net with keytab 
> /app/env/nifi.keytab
> 2016-03-31 13:24:23,984 WARN [StandardProcessScheduler Thread-5] 
> org.apache.hadoop.util.NativeCodeLoader Unable to load native-hadoop library 
> for your platform... using builtin-java classes where applicable
> 2016-03-31 13:24:24,101 INFO [StandardProcessScheduler Thread-5] 
> o.a.nifi.hbase.HBase_1_1_2_ClientService 
> HBase_1_1_2_ClientService[id=e7e9b2ed-d336-34be-acb4-6c8b60c735c2] 
> Successfully logged in as principal n...@hdp.supergrp.net with keytab 
> /app/env/nifi.keytab
> 2016-03-31 13:24:24,177 ERROR [StandardProcessScheduler Thread-5] 
> o.a.n.c.s.StandardControllerServiceNode 
> HBase_1_1_2_ClientService[id=e7e9b2ed-d336-34be-acb4-6c8b60c735c2] Failed to 
> invoke @OnEnabled method due to java.io.IOException: 
> java.lang.reflect.InvocationTargetException
> 2016-03-31 13:24:24,182 ERROR [StandardProcessScheduler Thread-5] 
> o.a.n.c.s.StandardControllerServiceNode
> java.io.IOException: java.lang.reflect.InvocationTargetException
> at 
> org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:240)
>  ~[hbase-client-1.1.2.jar:1.1.2]
> at 
> org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:218)
>  ~[hbase-client-1.1.2.jar:1.1.2]
> at 
> org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:119)
>  ~[hbase-client-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.hbase.HBase_1_1_2_ClientService$1.run(HBase_1_1_2_ClientService.java:215)
>  ~[nifi-hbase_1_1_2-client-service-0.6.0.jar:0.6.0]
> at 
> org.apache.nifi.hbase.HBase_1_1_2_ClientService$1.run(HBase_1_1_2_ClientService.java:212)
>  ~[nifi-hbase_1_1_2-client-service-0.6.0.jar:0.6.0]
> at java.security.AccessController.doPrivileged(Native Method) 
> ~[na:1.8.0_71]
> at javax.security.auth.Subject.doAs(Subject.java:422) ~[na:1.8.0_71]
> at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1656)
>  ~[hadoop-common-2.6.2.jar:na]
> at 
> org.apache.nifi.hbase.HBase_1_1_2_ClientService.createConnection(HBase_1_1_2_ClientService.java:212)
>  ~[nifi-hbase_1_1_2-client-service-0.6.0.jar:0.6.0]
> at 
> org.apache.nifi.hbase.HBase_1_1_2_ClientService.onEnabled(HBase_1_1_2_ClientService.java:161)
>  ~[nifi-hbase_1_1_2-client-service-0.6.0.jar:0.6.0]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> ~[na:1.8.0_71]
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> ~[na:1.8.0_71]
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  ~[na:1.8.0_71]
> at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_71]
> at 
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:137)
>  ~[na:na]
> at 
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:125)
>  ~[na:na]
> at 
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:70)
>  ~[na:na]
> at 
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotation(ReflectionUtils.java:47)
>  ~[na:na]
> at 
> org.apache.nifi.controller.service.StandardControllerServiceNode$1.run(StandardControllerServiceNode.java:285)
>  ~[na:na]
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [na:1.8.0_71]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
> [na:1.8.0_71]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
>  [na:1.8.0_71]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
>  [na:1.8.0_71]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [na:1.8.0_71]
>  

[GitHub] nifi-minifi-cpp pull request #15: MINIFI-111 Providing explicit inclusion of...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-minifi-cpp/pull/15


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

[GitHub] nifi-minifi-cpp issue #16: MINIFI-116 Initial Travis CI configuration for Ma...

[apiri]

Github user apiri commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/16
  
@trixpan Thanks for clarifying, let me do some merge magic and we can get 
rolling.  Glad to have you join in on the minifi-cpp party! 👍 


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

[GitHub] nifi-minifi-cpp issue #16: MINIFI-116 Initial Travis CI configuration for Ma...

[trixpan]

Github user trixpan commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/16
  
no no. just thinking about getting travis-ci working asap. Once that is 
done, evolving the work on #14 - i.e. CMake, windows, etc - should be easier 
due to the ability of iterating code until we get it right. :-)

Lets get this PR rolling and use it to complete the work started on #14 ;-)



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

[GitHub] nifi-minifi pull request #40: MINIFI-46 - Supporting multiple relationships ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-minifi/pull/40


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

[GitHub] nifi-minifi-cpp issue #16: MINIFI-116 Initial Travis CI configuration for Ma...

[apiri]

Github user apiri commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/16
  
@trixpan Yep, sounds good.  Onboard on all counts with that.  Would you 
like to draw up issues for those packaging formats (maybe one for each for the 
sake of granularity)?  Definitely getting functional on Windows is a priority.

Also, did you mean to put these comments on #14?  They seem a little more 
tailored around CMake or maybe I'm just overlooking something.


---
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-2691) nifi.properties and admin guide refer to kerberos "principle" instead of "principal"

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2691:
--

Github user asfgit closed the pull request at:

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


> nifi.properties and admin guide refer to kerberos "principle" instead of 
> "principal"
> 
>
> Key: NIFI-2691
> URL: https://issues.apache.org/jira/browse/NIFI-2691
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework, Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
>  Labels: beginner, kerberos
> Fix For: 1.1.0
>
>
> Need to change "principle" to "principal" in the following places:
> In nifi.properties:
> kerberos service *principle*
> kerberos spnego *principle*
> In Admin Guide for the description of the nifi.kerberos.krb5.file property:
> At this time, only a single krb5 file is allowed to be specified per NiFi 
> instance, so this property is configured here to support SPNEGO and service 
> *principles* rather than in individual Processors.



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

[GitHub] nifi pull request #1105: NIFI-2691 Replaced references to kerberos/spegno pr...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2691) nifi.properties and admin guide refer to kerberos "principle" instead of "principal"

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2691 Replaced references to kerberos/spegno principle with principal in 
nifi.properties and admin guide

This closes: #1105

Signed-off-by: Andre F de Miranda 


> nifi.properties and admin guide refer to kerberos "principle" instead of 
> "principal"
> 
>
> Key: NIFI-2691
> URL: https://issues.apache.org/jira/browse/NIFI-2691
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework, Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
>  Labels: beginner, kerberos
> Fix For: 1.1.0
>
>
> Need to change "principle" to "principal" in the following places:
> In nifi.properties:
> kerberos service *principle*
> kerberos spnego *principle*
> In Admin Guide for the description of the nifi.kerberos.krb5.file property:
> At this time, only a single krb5 file is allowed to be specified per NiFi 
> instance, so this property is configured here to support SPNEGO and service 
> *principles* rather than in individual Processors.



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

[jira] [Commented] (NIFI-2691) nifi.properties and admin guide refer to kerberos "principle" instead of "principal"

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2691:
--

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/1105
  
@andrewmlim great. Thanks for the clarification. Will merge soon.


> nifi.properties and admin guide refer to kerberos "principle" instead of 
> "principal"
> 
>
> Key: NIFI-2691
> URL: https://issues.apache.org/jira/browse/NIFI-2691
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework, Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
>  Labels: beginner, kerberos
> Fix For: 1.1.0
>
>
> Need to change "principle" to "principal" in the following places:
> In nifi.properties:
> kerberos service *principle*
> kerberos spnego *principle*
> In Admin Guide for the description of the nifi.kerberos.krb5.file property:
> At this time, only a single krb5 file is allowed to be specified per NiFi 
> instance, so this property is configured here to support SPNEGO and service 
> *principles* rather than in individual Processors.



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

[GitHub] nifi issue #1105: NIFI-2691 Replaced references to kerberos/spegno principle...

[trixpan]

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/1105
  
@andrewmlim great. Thanks for the clarification. Will merge soon.


---
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-2691) nifi.properties and admin guide refer to kerberos "principle" instead of "principal"

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2691:
--

Github user andrewmlim commented on the issue:

https://github.com/apache/nifi/pull/1105
  
@trixpan Thanks for taking a look at this.  These corrections aren't needed 
in 0.x.  The changes that introduced these errors were only made in 1.0.0  
(https://issues.apache.org/jira/browse/NIFI-2561).


> nifi.properties and admin guide refer to kerberos "principle" instead of 
> "principal"
> 
>
> Key: NIFI-2691
> URL: https://issues.apache.org/jira/browse/NIFI-2691
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework, Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
>  Labels: beginner, kerberos
> Fix For: 1.1.0
>
>
> Need to change "principle" to "principal" in the following places:
> In nifi.properties:
> kerberos service *principle*
> kerberos spnego *principle*
> In Admin Guide for the description of the nifi.kerberos.krb5.file property:
> At this time, only a single krb5 file is allowed to be specified per NiFi 
> instance, so this property is configured here to support SPNEGO and service 
> *principles* rather than in individual Processors.



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

[GitHub] nifi issue #1105: NIFI-2691 Replaced references to kerberos/spegno principle...

[andrewmlim]

Github user andrewmlim commented on the issue:

https://github.com/apache/nifi/pull/1105
  
@trixpan Thanks for taking a look at this.  These corrections aren't needed 
in 0.x.  The changes that introduced these errors were only made in 1.0.0  
(https://issues.apache.org/jira/browse/NIFI-2561).


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

[GitHub] nifi-minifi-cpp issue #16: MINIFI-116 Initial Travis CI configuration for Ma...

[trixpan]

Github user trixpan commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/16
  
once this is merged it should be easier to expand with CMake and different 
environments. I am particularly keen to ensure we are able to generate both deb 
and rpm files


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

[GitHub] nifi-minifi-cpp issue #16: MINIFI-116 Initial Travis CI configuration for Ma...

[trixpan]

Github user trixpan commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/16
  
@apiri LGTM


---
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 #1097: NIFI-2865: Refactored PublishKafka and PublishKafka...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #675: LSB Adherence

[trixpan]

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/675
  
@apiri have a look on 

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

and

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

Which are essentially addressing a number of the issues discussed here.




---
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-2865) Address issues of PublishKafka blocking when having trouble communicating with Kafka broker and improve performance

[Bryan Bende (JIRA)]

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

Bryan Bende resolved NIFI-2865.
---
Resolution: Fixed

> Address issues of PublishKafka blocking when having trouble communicating 
> with Kafka broker and improve performance
> ---
>
> Key: NIFI-2865
> URL: https://issues.apache.org/jira/browse/NIFI-2865
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.1.0
>
>
> When NiFi is unable to communicate properly with the Kafka broker, we see the 
> NiFi threads occasionally block. This should be resolvable by calling the 
> wakeup() method of the client. Additionally, if Kafka takes too long to 
> respond, we should be able to route the FlowFile to failure and move on.
> PublishKafka has a nice feature that allows a demarcated stream to be sent as 
> separate messages, so that a large number of messages can be sent as a single 
> FlowFile. However, in the case of individual messages per FlowFile, the 
> performance could be improved by batching together multiple FlowFiles per 
> session



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

[jira] [Commented] (NIFI-2865) Address issues of PublishKafka blocking when having trouble communicating with Kafka broker and improve performance

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2865:
--

Github user asfgit closed the pull request at:

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


> Address issues of PublishKafka blocking when having trouble communicating 
> with Kafka broker and improve performance
> ---
>
> Key: NIFI-2865
> URL: https://issues.apache.org/jira/browse/NIFI-2865
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.1.0
>
>
> When NiFi is unable to communicate properly with the Kafka broker, we see the 
> NiFi threads occasionally block. This should be resolvable by calling the 
> wakeup() method of the client. Additionally, if Kafka takes too long to 
> respond, we should be able to route the FlowFile to failure and move on.
> PublishKafka has a nice feature that allows a demarcated stream to be sent as 
> separate messages, so that a large number of messages can be sent as a single 
> FlowFile. However, in the case of individual messages per FlowFile, the 
> performance could be improved by batching together multiple FlowFiles per 
> session



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

[jira] [Commented] (NIFI-2865) Address issues of PublishKafka blocking when having trouble communicating with Kafka broker and improve performance

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2865: Refactored PublishKafka and PublishKafka_0_10 to allow batching of 
FlowFiles within a single publish and to let messages timeout if not 
acknowledged

This closes #1097.

Signed-off-by: Bryan Bende 


> Address issues of PublishKafka blocking when having trouble communicating 
> with Kafka broker and improve performance
> ---
>
> Key: NIFI-2865
> URL: https://issues.apache.org/jira/browse/NIFI-2865
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.1.0
>
>
> When NiFi is unable to communicate properly with the Kafka broker, we see the 
> NiFi threads occasionally block. This should be resolvable by calling the 
> wakeup() method of the client. Additionally, if Kafka takes too long to 
> respond, we should be able to route the FlowFile to failure and move on.
> PublishKafka has a nice feature that allows a demarcated stream to be sent as 
> separate messages, so that a large number of messages can be sent as a single 
> FlowFile. However, in the case of individual messages per FlowFile, the 
> performance could be improved by batching together multiple FlowFiles per 
> session



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

[jira] [Commented] (NIFI-2865) Address issues of PublishKafka blocking when having trouble communicating with Kafka broker and improve performance

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2865:
--

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

https://github.com/apache/nifi/pull/1097#discussion_r82194639
  
--- Diff: 
nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-0-10-processors/src/main/java/org/apache/nifi/processors/kafka/pubsub/PublisherLease.java
 ---
@@ -0,0 +1,132 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.nifi.processors.kafka.pubsub;
+
+import java.io.Closeable;
+import java.io.IOException;
+import java.io.InputStream;
+import java.util.concurrent.TimeUnit;
+import java.util.concurrent.TimeoutException;
+
+import org.apache.kafka.clients.producer.Callback;
+import org.apache.kafka.clients.producer.Producer;
+import org.apache.kafka.clients.producer.ProducerRecord;
+import org.apache.kafka.clients.producer.RecordMetadata;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.logging.ComponentLog;
+import org.apache.nifi.stream.io.exception.TokenTooLargeException;
+import org.apache.nifi.stream.io.util.StreamDemarcator;
+
+public class PublisherLease implements Closeable {
+private final ComponentLog logger;
+private final Producer producer;
+private final int maxMessageSize;
+private final long maxAckWaitMillis;
+private volatile boolean poisoned = false;
+
+private InFlightMessageTracker tracker;
+
+public PublisherLease(final Producer producer, final 
int maxMessageSize, final long maxAckWaitMillis, final ComponentLog logger) {
+this.producer = producer;
+this.maxMessageSize = maxMessageSize;
+this.logger = logger;
+this.maxAckWaitMillis = maxAckWaitMillis;
+}
+
+protected void poison() {
+this.poisoned = true;
+}
+
+public boolean isPoisoned() {
+return poisoned;
+}
+
+void publish(final FlowFile flowFile, final InputStream 
flowFileContent, final byte[] messageKey, final byte[] demarcatorBytes, final 
String topic) throws IOException {
+if (tracker == null) {
--- End diff --

We probably could... but I held off on doing that, because it may get 
poisoned in a background thread, and the caller may not know when calling 
publish() that it was poisoned. If that happens, the new FlowFile is likely to 
fail anyway. If it doesn't then it's okay - there's no reason it can't get 
published to Kafka at that point. We simply poison the lease to ensure that a 
new one gets created, in case there's an issue with the connection.


> Address issues of PublishKafka blocking when having trouble communicating 
> with Kafka broker and improve performance
> ---
>
> Key: NIFI-2865
> URL: https://issues.apache.org/jira/browse/NIFI-2865
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.1.0
>
>
> When NiFi is unable to communicate properly with the Kafka broker, we see the 
> NiFi threads occasionally block. This should be resolvable by calling the 
> wakeup() method of the client. Additionally, if Kafka takes too long to 
> respond, we should be able to route the FlowFile to failure and move on.
> PublishKafka has a nice feature that allows a demarcated stream to be sent as 
> separate messages, so that a large number of messages can be sent as a single 
> FlowFile. However, in the case of individual messages per FlowFile, the 
> performance could be improved by batching together multiple FlowFiles per 
> session



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

[GitHub] nifi pull request #1097: NIFI-2865: Refactored PublishKafka and PublishKafka...

[markap14]

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

https://github.com/apache/nifi/pull/1097#discussion_r82194639
  
--- Diff: 
nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-0-10-processors/src/main/java/org/apache/nifi/processors/kafka/pubsub/PublisherLease.java
 ---
@@ -0,0 +1,132 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.nifi.processors.kafka.pubsub;
+
+import java.io.Closeable;
+import java.io.IOException;
+import java.io.InputStream;
+import java.util.concurrent.TimeUnit;
+import java.util.concurrent.TimeoutException;
+
+import org.apache.kafka.clients.producer.Callback;
+import org.apache.kafka.clients.producer.Producer;
+import org.apache.kafka.clients.producer.ProducerRecord;
+import org.apache.kafka.clients.producer.RecordMetadata;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.logging.ComponentLog;
+import org.apache.nifi.stream.io.exception.TokenTooLargeException;
+import org.apache.nifi.stream.io.util.StreamDemarcator;
+
+public class PublisherLease implements Closeable {
+private final ComponentLog logger;
+private final Producer producer;
+private final int maxMessageSize;
+private final long maxAckWaitMillis;
+private volatile boolean poisoned = false;
+
+private InFlightMessageTracker tracker;
+
+public PublisherLease(final Producer producer, final 
int maxMessageSize, final long maxAckWaitMillis, final ComponentLog logger) {
+this.producer = producer;
+this.maxMessageSize = maxMessageSize;
+this.logger = logger;
+this.maxAckWaitMillis = maxAckWaitMillis;
+}
+
+protected void poison() {
+this.poisoned = true;
+}
+
+public boolean isPoisoned() {
+return poisoned;
+}
+
+void publish(final FlowFile flowFile, final InputStream 
flowFileContent, final byte[] messageKey, final byte[] demarcatorBytes, final 
String topic) throws IOException {
+if (tracker == null) {
--- End diff --

We probably could... but I held off on doing that, because it may get 
poisoned in a background thread, and the caller may not know when calling 
publish() that it was poisoned. If that happens, the new FlowFile is likely to 
fail anyway. If it doesn't then it's okay - there's no reason it can't get 
published to Kafka at that point. We simply poison the lease to ensure that a 
new one gets created, in case there's an issue with the connection.


---
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-2836) Cluster - Request Replication

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2836:
--

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1109
  
Reviewing...


> Cluster - Request Replication
> -
>
> Key: NIFI-2836
> URL: https://issues.apache.org/jira/browse/NIFI-2836
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.1.0
>
>
> When a request is replicated throughout the cluster, the cluster coordinator 
> needs to ensure that request completes (including both parts of the two-phase 
> commit if applicable) prior to replicating the next request.
> Looks like a write lock is obtained while submitted a background task. The 
> actually work completes outside the locks scope.



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

[GitHub] nifi issue #1109: NIFI-2836: Ensure that we wait until a request is complete...

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1109
  
Reviewing...


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

[GitHub] nifi-minifi-cpp issue #16: MINIFI-116 Initial Travis CI configuration for Ma...

[apiri]

Github user apiri commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/16
  
This relies on #15 as well.  Updated it to include that change.


---
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] [Updated] (NIFI-1792) User can create conditions or actions even when no rule exists to attach them to

[Matt Gilman (JIRA)]

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

Matt Gilman updated NIFI-1792:
--
   Resolution: Fixed
Fix Version/s: 1.1.0
   Status: Resolved  (was: Patch Available)

> User can create conditions or actions even when no rule exists to attach them 
> to
> 
>
> Key: NIFI-1792
> URL: https://issues.apache.org/jira/browse/NIFI-1792
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0, 0.6.0
>Reporter: Andrew Lim
>Assignee: Scott Aslan
>Priority: Minor
> Fix For: 1.1.0
>
> Attachments: NIFI-1792_ruleBlank.png
>
>
> Steps to Reproduce:
> 1. Add a Processor to the canvas that has the Advanced button/functionality 
> on the Properties Tab  (UpdateAttribute processor for example)
> 2.  Select "Advanced"
> 3.  If the user attempts to add a condition or action, the UI will not allow 
> it and display the Configuration Error message of "No rule is selected"
> 4.  Select the "+" button to create a new Rule
> 5.  Add the Rule name and select "Add".  A rule is created.
> 6.  Now delete the rule by selecting the "x" next to it and then confirming 
> the deletion.
> 7.  The user can now add multiple conditions and actions at will.  However, 
> when attempting to Save them, the Error message displayed is "Rule name 
> cannot be blank."  But there is no way to add/edit the rule name.  (See 
> attached screenshot)  Any of the work done to add conditions/actions will be 
> lost.



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

[jira] [Commented] (NIFI-1792) User can create conditions or actions even when no rule exists to attach them to

[ASF subversion and git services (JIRA)]

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

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

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

[NIFI-1792] Clear the selected rule id when deleting the last rule in the list. 
Add scrollable styles when appropriate. Close popups when appropriate. This PR 
also adjusts the position of the table cell nfel and long text editors. This 
closes #1099.


> User can create conditions or actions even when no rule exists to attach them 
> to
> 
>
> Key: NIFI-1792
> URL: https://issues.apache.org/jira/browse/NIFI-1792
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0, 0.6.0
>Reporter: Andrew Lim
>Assignee: Scott Aslan
>Priority: Minor
> Fix For: 1.1.0
>
> Attachments: NIFI-1792_ruleBlank.png
>
>
> Steps to Reproduce:
> 1. Add a Processor to the canvas that has the Advanced button/functionality 
> on the Properties Tab  (UpdateAttribute processor for example)
> 2.  Select "Advanced"
> 3.  If the user attempts to add a condition or action, the UI will not allow 
> it and display the Configuration Error message of "No rule is selected"
> 4.  Select the "+" button to create a new Rule
> 5.  Add the Rule name and select "Add".  A rule is created.
> 6.  Now delete the rule by selecting the "x" next to it and then confirming 
> the deletion.
> 7.  The user can now add multiple conditions and actions at will.  However, 
> when attempting to Save them, the Error message displayed is "Rule name 
> cannot be blank."  But there is no way to add/edit the rule name.  (See 
> attached screenshot)  Any of the work done to add conditions/actions will be 
> lost.



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

[jira] [Commented] (NIFI-1792) User can create conditions or actions even when no rule exists to attach them to

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1792:
--

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1099
  
Thanks @scottyaslan! This has been merged to master.


> User can create conditions or actions even when no rule exists to attach them 
> to
> 
>
> Key: NIFI-1792
> URL: https://issues.apache.org/jira/browse/NIFI-1792
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0, 0.6.0
>Reporter: Andrew Lim
>Assignee: Scott Aslan
>Priority: Minor
> Fix For: 1.1.0
>
> Attachments: NIFI-1792_ruleBlank.png
>
>
> Steps to Reproduce:
> 1. Add a Processor to the canvas that has the Advanced button/functionality 
> on the Properties Tab  (UpdateAttribute processor for example)
> 2.  Select "Advanced"
> 3.  If the user attempts to add a condition or action, the UI will not allow 
> it and display the Configuration Error message of "No rule is selected"
> 4.  Select the "+" button to create a new Rule
> 5.  Add the Rule name and select "Add".  A rule is created.
> 6.  Now delete the rule by selecting the "x" next to it and then confirming 
> the deletion.
> 7.  The user can now add multiple conditions and actions at will.  However, 
> when attempting to Save them, the Error message displayed is "Rule name 
> cannot be blank."  But there is no way to add/edit the rule name.  (See 
> attached screenshot)  Any of the work done to add conditions/actions will be 
> lost.



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

[GitHub] nifi pull request #1099: [NIFI-1792] Clear the selected rule id when deletin...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1099: [NIFI-1792] Clear the selected rule id when deleting the l...

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1099
  
Thanks @scottyaslan! This has been merged to master.


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

[GitHub] nifi-minifi-cpp pull request #16: MINIFI-116 Initial Travis CI configuration...

[apiri]

GitHub user apiri opened a pull request:

https://github.com/apache/nifi-minifi-cpp/pull/16

MINIFI-116 Initial Travis CI configuration for Make based build.

MINIFI-116 Initial Travis CI configuration for Make based build.

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

$ git pull https://github.com/apiri/nifi-minifi-cpp travis-ci

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

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


commit c98c701c983aed88c00e5b24171725fe4c219b2c
Author: Aldrin Piri 
Date:   2016-09-29T14:12:10Z

MINIFI-116 Initial Travis CI configuration for Make based build.




---
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-2816) The great typo cleanup

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2816:
- Fixing compilation error resulting from the initial NIFI-2816 commit.


> The great typo cleanup
> --
>
> Key: NIFI-2816
> URL: https://issues.apache.org/jira/browse/NIFI-2816
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Andre
>Assignee: Andre
>




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

[jira] [Commented] (NIFI-2816) The great typo cleanup

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2816:
- Fixing compilation error resulting from the initial NIFI-2816 commit.


> The great typo cleanup
> --
>
> Key: NIFI-2816
> URL: https://issues.apache.org/jira/browse/NIFI-2816
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Andre
>Assignee: Andre
>




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

[GitHub] nifi issue #675: LSB Adherence

[apiri]

Github user apiri commented on the issue:

https://github.com/apache/nifi/pull/675
  
It was my understanding there were to be some modifications based on the 
last review and then we would commit that to capture the effort already done 
with follow on work to get completely there.


---
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-2870) Allow to set replication factor in Kafka Consume Processor

[Bryan Bende (JIRA)]

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

Bryan Bende commented on NIFI-2870:
---

[~stephane.maa...@gmail.com] Could you provide an example of the logs from 
nifi-app.log when this happens?

Most of the posts about that error message are related to creating a topic, 
which sounds more like the producer side of things, is it possible this came 
from PublishKafka?

> Allow to set replication factor in Kafka Consume Processor
> --
>
> Key: NIFI-2870
> URL: https://issues.apache.org/jira/browse/NIFI-2870
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
> Environment: standard installation
>Reporter: Stephane Maarek
>
> I deployed a Kafka cluster with one broker only (I know it's bad), but then 
> when trying to read from the ConsumeKafka0.10, I came across this error:
> replication factor: 3 larger than available brokers: 1
> I believe the replication factor should be a parameter in the processor?



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

[GitHub] nifi issue #675: LSB Adherence

[trixpan]

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/675
  
@PuspenduBanerjee From what I understand from the trail, we can close PR?

Best regards


---
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 #984: Nifi 2624

[trixpan]

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/984
  
@ToivoAdams would you mind rebasing this PR?

Kind regards


---
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 #1073: Nifi 2829

[trixpan]

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/1073
  
@paulgibeault would you mind squashing this PR?

I thank you in advance


---
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-2691) nifi.properties and admin guide refer to kerberos "principle" instead of "principal"

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2691:
--

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/1105
  
@andrewmlim LGTM.

any chance of submitting a similar PR to 0.x?


> nifi.properties and admin guide refer to kerberos "principle" instead of 
> "principal"
> 
>
> Key: NIFI-2691
> URL: https://issues.apache.org/jira/browse/NIFI-2691
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework, Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
>  Labels: beginner, kerberos
> Fix For: 1.1.0
>
>
> Need to change "principle" to "principal" in the following places:
> In nifi.properties:
> kerberos service *principle*
> kerberos spnego *principle*
> In Admin Guide for the description of the nifi.kerberos.krb5.file property:
> At this time, only a single krb5 file is allowed to be specified per NiFi 
> instance, so this property is configured here to support SPNEGO and service 
> *principles* rather than in individual Processors.



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