date:20170130

[jira] (NIFI-3363) PutKafka throws NullPointerException when User-Defined partition strategy is used

2017-01-30 Thread ASF GitHub Bot (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ASF GitHub Bot commented on  NIFI-3363 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: PutKafka throws NullPointerException when User-Defined partition strategy is used  
 
 
 
 
 
 
 
 
 
 
Github user ijokarumawak closed the pull request at: 
 https://github.com/apache/nifi/pull/1426 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[GitHub] nifi pull request #1426: NIFI-3363: PutKafka NPE with User-Defined partition...

2017-01-30 Thread ijokarumawak

Github user ijokarumawak closed the pull request at:

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


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

[GitHub] nifi issue #1426: NIFI-3363: PutKafka NPE with User-Defined partition (0.x)

2017-01-30 Thread ijokarumawak

Github user ijokarumawak commented on the issue:

https://github.com/apache/nifi/pull/1426
  
Thanks @olegz !


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

[jira] (NIFI-3363) PutKafka throws NullPointerException when User-Defined partition strategy is used

2017-01-30 Thread ASF GitHub Bot (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ASF GitHub Bot commented on  NIFI-3363 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: PutKafka throws NullPointerException when User-Defined partition strategy is used  
 
 
 
 
 
 
 
 
 
 
Github user ijokarumawak commented on the issue: 
 https://github.com/apache/nifi/pull/1426 
 Thanks @olegz ! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (NIFI-3238) ListenLumberjack should support the *beat protocol

2017-01-30 Thread ASF GitHub Bot (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ASF GitHub Bot commented on  NIFI-3238 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: ListenLumberjack should support the *beat protocol  
 
 
 
 
 
 
 
 
 
 
Github user nickcarenza commented on the issue: 
 https://github.com/apache/nifi/pull/1418 
 I've been playing with this branch locally for a few days and I haven't experienced any issues yet. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[GitHub] nifi issue #1418: NIFI-3238 - Introduce ListenBeats processor and deprecates...

2017-01-30 Thread nickcarenza

Github user nickcarenza commented on the issue:

https://github.com/apache/nifi/pull/1418
  
I've been playing with this branch locally for a few days and I haven't 
experienced any issues yet.


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

[jira] (NIFI-3193) Update ConsumeAMQP and PublishAMQP to retrieve username from certificate common name

2017-01-30 Thread Oleg Zhurakousky (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Zhurakousky commented on  NIFI-3193 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Update ConsumeAMQP and PublishAMQP to retrieve username from certificate common name  
 
 
 
 
 
 
 
 
 
 
Brian thank you, I can work with that. Will let you know. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (NIFI-3193) Update ConsumeAMQP and PublishAMQP to retrieve username from certificate common name

2017-01-30 Thread Brian (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brian edited a comment on  NIFI-3193 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Update ConsumeAMQP and PublishAMQP to retrieve username from certificate common name  
 
 
 
 
 
 
 
 
 
 Oleg,I've just been trying to get a simple java application which connects to RabbitMQ using certificate CN names. I've attached the class to this ticket (it's not pretty but it does test the publish connection.    The key difference I found between the C# and java was that I had to set:  {noformat}    "factory.setSaslConfig(DefaultSaslConfig.EXTERNAL);" to get it to work as. {noformat}  The default is PLAIN so even if you provide certificates and set the SSLContext it won't be used in the rabbit connection until the SaslMechanism is set to EXTERNAL. Once I did this and added a Rabbitmq user matching the certificate CN name the publish worked fine.Just for completeness I've attached the latest rabbitmq.config file I used. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (NIFI-3193) Update ConsumeAMQP and PublishAMQP to retrieve username from certificate common name

2017-01-30 Thread Brian (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brian edited a comment on  NIFI-3193 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Update ConsumeAMQP and PublishAMQP to retrieve username from certificate common name  
 
 
 
 
 
 
 
 
 
 Sorry just realised I can't attach files to this ticket.Here is the rabbitmq.config:{noformat}[  {rabbit, [{tcp_listeners, []},{ssl_listeners, [5671]},{auth_mechanisms, ['EXTERNAL']},{ssl_options, [{cacertfile,"/cert/testca/cacert.pem"},{certfile,"/cert/server/cert.pem"},{keyfile,"/cert/server/key.pem"},{verify,verify_peer},{versions, ['tlsv1.2']},{password,  "MySecretPassword"},{verify,verify_peer},{ssl_cert_login_from, common_name},{fail_if_no_peer_cert,true}]}  ]}].{noformat}Here is the java class: {noformat} import com.rabbitmq.client.*;import java.io.*;import java.security.*;import javax.net.ssl.*;public class rabbitmq_test{  private final static String QUEUE_NAME = "hello";  public static void main(String[] argv) throws Exception {ConnectionFactory factory = new ConnectionFactory();char[] passphrase = "MySecretPassword".toCharArray();KeyStore ks = KeyStore.getInstance("PKCS12");ks.load(new FileInputStream("Z:\\rabbitmqcerts\\keycert.p12"), passphrase);KeyManagerFactory kmf = KeyManagerFactory.getInstance("SunX509");kmf.init(ks, passphrase);KeyStore tks = KeyStore.getInstance("JKS");tks.load(new FileInputStream("Z:\\rabbitmqcerts\\testca.jks"), passphrase);TrustManagerFactory tmf = TrustManagerFactory.getInstance("SunX509");tmf.init(tks);SSLContext context = SSLContext.getInstance("TLSv1.2");context.init(kmf.getKeyManagers(), tmf.getTrustManagers(), null);factory.useSslProtocol(context);// SET to external!!!factory.setSaslConfig(DefaultSaslConfig.EXTERNAL);factory.setVirtualHost("/");factory.setHost("rabbitmq_hostname");factory.setPort(5671);Connection connection = factory.newConnection();Channel channel = connection.createChannel();channel.queueDeclare(QUEUE_NAME, false, false, false, null);String message = "Hello World!";channel.basicPublish("", QUEUE_NAME, null, message.getBytes());System.out.println(" [x] Sent '" + message + "'");channel.close();connection.close();  }} {noformat} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (NIFI-3193) Update ConsumeAMQP and PublishAMQP to retrieve username from certificate common name

2017-01-30 Thread Brian (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brian edited a comment on  NIFI-3193 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Update ConsumeAMQP and PublishAMQP to retrieve username from certificate common name  
 
 
 
 
 
 
 
 
 
 Sorry just realised I can't attach files to this ticket.Here is the rabbitmq.config: {noformat} [  {rabbit, [{tcp_listeners, []},{ssl_listeners, [5671]},{auth_mechanisms, ['EXTERNAL']},{ssl_options, [{cacertfile,"/cert/testca/cacert.pem"},{certfile,"/cert/server/cert.pem"},{keyfile,"/cert/server/key.pem"},{verify,verify_peer},{versions, ['tlsv1.2']},{password,  "MySecretPassword"},{verify,verify_peer},{ssl_cert_login_from, common_name},{fail_if_no_peer_cert,true}]}  ]}]. {noformat}   Here is the java class:import com.rabbitmq.client.*;import java.io.*;import java.security.*;import javax.net.ssl.*;public class rabbitmq_test{  private final static String QUEUE_NAME = "hello";  public static void main(String[] argv) throws Exception {ConnectionFactory factory = new ConnectionFactory();char[] passphrase = "MySecretPassword".toCharArray();KeyStore ks = KeyStore.getInstance("PKCS12");ks.load(new FileInputStream("Z:\\rabbitmqcerts\\keycert.p12"), passphrase);KeyManagerFactory kmf = KeyManagerFactory.getInstance("SunX509");kmf.init(ks, passphrase);KeyStore tks = KeyStore.getInstance("JKS");tks.load(new FileInputStream("Z:\\rabbitmqcerts\\testca.jks"), passphrase);TrustManagerFactory tmf = TrustManagerFactory.getInstance("SunX509");tmf.init(tks);SSLContext context = SSLContext.getInstance("TLSv1.2");context.init(kmf.getKeyManagers(), tmf.getTrustManagers(), null);factory.useSslProtocol(context);// SET to external!!!factory.setSaslConfig(DefaultSaslConfig.EXTERNAL);factory.setVirtualHost("/");factory.setHost("rabbitmq_hostname");factory.setPort(5671);Connection connection = factory.newConnection();Channel channel = connection.createChannel();channel.queueDeclare(QUEUE_NAME, false, false, false, null);String message = "Hello World!";channel.basicPublish("", QUEUE_NAME, null, message.getBytes());System.out.println(" [x] Sent '" + message + "'");channel.close();connection.close();  }} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (NIFI-3193) Update ConsumeAMQP and PublishAMQP to retrieve username from certificate common name

2017-01-30 Thread Brian (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brian commented on  NIFI-3193 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Update ConsumeAMQP and PublishAMQP to retrieve username from certificate common name  
 
 
 
 
 
 
 
 
 
 
Oleg Zhurakousky was the above code snippet enough? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (NIFI-3193) Update ConsumeAMQP and PublishAMQP to retrieve username from certificate common name

2017-01-30 Thread Brian (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brian edited a comment on  NIFI-3193 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Update ConsumeAMQP and PublishAMQP to retrieve username from certificate common name  
 
 
 
 
 
 
 
 
 
 Sorry just realised I can't attach files to this ticket.Here is the rabbitmq.config:[  {rabbit, [ {tcp_listeners, []}, {ssl_listeners, [5671]}, {auth_mechanisms, ['EXTERNAL']}, {ssl_options, [{cacertfile,"/cert/testca/cacert.pem"},{certfile,"/cert/server/cert.pem"},{keyfile,"/cert/server/key.pem"},{verify,verify_peer}, {versions, ['tlsv1.2']},{password,  "MySecretPassword"}, {verify,verify_peer},{ssl_cert_login_from, common_name},{fail_if_no_peer_cert,true}]}   ]}].Here is the java class:import com.rabbitmq.client.*;import java.io.*;import java.security.*;import javax.net.ssl.*;public class rabbitmq_test{private final static String QUEUE_NAME = "hello";public static void main(String[] argv)  throws Exception {ConnectionFactory factory = new ConnectionFactory();char[] passphrase = "MySecretPassword".toCharArray();KeyStore ks = KeyStore.getInstance("PKCS12");ks.load(new FileInputStream("Z:\\rabbitmqcerts\\keycert.p12"), passphrase);KeyManagerFactory kmf = KeyManagerFactory.getInstance("SunX509");kmf.init(ks, passphrase);KeyStore tks = KeyStore.getInstance("JKS");tks.load(new FileInputStream("Z:\\rabbitmqcerts\\testca.jks"), passphrase);TrustManagerFactory tmf = TrustManagerFactory.getInstance("SunX509");tmf.init(tks);SSLContext context = SSLContext.getInstance("TLSv1.2");context.init(kmf.getKeyManagers(), tmf.getTrustManagers(), null);factory.useSslProtocol(context);// SET to external!!!factory.setSaslConfig(DefaultSaslConfig.EXTERNAL);factory.setVirtualHost("/");factory.setHost("rabbitmq_hostname");factory.setPort(5671);Connection connection = factory.newConnection();Channel channel = connection.createChannel();channel.queueDeclare(QUEUE_NAME, false, false, false, null);String message = "Hello World!";channel.basicPublish("", QUEUE_NAME, null, message.getBytes());System.out.println(" [x] Sent '" + message + "'");channel.close();connection.close();}  } 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (NIFI-3179) MergeContent extracts demarcator property value bytes without specifying charset encoding

2017-01-30 Thread ASF GitHub Bot (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ASF GitHub Bot commented on  NIFI-3179 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: MergeContent extracts demarcator property value bytes without specifying charset encoding  
 
 
 
 
 
 
 
 
 
 
Github user olegz commented on the issue: 
 https://github.com/apache/nifi/pull/1452 
 @pvillard31 should be all good now, sorry about that 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[GitHub] nifi issue #1452: NIFI-3179 Added support for default UTF-8 char encoding

2017-01-30 Thread olegz

Github user olegz commented on the issue:

https://github.com/apache/nifi/pull/1452
  
@pvillard31 should be all good now, sorry about that


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

[jira] (NIFI-3179) MergeContent extracts demarcator property value bytes without specifying charset encoding

2017-01-30 Thread ASF GitHub Bot (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ASF GitHub Bot commented on  NIFI-3179 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: MergeContent extracts demarcator property value bytes without specifying charset encoding  
 
 
 
 
 
 
 
 
 
 
Github user olegz commented on a diff in the pull request: 
 https://github.com/apache/nifi/pull/1452#discussion_r98547614 
 — Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/MergeContent.java — @@ -780,7 +781,7 @@ public void process(final InputStream rawIn) throws IOException { if (attributes.containsKey(CoreAttributes.MIME_TYPE.key()))  { attributes.put("content-type", attributes.get(CoreAttributes.MIME_TYPE.key())); } 
 - +StandCh — End diff – 
 Wow! Indeed strange 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[GitHub] nifi pull request #1452: NIFI-3179 Added support for default UTF-8 char enco...

2017-01-30 Thread olegz

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

https://github.com/apache/nifi/pull/1452#discussion_r98547614
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/MergeContent.java
 ---
@@ -780,7 +781,7 @@ public void process(final InputStream rawIn) throws 
IOException {
 if 
(attributes.containsKey(CoreAttributes.MIME_TYPE.key())) {
 attributes.put("content-type", 
attributes.get(CoreAttributes.MIME_TYPE.key()));
 }
-
+StandCh
--- End diff --

Wow! Indeed strange


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

[jira] (NIFI-3179) MergeContent extracts demarcator property value bytes without specifying charset encoding

2017-01-30 Thread ASF GitHub Bot (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ASF GitHub Bot commented on  NIFI-3179 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: MergeContent extracts demarcator property value bytes without specifying charset encoding  
 
 
 
 
 
 
 
 
 
 
Github user pvillard31 commented on a diff in the pull request: 
 https://github.com/apache/nifi/pull/1452#discussion_r98545128 
 — Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/MergeContent.java — @@ -780,7 +781,7 @@ public void process(final InputStream rawIn) throws IOException { if (attributes.containsKey(CoreAttributes.MIME_TYPE.key()))  { attributes.put("content-type", attributes.get(CoreAttributes.MIME_TYPE.key())); } 
 - +StandCh — End diff – 
 Hey @olegz, I think something went wrong here, it's not compiling  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[GitHub] nifi pull request #1452: NIFI-3179 Added support for default UTF-8 char enco...

2017-01-30 Thread pvillard31

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

https://github.com/apache/nifi/pull/1452#discussion_r98545128
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/MergeContent.java
 ---
@@ -780,7 +781,7 @@ public void process(final InputStream rawIn) throws 
IOException {
 if 
(attributes.containsKey(CoreAttributes.MIME_TYPE.key())) {
 attributes.put("content-type", 
attributes.get(CoreAttributes.MIME_TYPE.key()));
 }
-
+StandCh
--- End diff --

Hey @olegz, I think something went wrong here, it's not compiling ;)


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

[jira] (NIFI-3180) unable to import a flow template to NIFI 1.2 SNAPSHOT with "null" error

2017-01-30 Thread Pierre Villard (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pierre Villard updated  NIFI-3180 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Apache NiFi /  NIFI-3180 
 
 
 
  unable to import a flow template to NIFI 1.2 SNAPSHOT with "null" error  
 
 
 
 
 
 
 
 
 

Change By:
 
 Pierre Villard 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Patch Available Resolved 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (NIFI-3180) unable to import a flow template to NIFI 1.2 SNAPSHOT with "null" error

2017-01-30 Thread ASF GitHub Bot (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ASF GitHub Bot commented on  NIFI-3180 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: unable to import a flow template to NIFI 1.2 SNAPSHOT with "null" error  
 
 
 
 
 
 
 
 
 
 
Github user pvillard31 commented on the issue: 
 https://github.com/apache/nifi/pull/1451 
 LGTM, build with contrib-check OK, merged to master, thanks @olegz. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[GitHub] nifi issue #1451: NIFI-3180 Fixed NPE in TemplateUtils

2017-01-30 Thread pvillard31

Github user pvillard31 commented on the issue:

https://github.com/apache/nifi/pull/1451
  
LGTM, build with contrib-check OK, merged to master, thanks @olegz.


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

[jira] (NIFI-3180) unable to import a flow template to NIFI 1.2 SNAPSHOT with "null" error

2017-01-30 Thread ASF subversion and git services (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ASF subversion and git services commented on  NIFI-3180 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: unable to import a flow template to NIFI 1.2 SNAPSHOT with "null" error  
 
 
 
 
 
 
 
 
 
 
Commit 6518778c1158e52461d832ab18c44d1a5ed5cefb in nifi's branch refs/heads/master from Oleg Zhurakousky [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=6518778 ] 
NIFI-3180 Fixed NPE in TemplateUtils added null check for ProcessorDTO.getRelationship() removed deprecated usage of ByteArrayInputStream 
This closes #1451. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (NIFI-3180) unable to import a flow template to NIFI 1.2 SNAPSHOT with "null" error

2017-01-30 Thread ASF GitHub Bot (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ASF GitHub Bot commented on  NIFI-3180 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: unable to import a flow template to NIFI 1.2 SNAPSHOT with "null" error  
 
 
 
 
 
 
 
 
 
 
Github user asfgit closed the pull request at: 
 https://github.com/apache/nifi/pull/1451 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[GitHub] nifi pull request #1451: NIFI-3180 Fixed NPE in TemplateUtils

2017-01-30 Thread asfgit

Github user asfgit closed the pull request at:

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


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

[jira] (NIFI-3421) Start up failure - java.nio.channels.OverlappingFileLockException: null

2017-01-30 Thread Matt Gilman (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matt Gilman created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Apache NiFi /  NIFI-3421 
 
 
 
  Start up failure - java.nio.channels.OverlappingFileLockException: null  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Core Framework 
 
 
 

Created:
 

 30/Jan/17 21:15 
 
 
 

Fix Versions:
 

 1.2.0 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Matt Gilman 
 
 
 
 
 
 
 
 
 
 
If NiFi fails to start up successfully, the act of attempting to shut down appears to result in a duplicate FlowController instantiation. A symptom of this is initializing the flow file repo twice which fails with an overlapping file lock exception. 
The actual reason that start up failed is logged further back in the app log. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[jira] (NIFI-3161) nifi-mock pulls two different versions of ASM libraries

2017-01-30 Thread Pierre Villard (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pierre Villard updated  NIFI-3161 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Apache NiFi /  NIFI-3161 
 
 
 
  nifi-mock pulls two different versions of ASM libraries  
 
 
 
 
 
 
 
 
 

Change By:
 
 Pierre Villard 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Patch Available Resolved 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (NIFI-3161) nifi-mock pulls two different versions of ASM libraries

2017-01-30 Thread ASF GitHub Bot (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ASF GitHub Bot commented on  NIFI-3161 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: nifi-mock pulls two different versions of ASM libraries  
 
 
 
 
 
 
 
 
 
 
Github user pvillard31 commented on the issue: 
 https://github.com/apache/nifi/pull/1453 
 LGTM, fixed style (to avoid changes on all the file) and merged to master. Thanks @olegz. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (NIFI-3161) nifi-mock pulls two different versions of ASM libraries

2017-01-30 Thread ASF subversion and git services (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ASF subversion and git services commented on  NIFI-3161 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: nifi-mock pulls two different versions of ASM libraries  
 
 
 
 
 
 
 
 
 
 
Commit 910c1fa6f6bbf95c13ca646ee57be197f6ba9069 in nifi's branch refs/heads/master from Oleg Zhurakousky [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=910c1fa ] 
NIFI-3161 added ASM exclusion 
This closes #1453. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (NIFI-3161) nifi-mock pulls two different versions of ASM libraries

2017-01-30 Thread ASF GitHub Bot (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ASF GitHub Bot commented on  NIFI-3161 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: nifi-mock pulls two different versions of ASM libraries  
 
 
 
 
 
 
 
 
 
 
Github user asfgit closed the pull request at: 
 https://github.com/apache/nifi/pull/1453 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[GitHub] nifi issue #1453: NIFI-3161 added ASM exclusion

2017-01-30 Thread pvillard31

Github user pvillard31 commented on the issue:

https://github.com/apache/nifi/pull/1453
  
LGTM, fixed style (to avoid changes on all the file) and merged to master. 
Thanks @olegz.


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

[GitHub] nifi pull request #1453: NIFI-3161 added ASM exclusion

2017-01-30 Thread asfgit

Github user asfgit closed the pull request at:

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


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

[GitHub] nifi-minifi-cpp pull request #41: MINIFI-184: Add Security Support

2017-01-30 Thread apiri

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

https://github.com/apache/nifi-minifi-cpp/pull/41#discussion_r98259383
  
--- Diff: libminifi/src/Configure.cpp ---
@@ -29,6 +29,12 @@ const char *Configure::nifi_server_report_interval= 
"nifi.server.report.interval
 const char *Configure::nifi_provenance_repository_max_storage_size = 
"nifi.provenance.repository.max.storage.size";
 const char *Configure::nifi_provenance_repository_max_storage_time = 
"nifi.provenance.repository.max.storage.time";
 const char *Configure::nifi_provenance_repository_directory_default = 
"nifi.provenance.repository.directory.default";
+const char *Configure::nifi_remote_input_secure = 
"nifi.remote.input.secure";
+const char *Configure::nifi_security_need_ClientAuth = 
"nifi.security.need.ClientAuth";
--- End diff --

if we are matching nifi's, this should be nifi.security.needClientAuth


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

[GitHub] nifi-minifi-cpp pull request #41: MINIFI-184: Add Security Support

2017-01-30 Thread apiri

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

https://github.com/apache/nifi-minifi-cpp/pull/41#discussion_r98260259
  
--- Diff: README.md ---
@@ -243,6 +245,26 @@ Additionally, users can utilize the MiNiFi Toolkit 
Converter (version 0.0.1 - sc
 Port: 10001
 Host Name: localhost
 
+### Site2Site Security Configuration
+
+in minifi.properties 
+
+enable tls ssl
+nifi.remote.input.secure=true
+
+if you want to enable client certificate base authorization 
+nifi.security.need.ClientAuth=true
+setup the client certificate and private key PEM files
+nifi.security.client.certificate=./conf/client.pem
+nifi.security.client.private.key=./conf/client.pem
+setup the client private key passphase file
+nifi.security.client.pass.phase=./conf/password
--- End diff --

likely should just be passphrase


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

[GitHub] nifi-minifi-cpp pull request #41: MINIFI-184: Add Security Support

2017-01-30 Thread apiri

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

https://github.com/apache/nifi-minifi-cpp/pull/41#discussion_r98259083
  
--- Diff: cmake/FindOpenSSL.cmake ---
@@ -0,0 +1,28 @@
+#  OPENSSL_ROOT_DIR - Set this variable to the root installation of OpenSSL
--- End diff --

I believe this should be unneeded as cmake has a built in FindOpenSSL 
module.


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

[GitHub] nifi-minifi-cpp pull request #41: MINIFI-184: Add Security Support

2017-01-30 Thread apiri

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

https://github.com/apache/nifi-minifi-cpp/pull/41#discussion_r98476688
  
--- Diff: libminifi/src/Site2SitePeer.cpp ---
@@ -237,12 +271,31 @@ int Site2SitePeer::readData(uint8_t *buf, int buflen, 
CRC32 *crc)
Close();
return status;
}
-   status = recv(_socket, buf, buflen, 0);
-   if (status <= 0)
+   if (!_ssl)
{
-   Close();
-   // this->yield();
-   return status;
+   status = recv(_socket, buf, buflen, 0);
+   if (status <= 0)
+   {
+   Close();
+   // this->yield();
--- End diff --

should this be removed?


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

[GitHub] nifi-minifi-cpp pull request #41: MINIFI-184: Add Security Support

2017-01-30 Thread apiri

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

https://github.com/apache/nifi-minifi-cpp/pull/41#discussion_r98260232
  
--- Diff: libminifi/src/Configure.cpp ---
@@ -29,6 +29,12 @@ const char *Configure::nifi_server_report_interval= 
"nifi.server.report.interval
 const char *Configure::nifi_provenance_repository_max_storage_size = 
"nifi.provenance.repository.max.storage.size";
 const char *Configure::nifi_provenance_repository_max_storage_time = 
"nifi.provenance.repository.max.storage.time";
 const char *Configure::nifi_provenance_repository_directory_default = 
"nifi.provenance.repository.directory.default";
+const char *Configure::nifi_remote_input_secure = 
"nifi.remote.input.secure";
+const char *Configure::nifi_security_need_ClientAuth = 
"nifi.security.need.ClientAuth";
+const char *Configure::nifi_security_client_certificate = 
"nifi.security.client.certificate";
+const char *Configure::nifi_security_client_private_key = 
"nifi.security.client.private.key";
+const char *Configure::nifi_security_client_pass_phase = 
"nifi.security.client.pass.phase";
--- End diff --

likely should just be passphrase


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

[GitHub] nifi-minifi-cpp pull request #41: MINIFI-184: Add Security Support

2017-01-30 Thread apiri

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

https://github.com/apache/nifi-minifi-cpp/pull/41#discussion_r98517708
  
--- Diff: README.md ---
@@ -243,6 +245,26 @@ Additionally, users can utilize the MiNiFi Toolkit 
Converter (version 0.0.1 - sc
 Port: 10001
 Host Name: localhost
 
+### Site2Site Security Configuration
+
+in minifi.properties 
--- End diff --

We should stub these out as defaults in minifi.properties.  No values, but 
at least provide a quick way of having them be readily available.


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

[GitHub] nifi-minifi-cpp pull request #41: MINIFI-184: Add Security Support

2017-01-30 Thread apiri

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

https://github.com/apache/nifi-minifi-cpp/pull/41#discussion_r98259141
  
--- Diff: libminifi/src/Configure.cpp ---
@@ -29,6 +29,12 @@ const char *Configure::nifi_server_report_interval= 
"nifi.server.report.interval
 const char *Configure::nifi_provenance_repository_max_storage_size = 
"nifi.provenance.repository.max.storage.size";
 const char *Configure::nifi_provenance_repository_max_storage_time = 
"nifi.provenance.repository.max.storage.time";
 const char *Configure::nifi_provenance_repository_directory_default = 
"nifi.provenance.repository.directory.default";
+const char *Configure::nifi_remote_input_secure = 
"nifi.remote.input.secure";
+const char *Configure::nifi_security_need_ClientAuth = 
"nifi.security.need.ClientAuth";
+const char *Configure::nifi_security_client_certificate = 
"nifi.security.client.certificate";
+const char *Configure::nifi_security_client_private_key = 
"nifi.security.client.private.key";
+const char *Configure::nifi_security_client_pass_phase = 
"nifi.security.client.pass.phase";
+const char *Configure::nifi_security_client_ca_certificate = 
"nif.security.client.ca.certificate";
--- End diff --

typo for nifi


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

[GitHub] nifi-minifi-cpp pull request #41: MINIFI-184: Add Security Support

2017-01-30 Thread apiri

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

https://github.com/apache/nifi-minifi-cpp/pull/41#discussion_r98476667
  
--- Diff: libminifi/src/Site2SitePeer.cpp ---
@@ -237,12 +271,31 @@ int Site2SitePeer::readData(uint8_t *buf, int buflen, 
CRC32 *crc)
Close();
return status;
}
-   status = recv(_socket, buf, buflen, 0);
-   if (status <= 0)
+   if (!_ssl)
{
-   Close();
-   // this->yield();
-   return status;
+   status = recv(_socket, buf, buflen, 0);
+   if (status <= 0)
+   {
+   Close();
+   // this->yield();
+   return status;
+   }
+   }
+   else
+   {
+   // for SSL, wait for the TLS IO is completed
+   int sslStatus;
+   do {
+   status = SSL_read(_ssl, buf, buflen);
+   sslStatus = SSL_get_error(_ssl, status);
+   }
+   while (status < 0 && sslStatus == SSL_ERROR_WANT_READ);
+   if (status <= 0)
+   {
+   Close();
+   // this->yield();
--- End diff --

should this be removed?


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

[jira] (NIFI-3420) NIFI Should support generating Hadoop-readable Lz4 outside of HDFS Write

2017-01-30 Thread ASF GitHub Bot (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ASF GitHub Bot commented on  NIFI-3420 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: NIFI Should support generating Hadoop-readable Lz4 outside of HDFS Write  
 
 
 
 
 
 
 
 
 
 
GitHub user ilganeli opened a pull request: 
 https://github.com/apache/nifi/pull/1457 
 NIFI-3420 Add Hadoop-readable Lz4 compression  
 

This is an initial contribution of a fix for NIFI-3420
 

This code is not yet tested
 

Unit tests will be added soon.
 
 
 
 
 
 
 

For all changes:
 
 
 
 
 
 
 

[ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?
 
 
 

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

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

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

For code changes:

[jira] (NIFI-3158) ZooKeeper Migrator should be better about cleaning up resources and throw more specific exceptions

2017-01-30 Thread Jeff Storck (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jeff Storck updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Apache NiFi /  NIFI-3158 
 
 
 
  ZooKeeper Migrator should be better about cleaning up resources and throw more specific exceptions  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jeff Storck 
 
 
 

Fix Version/s:
 
 1.2.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[GitHub] nifi pull request #1457: NIFI-3420 Add Hadoop-readable Lz4 compression

2017-01-30 Thread ilganeli

GitHub user ilganeli opened a pull request:

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

NIFI-3420 Add Hadoop-readable Lz4 compression 

- This is an initial contribution of a fix for NIFI-3420
- This code is not yet tested
- Unit tests will be added soon. 

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

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

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

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

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

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

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


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

$ git pull https://github.com/ilganeli/nifi NIFI-3420

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

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


commit 906fdd280b305d18497eb8165ba39af1c4280e44
Author: Ilya Ganelin 
Date:   2017-01-30T19:20:55Z

Added Hadoop lz4 converter.

commit 9cbc45f3d7402ab0b876e6491c50cee3f1f3feac
Author: Ilya Ganelin 
Date:   2017-01-30T19:20:55Z

[NIFI-3420] Added code to create Hadoop readable lz4

commit fd387e9aa0ce619ade0cb37904141f49a255a093
Author: Ilya Ganelin 
Date:   2017-01-30T19:24:08Z

Merge branch 'NIFI-3420' of https://github.com/ilganeli/nifi into NIFI-3420




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

[jira] (NIFI-3420) NIFI Should support generating Hadoop-readable Lz4 outside of HDFS Write

2017-01-30 Thread Ilya Ganelin (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilya Ganelin created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Apache NiFi /  NIFI-3420 
 
 
 
  NIFI Should support generating Hadoop-readable Lz4 outside of HDFS Write  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 30/Jan/17 19:16 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Ilya Ganelin 
 
 
 
 
 
 
 
 
 
 
Per https://issues.apache.org/jira/browse/HADOOP-12990 data stored in Lz4 format on Hadoop is in a different format from the data generated by the Lz4 CLI. The Lz4 CLI can also not be used to generate the Hadoop-compatible format.  
At the moment, NiFi does not support compression to Lz4 for streaming data. 
Although PutHdfs in the Hadoop processors supports writing out Lz4 to HDFS (assuming the appropriate codec exists), if data is instead being saved to something like S3 or simply streamed, there's no way to generate Lz4 compressed data. 
If the Lz4 command line tool is used within a custom processor to perform Lz4 conversion, this data will then not be readable on Hadoop if it's subsequently loaded to HDFS. 
A processor can be added that performs the conversion streaming data into the Lz4 format that IS readable on Hadoop by using the Hadoop Lz4 Codec to do the compression.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[jira] (NIFI-3300) Zookeeper Migrator should allow importing of data to a new root node

2017-01-30 Thread ASF GitHub Bot (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ASF GitHub Bot commented on  NIFI-3300 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Zookeeper Migrator should allow importing of data to a new root node  
 
 
 
 
 
 
 
 
 
 
GitHub user jtstorck opened a pull request: 
 https://github.com/apache/nifi/pull/1456 
 NIFI-3300 Implemented usage of ZooKeeper chroot capability in the con… 
 …nect string 
 Updated ZooKeeper connect string parsing tests Updated admin doc for ZooKeeper Migrator migration of nifi root nodes, updated source and destination ZK check by servers in the connection string instead of the entire connection string 
 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:

[GitHub] nifi pull request #1456: NIFI-3300 Implemented usage of ZooKeeper chroot cap...

2017-01-30 Thread jtstorck

GitHub user jtstorck opened a pull request:

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

NIFI-3300 Implemented usage of ZooKeeper chroot capability in the conâ¦

â¦nect string

Updated ZooKeeper connect string parsing tests
Updated admin doc for ZooKeeper Migrator migration of nifi root nodes, 
updated source and destination ZK check by servers in the connection string 
instead of the entire connection string

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?
- [x] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
- [ ] If applicable, have you updated the LICENSE file, including the main 
LICENSE file under nifi-assembly?
- [ ] If applicable, have you updated the NOTICE file, including the main 
NOTICE file found under nifi-assembly?
- [ ] If adding new Properties, have you added .displayName in addition to 
.name (programmatic access) for each of the new properties?

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

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


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

$ git pull https://github.com/jtstorck/nifi NIFI-3300

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

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


commit 015836adc53fe532c3ede3dda122624a6d7c4980
Author: Jeff Storck 
Date:   2017-01-26T19:30:32Z

NIFI-3300 Implemented usage of ZooKeeper chroot capability in the connect 
string
Updated ZooKeeper connect string parsing tests
Updated admin doc for ZooKeeper Migrator migration of nifi root nodes, 
updated source and destination ZK check by servers in the connection string 
instead of the entire connection string




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

[GitHub] nifi pull request #1455: NIFI-3418 Add records-per-transaction property to p...

2017-01-30 Thread asfgit

Github user asfgit closed the pull request at:

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


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

[jira] (NIFI-3418) putHiveStreaming using "Transactions per Batch" property for records per transaction

2017-01-30 Thread ASF subversion and git services (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ASF subversion and git services commented on  NIFI-3418 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: putHiveStreaming using "Transactions per Batch" property for records per transaction  
 
 
 
 
 
 
 
 
 
 
Commit d5b139ffd4fea53bc004e86087beba4c204eed70 in nifi's branch refs/heads/master from Ben Schofield [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=d5b139f ] 


NIFI-3418
 Add records-per-transaction property to putHiveStreaming processor 
Signed-off-by: Matt Burgess  
This closes #1455 
Minor whitespace Checkstyle issue fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (NIFI-3418) putHiveStreaming using "Transactions per Batch" property for records per transaction

2017-01-30 Thread Matt Burgess (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matt Burgess updated  NIFI-3418 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Apache NiFi /  NIFI-3418 
 
 
 
  putHiveStreaming using "Transactions per Batch" property for records per transaction  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matt Burgess 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Patch Available Resolved 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[GitHub] nifi issue #1455: NIFI-3418 Add records-per-transaction property to putHiveS...

2017-01-30 Thread mattyb149

Github user mattyb149 commented on the issue:

https://github.com/apache/nifi/pull/1455
  
+1 LGTM, ran full Maven build (with CheckStyle, made a minor edit) and 
tested on a running NiFi instance connected to a HDP Sandbox.  Thank you for 
your contribution! Merging to master


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

[jira] (NIFI-3418) putHiveStreaming using "Transactions per Batch" property for records per transaction

2017-01-30 Thread ASF GitHub Bot (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ASF GitHub Bot commented on  NIFI-3418 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: putHiveStreaming using "Transactions per Batch" property for records per transaction  
 
 
 
 
 
 
 
 
 
 
Github user mattyb149 commented on the issue: 
 https://github.com/apache/nifi/pull/1455 
 +1 LGTM, ran full Maven build (with CheckStyle, made a minor edit) and tested on a running NiFi instance connected to a HDP Sandbox. Thank you for your contribution! Merging to master 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[GitHub] nifi pull request #1455: NIFI-3418 Add records-per-transaction property to p...

2017-01-30 Thread mattyb149

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

https://github.com/apache/nifi/pull/1455#discussion_r98484332
  
--- Diff: 
nifi-nar-bundles/nifi-hive-bundle/nifi-hive-processors/src/main/java/org/apache/nifi/processors/hive/PutHiveStreaming.java
 ---
@@ -218,6 +218,16 @@
 .addValidator(GREATER_THAN_ONE_VALIDATOR)
 .defaultValue("100")
 .build();
+
--- End diff --

This line is "empty" but has whitespace in it, causing a CheckStyle 
violation. I will fix while merging, so no worries.  In the future you can 
detect such things by adding -Pcontrib-check to your Maven command.


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

[jira] (NIFI-3418) putHiveStreaming using "Transactions per Batch" property for records per transaction

2017-01-30 Thread ASF GitHub Bot (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ASF GitHub Bot commented on  NIFI-3418 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: putHiveStreaming using "Transactions per Batch" property for records per transaction  
 
 
 
 
 
 
 
 
 
 
Github user mattyb149 commented on a diff in the pull request: 
 https://github.com/apache/nifi/pull/1455#discussion_r98484332 
 — Diff: nifi-nar-bundles/nifi-hive-bundle/nifi-hive-processors/src/main/java/org/apache/nifi/processors/hive/PutHiveStreaming.java — @@ -218,6 +218,16 @@ .addValidator(GREATER_THAN_ONE_VALIDATOR) .defaultValue("100") .build(); +  — End diff – 
 This line is "empty" but has whitespace in it, causing a CheckStyle violation. I will fix while merging, so no worries. In the future you can detect such things by adding -Pcontrib-check to your Maven command. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (NIFI-3419) MergeContent should route to failure on ZipException

2017-01-30 Thread Joseph Gresock (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joseph Gresock commented on  NIFI-3419 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: MergeContent should route to failure on ZipException  
 
 
 
 
 
 
 
 
 
 
I applied the attached patch to rel/nifi-1.1.1, rebuilt and deployed. This resolves the issue by routing flow files that cause a ZipException to the failure relationship. All other flow files are successfully merged into the zip. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (NIFI-3418) putHiveStreaming using "Transactions per Batch" property for records per transaction

2017-01-30 Thread Matt Burgess (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matt Burgess updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Apache NiFi /  NIFI-3418 
 
 
 
  putHiveStreaming using "Transactions per Batch" property for records per transaction  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matt Burgess 
 
 
 

Fix Version/s:
 
 1.2.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (NIFI-3418) putHiveStreaming using "Transactions per Batch" property for records per transaction

2017-01-30 Thread Matt Burgess (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matt Burgess updated  NIFI-3418 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Apache NiFi /  NIFI-3418 
 
 
 
  putHiveStreaming using "Transactions per Batch" property for records per transaction  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matt Burgess 
 
 
 

Affects Version/s:
 
 1.2.0 
 
 
 

Status:
 
 Open Patch Available 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (NIFI-3418) putHiveStreaming using "Transactions per Batch" property for records per transaction

2017-01-30 Thread ASF GitHub Bot (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ASF GitHub Bot commented on  NIFI-3418 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: putHiveStreaming using "Transactions per Batch" property for records per transaction  
 
 
 
 
 
 
 
 
 
 
Github user mattyb149 commented on the issue: 
 https://github.com/apache/nifi/pull/1455 
 Reviewing... 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[GitHub] nifi issue #1455: NIFI-3418 Add records-per-transaction property to putHiveS...

2017-01-30 Thread mattyb149

Github user mattyb149 commented on the issue:

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


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

[jira] (NIFI-3290) Reporting task to send bulletins over S2S

2017-01-30 Thread ASF GitHub Bot (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ASF GitHub Bot commented on  NIFI-3290 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Reporting task to send bulletins over S2S  
 
 
 
 
 
 
 
 
 
 
Github user asfgit closed the pull request at: 
 https://github.com/apache/nifi/pull/1401 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[GitHub] nifi pull request #1401: NIFI-3290 Reporting task to send bulletins with S2S

2017-01-30 Thread asfgit

Github user asfgit closed the pull request at:

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


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

[jira] (NIFI-3290) Reporting task to send bulletins over S2S

2017-01-30 Thread Oleg Zhurakousky (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Zhurakousky updated  NIFI-3290 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Apache NiFi /  NIFI-3290 
 
 
 
  Reporting task to send bulletins over S2S  
 
 
 
 
 
 
 
 
 

Change By:
 
 Oleg Zhurakousky 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Patch Available Resolved 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (NIFI-3290) Reporting task to send bulletins over S2S

2017-01-30 Thread ASF subversion and git services (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ASF subversion and git services commented on  NIFI-3290 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Reporting task to send bulletins over S2S  
 
 
 
 
 
 
 
 
 
 
Commit 78a0e1e18b9d40a10bac4612a9a0ebdc4b7d13bb in nifi's branch refs/heads/master from Pierre Villard [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=78a0e1e ] 


NIFI-3290
 Reporting task to send bulletins with S2S 
This closes #1401 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (NIFI-3290) Reporting task to send bulletins over S2S

2017-01-30 Thread Oleg Zhurakousky (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Zhurakousky updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Apache NiFi /  NIFI-3290 
 
 
 
  Reporting task to send bulletins over S2S  
 
 
 
 
 
 
 
 
 

Change By:
 
 Oleg Zhurakousky 
 
 
 

Fix Version/s:
 
 1.2.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (NIFI-3418) putHiveStreaming using "Transactions per Batch" property for records per transaction

2017-01-30 Thread ASF GitHub Bot (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ASF GitHub Bot commented on  NIFI-3418 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: putHiveStreaming using "Transactions per Batch" property for records per transaction  
 
 
 
 
 
 
 
 
 
 
GitHub user dbschofield opened a pull request: 
 https://github.com/apache/nifi/pull/1455 
 NIFI-3418 Add records-per-transaction property to putHiveStreaming pr… 
You can merge this pull request into a Git repository by running: 
 $ git pull https://github.com/dbschofield/nifi NIFI-3418 
Alternatively you can review and apply these changes as the patch at: 
 https://github.com/apache/nifi/pull/1455.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 #1455 
 
commit 440e33d35e03780112dd9ac3d45e9af8b4244c54 Author: Ben Schofield  Date: 2017-01-30T10:44:19Z 
 NIFI-3418 Add records-per-transaction property to putHiveStreaming processor 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[GitHub] nifi pull request #1455: NIFI-3418 Add records-per-transaction property to p...

2017-01-30 Thread dbschofield

GitHub user dbschofield opened a pull request:

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

NIFI-3418 Add records-per-transaction property to putHiveStreaming prâ¦




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

$ git pull https://github.com/dbschofield/nifi NIFI-3418

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

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


commit 440e33d35e03780112dd9ac3d45e9af8b4244c54
Author: Ben Schofield 
Date:   2017-01-30T10:44:19Z

NIFI-3418 Add records-per-transaction property to putHiveStreaming processor




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

[jira] (NIFI-957) Ability to provide default schedules per type

2017-01-30 Thread Oleg Zhurakousky (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Zhurakousky updated  NIFI-957 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Apache NiFi /  NIFI-957 
 
 
 
  Ability to provide default schedules per type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Oleg Zhurakousky 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Patch Available Resolved 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (NIFI-957) Ability to provide default schedules per type

2017-01-30 Thread ASF GitHub Bot (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ASF GitHub Bot commented on  NIFI-957 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Ability to provide default schedules per type  
 
 
 
 
 
 
 
 
 
 
Github user asfgit closed the pull request at: 
 https://github.com/apache/nifi/pull/1400 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (NIFI-957) Ability to provide default schedules per type

2017-01-30 Thread ASF subversion and git services (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ASF subversion and git services commented on  NIFI-957 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Ability to provide default schedules per type  
 
 
 
 
 
 
 
 
 
 
Commit 89f1bd3189970f9930bfdd4861fc2043dfd30c90 in nifi's branch refs/heads/master from Pierre Villard [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=89f1bd3 ] 
NIFI-957 Added the possibility to use DefaultSchedule annotation in reporting tasks 
This closes #1400 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (NIFI-957) Ability to provide default schedules per type

2017-01-30 Thread Oleg Zhurakousky (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Zhurakousky updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Apache NiFi /  NIFI-957 
 
 
 
  Ability to provide default schedules per type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Oleg Zhurakousky 
 
 
 

Fix Version/s:
 
 1.2.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[GitHub] nifi pull request #1400: NIFI-957 Added the possibility to use DefaultSchedu...

2017-01-30 Thread asfgit

Github user asfgit closed the pull request at:

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


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

[jira] (NIFI-3419) MergeContent should route to failure on ZipException

2017-01-30 Thread Joseph Gresock (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joseph Gresock updated  NIFI-3419 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Apache NiFi /  NIFI-3419 
 
 
 
  MergeContent should route to failure on ZipException  
 
 
 
 
 
 
 
 
 

Change By:
 
 Joseph Gresock 
 
 
 

Assignee:
 
 Joseph Gresock 
 
 
 

Status:
 
 Open Patch Available 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[GitHub] nifi pull request #1454: NIFI-3419: Routing flow files causing ZipException ...

2017-01-30 Thread gresockj

GitHub user gresockj opened a pull request:

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

NIFI-3419: Routing flow files causing ZipException to failure in 
MergeContent

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?
- [ ] 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/gresockj/nifi NIFI-3419

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

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


commit 95c5cbe9c85d4f5d49d8ca99b459d4c8b3ba8208
Author: Joe Gresock 
Date:   2017-01-30T12:19:32Z

NIFI-3419: Routing flow files causing ZipException to failure in 
MergeContent




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

[jira] (NIFI-3419) MergeContent should route to failure on ZipException

2017-01-30 Thread ASF GitHub Bot (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ASF GitHub Bot commented on  NIFI-3419 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: MergeContent should route to failure on ZipException  
 
 
 
 
 
 
 
 
 
 
GitHub user gresockj opened a pull request: 
 https://github.com/apache/nifi/pull/1454 
 NIFI-3419: Routing flow files causing ZipException to failure in MergeContent 
 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?

[jira] (NIFI-3419) MergeContent should route to failure on ZipException

2017-01-30 Thread Joseph Gresock (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joseph Gresock updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Apache NiFi /  NIFI-3419 
 
 
 
  MergeContent should route to failure on ZipException  
 
 
 
 
 
 
 
 
 

Change By:
 
 Joseph Gresock 
 
 
 
 
 
 
 
 
 
 In cases like duplicate entries using the Zip format in MergeContent, the processor should route to failure instead of leaving the exception uncaught, which causes flow files to administratively yield and never be processed.2017-01-30 11:11:39,106 ERROR [Timer-Driven Process Thread-142] o.a.n.processors.standard.MergeContentorg.apache.nifi.processor.exception.ProcessException: IOException thrown from MergeContent[id=a9476272-dab0-3d2f-acef-abf11f7d1b80]: java.util.zip.ZipException: duplicate entry: c8e206d2c658b14c386b8c8ffc8d3db88c082874.jsonat org.apache.nifi.controller.repository.StandardProcessSession.write(StandardProcessSession.java:2348) ~[na:na]at org.apache.nifi.processors.standard.MergeContent$ZipMerge.merge(MergeContent.java:826) ~[nifi-standard-processors-1.1.1.jar:1.1.1]at org.apache.nifi.processors.standard.MergeContent.processBin(MergeContent.java:459) ~[nifi-standard-processors-1.1.1.jar:1.1.1]at org.apache.nifi.processor.util.bin.BinFiles.processBins(BinFiles.java:231) [nifi-processor-utils-1.1.1.jar:1.1.1]at org.apache.nifi.processor.util.bin.BinFiles.onTrigger(BinFiles.java:191) [nifi-processor-utils-1.1.1.jar:1.1.1] Caused by: java.util.zip.ZipException: duplicate entry: c8e206d2c658b14c386b8c8ffc8d3db88c082874.jsonat java.util.zip.ZipOutputStream.putNextEntry(ZipOutputStream.java:232) ~[na:1.8.0_111]at org.apache.nifi.processors.standard.MergeContent$ZipMerge$1.process(MergeContent.java:837) ~[nifi-standard-processors-1.1.1.jar:1.1.1]at org.apache.nifi.controller.repository.StandardProcessSession.write(StandardProcessSession.java:2329) ~[na:na] 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (NIFI-3419) MergeContent should route to failure on ZipException

2017-01-30 Thread Joseph Gresock (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joseph Gresock created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Apache NiFi /  NIFI-3419 
 
 
 
  MergeContent should route to failure on ZipException  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 1.1.1 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Core Framework 
 
 
 

Created:
 

 30/Jan/17 11:19 
 
 
 

Fix Versions:
 

 1.2.0 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Joseph Gresock 
 
 
 
 
 
 
 
 
 
 
In cases like duplicate entries using the Zip format in MergeContent, the processor should route to failure instead of leaving the exception uncaught, which causes flow files to administratively yield and never be processed. 
2017-01-30 11:11:39,106 ERROR [Timer-Driven Process Thread-142] o.a.n.processors.standard.MergeContent org.apache.nifi.processor.exception.ProcessException: IOException thrown from MergeContent[id=a9476272-dab0-3d2f-acef-abf11f7d1b80]: java.util.zip.ZipException: duplicate entry: c8e206d2c658b14c386b8c8ffc8d3db88c082874.json at org.apache.nifi.controller.repository.StandardProcessSession.write(StandardProcessSession.java:2348) ~[na:na] at

74 matches

Mail list logo