[jira] [Commented] (NIFI-4256) Add support for all AWS S3 Encryption Options

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4256:
--

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

https://github.com/apache/nifi/pull/2291#discussion_r153396888
  
--- Diff: 
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/s3/PutS3Object.java
 ---
@@ -154,6 +155,14 @@
 .defaultValue(StorageClass.Standard.name())
 .build();
 
+
+public static final PropertyDescriptor PUT_ENRICHMENT_SERVICE = new 
PropertyDescriptor.Builder()
+.name("Put Enrichment Service")
--- End diff --

Same request for machine-readable name and human-readable displayName.


> Add support for all AWS S3 Encryption Options
> -
>
> Key: NIFI-4256
> URL: https://issues.apache.org/jira/browse/NIFI-4256
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Affects Versions: 1.2.0
>Reporter: Franco
>  Labels: aws, aws-s3, security
>
> NiFi currently only supports SSE-S3 encryption (AES256).
> Support needs to be added for:
> * SSE-S3
> * SSE-KMS
> * SSE-C
> * CSE-KMS CMK
> * CSE-Master Key
> With all of the appropriate configuration options and such that SSE is 
> available only for PutS3Object whilst CSE is available also for FetchS3Object.
> Given that this will add another 20 or so UI properties the intention is to 
> split it into a Client Side Encryption Service and Server Side Encryption 
> Service. This will allow users to reuse "encryption" across different 
> workflows.
> Existing flows using the Server Side Encryption option will still work as is 
> but will be overridden if a service is added.



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

[jira] [Commented] (NIFI-4256) Add support for all AWS S3 Encryption Options

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4256:
--

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

https://github.com/apache/nifi/pull/2291#discussion_r153398470
  
--- Diff: 
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/s3/encryption/EncryptedS3PutEnrichmentService.java
 ---
@@ -0,0 +1,181 @@
+/*
+ * 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.aws.s3.encryption;
+
+import java.util.ArrayList;
+import java.util.Collections;
+import java.util.List;
+
+import com.amazonaws.services.s3.model.InitiateMultipartUploadRequest;
+import com.amazonaws.services.s3.model.ObjectMetadata;
+import com.amazonaws.services.s3.model.PutObjectRequest;
+import com.amazonaws.services.s3.model.SSEAwsKeyManagementParams;
+import com.amazonaws.services.s3.model.SSECustomerKey;
+import org.apache.commons.lang3.StringUtils;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.annotation.lifecycle.OnEnabled;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.controller.AbstractControllerService;
+import org.apache.nifi.controller.ConfigurationContext;
+import org.apache.nifi.processor.util.StandardValidators;
+import org.apache.nifi.processors.aws.s3.service.S3PutEnrichmentService;
+import org.apache.nifi.reporting.InitializationException;
+
+@Tags({"aws", "s3", "encryption", "server", "kms", "key"})
+@CapabilityDescription("Provides the ability to configure S3 Server Side 
Encryption once and reuse " +
+"that configuration throughout the application")
+public class EncryptedS3PutEnrichmentService extends 
AbstractControllerService implements S3PutEnrichmentService {
+
+public static final String METHOD_SSE_S3 = "SSE-S3";
+public static final String METHOD_SSE_KMS = "SSE-KMS";
+public static final String METHOD_SSE_C = "SSE-C";
+
+public static final String ALGORITHM_AES256 = "AES256";
+public static final String CUSTOMER_ALGORITHM_AES256 = "AES256";
+
+
+public static final PropertyDescriptor ENCRYPTION_METHOD = new 
PropertyDescriptor.Builder()
+.name("encryption-method")
+.displayName("Encryption Method")
+.required(true)
+.allowableValues(METHOD_SSE_S3, METHOD_SSE_KMS, METHOD_SSE_C)
+.defaultValue(METHOD_SSE_S3)
+.description("Method by which the S3 object will be encrypted 
server-side.")
+.build();
+
+public static final PropertyDescriptor ALGORITHM = new 
PropertyDescriptor.Builder()
+.name("sse-algorithm")
+.displayName("Algorithm")
+.allowableValues(ALGORITHM_AES256)
+.defaultValue(ALGORITHM_AES256)
+.description("Encryption algorithm to use (only AES256 
currently supported)")
+.build();
+
+public static final PropertyDescriptor KMS_KEY_ID = new 
PropertyDescriptor.Builder()
+.name("sse-kme-key-id")
+.displayName("KMS Key Id")
+.required(false)
+.expressionLanguageSupported(true)
+.addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
+.description("Custom KMS key identifier. Supports key or alias 
ARN.")
+.build();
+
+public static final PropertyDescriptor CUSTOMER_KEY = new 
PropertyDescriptor.Builder()
+.name("sse-customer-key")
+.displayName("Customer Key")
+.required(false)
+.expressionLanguageSupported(true)
+.addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
+

[GitHub] nifi pull request #2291: NIFI-4256 - Add support for all AWS S3 Encryption O...

[jvwing]

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

https://github.com/apache/nifi/pull/2291#discussion_r153396888
  
--- Diff: 
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/s3/PutS3Object.java
 ---
@@ -154,6 +155,14 @@
 .defaultValue(StorageClass.Standard.name())
 .build();
 
+
+public static final PropertyDescriptor PUT_ENRICHMENT_SERVICE = new 
PropertyDescriptor.Builder()
+.name("Put Enrichment Service")
--- End diff --

Same request for machine-readable name and human-readable displayName.


---

[jira] [Commented] (NIFI-4256) Add support for all AWS S3 Encryption Options

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4256:
--

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

https://github.com/apache/nifi/pull/2291#discussion_r153398527
  
--- Diff: 
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/s3/encryption/EncryptedS3ClientService.java
 ---
@@ -0,0 +1,297 @@
+/*
+ * 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.aws.s3.encryption;
+
+import com.amazonaws.ClientConfiguration;
+import com.amazonaws.auth.AWSCredentials;
+import com.amazonaws.auth.AWSCredentialsProvider;
+import com.amazonaws.regions.Region;
+import com.amazonaws.regions.Regions;
+import com.amazonaws.services.s3.AmazonS3Client;
+import com.amazonaws.services.s3.AmazonS3EncryptionClient;
+import com.amazonaws.services.s3.model.CryptoConfiguration;
+import com.amazonaws.services.s3.model.CryptoMode;
+import com.amazonaws.services.s3.model.CryptoStorageMode;
+import com.amazonaws.services.s3.model.EncryptionMaterials;
+import com.amazonaws.services.s3.model.KMSEncryptionMaterials;
+import com.amazonaws.services.s3.model.StaticEncryptionMaterialsProvider;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.annotation.lifecycle.OnEnabled;
+import org.apache.nifi.components.AllowableValue;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.controller.AbstractControllerService;
+import org.apache.nifi.controller.ConfigurationContext;
+import org.apache.nifi.processor.util.StandardValidators;
+import org.apache.nifi.processors.aws.s3.S3ClientService;
+import org.apache.nifi.reporting.InitializationException;
+import org.apache.nifi.util.StringUtils;
+
+import javax.crypto.spec.SecretKeySpec;
+import java.security.KeyFactory;
+import java.security.KeyPair;
+import java.security.spec.PKCS8EncodedKeySpec;
+import java.security.spec.X509EncodedKeySpec;
+import java.util.ArrayList;
+import java.util.Collections;
+import java.util.List;
+
+@Tags({"aws", "s3", "encryption", "client", "kms", "key"})
+@CapabilityDescription("Provides the ability to configure S3 Client Side 
Encryption once and reuse " +
+"that configuration throughout the application")
+public class EncryptedS3ClientService extends AbstractControllerService 
implements S3ClientService {
+
+public static final String METHOD_CSE_MK = "Client Side Master Key";
+public static final String METHOD_CSE_KMS = "KMS-Managed Customer 
Master Key";
+
+public static final PropertyDescriptor ENCRYPTION_METHOD = new 
PropertyDescriptor.Builder()
+.name("encryption-method")
+.displayName("Encryption Method")
+.required(true)
+.allowableValues(METHOD_CSE_MK, METHOD_CSE_KMS)
+.defaultValue(METHOD_CSE_MK)
+.description("Method by which the S3 object will be encrypted 
client-side.")
+.build();
+
+public static final PropertyDescriptor KMS_CMK_ID = new 
PropertyDescriptor.Builder()
+.name("kms-cmk-id")
+.displayName("KMS Customer Master Key Id")
+.required(false)
+.expressionLanguageSupported(true)
+.addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
+.description("Identifier belonging to the custom master key 
managed by the KMS.")
+.build();
+
+public static final PropertyDescriptor KMS_REGION = new 
PropertyDescriptor.Builder()
+.name("kms-region")
+.displayName("KMS Region")
+.required(false)
+.allowableValues(getAvailableRegions())
+ 

[jira] [Commented] (NIFI-4256) Add support for all AWS S3 Encryption Options

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4256:
--

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

https://github.com/apache/nifi/pull/2291#discussion_r153396684
  
--- Diff: 
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-abstract-processors/src/main/java/org/apache/nifi/processors/aws/s3/AbstractS3Processor.java
 ---
@@ -125,16 +125,31 @@
 new AllowableValue("S3SignerType", "Signature v2"))
 .defaultValue("Default Signature")
 .build();
+
+public static final PropertyDescriptor CLIENT_SERVICE = new 
PropertyDescriptor.Builder()
+.name("Client Service")
--- End diff --

Name should be a machine-readable key like "client-service" with a 
human-readable displayName like "Client Service".  I know this has not been 
done previously in this file, but we should try to do it going forward.


> Add support for all AWS S3 Encryption Options
> -
>
> Key: NIFI-4256
> URL: https://issues.apache.org/jira/browse/NIFI-4256
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Affects Versions: 1.2.0
>Reporter: Franco
>  Labels: aws, aws-s3, security
>
> NiFi currently only supports SSE-S3 encryption (AES256).
> Support needs to be added for:
> * SSE-S3
> * SSE-KMS
> * SSE-C
> * CSE-KMS CMK
> * CSE-Master Key
> With all of the appropriate configuration options and such that SSE is 
> available only for PutS3Object whilst CSE is available also for FetchS3Object.
> Given that this will add another 20 or so UI properties the intention is to 
> split it into a Client Side Encryption Service and Server Side Encryption 
> Service. This will allow users to reuse "encryption" across different 
> workflows.
> Existing flows using the Server Side Encryption option will still work as is 
> but will be overridden if a service is added.



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

[GitHub] nifi pull request #2291: NIFI-4256 - Add support for all AWS S3 Encryption O...

[jvwing]

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

https://github.com/apache/nifi/pull/2291#discussion_r153396684
  
--- Diff: 
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-abstract-processors/src/main/java/org/apache/nifi/processors/aws/s3/AbstractS3Processor.java
 ---
@@ -125,16 +125,31 @@
 new AllowableValue("S3SignerType", "Signature v2"))
 .defaultValue("Default Signature")
 .build();
+
+public static final PropertyDescriptor CLIENT_SERVICE = new 
PropertyDescriptor.Builder()
+.name("Client Service")
--- End diff --

Name should be a machine-readable key like "client-service" with a 
human-readable displayName like "Client Service".  I know this has not been 
done previously in this file, but we should try to do it going forward.


---

[GitHub] nifi pull request #2291: NIFI-4256 - Add support for all AWS S3 Encryption O...

[jvwing]

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

https://github.com/apache/nifi/pull/2291#discussion_r153398470
  
--- Diff: 
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/s3/encryption/EncryptedS3PutEnrichmentService.java
 ---
@@ -0,0 +1,181 @@
+/*
+ * 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.aws.s3.encryption;
+
+import java.util.ArrayList;
+import java.util.Collections;
+import java.util.List;
+
+import com.amazonaws.services.s3.model.InitiateMultipartUploadRequest;
+import com.amazonaws.services.s3.model.ObjectMetadata;
+import com.amazonaws.services.s3.model.PutObjectRequest;
+import com.amazonaws.services.s3.model.SSEAwsKeyManagementParams;
+import com.amazonaws.services.s3.model.SSECustomerKey;
+import org.apache.commons.lang3.StringUtils;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.annotation.lifecycle.OnEnabled;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.controller.AbstractControllerService;
+import org.apache.nifi.controller.ConfigurationContext;
+import org.apache.nifi.processor.util.StandardValidators;
+import org.apache.nifi.processors.aws.s3.service.S3PutEnrichmentService;
+import org.apache.nifi.reporting.InitializationException;
+
+@Tags({"aws", "s3", "encryption", "server", "kms", "key"})
+@CapabilityDescription("Provides the ability to configure S3 Server Side 
Encryption once and reuse " +
+"that configuration throughout the application")
+public class EncryptedS3PutEnrichmentService extends 
AbstractControllerService implements S3PutEnrichmentService {
+
+public static final String METHOD_SSE_S3 = "SSE-S3";
+public static final String METHOD_SSE_KMS = "SSE-KMS";
+public static final String METHOD_SSE_C = "SSE-C";
+
+public static final String ALGORITHM_AES256 = "AES256";
+public static final String CUSTOMER_ALGORITHM_AES256 = "AES256";
+
+
+public static final PropertyDescriptor ENCRYPTION_METHOD = new 
PropertyDescriptor.Builder()
+.name("encryption-method")
+.displayName("Encryption Method")
+.required(true)
+.allowableValues(METHOD_SSE_S3, METHOD_SSE_KMS, METHOD_SSE_C)
+.defaultValue(METHOD_SSE_S3)
+.description("Method by which the S3 object will be encrypted 
server-side.")
+.build();
+
+public static final PropertyDescriptor ALGORITHM = new 
PropertyDescriptor.Builder()
+.name("sse-algorithm")
+.displayName("Algorithm")
+.allowableValues(ALGORITHM_AES256)
+.defaultValue(ALGORITHM_AES256)
+.description("Encryption algorithm to use (only AES256 
currently supported)")
+.build();
+
+public static final PropertyDescriptor KMS_KEY_ID = new 
PropertyDescriptor.Builder()
+.name("sse-kme-key-id")
+.displayName("KMS Key Id")
+.required(false)
+.expressionLanguageSupported(true)
+.addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
+.description("Custom KMS key identifier. Supports key or alias 
ARN.")
+.build();
+
+public static final PropertyDescriptor CUSTOMER_KEY = new 
PropertyDescriptor.Builder()
+.name("sse-customer-key")
+.displayName("Customer Key")
+.required(false)
+.expressionLanguageSupported(true)
+.addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
+.description("Customer provided 256-bit, base64-encoded 
encryption key.")
+.build();
+
+public static final PropertyDescriptor CUSTOMER_ALGORITHM = new 
PropertyDescriptor.Builder()
+

[GitHub] nifi issue #2291: NIFI-4256 - Add support for all AWS S3 Encryption Options

[jvwing]

Github user jvwing commented on the issue:

https://github.com/apache/nifi/pull/2291
  
@baank, thanks for the latest update.  Good news, we're getting down to the 
nit-picks:

1.  I had a checkstyle error running the full build with contrib check on 
nifi-aws-service-api `UnusedImports: Unused import - 
com.amazonaws.services.s3.AmazonS3Encryption`.

2.  In your services, some of the Property Descriptors are marked as 
supporting expression language, but EL is not evaluated when extracting the 
value of the property (like 
`context.getProperty(KMS_CMK_ID).evaluateAttributeExpressions().getValue()` or 
similar).  We should either evaluate the expressions or not mark them as 
supporting expression language:
  * EncryptedS3ClientService (KMS_CMK_ID, SECRET_KEY, PRIVATE_KEY, 
PUBLIC_KEY)
  * EncryptedS3PutEnrichmentService (KMS_KEY_ID, CUSTOMER_KEY)

It's fine to update this PR.  I'll work out rebasing and squashing when 
we're ready.




---

[jira] [Updated] (NIFI-4632) Site-to-Site failing with default configuration

[Andy LoPresto (JIRA)]

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

Andy LoPresto updated NIFI-4632:

Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Site-to-Site failing with default configuration
> ---
>
> Key: NIFI-4632
> URL: https://issues.apache.org/jira/browse/NIFI-4632
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.5.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.5.0
>
>
> With a new install, from 'master' branch I created an Input Port and then a 
> Remote Process Group pointing to localhost:8080/nifi. When attempting to send 
> data to my Input Port, nothing appears to happen in the UI. In the logs, I 
> see the following:
> {code}
> 2017-11-22 09:30:39,918 WARN [NiFi Web Server-184] 
> o.a.nifi.web.server.HostHeaderHandler Request host header 
> [.local:8080] different from web hostname [localhost(:8080)]. 
> Overriding to [localhost:8080/nifi-api/site-to-site/peers]
> 2017-11-22 09:30:39,918 WARN [Http Site-to-Site PeerSelector] 
> o.a.n.r.util.SiteToSiteRestApiClient Failed to parse Json. The specified URL 
> http://.local:8080/nifi-api is not a proper remote NiFi endpoint 
> for Site-to-Site communication. 
> requestedUrl=http://.local:8080/nifi-api/site-to-site/peers, 
> response=System Error
> The request contained an invalid host header [.local:8080] in 
> the request [/nifi-api/site-to-site/peers]. Check for request manipulation or 
> third-party intercept. 
> {code}
> I tried updating nifi.properties to set the "nifi.web.http.host" property to 
> .local and that did resolve the issue... but then I could not 
> connect to the UI using localhost:8080 but instead had to connect using 
> .local. 
> This appears to not affect any released versions of NiFi.



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

[jira] [Commented] (NIFI-4632) Site-to-Site failing with default configuration

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4632:
--

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/2288
  
I built this and set up a local instance doing S2S without having to 
populate the `nifi.web.http.host` value. I got a weird error message briefly 
but I had put the wrong remote port in to the RPG configuration. With the 
correct values, everything worked normally. 

Error message for posterity/future recall:

`2017-11-27 19:01:38,897 ERROR [Site-to-Site Worker Thread-11] 
o.a.nifi.remote.SocketRemoteSiteListener Unable to communicate with remote 
instance null due to org.apache.nifi.remote.exception.HandshakeException: 
Handshake with nifi://localhost:56899 failed because the Magic Header was not 
present; closing connection`

Ran `contrib-check` and all tests pass. +1, merging. 


> Site-to-Site failing with default configuration
> ---
>
> Key: NIFI-4632
> URL: https://issues.apache.org/jira/browse/NIFI-4632
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.5.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.5.0
>
>
> With a new install, from 'master' branch I created an Input Port and then a 
> Remote Process Group pointing to localhost:8080/nifi. When attempting to send 
> data to my Input Port, nothing appears to happen in the UI. In the logs, I 
> see the following:
> {code}
> 2017-11-22 09:30:39,918 WARN [NiFi Web Server-184] 
> o.a.nifi.web.server.HostHeaderHandler Request host header 
> [.local:8080] different from web hostname [localhost(:8080)]. 
> Overriding to [localhost:8080/nifi-api/site-to-site/peers]
> 2017-11-22 09:30:39,918 WARN [Http Site-to-Site PeerSelector] 
> o.a.n.r.util.SiteToSiteRestApiClient Failed to parse Json. The specified URL 
> http://.local:8080/nifi-api is not a proper remote NiFi endpoint 
> for Site-to-Site communication. 
> requestedUrl=http://.local:8080/nifi-api/site-to-site/peers, 
> response=System Error
> The request contained an invalid host header [.local:8080] in 
> the request [/nifi-api/site-to-site/peers]. Check for request manipulation or 
> third-party intercept. 
> {code}
> I tried updating nifi.properties to set the "nifi.web.http.host" property to 
> .local and that did resolve the issue... but then I could not 
> connect to the UI using localhost:8080 but instead had to connect using 
> .local. 
> This appears to not affect any released versions of NiFi.



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

[GitHub] nifi issue #2288: NIFI-4632: Add the local hostname to the list of validated...

[alopresto]

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/2288
  
I built this and set up a local instance doing S2S without having to 
populate the `nifi.web.http.host` value. I got a weird error message briefly 
but I had put the wrong remote port in to the RPG configuration. With the 
correct values, everything worked normally. 

Error message for posterity/future recall:

`2017-11-27 19:01:38,897 ERROR [Site-to-Site Worker Thread-11] 
o.a.nifi.remote.SocketRemoteSiteListener Unable to communicate with remote 
instance null due to org.apache.nifi.remote.exception.HandshakeException: 
Handshake with nifi://localhost:56899 failed because the Magic Header was not 
present; closing connection`

Ran `contrib-check` and all tests pass. +1, merging. 


---

[jira] [Commented] (NIFI-4632) Site-to-Site failing with default configuration

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4632:
--

Github user asfgit closed the pull request at:

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


> Site-to-Site failing with default configuration
> ---
>
> Key: NIFI-4632
> URL: https://issues.apache.org/jira/browse/NIFI-4632
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.5.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.5.0
>
>
> With a new install, from 'master' branch I created an Input Port and then a 
> Remote Process Group pointing to localhost:8080/nifi. When attempting to send 
> data to my Input Port, nothing appears to happen in the UI. In the logs, I 
> see the following:
> {code}
> 2017-11-22 09:30:39,918 WARN [NiFi Web Server-184] 
> o.a.nifi.web.server.HostHeaderHandler Request host header 
> [.local:8080] different from web hostname [localhost(:8080)]. 
> Overriding to [localhost:8080/nifi-api/site-to-site/peers]
> 2017-11-22 09:30:39,918 WARN [Http Site-to-Site PeerSelector] 
> o.a.n.r.util.SiteToSiteRestApiClient Failed to parse Json. The specified URL 
> http://.local:8080/nifi-api is not a proper remote NiFi endpoint 
> for Site-to-Site communication. 
> requestedUrl=http://.local:8080/nifi-api/site-to-site/peers, 
> response=System Error
> The request contained an invalid host header [.local:8080] in 
> the request [/nifi-api/site-to-site/peers]. Check for request manipulation or 
> third-party intercept. 
> {code}
> I tried updating nifi.properties to set the "nifi.web.http.host" property to 
> .local and that did resolve the issue... but then I could not 
> connect to the UI using localhost:8080 but instead had to connect using 
> .local. 
> This appears to not affect any released versions of NiFi.



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

[GitHub] nifi pull request #2288: NIFI-4632: Add the local hostname to the list of va...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[jira] [Commented] (NIFI-4632) Site-to-Site failing with default configuration

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-4632: Add the local hostname to the list of validated host headers

This closes #2288.

Signed-off-by: Andy LoPresto 


> Site-to-Site failing with default configuration
> ---
>
> Key: NIFI-4632
> URL: https://issues.apache.org/jira/browse/NIFI-4632
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.5.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.5.0
>
>
> With a new install, from 'master' branch I created an Input Port and then a 
> Remote Process Group pointing to localhost:8080/nifi. When attempting to send 
> data to my Input Port, nothing appears to happen in the UI. In the logs, I 
> see the following:
> {code}
> 2017-11-22 09:30:39,918 WARN [NiFi Web Server-184] 
> o.a.nifi.web.server.HostHeaderHandler Request host header 
> [.local:8080] different from web hostname [localhost(:8080)]. 
> Overriding to [localhost:8080/nifi-api/site-to-site/peers]
> 2017-11-22 09:30:39,918 WARN [Http Site-to-Site PeerSelector] 
> o.a.n.r.util.SiteToSiteRestApiClient Failed to parse Json. The specified URL 
> http://.local:8080/nifi-api is not a proper remote NiFi endpoint 
> for Site-to-Site communication. 
> requestedUrl=http://.local:8080/nifi-api/site-to-site/peers, 
> response=System Error
> The request contained an invalid host header [.local:8080] in 
> the request [/nifi-api/site-to-site/peers]. Check for request manipulation or 
> third-party intercept. 
> {code}
> I tried updating nifi.properties to set the "nifi.web.http.host" property to 
> .local and that did resolve the issue... but then I could not 
> connect to the UI using localhost:8080 but instead had to connect using 
> .local. 
> This appears to not affect any released versions of NiFi.



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

[jira] [Commented] (NIFI-4193) Transition to Spotify dockerfile-maven plugin

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4193:
--

Github user asfgit closed the pull request at:

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


> Transition to Spotify dockerfile-maven plugin
> -
>
> Key: NIFI-4193
> URL: https://issues.apache.org/jira/browse/NIFI-4193
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Docker
>Reporter: Aldrin Piri
>Assignee: Aldrin Piri
> Fix For: 1.5.0
>
>
> As per 
> https://github.com/spotify/docker-maven-plugin#the-future-of-docker-maven-plugin,
>  it is preferred to make use of the dockerfile-maven plugin 
> (https://github.com/spotify/dockerfile-maven).  We should consider using this 
> plugin instead as well.



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

[jira] [Updated] (NIFI-4193) Transition to Spotify dockerfile-maven plugin

[Aldrin Piri (JIRA)]

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

Aldrin Piri updated NIFI-4193:
--
Fix Version/s: 1.5.0

> Transition to Spotify dockerfile-maven plugin
> -
>
> Key: NIFI-4193
> URL: https://issues.apache.org/jira/browse/NIFI-4193
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Docker
>Reporter: Aldrin Piri
>Assignee: Aldrin Piri
> Fix For: 1.5.0
>
>
> As per 
> https://github.com/spotify/docker-maven-plugin#the-future-of-docker-maven-plugin,
>  it is preferred to make use of the dockerfile-maven plugin 
> (https://github.com/spotify/dockerfile-maven).  We should consider using this 
> plugin instead as well.



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

[jira] [Updated] (NIFI-4193) Transition to Spotify dockerfile-maven plugin

[Aldrin Piri (JIRA)]

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

Aldrin Piri updated NIFI-4193:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Transition to Spotify dockerfile-maven plugin
> -
>
> Key: NIFI-4193
> URL: https://issues.apache.org/jira/browse/NIFI-4193
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Docker
>Reporter: Aldrin Piri
>Assignee: Aldrin Piri
> Fix For: 1.5.0
>
>
> As per 
> https://github.com/spotify/docker-maven-plugin#the-future-of-docker-maven-plugin,
>  it is preferred to make use of the dockerfile-maven plugin 
> (https://github.com/spotify/dockerfile-maven).  We should consider using this 
> plugin instead as well.



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

[jira] [Commented] (NIFI-4193) Transition to Spotify dockerfile-maven plugin

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-4193 Converting to use the dockerfile-maven plugin to replace deprecated 
plugin.

This closes #2155.


> Transition to Spotify dockerfile-maven plugin
> -
>
> Key: NIFI-4193
> URL: https://issues.apache.org/jira/browse/NIFI-4193
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Docker
>Reporter: Aldrin Piri
>Assignee: Aldrin Piri
>
> As per 
> https://github.com/spotify/docker-maven-plugin#the-future-of-docker-maven-plugin,
>  it is preferred to make use of the dockerfile-maven plugin 
> (https://github.com/spotify/dockerfile-maven).  We should consider using this 
> plugin instead as well.



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

[GitHub] nifi pull request #2155: NIFI-4193 Converting to use the dockerfile-maven pl...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[jira] [Commented] (MINIFICPP-49) NiFi Expression Language support

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFICPP-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267827#comment-16267827
 ] 

ASF GitHub Bot commented on MINIFICPP-49:
-

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

https://github.com/apache/nifi-minifi-cpp/pull/188#discussion_r153360632
  
--- Diff: extensions/expression-language/ProcessContextExpr.cpp ---
@@ -0,0 +1,43 @@
+/**
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+#include 
+
+namespace org {
+namespace apache {
+namespace nifi {
+namespace minifi {
+namespace core {
+
+bool ProcessContext::getProperty(const std::string , std::string 
,
+ const std::shared_ptr 
_file) {
+  if (expressions_.find(name) == expressions_.end()) {
--- End diff --

where is the expressions_ map populated?


> NiFi Expression Language support
> 
>
> Key: MINIFICPP-49
> URL: https://issues.apache.org/jira/browse/MINIFICPP-49
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Jeremy Dyer
>Assignee: Andrew Christianson
>
> An implementation of NiFi's expression language is needed for the cpp version 
> of the project. The feature should support all of the same EL syntax that 
> NiFi supports so that any flow developed in NiFi and then ran through the 
> minifi-toolkit will generate a valid .yml configuration file. Currently if 
> there are any expression language values in the flow.yml file the agent will 
> not act as anticipated or crash.



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

[GitHub] nifi issue #2155: NIFI-4193 Converting to use the dockerfile-maven plugin

[jfrazee]

Github user jfrazee commented on the issue:

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

Successfully ran build w/ -Pcontrib-check and tested image w/ `docker run 
-it -p 8080:8080 apache/nifi:latest`


---

[jira] [Commented] (NIFI-4193) Transition to Spotify dockerfile-maven plugin

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4193:
--

Github user jfrazee commented on the issue:

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

Successfully ran build w/ -Pcontrib-check and tested image w/ `docker run 
-it -p 8080:8080 apache/nifi:latest`


> Transition to Spotify dockerfile-maven plugin
> -
>
> Key: NIFI-4193
> URL: https://issues.apache.org/jira/browse/NIFI-4193
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Docker
>Reporter: Aldrin Piri
>Assignee: Aldrin Piri
>
> As per 
> https://github.com/spotify/docker-maven-plugin#the-future-of-docker-maven-plugin,
>  it is preferred to make use of the dockerfile-maven plugin 
> (https://github.com/spotify/dockerfile-maven).  We should consider using this 
> plugin instead as well.



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

[jira] [Commented] (MINIFICPP-326) Build failure in Fedora 27

[marco polo (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFICPP-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267794#comment-16267794
 ] 

marco polo commented on MINIFICPP-326:
--

[~joewitt] Please try the following

0) sudo yum install clang
1) export CC=/usr/bin/clang
export CXX=/usr/bin/clang++
2) rm -rf build ( your build dir)
3) mkdir build && cmake .. [ proceed as normal]

> Build failure in Fedora 27
> --
>
> Key: MINIFICPP-326
> URL: https://issues.apache.org/jira/browse/MINIFICPP-326
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Affects Versions: 0.3.0
> Environment: Linux vandal 4.13.13-300.fc27.x86_64 #1 SMP Wed Nov 15 
> 15:47:50 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
> gcc (GCC) 7.2.1 20170915 (Red Hat 7.2.1-2)
> Copyright (C) 2017 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>Reporter: Joseph Witt
>
> Following is the last many lines of output from
> {quote}
>  #define __USE_POSIX
>  
> In file included from 
> /usr/include/c++/7/x86_64-redhat-linux/bits/os_defines.h:39:0,
>  from 
> /usr/include/c++/7/x86_64-redhat-linux/bits/c++config.h:2494,
>  from /usr/include/c++/7/utility:68,
>  from /usr/include/c++/7/algorithm:60,
>  from 
> /development/build-verify/nifi-minifi-cpp-0.3.0-source/libminifi/include/core/Property.h:21,
>  from 
> /development/build-verify/nifi-minifi-cpp-0.3.0-source/libminifi/include/processors/AppendHostInfo.h:23,
>  from 
> /development/build-verify/nifi-minifi-cpp-0.3.0-source/libminifi/src/processors/AppendHostInfo.cpp:20:
> /usr/include/features.h:295:0: note: this is the location of the previous 
> definition
>  # define __USE_POSIX 1
>  
> [ 16%] Building CXX object 
> libminifi/CMakeFiles/minifi.dir/src/processors/ExecuteProcess.cpp.o
> [ 16%] Building CXX object 
> libminifi/CMakeFiles/minifi.dir/src/processors/ExtractText.cpp.o
> [ 16%] Building CXX object 
> libminifi/CMakeFiles/minifi.dir/src/processors/GenerateFlowFile.cpp.o
> [ 16%] Building CXX object 
> libminifi/CMakeFiles/minifi.dir/src/processors/GetFile.cpp.o
> [ 16%] Building CXX object 
> libminifi/CMakeFiles/minifi.dir/src/processors/GetTCP.cpp.o
> [ 16%] Building CXX object 
> libminifi/CMakeFiles/minifi.dir/src/processors/ListenHTTP.cpp.o
> [ 16%] Building CXX object 
> libminifi/CMakeFiles/minifi.dir/src/processors/ListenSyslog.cpp.o
> [ 17%] Building CXX object 
> libminifi/CMakeFiles/minifi.dir/src/processors/LogAttribute.cpp.o
> [ 17%] Building CXX object 
> libminifi/CMakeFiles/minifi.dir/src/processors/PutFile.cpp.o
> [ 17%] Building CXX object 
> libminifi/CMakeFiles/minifi.dir/src/processors/TailFile.cpp.o
> [ 17%] Linking CXX static library libminifi.a
> [ 17%] Built target minifi
> Scanning dependencies of target spd_lib
> [ 17%] Building CXX object 
> CMakeFiles/spd_lib.dir/thirdparty/spdlog-20170710/include/spdlog/dummy.cpp.o
> [ 17%] Linking CXX static library libspd_lib.a
> [ 17%] Built target spd_lib
> Scanning dependencies of target catch_main
> [ 18%] Building CXX object 
> CMakeFiles/catch_main.dir/libminifi/test/CatchMain.cpp.o
> [ 18%] Linking CXX static library libcatch_main.a
> [ 18%] Built target catch_main
> Scanning dependencies of target test_base
> [ 18%] Building CXX object 
> CMakeFiles/test_base.dir/libminifi/test/TestBase.cpp.o
> [ 18%] Linking CXX static library libtest_base.a
> [ 18%] Built target test_base
> Scanning dependencies of target civetweb-cpp
> [ 18%] Building CXX object 
> thirdparty/civetweb-1.9.1/src/CMakeFiles/civetweb-cpp.dir/CivetServer.cpp.o
> [ 18%] Linking CXX static library libcivetweb-cpp.a
> Error running link command: Segmentation fault
> make[2]: *** 
> [thirdparty/civetweb-1.9.1/src/CMakeFiles/civetweb-cpp.dir/build.make:96: 
> thirdparty/civetweb-1.9.1/src/libcivetweb-cpp.a] Error 1
> make[1]: *** [CMakeFiles/Makefile2:1759: 
> thirdparty/civetweb-1.9.1/src/CMakeFiles/civetweb-cpp.dir/all] Error 2
> make: *** [Makefile:163: all] Error 2
> {quote}
> Here is the command history i ran as privileged user to prepare the env
> {quote}
>   116  yum install cmake   gcc gcc-c++   libcurl-devel   rocksdb-devel 
> rocksdb   libuuid libuuid-devel   boost-devel   openssl-devel   bzip2-devel   
> xz-devel   doxygen
>   117  yum install python34-devel
>   118  dnf install python34-devel
>   119  dnf list installed python
>   120  dnf list installed python3
>   121  dnf install python3-devel
>   122  dnf install lua-devel
>   123  dnf install libusb-devel libpng-devel
>   124  dnf install docker
>   125  dnf install docker python-virtualenv
>   126  python --version
>   127  python3 --version
>   128  dnf install gpsd-devel
>   129  dfn install 

[jira] [Resolved] (NIFIREG-57) Provide ability to provide different 'verbiage providers' for flow differences when comparing two flows

[Bryan Bende (JIRA)]

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

Bryan Bende resolved NIFIREG-57.

   Resolution: Fixed
Fix Version/s: 0.0.1

> Provide ability to provide different 'verbiage providers' for flow 
> differences when comparing two flows
> ---
>
> Key: NIFIREG-57
> URL: https://issues.apache.org/jira/browse/NIFIREG-57
> Project: NiFi Registry
>  Issue Type: Improvement
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 0.0.1
>
>




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

[jira] [Commented] (NIFIREG-57) Provide ability to provide different 'verbiage providers' for flow differences when comparing two flows

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFIREG-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267751#comment-16267751
 ] 

ASF GitHub Bot commented on NIFIREG-57:
---

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-registry/pull/42


> Provide ability to provide different 'verbiage providers' for flow 
> differences when comparing two flows
> ---
>
> Key: NIFIREG-57
> URL: https://issues.apache.org/jira/browse/NIFIREG-57
> Project: NiFi Registry
>  Issue Type: Improvement
>Reporter: Mark Payne
>Assignee: Mark Payne
>




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

[GitHub] nifi-registry pull request #42: NIFIREG-57: Added EvolvingDifferenceDescript...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-registry/pull/42


---

[jira] [Commented] (NIFIREG-57) Provide ability to provide different 'verbiage providers' for flow differences when comparing two flows

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFIREG-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267750#comment-16267750
 ] 

ASF GitHub Bot commented on NIFIREG-57:
---

Github user bbende commented on the issue:

https://github.com/apache/nifi-registry/pull/42
  
+1 looks good, will merge


> Provide ability to provide different 'verbiage providers' for flow 
> differences when comparing two flows
> ---
>
> Key: NIFIREG-57
> URL: https://issues.apache.org/jira/browse/NIFIREG-57
> Project: NiFi Registry
>  Issue Type: Improvement
>Reporter: Mark Payne
>Assignee: Mark Payne
>




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

[GitHub] nifi-registry issue #42: NIFIREG-57: Added EvolvingDifferenceDescriptor vs. ...

[bbende]

Github user bbende commented on the issue:

https://github.com/apache/nifi-registry/pull/42
  
+1 looks good, will merge


---

[GitHub] nifi-minifi-cpp pull request #195: MINIFICPP-307: Support text mode in Gener...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[jira] [Commented] (MINIFICPP-307) GenerateFlowFile ignores type property

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFICPP-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267742#comment-16267742
 ] 

ASF GitHub Bot commented on MINIFICPP-307:
--

Github user asfgit closed the pull request at:

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


> GenerateFlowFile ignores type property
> --
>
> Key: MINIFICPP-307
> URL: https://issues.apache.org/jira/browse/MINIFICPP-307
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Andrew Christianson
>Priority: Minor
> Fix For: 0.4.0
>
>
> It is currently stuck on generating binary data only.



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

[jira] [Created] (MINIFICPP-326) Build failure in Fedora 27

[Joseph Witt (JIRA)]

Joseph Witt created MINIFICPP-326:
-

 Summary: Build failure in Fedora 27
 Key: MINIFICPP-326
 URL: https://issues.apache.org/jira/browse/MINIFICPP-326
 Project: NiFi MiNiFi C++
  Issue Type: Bug
Affects Versions: 0.3.0
 Environment: Linux vandal 4.13.13-300.fc27.x86_64 #1 SMP Wed Nov 15 
15:47:50 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

gcc (GCC) 7.2.1 20170915 (Red Hat 7.2.1-2)
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Reporter: Joseph Witt


Following is the last many lines of output from

{quote}
 #define __USE_POSIX
 
In file included from 
/usr/include/c++/7/x86_64-redhat-linux/bits/os_defines.h:39:0,
 from 
/usr/include/c++/7/x86_64-redhat-linux/bits/c++config.h:2494,
 from /usr/include/c++/7/utility:68,
 from /usr/include/c++/7/algorithm:60,
 from 
/development/build-verify/nifi-minifi-cpp-0.3.0-source/libminifi/include/core/Property.h:21,
 from 
/development/build-verify/nifi-minifi-cpp-0.3.0-source/libminifi/include/processors/AppendHostInfo.h:23,
 from 
/development/build-verify/nifi-minifi-cpp-0.3.0-source/libminifi/src/processors/AppendHostInfo.cpp:20:
/usr/include/features.h:295:0: note: this is the location of the previous 
definition
 # define __USE_POSIX 1
 
[ 16%] Building CXX object 
libminifi/CMakeFiles/minifi.dir/src/processors/ExecuteProcess.cpp.o
[ 16%] Building CXX object 
libminifi/CMakeFiles/minifi.dir/src/processors/ExtractText.cpp.o
[ 16%] Building CXX object 
libminifi/CMakeFiles/minifi.dir/src/processors/GenerateFlowFile.cpp.o
[ 16%] Building CXX object 
libminifi/CMakeFiles/minifi.dir/src/processors/GetFile.cpp.o
[ 16%] Building CXX object 
libminifi/CMakeFiles/minifi.dir/src/processors/GetTCP.cpp.o
[ 16%] Building CXX object 
libminifi/CMakeFiles/minifi.dir/src/processors/ListenHTTP.cpp.o
[ 16%] Building CXX object 
libminifi/CMakeFiles/minifi.dir/src/processors/ListenSyslog.cpp.o
[ 17%] Building CXX object 
libminifi/CMakeFiles/minifi.dir/src/processors/LogAttribute.cpp.o
[ 17%] Building CXX object 
libminifi/CMakeFiles/minifi.dir/src/processors/PutFile.cpp.o
[ 17%] Building CXX object 
libminifi/CMakeFiles/minifi.dir/src/processors/TailFile.cpp.o
[ 17%] Linking CXX static library libminifi.a
[ 17%] Built target minifi
Scanning dependencies of target spd_lib
[ 17%] Building CXX object 
CMakeFiles/spd_lib.dir/thirdparty/spdlog-20170710/include/spdlog/dummy.cpp.o
[ 17%] Linking CXX static library libspd_lib.a
[ 17%] Built target spd_lib
Scanning dependencies of target catch_main
[ 18%] Building CXX object 
CMakeFiles/catch_main.dir/libminifi/test/CatchMain.cpp.o
[ 18%] Linking CXX static library libcatch_main.a
[ 18%] Built target catch_main
Scanning dependencies of target test_base
[ 18%] Building CXX object 
CMakeFiles/test_base.dir/libminifi/test/TestBase.cpp.o
[ 18%] Linking CXX static library libtest_base.a
[ 18%] Built target test_base
Scanning dependencies of target civetweb-cpp
[ 18%] Building CXX object 
thirdparty/civetweb-1.9.1/src/CMakeFiles/civetweb-cpp.dir/CivetServer.cpp.o
[ 18%] Linking CXX static library libcivetweb-cpp.a
Error running link command: Segmentation fault
make[2]: *** 
[thirdparty/civetweb-1.9.1/src/CMakeFiles/civetweb-cpp.dir/build.make:96: 
thirdparty/civetweb-1.9.1/src/libcivetweb-cpp.a] Error 1
make[1]: *** [CMakeFiles/Makefile2:1759: 
thirdparty/civetweb-1.9.1/src/CMakeFiles/civetweb-cpp.dir/all] Error 2
make: *** [Makefile:163: all] Error 2
{quote}

Here is the command history i ran as privileged user to prepare the env

{quote}
  116  yum install cmake   gcc gcc-c++   libcurl-devel   rocksdb-devel rocksdb  
 libuuid libuuid-devel   boost-devel   openssl-devel   bzip2-devel   xz-devel   
doxygen
  117  yum install python34-devel
  118  dnf install python34-devel
  119  dnf list installed python
  120  dnf list installed python3
  121  dnf install python3-devel
  122  dnf install lua-devel
  123  dnf install libusb-devel libpng-devel
  124  dnf install docker
  125  dnf install docker python-virtualenv
  126  python --version
  127  python3 --version
  128  dnf install gpsd-devel
  129  dfn install libpcap-devel
  130  dnf install libpcap-devel
{quote}

Here is the commands ran as build user
{quote}
  598  mkdir build
  599  cd build/
  600  ls
  601  cmake ..
  602  make
{quote}



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

[jira] [Closed] (NIFI-1611) Enhancements to PutMongo processor: Upserts

[Matt Burgess (JIRA)]

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

Matt Burgess closed NIFI-1611.
--
Assignee: (was: Matt Burgess)

> Enhancements to PutMongo processor: Upserts
> ---
>
> Key: NIFI-1611
> URL: https://issues.apache.org/jira/browse/NIFI-1611
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.5.1
> Environment: all
>Reporter: Uwe Geercken
>Priority: Minor
>
> The current implementation of the PutMongo processor does not allow to use 
> operators such as $push or $inc.
> Enhance the processor to allow the use of mongodb operators to allow a more 
> flexible usage.
> As mongodb has a lot of these operators maybe an idea would be to allow a 
> "raw" mode, where the content of the Json document is directly sent to 
> mongodb as-is and thus is executed as-is.



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

[jira] [Assigned] (NIFI-1611) Enhancements to PutMongo processor: Upserts

[Matt Burgess (JIRA)]

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

Matt Burgess reassigned NIFI-1611:
--

Assignee: Matt Burgess

> Enhancements to PutMongo processor: Upserts
> ---
>
> Key: NIFI-1611
> URL: https://issues.apache.org/jira/browse/NIFI-1611
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.5.1
> Environment: all
>Reporter: Uwe Geercken
>Assignee: Matt Burgess
>Priority: Minor
>
> The current implementation of the PutMongo processor does not allow to use 
> operators such as $push or $inc.
> Enhance the processor to allow the use of mongodb operators to allow a more 
> flexible usage.
> As mongodb has a lot of these operators maybe an idea would be to allow a 
> "raw" mode, where the content of the Json document is directly sent to 
> mongodb as-is and thus is executed as-is.



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

[jira] [Commented] (NIFIREG-57) Provide ability to provide different 'verbiage providers' for flow differences when comparing two flows

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFIREG-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267598#comment-16267598
 ] 

ASF GitHub Bot commented on NIFIREG-57:
---

GitHub user markap14 opened a pull request:

https://github.com/apache/nifi-registry/pull/42

NIFIREG-57: Added EvolvingDifferenceDescriptor vs. StaticDifferenceDe…

…scriptor

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

$ git pull https://github.com/markap14/nifi-registry NIFIREG-57

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

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


commit e35ec5b0ec3802033a0a55ebcaab44fdd202bca6
Author: Mark Payne 
Date:   2017-11-21T19:40:00Z

NIFIREG-57: Added EvolvingDifferenceDescriptor vs. 
StaticDifferenceDescriptor




> Provide ability to provide different 'verbiage providers' for flow 
> differences when comparing two flows
> ---
>
> Key: NIFIREG-57
> URL: https://issues.apache.org/jira/browse/NIFIREG-57
> Project: NiFi Registry
>  Issue Type: Improvement
>Reporter: Mark Payne
>Assignee: Mark Payne
>




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

[GitHub] nifi-registry pull request #42: NIFIREG-57: Added EvolvingDifferenceDescript...

[markap14]

GitHub user markap14 opened a pull request:

https://github.com/apache/nifi-registry/pull/42

NIFIREG-57: Added EvolvingDifferenceDescriptor vs. StaticDifferenceDe…

…scriptor

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

$ git pull https://github.com/markap14/nifi-registry NIFIREG-57

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

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


commit e35ec5b0ec3802033a0a55ebcaab44fdd202bca6
Author: Mark Payne 
Date:   2017-11-21T19:40:00Z

NIFIREG-57: Added EvolvingDifferenceDescriptor vs. 
StaticDifferenceDescriptor




---

[jira] [Updated] (NIFI-4526) The REST API and NiFi UI should allow the target URL for a remote process group to be edited

[Matt Gilman (JIRA)]

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

Matt Gilman updated NIFI-4526:
--
Status: Patch Available  (was: In Progress)

PR is available in https://github.com/apache/nifi/pull/2219

> The REST API and NiFi UI should allow the target URL for a remote process 
> group to be edited
> 
>
> Key: NIFI-4526
> URL: https://issues.apache.org/jira/browse/NIFI-4526
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework, Core UI, Flow Versioning
>Reporter: Joseph Witt
>Assignee: Matt Gilman
>Priority: Critical
> Fix For: 1.5.0
>
>
> Today remote process groups (RPG) once established cannot have the target URL 
> edited.  If a user wants to change the URL they have to add a new RPG for the 
> new target and change the relationships/connections to point to it.  Then 
> they can remove the old one.
> That process ensures that there is explicit (user provided mapping) to the 
> new ports available at the new target.  However, this is very limiting in 
> templates today and would be very limiting to the effectiveness of the 
> versioned flow registry and porting between environments.
> We could make the URL support expression language statements but at present 
> that would be the first non component property (like processor properties) 
> where EL is allowed and we need to have a more thoughtful and consistent 
> approach for that to include things like number of processor threads/etc.. A 
> cleaner and more consistent option is to do this like sensitive properties 
> are being handled in versioned flows which is they are not part of the 
> versioned flow definition but rather on import or when edited we allow the 
> user to set their environment/flow specific values all without making the 
> local flow version dirty in terms of versioned flow management.
> So, we should allow the user via the UI and obviously through REST API calls 
> to change the URL.  This would require stopping the RPG, changing the target 
> URL (resycing/establishing remote ports/auth/etc..), then starting it.  We 
> need to make sure this change does not necessitate a new version of the flow.



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

[jira] [Commented] (NIFI-4333) Dockerize NiFi Toolkit

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4333:
--

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

https://github.com/apache/nifi/pull/2161#discussion_r153320426
  
--- Diff: nifi-toolkit/nifi-toolkit-assembly/docker/Dockerfile ---
@@ -0,0 +1,48 @@
+# 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.
+#
+
+FROM openjdk:8-jre-alpine
+LABEL maintainer "Apache NiFi "
+
+ARG UID=1000
+ARG GID=1000
+ARG NIFI_TOOLKIT_VERSION=1.4.0-SNAPSHOT
--- End diff --

@MikeThomsen Will evaluate the latter but given how the structure of docker 
images is currently composed this is needed as it will be making use of the 
generated nifi toolkit as part of the build which will be a SNAPSHOT.

The Dockerfile.hub version is devoid of this given that it only is built 
against generated releases.


> Dockerize NiFi Toolkit
> --
>
> Key: NIFI-4333
> URL: https://issues.apache.org/jira/browse/NIFI-4333
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Docker
>Reporter: Aldrin Piri
>Assignee: Aldrin Piri
>
> It would be helpful to have a TLS Toolkit image to work in conjunction with 
> NiFI and would help in orchestration of clustered instances as well as 
> provisioning security items.
> As this is one assembly, we should support all tooling provided through one 
> image.



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

[GitHub] nifi pull request #2161: NIFI-4333: Providing Docker support of the NiFi Too...

[apiri]

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

https://github.com/apache/nifi/pull/2161#discussion_r153320426
  
--- Diff: nifi-toolkit/nifi-toolkit-assembly/docker/Dockerfile ---
@@ -0,0 +1,48 @@
+# 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.
+#
+
+FROM openjdk:8-jre-alpine
+LABEL maintainer "Apache NiFi "
+
+ARG UID=1000
+ARG GID=1000
+ARG NIFI_TOOLKIT_VERSION=1.4.0-SNAPSHOT
--- End diff --

@MikeThomsen Will evaluate the latter but given how the structure of docker 
images is currently composed this is needed as it will be making use of the 
generated nifi toolkit as part of the build which will be a SNAPSHOT.

The Dockerfile.hub version is devoid of this given that it only is built 
against generated releases.


---

[jira] [Commented] (NIFI-1611) Enhancements to PutMongo processor: Upserts

[Mike Thomsen (JIRA)]

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

Mike Thomsen commented on NIFI-1611:


I think #4588 resolves this ticket. [~mattyb149]

> Enhancements to PutMongo processor: Upserts
> ---
>
> Key: NIFI-1611
> URL: https://issues.apache.org/jira/browse/NIFI-1611
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.5.1
> Environment: all
>Reporter: Uwe Geercken
>Priority: Minor
>
> The current implementation of the PutMongo processor does not allow to use 
> operators such as $push or $inc.
> Enhance the processor to allow the use of mongodb operators to allow a more 
> flexible usage.
> As mongodb has a lot of these operators maybe an idea would be to allow a 
> "raw" mode, where the content of the Json document is directly sent to 
> mongodb as-is and thus is executed as-is.



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

[jira] [Commented] (NIFI-4642) Unstable nifi core build due to validate process scheduler test

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-4642:
---


Linux vandal 4.13.13-300.fc27.x86_64 #1 SMP Wed Nov 15 15:47:50 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux

Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 
2017-04-03T15:39:06-04:00)
Maven home: /development/apache-maven-3.5.0
Java version: 1.8.0_144, vendor: Oracle Corporation
Java home: /usr/java/jdk1.8.0_144/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.13.13-300.fc27.x86_64", arch: "amd64", family: 
"unix"

> Unstable nifi core build due to validate process scheduler test
> ---
>
> Key: NIFI-4642
> URL: https://issues.apache.org/jira/browse/NIFI-4642
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Joseph Witt
>Assignee: Joseph Witt
>
> Tests run: 16, Failures: 1, Errors: 0, Skipped: 2, Time elapsed: 34.747 sec 
> <<< FAILURE! - in org.apache.nifi.controller.scheduling.TestProcessorLifecycle
> validateProcessScheduledAfterAdministrativeDelayDueToTheOnScheduledException(org.apache.nifi.controller.scheduling.TestProcessorLifecycle)
>   Time elapsed: 3.147 sec  <<< FAILURE!
> java.lang.AssertionError: null
>   at org.junit.Assert.fail(Assert.java:86)
>   at org.junit.Assert.assertTrue(Assert.java:41)
>   at org.junit.Assert.assertTrue(Assert.java:52)
>   at 
> org.apache.nifi.controller.scheduling.TestProcessorLifecycle.validateProcessScheduledAfterAdministrativeDelayDueToTheOnScheduledException(TestProcessorLifecycle.java:372)



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

[jira] [Commented] (MINIFICPP-325) Update version in CMAKE

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFICPP-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267469#comment-16267469
 ] 

ASF GitHub Bot commented on MINIFICPP-325:
--

GitHub user phrocker opened a pull request:

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

MINIFICPP-325: Up semantic version

Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.

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 MINIFI- 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:
- [ ] 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?
- [ ] If applicable, have you updated the NOTICE file?

### 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/phrocker/nifi-minifi-cpp MINIFICPP-325

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

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


commit 60170fb7da0456ccb556a352dfe919ae7fc964db
Author: Marc Parisi 
Date:   2017-11-27T20:22:15Z

MINIFICPP-325: Up semantic version




> Update version in CMAKE
> ---
>
> Key: MINIFICPP-325
> URL: https://issues.apache.org/jira/browse/MINIFICPP-325
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Reporter: marco polo
>Assignee: marco polo
>




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

[jira] [Created] (NIFI-4642) Unstable nifi core build due to validate process scheduler test

[Joseph Witt (JIRA)]

Joseph Witt created NIFI-4642:
-

 Summary: Unstable nifi core build due to validate process 
scheduler test
 Key: NIFI-4642
 URL: https://issues.apache.org/jira/browse/NIFI-4642
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core Framework
Reporter: Joseph Witt
Assignee: Joseph Witt


Tests run: 16, Failures: 1, Errors: 0, Skipped: 2, Time elapsed: 34.747 sec <<< 
FAILURE! - in org.apache.nifi.controller.scheduling.TestProcessorLifecycle
validateProcessScheduledAfterAdministrativeDelayDueToTheOnScheduledException(org.apache.nifi.controller.scheduling.TestProcessorLifecycle)
  Time elapsed: 3.147 sec  <<< FAILURE!
java.lang.AssertionError: null
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at 
org.apache.nifi.controller.scheduling.TestProcessorLifecycle.validateProcessScheduledAfterAdministrativeDelayDueToTheOnScheduledException(TestProcessorLifecycle.java:372)




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

[jira] [Commented] (NIFI-4628) Update ListS3 proccesor to support List Objects Version 2

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4628:
--

GitHub user aburkard opened a pull request:

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

NIFI-4628 Add support for ListS3Version2 API

Thank you for submitting a contribution to Apache NiFi.

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

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

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

- [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?
- [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?
- [x] 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/aburkard/nifi NIFI-4628

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

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


commit 17af6677e4c65886f1a928c0cf10faac52809eff
Author: aburkard 
Date:   2017-11-27T20:18:47Z

NIFI-4628 Add support for ListS3Version2 API




> Update ListS3 proccesor to support List Objects Version 2
> -
>
> Key: NIFI-4628
> URL: https://issues.apache.org/jira/browse/NIFI-4628
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Andrew Burkard
>Priority: Minor
>
> AWS has revised the List Objects API: 
> http://docs.aws.amazon.com/AmazonS3/latest/API/v2-RESTBucketGET.html
> The main difference is the new API passes a continuation token in the 
> response for multi-page listings rather than requiring the client to keep 
> track of the lexicographically last key listed. The new version also appears 
> to be the only API supported going forward for new AWS services (e.g. 
> Snowball). It would be nice if the ListS3 processor supported either via an 
> attribute.



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

[GitHub] nifi pull request #2300: NIFI-4628 Add support for ListS3Version2 API

[aburkard]

GitHub user aburkard opened a pull request:

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

NIFI-4628 Add support for ListS3Version2 API

Thank you for submitting a contribution to Apache NiFi.

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

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

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

- [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?
- [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?
- [x] 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/aburkard/nifi NIFI-4628

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

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


commit 17af6677e4c65886f1a928c0cf10faac52809eff
Author: aburkard 
Date:   2017-11-27T20:18:47Z

NIFI-4628 Add support for ListS3Version2 API




---

[jira] [Commented] (NIFI-4445) Unit Test Failure for Scripted Reporting Task

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4445:
--

Github user aburkard closed the pull request at:

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


> Unit Test Failure for Scripted Reporting Task
> -
>
> Key: NIFI-4445
> URL: https://issues.apache.org/jira/browse/NIFI-4445
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.4.0
> Environment: Apache Maven 3.5.0 
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
> Maven home: /data1/apache-maven-3.5.0
> Java version: 1.8.0_144, vendor: Oracle Corporation
> Java home: /usr/java/jdk1.8.0_144/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.12.14-300.fc26.x86_64", arch: "amd64", family: 
> "unix"
>Reporter: Joseph Witt
>Assignee: Joseph Witt
> Fix For: 1.5.0
>
>
> ---
>  T E S T S
> ---
> Running org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest
> Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.641 sec <<< 
> FAILURE! - in org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest
> testVMEventsGroovyScript(org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest)
>   Time elapsed: 0.024 sec  <<< FAILURE!
> java.lang.AssertionError: null
>   at org.junit.Assert.fail(Assert.java:86)
>   at org.junit.Assert.assertTrue(Assert.java:41)
>   at org.junit.Assert.assertTrue(Assert.java:52)
>   at org.junit.Assert$assertTrue$0.callStatic(Unknown Source)
>   at 
> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:56)
>   at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:194)
>   at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:206)
>   at 
> org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest.testVMEventsGroovyScript(ScriptedReportingTaskGroovyTest.groovy:195)
> Appears to be related to the JDK/JRE.  The same environment in terms of 
> kernel/maven/etc... just slightly older JDK/JRE works perfectly fine.
> Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 
> 2017-04-03T15:39:06-04:00)
> Maven home: /opt/apache-maven-3.5.0
> Java version: 1.8.0_141, vendor: Oracle Corporation
> Java home: /usr/java/jdk1.8.0_141/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.12.14-300.fc26.x86_64", arch: "amd64", family: 
> "unix"



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

[GitHub] nifi-minifi-cpp pull request #208: MINIFICPP-325: Up semantic version

[phrocker]

GitHub user phrocker opened a pull request:

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

MINIFICPP-325: Up semantic version

Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.

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 MINIFI- 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:
- [ ] 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?
- [ ] If applicable, have you updated the NOTICE file?

### 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/phrocker/nifi-minifi-cpp MINIFICPP-325

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

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


commit 60170fb7da0456ccb556a352dfe919ae7fc964db
Author: Marc Parisi 
Date:   2017-11-27T20:22:15Z

MINIFICPP-325: Up semantic version




---

[jira] [Commented] (NIFI-4445) Unit Test Failure for Scripted Reporting Task

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4445:
--

Github user aburkard commented on the issue:

https://github.com/apache/nifi/pull/2299
  
@joewitt yep my bad, NIFI-4628 is the right issue.


> Unit Test Failure for Scripted Reporting Task
> -
>
> Key: NIFI-4445
> URL: https://issues.apache.org/jira/browse/NIFI-4445
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.4.0
> Environment: Apache Maven 3.5.0 
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
> Maven home: /data1/apache-maven-3.5.0
> Java version: 1.8.0_144, vendor: Oracle Corporation
> Java home: /usr/java/jdk1.8.0_144/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.12.14-300.fc26.x86_64", arch: "amd64", family: 
> "unix"
>Reporter: Joseph Witt
>Assignee: Joseph Witt
> Fix For: 1.5.0
>
>
> ---
>  T E S T S
> ---
> Running org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest
> Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.641 sec <<< 
> FAILURE! - in org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest
> testVMEventsGroovyScript(org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest)
>   Time elapsed: 0.024 sec  <<< FAILURE!
> java.lang.AssertionError: null
>   at org.junit.Assert.fail(Assert.java:86)
>   at org.junit.Assert.assertTrue(Assert.java:41)
>   at org.junit.Assert.assertTrue(Assert.java:52)
>   at org.junit.Assert$assertTrue$0.callStatic(Unknown Source)
>   at 
> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:56)
>   at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:194)
>   at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:206)
>   at 
> org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest.testVMEventsGroovyScript(ScriptedReportingTaskGroovyTest.groovy:195)
> Appears to be related to the JDK/JRE.  The same environment in terms of 
> kernel/maven/etc... just slightly older JDK/JRE works perfectly fine.
> Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 
> 2017-04-03T15:39:06-04:00)
> Maven home: /opt/apache-maven-3.5.0
> Java version: 1.8.0_141, vendor: Oracle Corporation
> Java home: /usr/java/jdk1.8.0_141/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.12.14-300.fc26.x86_64", arch: "amd64", family: 
> "unix"



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

[GitHub] nifi issue #2299: NIFI-4445 Add support for ListS3Version2 API

[aburkard]

Github user aburkard commented on the issue:

https://github.com/apache/nifi/pull/2299
  
@joewitt yep my bad, NIFI-4628 is the right issue.


---

[GitHub] nifi pull request #2299: NIFI-4445 Add support for ListS3Version2 API

[aburkard]

Github user aburkard closed the pull request at:

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


---

[jira] [Commented] (NIFI-4445) Unit Test Failure for Scripted Reporting Task

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4445:
--

Github user joewitt commented on the issue:

https://github.com/apache/nifi/pull/2299
  
@aburkard can you confirm the JIRA you meant this for?  NIFI-4445 looks 
like a typo.

Thanks


> Unit Test Failure for Scripted Reporting Task
> -
>
> Key: NIFI-4445
> URL: https://issues.apache.org/jira/browse/NIFI-4445
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.4.0
> Environment: Apache Maven 3.5.0 
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
> Maven home: /data1/apache-maven-3.5.0
> Java version: 1.8.0_144, vendor: Oracle Corporation
> Java home: /usr/java/jdk1.8.0_144/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.12.14-300.fc26.x86_64", arch: "amd64", family: 
> "unix"
>Reporter: Joseph Witt
>Assignee: Joseph Witt
> Fix For: 1.5.0
>
>
> ---
>  T E S T S
> ---
> Running org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest
> Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.641 sec <<< 
> FAILURE! - in org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest
> testVMEventsGroovyScript(org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest)
>   Time elapsed: 0.024 sec  <<< FAILURE!
> java.lang.AssertionError: null
>   at org.junit.Assert.fail(Assert.java:86)
>   at org.junit.Assert.assertTrue(Assert.java:41)
>   at org.junit.Assert.assertTrue(Assert.java:52)
>   at org.junit.Assert$assertTrue$0.callStatic(Unknown Source)
>   at 
> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:56)
>   at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:194)
>   at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:206)
>   at 
> org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest.testVMEventsGroovyScript(ScriptedReportingTaskGroovyTest.groovy:195)
> Appears to be related to the JDK/JRE.  The same environment in terms of 
> kernel/maven/etc... just slightly older JDK/JRE works perfectly fine.
> Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 
> 2017-04-03T15:39:06-04:00)
> Maven home: /opt/apache-maven-3.5.0
> Java version: 1.8.0_141, vendor: Oracle Corporation
> Java home: /usr/java/jdk1.8.0_141/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.12.14-300.fc26.x86_64", arch: "amd64", family: 
> "unix"



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

[GitHub] nifi issue #2299: NIFI-4445 Add support for ListS3Version2 API

[joewitt]

Github user joewitt commented on the issue:

https://github.com/apache/nifi/pull/2299
  
@aburkard can you confirm the JIRA you meant this for?  NIFI-4445 looks 
like a typo.

Thanks


---

[jira] [Created] (NIFI-4641) If I copy and paste a Remote Process Group, the Batch Settings for the ports are not copied over to the new RPG

[Mark Payne (JIRA)]

Mark Payne created NIFI-4641:


 Summary: If I copy and paste a Remote Process Group, the Batch 
Settings for the ports are not copied over to the new RPG
 Key: NIFI-4641
 URL: https://issues.apache.org/jira/browse/NIFI-4641
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core Framework
Reporter: Mark Payne
Assignee: Mark Payne


I can create a Remote Process Group and go to Manage Ports. If I set one of the 
Batch Settings, and then I copy & Paste the RPG, then the newly created RPG has 
'No value set' for all of the batch settings for all ports.



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

[jira] [Commented] (NIFI-4445) Unit Test Failure for Scripted Reporting Task

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4445:
--

GitHub user aburkard opened a pull request:

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

NIFI-4445 Add support for ListS3Version2 API

Thank you for submitting a contribution to Apache NiFi.

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

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

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

- [ 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?
- [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?
- [ x] 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/aburkard/nifi NIFI-4445

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

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


commit 8482d35c291099ad1fd816ac14f98340afe56f09
Author: aburkard 
Date:   2017-11-27T20:18:47Z

NIFI-4445 Add support for ListS3Version2 API




> Unit Test Failure for Scripted Reporting Task
> -
>
> Key: NIFI-4445
> URL: https://issues.apache.org/jira/browse/NIFI-4445
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.4.0
> Environment: Apache Maven 3.5.0 
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
> Maven home: /data1/apache-maven-3.5.0
> Java version: 1.8.0_144, vendor: Oracle Corporation
> Java home: /usr/java/jdk1.8.0_144/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.12.14-300.fc26.x86_64", arch: "amd64", family: 
> "unix"
>Reporter: Joseph Witt
>Assignee: Joseph Witt
> Fix For: 1.5.0
>
>
> ---
>  T E S T S
> ---
> Running org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest
> Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.641 sec <<< 
> FAILURE! - in org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest
> testVMEventsGroovyScript(org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest)
>   Time elapsed: 0.024 sec  <<< FAILURE!
> java.lang.AssertionError: null
>   at org.junit.Assert.fail(Assert.java:86)
>   at org.junit.Assert.assertTrue(Assert.java:41)
>   at org.junit.Assert.assertTrue(Assert.java:52)
>   at org.junit.Assert$assertTrue$0.callStatic(Unknown Source)
>   at 
> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:56)
>   at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:194)
>   at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:206)
>   at 
> org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest.testVMEventsGroovyScript(ScriptedReportingTaskGroovyTest.groovy:195)
> Appears to be related to the JDK/JRE.  The same environment in terms of 
> kernel/maven/etc... just slightly older JDK/JRE works perfectly fine.
> Apache Maven 3.5.0 

[GitHub] nifi pull request #2299: NIFI-4445 Add support for ListS3Version2 API

[aburkard]

GitHub user aburkard opened a pull request:

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

NIFI-4445 Add support for ListS3Version2 API

Thank you for submitting a contribution to Apache NiFi.

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

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

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

- [ 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?
- [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?
- [ x] 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/aburkard/nifi NIFI-4445

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

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


commit 8482d35c291099ad1fd816ac14f98340afe56f09
Author: aburkard 
Date:   2017-11-27T20:18:47Z

NIFI-4445 Add support for ListS3Version2 API




---

[jira] [Updated] (NIFI-4632) Site-to-Site failing with default configuration

[Mark Payne (JIRA)]

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

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

> Site-to-Site failing with default configuration
> ---
>
> Key: NIFI-4632
> URL: https://issues.apache.org/jira/browse/NIFI-4632
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.5.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.5.0
>
>
> With a new install, from 'master' branch I created an Input Port and then a 
> Remote Process Group pointing to localhost:8080/nifi. When attempting to send 
> data to my Input Port, nothing appears to happen in the UI. In the logs, I 
> see the following:
> {code}
> 2017-11-22 09:30:39,918 WARN [NiFi Web Server-184] 
> o.a.nifi.web.server.HostHeaderHandler Request host header 
> [.local:8080] different from web hostname [localhost(:8080)]. 
> Overriding to [localhost:8080/nifi-api/site-to-site/peers]
> 2017-11-22 09:30:39,918 WARN [Http Site-to-Site PeerSelector] 
> o.a.n.r.util.SiteToSiteRestApiClient Failed to parse Json. The specified URL 
> http://.local:8080/nifi-api is not a proper remote NiFi endpoint 
> for Site-to-Site communication. 
> requestedUrl=http://.local:8080/nifi-api/site-to-site/peers, 
> response=System Error
> The request contained an invalid host header [.local:8080] in 
> the request [/nifi-api/site-to-site/peers]. Check for request manipulation or 
> third-party intercept. 
> {code}
> I tried updating nifi.properties to set the "nifi.web.http.host" property to 
> .local and that did resolve the issue... but then I could not 
> connect to the UI using localhost:8080 but instead had to connect using 
> .local. 
> This appears to not affect any released versions of NiFi.



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

[jira] [Created] (MINIFICPP-325) Update version in CMAKE

[marco polo (JIRA)]

marco polo created MINIFICPP-325:


 Summary: Update version in CMAKE
 Key: MINIFICPP-325
 URL: https://issues.apache.org/jira/browse/MINIFICPP-325
 Project: NiFi MiNiFi C++
  Issue Type: Bug
Reporter: marco polo
Assignee: marco polo






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

[GitHub] nifi-minifi pull request #101: MINIFI-412 Upgrading commons-daemon to 1.1.0 ...

[apiri]

GitHub user apiri opened a pull request:

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

MINIFI-412 Upgrading commons-daemon to 1.1.0 and making use of a mirror

MINIFI-412 Upgrading commons-daemon to 1.1.0 and making use of a mirror 
instead of Apache dist.

Thank you for submitting a contribution to Apache NiFi - MiNiFi.

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

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

- [X] Does your PR title start with MINIFI- 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-minifi 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 minifi-assembly?
- [-] If applicable, have you updated the NOTICE file, including the main 
NOTICE file found under minifi-assembly?

### 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/apiri/nifi-minifi minifi-412

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

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


commit 711d5844471bb8f4547e7f265b7546ae028ceb1b
Author: Aldrin Piri 
Date:   2017-11-27T19:50:41Z

MINIFI-412 Upgrading commons-daemon to 1.1.0 and making use of a mirror 
instead of Apache dist.




---

[jira] [Commented] (MINIFICPP-324) Resolve RHEL7 build issues

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFICPP-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267252#comment-16267252
 ] 

ASF GitHub Bot commented on MINIFICPP-324:
--

Github user asfgit closed the pull request at:

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


> Resolve RHEL7 build issues
> --
>
> Key: MINIFICPP-324
> URL: https://issues.apache.org/jira/browse/MINIFICPP-324
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Reporter: marco polo
>Assignee: marco polo
>




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

[GitHub] nifi-minifi-cpp pull request #207: MINIFICPP-324: Resolve build issues with ...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[jira] [Commented] (MINIFICPP-320) Break apart core minifi from libminifi

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFICPP-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267245#comment-16267245
 ] 

ASF GitHub Bot commented on MINIFICPP-320:
--

Github user phrocker commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/206
  
@calebj There was a commit to resolve it on my rhel7 platform. This was 
merged before that could be added ( once I saw Travis ) -- I put that commit 
within https://github.com/apache/nifi-minifi-cpp/pull/207


> Break apart core minifi from libminifi
> --
>
> Key: MINIFICPP-320
> URL: https://issues.apache.org/jira/browse/MINIFICPP-320
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Reporter: marco polo
>Assignee: marco polo
> Fix For: 0.4.0
>
>
> This will facilitate moving core processors to an extension



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

[jira] [Commented] (MINIFICPP-324) Resolve RHEL7 build issues

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFICPP-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267243#comment-16267243
 ] 

ASF GitHub Bot commented on MINIFICPP-324:
--

GitHub user phrocker opened a pull request:

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

MINIFICPP-324: Resolve build issues with missing civet dependencies

Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.

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 MINIFI- 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:
- [ ] 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?
- [ ] If applicable, have you updated the NOTICE file?

### 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/phrocker/nifi-minifi-cpp MINIFICPP-324

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

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






> Resolve RHEL7 build issues
> --
>
> Key: MINIFICPP-324
> URL: https://issues.apache.org/jira/browse/MINIFICPP-324
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Reporter: marco polo
>Assignee: marco polo
>




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

[GitHub] nifi-minifi-cpp issue #206: MINIFICPP-320: Change Processors to be within th...

[phrocker]

Github user phrocker commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/206
  
@calebj There was a commit to resolve it on my rhel7 platform. This was 
merged before that could be added ( once I saw Travis ) -- I put that commit 
within https://github.com/apache/nifi-minifi-cpp/pull/207


---

[GitHub] nifi-minifi-cpp pull request #207: MINIFICPP-324: Resolve build issues with ...

[phrocker]

GitHub user phrocker opened a pull request:

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

MINIFICPP-324: Resolve build issues with missing civet dependencies

Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.

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 MINIFI- 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:
- [ ] 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?
- [ ] If applicable, have you updated the NOTICE file?

### 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/phrocker/nifi-minifi-cpp MINIFICPP-324

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

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






---

[jira] [Commented] (MINIFICPP-320) Break apart core minifi from libminifi

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFICPP-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267236#comment-16267236
 ] 

ASF GitHub Bot commented on MINIFICPP-320:
--

Github user calebj commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/206
  
This causes some tests to fail to link on Linux both on Travis CI and 
cloud9, both of which are Ubuntu Trusty. Here's the output:
```
[ 19%] Linking CXX executable TestExecuteProcess
libminifi/libminifi.a(ListenHTTP.cpp.o): In function 
`org::apache::nifi::minifi::processors::ListenHTTP::WriteCallback::process(std::shared_ptr)':
ListenHTTP.cpp:(.text+0x9e): undefined reference to `mg_read'
ListenHTTP.cpp:(.text+0x10e): undefined reference to `mg_read'
libminifi/libminifi.a(ListenHTTP.cpp.o): In function 
`org::apache::nifi::minifi::processors::ListenHTTP::Handler::handlePost(CivetServer*,
 mg_connection*)':
ListenHTTP.cpp:(.text+0xd80): undefined reference to `mg_get_request_info'
ListenHTTP.cpp:(.text+0xe50): undefined reference to `mg_printf'
ListenHTTP.cpp:(.text+0x133d): undefined reference to `mg_printf'
ListenHTTP.cpp:(.text+0x14c8): undefined reference to `mg_printf'
ListenHTTP.cpp:(.text+0x1508): undefined reference to `mg_printf'
ListenHTTP.cpp:(.text+0x15a4): undefined reference to `mg_printf'
libminifi/libminifi.a(ListenHTTP.cpp.o):ListenHTTP.cpp:(.text+0x16a6): more 
undefined references to `mg_printf' follow
libminifi/libminifi.a(ListenHTTP.cpp.o): In function 
`org::apache::nifi::minifi::processors::ListenHTTP::onSchedule(org::apache::nifi::minifi::core::ProcessContext*,
 org::apache::nifi::minifi::core::ProcessSessionFactory*)':
ListenHTTP.cpp:(.text+0x254a): undefined reference to 
`CivetServer::CivetServer(std::vector, CivetCallbacks const*)'
ListenHTTP.cpp:(.text+0x25cb): undefined reference to 
`CivetServer::addHandler(std::string const&, CivetHandler*)'
libminifi/libminifi.a(ListenHTTP.cpp.o): In function 
`org::apache::nifi::minifi::processors::ListenHTTP::Handler::sendErrorResponse(mg_connection*)':
ListenHTTP.cpp:(.text+0x76b): undefined reference to `mg_printf'

libminifi/libminifi.a(ListenHTTP.cpp.o):(.rodata._ZTIN3org6apache4nifi6minifi10processors10ListenHTTP7HandlerE[_ZTIN3org6apache4nifi6minifi10processors10ListenHTTP7HandlerE]+0x10):
 undefined reference to `typeinfo for CivetHandler'

libminifi/libminifi.a(ListenHTTP.cpp.o):(.rodata._ZTVN3org6apache4nifi6minifi10processors10ListenHTTP7HandlerE[_ZTVN3org6apache4nifi6minifi10processors10ListenHTTP7HandlerE]+0x20):
 undefined reference to `CivetHandler::handleGet(CivetServer*, mg_connection*)'

libminifi/libminifi.a(ListenHTTP.cpp.o):(.rodata._ZTVN3org6apache4nifi6minifi10processors10ListenHTTP7HandlerE[_ZTVN3org6apache4nifi6minifi10processors10ListenHTTP7HandlerE]+0x30):
 undefined reference to `CivetHandler::handleHead(CivetServer*, mg_connection*)'

libminifi/libminifi.a(ListenHTTP.cpp.o):(.rodata._ZTVN3org6apache4nifi6minifi10processors10ListenHTTP7HandlerE[_ZTVN3org6apache4nifi6minifi10processors10ListenHTTP7HandlerE]+0x38):
 undefined reference to `CivetHandler::handlePut(CivetServer*, mg_connection*)'

libminifi/libminifi.a(ListenHTTP.cpp.o):(.rodata._ZTVN3org6apache4nifi6minifi10processors10ListenHTTP7HandlerE[_ZTVN3org6apache4nifi6minifi10processors10ListenHTTP7HandlerE]+0x40):
 undefined reference to `CivetHandler::handleDelete(CivetServer*, 
mg_connection*)'

libminifi/libminifi.a(ListenHTTP.cpp.o):(.rodata._ZTVN3org6apache4nifi6minifi10processors10ListenHTTP7HandlerE[_ZTVN3org6apache4nifi6minifi10processors10ListenHTTP7HandlerE]+0x48):
 undefined reference to `CivetHandler::handleOptions(CivetServer*, 
mg_connection*)'

libminifi/libminifi.a(ListenHTTP.cpp.o):(.rodata._ZTVN3org6apache4nifi6minifi10processors10ListenHTTP7HandlerE[_ZTVN3org6apache4nifi6minifi10processors10ListenHTTP7HandlerE]+0x50):
 undefined reference to `CivetHandler::handlePatch(CivetServer*, 
mg_connection*)'
collect2: error: ld returned 1 exit status
make[2]: *** [TestExecuteProcess] Error 1
make[1]: *** [CMakeFiles/TestExecuteProcess.dir/all] Error 2
make: *** [all] Error 2
```


> Break apart core minifi from libminifi
> --
>
> Key: MINIFICPP-320
> URL: https://issues.apache.org/jira/browse/MINIFICPP-320
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Reporter: marco polo
>Assignee: marco polo
> Fix For: 0.4.0
>
>
> This will facilitate moving core processors to an extension



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

[GitHub] nifi-minifi-cpp issue #206: MINIFICPP-320: Change Processors to be within th...

[calebj]

Github user calebj commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/206
  
This causes some tests to fail to link on Linux both on Travis CI and 
cloud9, both of which are Ubuntu Trusty. Here's the output:
```
[ 19%] Linking CXX executable TestExecuteProcess
libminifi/libminifi.a(ListenHTTP.cpp.o): In function 
`org::apache::nifi::minifi::processors::ListenHTTP::WriteCallback::process(std::shared_ptr)':
ListenHTTP.cpp:(.text+0x9e): undefined reference to `mg_read'
ListenHTTP.cpp:(.text+0x10e): undefined reference to `mg_read'
libminifi/libminifi.a(ListenHTTP.cpp.o): In function 
`org::apache::nifi::minifi::processors::ListenHTTP::Handler::handlePost(CivetServer*,
 mg_connection*)':
ListenHTTP.cpp:(.text+0xd80): undefined reference to `mg_get_request_info'
ListenHTTP.cpp:(.text+0xe50): undefined reference to `mg_printf'
ListenHTTP.cpp:(.text+0x133d): undefined reference to `mg_printf'
ListenHTTP.cpp:(.text+0x14c8): undefined reference to `mg_printf'
ListenHTTP.cpp:(.text+0x1508): undefined reference to `mg_printf'
ListenHTTP.cpp:(.text+0x15a4): undefined reference to `mg_printf'
libminifi/libminifi.a(ListenHTTP.cpp.o):ListenHTTP.cpp:(.text+0x16a6): more 
undefined references to `mg_printf' follow
libminifi/libminifi.a(ListenHTTP.cpp.o): In function 
`org::apache::nifi::minifi::processors::ListenHTTP::onSchedule(org::apache::nifi::minifi::core::ProcessContext*,
 org::apache::nifi::minifi::core::ProcessSessionFactory*)':
ListenHTTP.cpp:(.text+0x254a): undefined reference to 
`CivetServer::CivetServer(std::vector, CivetCallbacks const*)'
ListenHTTP.cpp:(.text+0x25cb): undefined reference to 
`CivetServer::addHandler(std::string const&, CivetHandler*)'
libminifi/libminifi.a(ListenHTTP.cpp.o): In function 
`org::apache::nifi::minifi::processors::ListenHTTP::Handler::sendErrorResponse(mg_connection*)':
ListenHTTP.cpp:(.text+0x76b): undefined reference to `mg_printf'

libminifi/libminifi.a(ListenHTTP.cpp.o):(.rodata._ZTIN3org6apache4nifi6minifi10processors10ListenHTTP7HandlerE[_ZTIN3org6apache4nifi6minifi10processors10ListenHTTP7HandlerE]+0x10):
 undefined reference to `typeinfo for CivetHandler'

libminifi/libminifi.a(ListenHTTP.cpp.o):(.rodata._ZTVN3org6apache4nifi6minifi10processors10ListenHTTP7HandlerE[_ZTVN3org6apache4nifi6minifi10processors10ListenHTTP7HandlerE]+0x20):
 undefined reference to `CivetHandler::handleGet(CivetServer*, mg_connection*)'

libminifi/libminifi.a(ListenHTTP.cpp.o):(.rodata._ZTVN3org6apache4nifi6minifi10processors10ListenHTTP7HandlerE[_ZTVN3org6apache4nifi6minifi10processors10ListenHTTP7HandlerE]+0x30):
 undefined reference to `CivetHandler::handleHead(CivetServer*, mg_connection*)'

libminifi/libminifi.a(ListenHTTP.cpp.o):(.rodata._ZTVN3org6apache4nifi6minifi10processors10ListenHTTP7HandlerE[_ZTVN3org6apache4nifi6minifi10processors10ListenHTTP7HandlerE]+0x38):
 undefined reference to `CivetHandler::handlePut(CivetServer*, mg_connection*)'

libminifi/libminifi.a(ListenHTTP.cpp.o):(.rodata._ZTVN3org6apache4nifi6minifi10processors10ListenHTTP7HandlerE[_ZTVN3org6apache4nifi6minifi10processors10ListenHTTP7HandlerE]+0x40):
 undefined reference to `CivetHandler::handleDelete(CivetServer*, 
mg_connection*)'

libminifi/libminifi.a(ListenHTTP.cpp.o):(.rodata._ZTVN3org6apache4nifi6minifi10processors10ListenHTTP7HandlerE[_ZTVN3org6apache4nifi6minifi10processors10ListenHTTP7HandlerE]+0x48):
 undefined reference to `CivetHandler::handleOptions(CivetServer*, 
mg_connection*)'

libminifi/libminifi.a(ListenHTTP.cpp.o):(.rodata._ZTVN3org6apache4nifi6minifi10processors10ListenHTTP7HandlerE[_ZTVN3org6apache4nifi6minifi10processors10ListenHTTP7HandlerE]+0x50):
 undefined reference to `CivetHandler::handlePatch(CivetServer*, 
mg_connection*)'
collect2: error: ld returned 1 exit status
make[2]: *** [TestExecuteProcess] Error 1
make[1]: *** [CMakeFiles/TestExecuteProcess.dir/all] Error 2
make: *** [all] Error 2
```


---

[jira] [Created] (MINIFICPP-324) Resolve RHEL7 build issues

[marco polo (JIRA)]

marco polo created MINIFICPP-324:


 Summary: Resolve RHEL7 build issues
 Key: MINIFICPP-324
 URL: https://issues.apache.org/jira/browse/MINIFICPP-324
 Project: NiFi MiNiFi C++
  Issue Type: Bug
Reporter: marco polo
Assignee: marco polo






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

[jira] [Commented] (NIFI-4632) Site-to-Site failing with default configuration

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4632:
--

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/2288
  
Thanks Mark. I’ll take a look and hopefully merge this in tonight. 


> Site-to-Site failing with default configuration
> ---
>
> Key: NIFI-4632
> URL: https://issues.apache.org/jira/browse/NIFI-4632
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.5.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.5.0
>
>
> With a new install, from 'master' branch I created an Input Port and then a 
> Remote Process Group pointing to localhost:8080/nifi. When attempting to send 
> data to my Input Port, nothing appears to happen in the UI. In the logs, I 
> see the following:
> {code}
> 2017-11-22 09:30:39,918 WARN [NiFi Web Server-184] 
> o.a.nifi.web.server.HostHeaderHandler Request host header 
> [.local:8080] different from web hostname [localhost(:8080)]. 
> Overriding to [localhost:8080/nifi-api/site-to-site/peers]
> 2017-11-22 09:30:39,918 WARN [Http Site-to-Site PeerSelector] 
> o.a.n.r.util.SiteToSiteRestApiClient Failed to parse Json. The specified URL 
> http://.local:8080/nifi-api is not a proper remote NiFi endpoint 
> for Site-to-Site communication. 
> requestedUrl=http://.local:8080/nifi-api/site-to-site/peers, 
> response=System Error
> The request contained an invalid host header [.local:8080] in 
> the request [/nifi-api/site-to-site/peers]. Check for request manipulation or 
> third-party intercept. 
> {code}
> I tried updating nifi.properties to set the "nifi.web.http.host" property to 
> .local and that did resolve the issue... but then I could not 
> connect to the UI using localhost:8080 but instead had to connect using 
> .local. 
> This appears to not affect any released versions of NiFi.



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

[jira] [Commented] (NIFI-3366) MoveHDFS Processor

[Jeff Storck (JIRA)]

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

Jeff Storck commented on NIFI-3366:
---

[~ggwizdz1] I'll go ahead and make the changes I mentioned in my previous 
comments, and post a PR that includes your patch after running some tests.

> MoveHDFS Processor
> --
>
> Key: NIFI-3366
> URL: https://issues.apache.org/jira/browse/NIFI-3366
> Project: Apache NiFi
>  Issue Type: New Feature
>Reporter: Joseph Niemiec
>Assignee: Gray Gwizdz
>Priority: Minor
> Attachments: 0001-MoveHDFS-Processor.patch, 
> 0001-NIFI-3366-MoveHDFS-processor-supports-expressions-la.patch
>
>
> Today the PutHDFS Processor merely places a file into HDFS from NiFi. There 
> are times when we may want to move Files/Directories around on HDFS as part 
> of a workflow.  This could be after the PutHDFS processor has placed the 
> file, or from some other trigger. 
> Initially we are targeting to take a flow file attribute of an absolute HDFS 
> path, and be able to move it to a target HDFS Path using the Filesystem 
> RENAME API. 



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

[GitHub] nifi issue #2288: NIFI-4632: Add the local hostname to the list of validated...

[alopresto]

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/2288
  
Thanks Mark. I’ll take a look and hopefully merge this in tonight. 


---

[jira] [Commented] (MINIFICPP-320) Break apart core minifi from libminifi

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFICPP-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267116#comment-16267116
 ] 

ASF GitHub Bot commented on MINIFICPP-320:
--

Github user asfgit closed the pull request at:

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


> Break apart core minifi from libminifi
> --
>
> Key: MINIFICPP-320
> URL: https://issues.apache.org/jira/browse/MINIFICPP-320
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Reporter: marco polo
>Assignee: marco polo
> Fix For: 0.4.0
>
>
> This will facilitate moving core processors to an extension



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

[GitHub] nifi-minifi-cpp pull request #206: MINIFICPP-320: Change Processors to be wi...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[jira] [Created] (MINIFICPP-323) Create templated ExtensionFactory that uses the template argument pack to auto determine the classes.

[marco polo (JIRA)]

marco polo created MINIFICPP-323:


 Summary: Create templated ExtensionFactory that uses the template 
argument pack to auto determine the classes.
 Key: MINIFICPP-323
 URL: https://issues.apache.org/jira/browse/MINIFICPP-323
 Project: NiFi MiNiFi C++
  Issue Type: Sub-task
Reporter: marco polo
Assignee: marco polo






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

[jira] [Created] (MINIFICPP-322) Improve extension development and the documentation therein.

[marco polo (JIRA)]

marco polo created MINIFICPP-322:


 Summary: Improve extension development and the documentation 
therein.
 Key: MINIFICPP-322
 URL: https://issues.apache.org/jira/browse/MINIFICPP-322
 Project: NiFi MiNiFi C++
  Issue Type: Epic
Reporter: marco polo
Assignee: marco polo






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

[GitHub] nifi issue #2297: #77864: Fixed error handling for the large file (OutOfMemo...

[joewitt]

Github user joewitt commented on the issue:

https://github.com/apache/nifi/pull/2297
  
can definitely appreciate the intent of this patch but I suspect we'll need 
to handle this differently.  Once an OOME has happened the JVM might still 
function well but things can be unpredictable/unreliable.  Rather than catching 
such a thing and warning the user we should instead prevent data of a certain 
size from being retrieved via this mechanism.




---

[jira] [Commented] (NIFI-4445) Unit Test Failure for Scripted Reporting Task

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-4445 on fast machines the engine ran for 0 millis so the test needs to 
allow this case

Signed-off-by: Matthew Burgess 

This closes #2296


> Unit Test Failure for Scripted Reporting Task
> -
>
> Key: NIFI-4445
> URL: https://issues.apache.org/jira/browse/NIFI-4445
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.4.0
> Environment: Apache Maven 3.5.0 
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
> Maven home: /data1/apache-maven-3.5.0
> Java version: 1.8.0_144, vendor: Oracle Corporation
> Java home: /usr/java/jdk1.8.0_144/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.12.14-300.fc26.x86_64", arch: "amd64", family: 
> "unix"
>Reporter: Joseph Witt
>Assignee: Joseph Witt
> Fix For: 1.5.0
>
>
> ---
>  T E S T S
> ---
> Running org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest
> Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.641 sec <<< 
> FAILURE! - in org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest
> testVMEventsGroovyScript(org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest)
>   Time elapsed: 0.024 sec  <<< FAILURE!
> java.lang.AssertionError: null
>   at org.junit.Assert.fail(Assert.java:86)
>   at org.junit.Assert.assertTrue(Assert.java:41)
>   at org.junit.Assert.assertTrue(Assert.java:52)
>   at org.junit.Assert$assertTrue$0.callStatic(Unknown Source)
>   at 
> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:56)
>   at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:194)
>   at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:206)
>   at 
> org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest.testVMEventsGroovyScript(ScriptedReportingTaskGroovyTest.groovy:195)
> Appears to be related to the JDK/JRE.  The same environment in terms of 
> kernel/maven/etc... just slightly older JDK/JRE works perfectly fine.
> Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 
> 2017-04-03T15:39:06-04:00)
> Maven home: /opt/apache-maven-3.5.0
> Java version: 1.8.0_141, vendor: Oracle Corporation
> Java home: /usr/java/jdk1.8.0_141/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.12.14-300.fc26.x86_64", arch: "amd64", family: 
> "unix"



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

[jira] [Updated] (NIFI-4445) Unit Test Failure for Scripted Reporting Task

[Matt Burgess (JIRA)]

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

Matt Burgess updated NIFI-4445:
---
Fix Version/s: 1.5.0

> Unit Test Failure for Scripted Reporting Task
> -
>
> Key: NIFI-4445
> URL: https://issues.apache.org/jira/browse/NIFI-4445
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.4.0
> Environment: Apache Maven 3.5.0 
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
> Maven home: /data1/apache-maven-3.5.0
> Java version: 1.8.0_144, vendor: Oracle Corporation
> Java home: /usr/java/jdk1.8.0_144/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.12.14-300.fc26.x86_64", arch: "amd64", family: 
> "unix"
>Reporter: Joseph Witt
>Assignee: Joseph Witt
> Fix For: 1.5.0
>
>
> ---
>  T E S T S
> ---
> Running org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest
> Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.641 sec <<< 
> FAILURE! - in org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest
> testVMEventsGroovyScript(org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest)
>   Time elapsed: 0.024 sec  <<< FAILURE!
> java.lang.AssertionError: null
>   at org.junit.Assert.fail(Assert.java:86)
>   at org.junit.Assert.assertTrue(Assert.java:41)
>   at org.junit.Assert.assertTrue(Assert.java:52)
>   at org.junit.Assert$assertTrue$0.callStatic(Unknown Source)
>   at 
> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:56)
>   at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:194)
>   at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:206)
>   at 
> org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest.testVMEventsGroovyScript(ScriptedReportingTaskGroovyTest.groovy:195)
> Appears to be related to the JDK/JRE.  The same environment in terms of 
> kernel/maven/etc... just slightly older JDK/JRE works perfectly fine.
> Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 
> 2017-04-03T15:39:06-04:00)
> Maven home: /opt/apache-maven-3.5.0
> Java version: 1.8.0_141, vendor: Oracle Corporation
> Java home: /usr/java/jdk1.8.0_141/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.12.14-300.fc26.x86_64", arch: "amd64", family: 
> "unix"



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

[GitHub] nifi pull request #2296: NIFI-4445 on fast machines the engine ran for 0 mil...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[jira] [Commented] (NIFI-4445) Unit Test Failure for Scripted Reporting Task

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4445:
--

Github user mattyb149 commented on the issue:

https://github.com/apache/nifi/pull/2296
  
+1 LGTM, merging to master


> Unit Test Failure for Scripted Reporting Task
> -
>
> Key: NIFI-4445
> URL: https://issues.apache.org/jira/browse/NIFI-4445
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.4.0
> Environment: Apache Maven 3.5.0 
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
> Maven home: /data1/apache-maven-3.5.0
> Java version: 1.8.0_144, vendor: Oracle Corporation
> Java home: /usr/java/jdk1.8.0_144/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.12.14-300.fc26.x86_64", arch: "amd64", family: 
> "unix"
>Reporter: Joseph Witt
>Assignee: Joseph Witt
>
> ---
>  T E S T S
> ---
> Running org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest
> Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.641 sec <<< 
> FAILURE! - in org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest
> testVMEventsGroovyScript(org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest)
>   Time elapsed: 0.024 sec  <<< FAILURE!
> java.lang.AssertionError: null
>   at org.junit.Assert.fail(Assert.java:86)
>   at org.junit.Assert.assertTrue(Assert.java:41)
>   at org.junit.Assert.assertTrue(Assert.java:52)
>   at org.junit.Assert$assertTrue$0.callStatic(Unknown Source)
>   at 
> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:56)
>   at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:194)
>   at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:206)
>   at 
> org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest.testVMEventsGroovyScript(ScriptedReportingTaskGroovyTest.groovy:195)
> Appears to be related to the JDK/JRE.  The same environment in terms of 
> kernel/maven/etc... just slightly older JDK/JRE works perfectly fine.
> Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 
> 2017-04-03T15:39:06-04:00)
> Maven home: /opt/apache-maven-3.5.0
> Java version: 1.8.0_141, vendor: Oracle Corporation
> Java home: /usr/java/jdk1.8.0_141/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.12.14-300.fc26.x86_64", arch: "amd64", family: 
> "unix"



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

[GitHub] nifi issue #2296: NIFI-4445 on fast machines the engine ran for 0 millis so ...

[mattyb149]

Github user mattyb149 commented on the issue:

https://github.com/apache/nifi/pull/2296
  
+1 LGTM, merging to master


---

[jira] [Updated] (NIFI-4445) Unit Test Failure for Scripted Reporting Task

[Matt Burgess (JIRA)]

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

Matt Burgess updated NIFI-4445:
---
Assignee: Joseph Witt  (was: Matt Burgess)
  Status: Patch Available  (was: In Progress)

> Unit Test Failure for Scripted Reporting Task
> -
>
> Key: NIFI-4445
> URL: https://issues.apache.org/jira/browse/NIFI-4445
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.4.0
> Environment: Apache Maven 3.5.0 
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
> Maven home: /data1/apache-maven-3.5.0
> Java version: 1.8.0_144, vendor: Oracle Corporation
> Java home: /usr/java/jdk1.8.0_144/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.12.14-300.fc26.x86_64", arch: "amd64", family: 
> "unix"
>Reporter: Joseph Witt
>Assignee: Joseph Witt
>
> ---
>  T E S T S
> ---
> Running org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest
> Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.641 sec <<< 
> FAILURE! - in org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest
> testVMEventsGroovyScript(org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest)
>   Time elapsed: 0.024 sec  <<< FAILURE!
> java.lang.AssertionError: null
>   at org.junit.Assert.fail(Assert.java:86)
>   at org.junit.Assert.assertTrue(Assert.java:41)
>   at org.junit.Assert.assertTrue(Assert.java:52)
>   at org.junit.Assert$assertTrue$0.callStatic(Unknown Source)
>   at 
> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:56)
>   at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:194)
>   at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:206)
>   at 
> org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest.testVMEventsGroovyScript(ScriptedReportingTaskGroovyTest.groovy:195)
> Appears to be related to the JDK/JRE.  The same environment in terms of 
> kernel/maven/etc... just slightly older JDK/JRE works perfectly fine.
> Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 
> 2017-04-03T15:39:06-04:00)
> Maven home: /opt/apache-maven-3.5.0
> Java version: 1.8.0_141, vendor: Oracle Corporation
> Java home: /usr/java/jdk1.8.0_141/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.12.14-300.fc26.x86_64", arch: "amd64", family: 
> "unix"



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

[jira] [Assigned] (NIFI-4445) Unit Test Failure for Scripted Reporting Task

[Matt Burgess (JIRA)]

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

Matt Burgess reassigned NIFI-4445:
--

Assignee: Matt Burgess  (was: Joseph Witt)

> Unit Test Failure for Scripted Reporting Task
> -
>
> Key: NIFI-4445
> URL: https://issues.apache.org/jira/browse/NIFI-4445
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.4.0
> Environment: Apache Maven 3.5.0 
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
> Maven home: /data1/apache-maven-3.5.0
> Java version: 1.8.0_144, vendor: Oracle Corporation
> Java home: /usr/java/jdk1.8.0_144/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.12.14-300.fc26.x86_64", arch: "amd64", family: 
> "unix"
>Reporter: Joseph Witt
>Assignee: Matt Burgess
>
> ---
>  T E S T S
> ---
> Running org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest
> Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.641 sec <<< 
> FAILURE! - in org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest
> testVMEventsGroovyScript(org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest)
>   Time elapsed: 0.024 sec  <<< FAILURE!
> java.lang.AssertionError: null
>   at org.junit.Assert.fail(Assert.java:86)
>   at org.junit.Assert.assertTrue(Assert.java:41)
>   at org.junit.Assert.assertTrue(Assert.java:52)
>   at org.junit.Assert$assertTrue$0.callStatic(Unknown Source)
>   at 
> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:56)
>   at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:194)
>   at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:206)
>   at 
> org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest.testVMEventsGroovyScript(ScriptedReportingTaskGroovyTest.groovy:195)
> Appears to be related to the JDK/JRE.  The same environment in terms of 
> kernel/maven/etc... just slightly older JDK/JRE works perfectly fine.
> Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 
> 2017-04-03T15:39:06-04:00)
> Maven home: /opt/apache-maven-3.5.0
> Java version: 1.8.0_141, vendor: Oracle Corporation
> Java home: /usr/java/jdk1.8.0_141/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.12.14-300.fc26.x86_64", arch: "amd64", family: 
> "unix"



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

[jira] [Assigned] (NIFI-4445) Unit Test Failure for Scripted Reporting Task

[Matt Burgess (JIRA)]

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

Matt Burgess reassigned NIFI-4445:
--

Assignee: Joseph Witt  (was: Matt Burgess)

> Unit Test Failure for Scripted Reporting Task
> -
>
> Key: NIFI-4445
> URL: https://issues.apache.org/jira/browse/NIFI-4445
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.4.0
> Environment: Apache Maven 3.5.0 
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
> Maven home: /data1/apache-maven-3.5.0
> Java version: 1.8.0_144, vendor: Oracle Corporation
> Java home: /usr/java/jdk1.8.0_144/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.12.14-300.fc26.x86_64", arch: "amd64", family: 
> "unix"
>Reporter: Joseph Witt
>Assignee: Joseph Witt
>
> ---
>  T E S T S
> ---
> Running org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest
> Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.641 sec <<< 
> FAILURE! - in org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest
> testVMEventsGroovyScript(org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest)
>   Time elapsed: 0.024 sec  <<< FAILURE!
> java.lang.AssertionError: null
>   at org.junit.Assert.fail(Assert.java:86)
>   at org.junit.Assert.assertTrue(Assert.java:41)
>   at org.junit.Assert.assertTrue(Assert.java:52)
>   at org.junit.Assert$assertTrue$0.callStatic(Unknown Source)
>   at 
> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:56)
>   at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:194)
>   at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:206)
>   at 
> org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest.testVMEventsGroovyScript(ScriptedReportingTaskGroovyTest.groovy:195)
> Appears to be related to the JDK/JRE.  The same environment in terms of 
> kernel/maven/etc... just slightly older JDK/JRE works perfectly fine.
> Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 
> 2017-04-03T15:39:06-04:00)
> Maven home: /opt/apache-maven-3.5.0
> Java version: 1.8.0_141, vendor: Oracle Corporation
> Java home: /usr/java/jdk1.8.0_141/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.12.14-300.fc26.x86_64", arch: "amd64", family: 
> "unix"



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

[jira] [Updated] (NIFI-4526) The REST API and NiFi UI should allow the target URL for a remote process group to be edited

[Matt Gilman (JIRA)]

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

Matt Gilman updated NIFI-4526:
--
Assignee: Matt Gilman  (was: Mark Payne)
  Status: In Progress  (was: Patch Available)

> The REST API and NiFi UI should allow the target URL for a remote process 
> group to be edited
> 
>
> Key: NIFI-4526
> URL: https://issues.apache.org/jira/browse/NIFI-4526
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework, Core UI, Flow Versioning
>Reporter: Joseph Witt
>Assignee: Matt Gilman
>Priority: Critical
> Fix For: 1.5.0
>
>
> Today remote process groups (RPG) once established cannot have the target URL 
> edited.  If a user wants to change the URL they have to add a new RPG for the 
> new target and change the relationships/connections to point to it.  Then 
> they can remove the old one.
> That process ensures that there is explicit (user provided mapping) to the 
> new ports available at the new target.  However, this is very limiting in 
> templates today and would be very limiting to the effectiveness of the 
> versioned flow registry and porting between environments.
> We could make the URL support expression language statements but at present 
> that would be the first non component property (like processor properties) 
> where EL is allowed and we need to have a more thoughtful and consistent 
> approach for that to include things like number of processor threads/etc.. A 
> cleaner and more consistent option is to do this like sensitive properties 
> are being handled in versioned flows which is they are not part of the 
> versioned flow definition but rather on import or when edited we allow the 
> user to set their environment/flow specific values all without making the 
> local flow version dirty in terms of versioned flow management.
> So, we should allow the user via the UI and obviously through REST API calls 
> to change the URL.  This would require stopping the RPG, changing the target 
> URL (resycing/establishing remote ports/auth/etc..), then starting it.  We 
> need to make sure this change does not necessitate a new version of the flow.



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

[jira] [Commented] (NIFI-4526) The REST API and NiFi UI should allow the target URL for a remote process group to be edited

[Matt Gilman (JIRA)]

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

Matt Gilman commented on NIFI-4526:
---

Keeping this JIRA open in order to implement the necessary front end changes. 
These changes will likely be included in the PR for NIFI-4436 since that is 
where the majority of this work it taking place.

> The REST API and NiFi UI should allow the target URL for a remote process 
> group to be edited
> 
>
> Key: NIFI-4526
> URL: https://issues.apache.org/jira/browse/NIFI-4526
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework, Core UI, Flow Versioning
>Reporter: Joseph Witt
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.5.0
>
>
> Today remote process groups (RPG) once established cannot have the target URL 
> edited.  If a user wants to change the URL they have to add a new RPG for the 
> new target and change the relationships/connections to point to it.  Then 
> they can remove the old one.
> That process ensures that there is explicit (user provided mapping) to the 
> new ports available at the new target.  However, this is very limiting in 
> templates today and would be very limiting to the effectiveness of the 
> versioned flow registry and porting between environments.
> We could make the URL support expression language statements but at present 
> that would be the first non component property (like processor properties) 
> where EL is allowed and we need to have a more thoughtful and consistent 
> approach for that to include things like number of processor threads/etc.. A 
> cleaner and more consistent option is to do this like sensitive properties 
> are being handled in versioned flows which is they are not part of the 
> versioned flow definition but rather on import or when edited we allow the 
> user to set their environment/flow specific values all without making the 
> local flow version dirty in terms of versioned flow management.
> So, we should allow the user via the UI and obviously through REST API calls 
> to change the URL.  This would require stopping the RPG, changing the target 
> URL (resycing/establishing remote ports/auth/etc..), then starting it.  We 
> need to make sure this change does not necessitate a new version of the flow.



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

[jira] [Commented] (NIFI-4526) The REST API and NiFi UI should allow the target URL for a remote process group to be edited

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4526:
--

Github user asfgit closed the pull request at:

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


> The REST API and NiFi UI should allow the target URL for a remote process 
> group to be edited
> 
>
> Key: NIFI-4526
> URL: https://issues.apache.org/jira/browse/NIFI-4526
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework, Core UI, Flow Versioning
>Reporter: Joseph Witt
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.5.0
>
>
> Today remote process groups (RPG) once established cannot have the target URL 
> edited.  If a user wants to change the URL they have to add a new RPG for the 
> new target and change the relationships/connections to point to it.  Then 
> they can remove the old one.
> That process ensures that there is explicit (user provided mapping) to the 
> new ports available at the new target.  However, this is very limiting in 
> templates today and would be very limiting to the effectiveness of the 
> versioned flow registry and porting between environments.
> We could make the URL support expression language statements but at present 
> that would be the first non component property (like processor properties) 
> where EL is allowed and we need to have a more thoughtful and consistent 
> approach for that to include things like number of processor threads/etc.. A 
> cleaner and more consistent option is to do this like sensitive properties 
> are being handled in versioned flows which is they are not part of the 
> versioned flow definition but rather on import or when edited we allow the 
> user to set their environment/flow specific values all without making the 
> local flow version dirty in terms of versioned flow management.
> So, we should allow the user via the UI and obviously through REST API calls 
> to change the URL.  This would require stopping the RPG, changing the target 
> URL (resycing/establishing remote ports/auth/etc..), then starting it.  We 
> need to make sure this change does not necessitate a new version of the flow.



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

[jira] [Commented] (NIFI-4526) The REST API and NiFi UI should allow the target URL for a remote process group to be edited

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-4526: Allow Target URI's of Remote Process Groups to be changed. This 
closes #2298


> The REST API and NiFi UI should allow the target URL for a remote process 
> group to be edited
> 
>
> Key: NIFI-4526
> URL: https://issues.apache.org/jira/browse/NIFI-4526
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework, Core UI, Flow Versioning
>Reporter: Joseph Witt
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.5.0
>
>
> Today remote process groups (RPG) once established cannot have the target URL 
> edited.  If a user wants to change the URL they have to add a new RPG for the 
> new target and change the relationships/connections to point to it.  Then 
> they can remove the old one.
> That process ensures that there is explicit (user provided mapping) to the 
> new ports available at the new target.  However, this is very limiting in 
> templates today and would be very limiting to the effectiveness of the 
> versioned flow registry and porting between environments.
> We could make the URL support expression language statements but at present 
> that would be the first non component property (like processor properties) 
> where EL is allowed and we need to have a more thoughtful and consistent 
> approach for that to include things like number of processor threads/etc.. A 
> cleaner and more consistent option is to do this like sensitive properties 
> are being handled in versioned flows which is they are not part of the 
> versioned flow definition but rather on import or when edited we allow the 
> user to set their environment/flow specific values all without making the 
> local flow version dirty in terms of versioned flow management.
> So, we should allow the user via the UI and obviously through REST API calls 
> to change the URL.  This would require stopping the RPG, changing the target 
> URL (resycing/establishing remote ports/auth/etc..), then starting it.  We 
> need to make sure this change does not necessitate a new version of the flow.



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

[jira] [Commented] (NIFI-4526) The REST API and NiFi UI should allow the target URL for a remote process group to be edited

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4526:
--

Github user mcgilman commented on the issue:

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


> The REST API and NiFi UI should allow the target URL for a remote process 
> group to be edited
> 
>
> Key: NIFI-4526
> URL: https://issues.apache.org/jira/browse/NIFI-4526
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework, Core UI, Flow Versioning
>Reporter: Joseph Witt
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.5.0
>
>
> Today remote process groups (RPG) once established cannot have the target URL 
> edited.  If a user wants to change the URL they have to add a new RPG for the 
> new target and change the relationships/connections to point to it.  Then 
> they can remove the old one.
> That process ensures that there is explicit (user provided mapping) to the 
> new ports available at the new target.  However, this is very limiting in 
> templates today and would be very limiting to the effectiveness of the 
> versioned flow registry and porting between environments.
> We could make the URL support expression language statements but at present 
> that would be the first non component property (like processor properties) 
> where EL is allowed and we need to have a more thoughtful and consistent 
> approach for that to include things like number of processor threads/etc.. A 
> cleaner and more consistent option is to do this like sensitive properties 
> are being handled in versioned flows which is they are not part of the 
> versioned flow definition but rather on import or when edited we allow the 
> user to set their environment/flow specific values all without making the 
> local flow version dirty in terms of versioned flow management.
> So, we should allow the user via the UI and obviously through REST API calls 
> to change the URL.  This would require stopping the RPG, changing the target 
> URL (resycing/establishing remote ports/auth/etc..), then starting it.  We 
> need to make sure this change does not necessitate a new version of the flow.



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

[GitHub] nifi issue #2298: NIFI-4526: Allow Target URI's of Remote Process Groups to ...

[mcgilman]

Github user mcgilman commented on the issue:

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


---

[GitHub] nifi pull request #2298: NIFI-4526: Allow Target URI's of Remote Process Gro...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[jira] [Commented] (MINIFICPP-319) Update LICENSE with dependency libs for leveldb.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFICPP-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16266930#comment-16266930
 ] 

ASF GitHub Bot commented on MINIFICPP-319:
--

Github user asfgit closed the pull request at:

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


> Update LICENSE with dependency libs for leveldb. 
> -
>
> Key: MINIFICPP-319
> URL: https://issues.apache.org/jira/browse/MINIFICPP-319
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Reporter: marco polo
>Assignee: marco polo
> Fix For: 0.3.0
>
>




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

[jira] [Resolved] (MINIFICPP-319) Update LICENSE with dependency libs for leveldb.

[Aldrin Piri (JIRA)]

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

Aldrin Piri resolved MINIFICPP-319.
---
Resolution: Fixed

> Update LICENSE with dependency libs for leveldb. 
> -
>
> Key: MINIFICPP-319
> URL: https://issues.apache.org/jira/browse/MINIFICPP-319
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Reporter: marco polo
>Assignee: marco polo
> Fix For: 0.3.0
>
>




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

[GitHub] nifi-minifi-cpp pull request #205: MINIFICPP-319: Resolve missing licenses

[asfgit]

Github user asfgit closed the pull request at:

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


---

[jira] [Commented] (MINIFICPP-319) Update LICENSE with dependency libs for leveldb.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFICPP-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16266929#comment-16266929
 ] 

ASF GitHub Bot commented on MINIFICPP-319:
--

Github user apiri commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/205
  
This looks to address the issues raised on the RC1 vote as well as covering 
some additional items included in our thirdparty deps.  Will merge this in.


> Update LICENSE with dependency libs for leveldb. 
> -
>
> Key: MINIFICPP-319
> URL: https://issues.apache.org/jira/browse/MINIFICPP-319
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Reporter: marco polo
>Assignee: marco polo
> Fix For: 0.3.0
>
>




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

[GitHub] nifi-minifi-cpp issue #205: MINIFICPP-319: Resolve missing licenses

[apiri]

Github user apiri commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/205
  
This looks to address the issues raised on the RC1 vote as well as covering 
some additional items included in our thirdparty deps.  Will merge this in.


---

[jira] [Updated] (NIFI-4622) Add TLS status tool to nifi-toolkit

[Bryan Bende (JIRA)]

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

Bryan Bende updated NIFI-4622:
--
   Resolution: Fixed
Fix Version/s: 1.5.0
   Status: Resolved  (was: Patch Available)

> Add TLS status tool to nifi-toolkit
> ---
>
> Key: NIFI-4622
> URL: https://issues.apache.org/jira/browse/NIFI-4622
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Bryan Bende
>Assignee: Bryan Bende
>Priority: Minor
> Fix For: 1.5.0
>
>
> Currently nifi-toolkit has a way to check the status of NiFi node through the 
> node-manager tool, but the node-manager tool is specific to NiFi because it 
> depends on NiFiProperties.
> We should add a generic status tool to the TLS tool that can take a URL and 
> keystore/truststore properties, and return the status code of making a 
> request to the given URL, or print an error.



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

[jira] [Commented] (MINIFICPP-319) Update LICENSE with dependency libs for leveldb.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFICPP-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16266903#comment-16266903
 ] 

ASF GitHub Bot commented on MINIFICPP-319:
--

Github user apiri commented on the issue:

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


> Update LICENSE with dependency libs for leveldb. 
> -
>
> Key: MINIFICPP-319
> URL: https://issues.apache.org/jira/browse/MINIFICPP-319
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Reporter: marco polo
>Assignee: marco polo
> Fix For: 0.3.0
>
>




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

[GitHub] nifi pull request #2280: NIFI-4622 Adding status tool to TLS toolkit

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] nifi-minifi-cpp issue #205: MINIFICPP-319: Resolve missing licenses

[apiri]

Github user apiri commented on the issue:

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


---

[jira] [Commented] (NIFI-4622) Add TLS status tool to nifi-toolkit

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4622:
--

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/2280
  
Thanks Kevin, going to merge


> Add TLS status tool to nifi-toolkit
> ---
>
> Key: NIFI-4622
> URL: https://issues.apache.org/jira/browse/NIFI-4622
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Bryan Bende
>Assignee: Bryan Bende
>Priority: Minor
>
> Currently nifi-toolkit has a way to check the status of NiFi node through the 
> node-manager tool, but the node-manager tool is specific to NiFi because it 
> depends on NiFiProperties.
> We should add a generic status tool to the TLS tool that can take a URL and 
> keystore/truststore properties, and return the status code of making a 
> request to the given URL, or print an error.



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

[GitHub] nifi pull request #2285: NIFI-4583 Restructure nifi-solr-processors

[bbende]

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

https://github.com/apache/nifi/pull/2285#discussion_r153216223
  
--- Diff: 
nifi-nar-bundles/nifi-solr-bundle/nifi-solr-processors/src/main/java/org/apache/nifi/processors/solr/SolrUtils.java
 ---
@@ -0,0 +1,202 @@
+/*
+ * 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.solr;
+
+import org.apache.commons.io.IOUtils;
+import org.apache.commons.lang3.StringUtils;
+import org.apache.http.client.HttpClient;
+import org.apache.http.conn.scheme.Scheme;
+import org.apache.http.conn.ssl.SSLSocketFactory;
+import org.apache.nifi.components.AllowableValue;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.context.PropertyContext;
+import org.apache.nifi.processor.io.OutputStreamCallback;
+import org.apache.nifi.serialization.record.ListRecordSet;
+import org.apache.nifi.serialization.record.MapRecord;
+import org.apache.nifi.serialization.record.Record;
+import org.apache.nifi.serialization.record.RecordField;
+import org.apache.nifi.serialization.record.RecordFieldType;
+import org.apache.nifi.serialization.record.RecordSchema;
+import org.apache.nifi.serialization.record.RecordSet;
+import org.apache.nifi.ssl.SSLContextService;
+import org.apache.solr.client.solrj.SolrClient;
+import org.apache.solr.client.solrj.impl.CloudSolrClient;
+import org.apache.solr.client.solrj.impl.HttpClientUtil;
+import org.apache.solr.client.solrj.impl.HttpSolrClient;
+import org.apache.solr.client.solrj.impl.Krb5HttpClientConfigurer;
+import org.apache.solr.client.solrj.response.QueryResponse;
+import org.apache.solr.client.solrj.util.ClientUtils;
+import org.apache.solr.common.SolrDocument;
+import org.apache.solr.common.SolrInputDocument;
+import org.apache.solr.common.params.ModifiableSolrParams;
+
+import javax.net.ssl.SSLContext;
+import java.io.IOException;
+import java.io.OutputStream;
+import java.nio.charset.StandardCharsets;
+import java.util.ArrayList;
+import java.util.LinkedHashMap;
+import java.util.List;
+import java.util.Map;
+import java.util.concurrent.TimeUnit;
+
+public class SolrUtils {
--- End diff --

Can we move all the static property descriptors to this class, and make 
SolrUtils consist of only static variables and methods? I think that would fit 
better with other existing patterns in already in the code-base.


---