[jira] [Resolved] (NIFI-2470) WritesAttributes annotations in ListFile are incorrect

[Joseph Witt (JIRA)]

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

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

> WritesAttributes annotations in ListFile are incorrect
> --
>
> Key: NIFI-2470
> URL: https://issues.apache.org/jira/browse/NIFI-2470
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 0.7.0
>Reporter: Kirk Tarou
>Assignee: Joseph Witt
>Priority: Minor
>  Labels: beginner, beginners, documentation, easyfix
> Fix For: 1.0.0
>
> Attachments: ListFileAttributes.png, ListFileUsage.png
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> The WritesAttributes annotations section has a variety of problems that need 
> to be cleaned up. Otherwise, 'Usage' documentation will be incorrect.
> # Some of the WritesAttributes annotations don't match the actual attribute 
> names:
> #* fs.owner -> file.owner
> #* fs.group -> file.group
> #* fs.lastModified -> file.lastModifiedTime
> #* fs.length -> file.length
> #* fs.permissions -> file.permissions
> # missing:
> #* file.creationTime
> #* file.lastAccessTime
> # Incorrect description
> #* file.lastModifiedTime is a formatted date/time



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

[jira] [Commented] (NIFI-2470) WritesAttributes annotations in ListFile are incorrect

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2470:
---

+1 merged to master.

> WritesAttributes annotations in ListFile are incorrect
> --
>
> Key: NIFI-2470
> URL: https://issues.apache.org/jira/browse/NIFI-2470
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 0.7.0
>Reporter: Kirk Tarou
>Assignee: Joseph Witt
>Priority: Minor
>  Labels: beginner, beginners, documentation, easyfix
> Fix For: 1.0.0
>
> Attachments: ListFileAttributes.png, ListFileUsage.png
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> The WritesAttributes annotations section has a variety of problems that need 
> to be cleaned up. Otherwise, 'Usage' documentation will be incorrect.
> # Some of the WritesAttributes annotations don't match the actual attribute 
> names:
> #* fs.owner -> file.owner
> #* fs.group -> file.group
> #* fs.lastModified -> file.lastModifiedTime
> #* fs.length -> file.length
> #* fs.permissions -> file.permissions
> # missing:
> #* file.creationTime
> #* file.lastAccessTime
> # Incorrect description
> #* file.lastModifiedTime is a formatted date/time



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

[jira] [Assigned] (NIFI-2470) WritesAttributes annotations in ListFile are incorrect

[Joseph Witt (JIRA)]

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

Joseph Witt reassigned NIFI-2470:
-

Assignee: Joseph Witt

> WritesAttributes annotations in ListFile are incorrect
> --
>
> Key: NIFI-2470
> URL: https://issues.apache.org/jira/browse/NIFI-2470
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 0.7.0
>Reporter: Kirk Tarou
>Assignee: Joseph Witt
>Priority: Minor
>  Labels: beginner, beginners, documentation, easyfix
> Fix For: 1.0.0
>
> Attachments: ListFileAttributes.png, ListFileUsage.png
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> The WritesAttributes annotations section has a variety of problems that need 
> to be cleaned up. Otherwise, 'Usage' documentation will be incorrect.
> # Some of the WritesAttributes annotations don't match the actual attribute 
> names:
> #* fs.owner -> file.owner
> #* fs.group -> file.group
> #* fs.lastModified -> file.lastModifiedTime
> #* fs.length -> file.length
> #* fs.permissions -> file.permissions
> # missing:
> #* file.creationTime
> #* file.lastAccessTime
> # Incorrect description
> #* file.lastModifiedTime is a formatted date/time



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

[GitHub] nifi pull request #802: NIFI-2470 - Fix WritesAttributes section of ListFile...

[asfgit]

Github user asfgit closed the pull request at:

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


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

[jira] [Commented] (NIFI-2470) WritesAttributes annotations in ListFile are incorrect

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2470:
--

Github user asfgit closed the pull request at:

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


> WritesAttributes annotations in ListFile are incorrect
> --
>
> Key: NIFI-2470
> URL: https://issues.apache.org/jira/browse/NIFI-2470
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 0.7.0
>Reporter: Kirk Tarou
>Priority: Minor
>  Labels: beginner, beginners, documentation, easyfix
> Fix For: 1.0.0
>
> Attachments: ListFileAttributes.png, ListFileUsage.png
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> The WritesAttributes annotations section has a variety of problems that need 
> to be cleaned up. Otherwise, 'Usage' documentation will be incorrect.
> # Some of the WritesAttributes annotations don't match the actual attribute 
> names:
> #* fs.owner -> file.owner
> #* fs.group -> file.group
> #* fs.lastModified -> file.lastModifiedTime
> #* fs.length -> file.length
> #* fs.permissions -> file.permissions
> # missing:
> #* file.creationTime
> #* file.lastAccessTime
> # Incorrect description
> #* file.lastModifiedTime is a formatted date/time



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

[jira] [Commented] (NIFI-2509) KafkaConsumer results in NPE if check.connection property is not provided

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2509:
---

+1 merged to both 0.x and master.

> KafkaConsumer results in NPE if check.connection property is not provided
> -
>
> Key: NIFI-2509
> URL: https://issues.apache.org/jira/browse/NIFI-2509
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0-Beta
>Reporter: Arpit Gupta
>Assignee: Oleg Zhurakousky
> Fix For: 1.0.0, 0.8.0
>
>
> If the user does not provide check connection property consume kafka returns 
> a NPE
> {code}
> java.lang.NullPointerException: null
> at 
> org.apache.nifi.processors.kafka.pubsub.ConsumeKafka.buildKafkaResource(ConsumeKafka.java:241)
>  
> {code}



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

[jira] [Updated] (NIFI-2509) KafkaConsumer results in NPE if check.connection property is not provided

[Joseph Witt (JIRA)]

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

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

> KafkaConsumer results in NPE if check.connection property is not provided
> -
>
> Key: NIFI-2509
> URL: https://issues.apache.org/jira/browse/NIFI-2509
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0-Beta
>Reporter: Arpit Gupta
>Assignee: Oleg Zhurakousky
> Fix For: 1.0.0, 0.8.0
>
>
> If the user does not provide check connection property consume kafka returns 
> a NPE
> {code}
> java.lang.NullPointerException: null
> at 
> org.apache.nifi.processors.kafka.pubsub.ConsumeKafka.buildKafkaResource(ConsumeKafka.java:241)
>  
> {code}



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

[jira] [Commented] (NIFI-2509) KafkaConsumer results in NPE if check.connection property is not provided

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2509:
--

Github user asfgit closed the pull request at:

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


> KafkaConsumer results in NPE if check.connection property is not provided
> -
>
> Key: NIFI-2509
> URL: https://issues.apache.org/jira/browse/NIFI-2509
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0-Beta
>Reporter: Arpit Gupta
>Assignee: Oleg Zhurakousky
> Fix For: 1.0.0, 0.8.0
>
>
> If the user does not provide check connection property consume kafka returns 
> a NPE
> {code}
> java.lang.NullPointerException: null
> at 
> org.apache.nifi.processors.kafka.pubsub.ConsumeKafka.buildKafkaResource(ConsumeKafka.java:241)
>  
> {code}



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

[jira] [Commented] (NIFI-2509) KafkaConsumer results in NPE if check.connection property is not provided

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2509 This closes #805. fixed NPE condition in KafkaConsumer


> KafkaConsumer results in NPE if check.connection property is not provided
> -
>
> Key: NIFI-2509
> URL: https://issues.apache.org/jira/browse/NIFI-2509
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0-Beta
>Reporter: Arpit Gupta
>Assignee: Oleg Zhurakousky
> Fix For: 1.0.0, 0.8.0
>
>
> If the user does not provide check connection property consume kafka returns 
> a NPE
> {code}
> java.lang.NullPointerException: null
> at 
> org.apache.nifi.processors.kafka.pubsub.ConsumeKafka.buildKafkaResource(ConsumeKafka.java:241)
>  
> {code}



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

[GitHub] nifi pull request #805: NIFI-2509 fixed NPE condition in KafkaConsumer

[asfgit]

Github user asfgit closed the pull request at:

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


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

[jira] [Commented] (NIFI-2508) Revert to using getKeyStorePassword() for key-password in AbstractKafkaProcessor

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2508:
---

+1 merged to 0.x

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



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

[jira] [Commented] (NIFI-2509) KafkaConsumer results in NPE if check.connection property is not provided

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2509 This closes #805. fixed NPE condition in KafkaConsumer


> KafkaConsumer results in NPE if check.connection property is not provided
> -
>
> Key: NIFI-2509
> URL: https://issues.apache.org/jira/browse/NIFI-2509
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0-Beta
>Reporter: Arpit Gupta
>Assignee: Oleg Zhurakousky
> Fix For: 1.0.0, 0.8.0
>
>
> If the user does not provide check connection property consume kafka returns 
> a NPE
> {code}
> java.lang.NullPointerException: null
> at 
> org.apache.nifi.processors.kafka.pubsub.ConsumeKafka.buildKafkaResource(ConsumeKafka.java:241)
>  
> {code}



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

[jira] [Updated] (NIFI-2508) Revert to using getKeyStorePassword() for key-password in AbstractKafkaProcessor

[Joseph Witt (JIRA)]

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

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

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



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

[jira] [Commented] (NIFI-2508) Revert to using getKeyStorePassword() for key-password in AbstractKafkaProcessor

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2508 This closes #804. fixed compilation errors in AbstractKafkaProcessor


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



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

[GitHub] nifi pull request #806: Extend REST API docs template to handle read only pr...

[jskora]

GitHub user jskora opened a pull request:

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

Extend REST API docs template to handle read only properties.

* Add read only property handling to type.hbs template.
* Add flag to ProcessorDTO.getRelationships to reflect read only nature of 
the property.
* Remove explicit "read only" message from 
ConnectionDTO.getAvailableRelationships to avoid duplicate text.

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

$ git pull https://github.com/jskora/nifi NIFI-2237

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

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


commit a74080987f4da517a0d00bcb0e6997248ae94c24
Author: Joe Skora 
Date:   2016-08-08T02:13:13Z

Extend template handling to read only properties.
* Add read only property handling to type.hbs template.
* Add flag to ProcessorDTO.getRelationships to reflect read only nature of 
the property.
* Remove explicit "read only" message from 
ConnectionDTO.getAvailableRelationships to avoid duplicate text.




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

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

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1965:
--

Github user pvillard31 commented on the issue:

https://github.com/apache/nifi/pull/496
  
@trixpan 
You've given the same .name() to multiple properties, this has to be 
unique. The consequence is that properties are not longer displayed in the UI. 
Besides, there is a checkstyle violation in the build (-Pcontrib-check). I'll 
have another look when it is OK.


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



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

[GitHub] nifi issue #496: NIFI-1965 - Implement QueryDNS Processor

[pvillard31]

Github user pvillard31 commented on the issue:

https://github.com/apache/nifi/pull/496
  
@trixpan 
You've given the same .name() to multiple properties, this has to be 
unique. The consequence is that properties are not longer displayed in the UI. 
Besides, there is a checkstyle violation in the build (-Pcontrib-check). I'll 
have another look when it is OK.


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

[jira] [Commented] (NIFI-2509) KafkaConsumer results in NPE if check.connection property is not provided

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2509:
--

GitHub user olegz opened a pull request:

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

NIFI-2509 fixed NPE condition in KafkaConsumer



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

$ git pull https://github.com/olegz/nifi NIFI-2509

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

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


commit 5e946bfefb92c3804dc5118d3bb2668d4141cfbf
Author: Oleg Zhurakousky 
Date:   2016-08-07T17:36:34Z

NIFI-2509 fixed NPE condition in KafkaConsumer




> KafkaConsumer results in NPE if check.connection property is not provided
> -
>
> Key: NIFI-2509
> URL: https://issues.apache.org/jira/browse/NIFI-2509
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0-Beta
>Reporter: Arpit Gupta
>Assignee: Oleg Zhurakousky
> Fix For: 1.0.0, 0.8.0
>
>
> If the user does not provide check connection property consume kafka returns 
> a NPE
> {code}
> java.lang.NullPointerException: null
> at 
> org.apache.nifi.processors.kafka.pubsub.ConsumeKafka.buildKafkaResource(ConsumeKafka.java:241)
>  
> {code}



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

[jira] [Updated] (NIFI-2509) KafkaConsumer results in NPE if check.connection property is not provided

[Oleg Zhurakousky (JIRA)]

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

Oleg Zhurakousky updated NIFI-2509:
---
Status: Patch Available  (was: Open)

> KafkaConsumer results in NPE if check.connection property is not provided
> -
>
> Key: NIFI-2509
> URL: https://issues.apache.org/jira/browse/NIFI-2509
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0-Beta
>Reporter: Arpit Gupta
>Assignee: Oleg Zhurakousky
> Fix For: 1.0.0, 0.8.0
>
>
> If the user does not provide check connection property consume kafka returns 
> a NPE
> {code}
> java.lang.NullPointerException: null
> at 
> org.apache.nifi.processors.kafka.pubsub.ConsumeKafka.buildKafkaResource(ConsumeKafka.java:241)
>  
> {code}



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

[jira] [Commented] (NIFI-2509) KafkaConsumer results in NPE if check.connection property is not provided

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2509:
--

Github user olegz commented on the issue:

https://github.com/apache/nifi/pull/805
  
NOTE: This PR must be applied to both master and 0.x branch. I've verified 
that it is cherry-pickable.


> KafkaConsumer results in NPE if check.connection property is not provided
> -
>
> Key: NIFI-2509
> URL: https://issues.apache.org/jira/browse/NIFI-2509
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0-Beta
>Reporter: Arpit Gupta
>Assignee: Oleg Zhurakousky
> Fix For: 1.0.0, 0.8.0
>
>
> If the user does not provide check connection property consume kafka returns 
> a NPE
> {code}
> java.lang.NullPointerException: null
> at 
> org.apache.nifi.processors.kafka.pubsub.ConsumeKafka.buildKafkaResource(ConsumeKafka.java:241)
>  
> {code}



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

[GitHub] nifi issue #805: NIFI-2509 fixed NPE condition in KafkaConsumer

[olegz]

Github user olegz commented on the issue:

https://github.com/apache/nifi/pull/805
  
NOTE: This PR must be applied to both master and 0.x branch. I've verified 
that it is cherry-pickable.


---
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 #805: NIFI-2509 fixed NPE condition in KafkaConsumer

[olegz]

GitHub user olegz opened a pull request:

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

NIFI-2509 fixed NPE condition in KafkaConsumer



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

$ git pull https://github.com/olegz/nifi NIFI-2509

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

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


commit 5e946bfefb92c3804dc5118d3bb2668d4141cfbf
Author: Oleg Zhurakousky 
Date:   2016-08-07T17:36:34Z

NIFI-2509 fixed NPE condition in KafkaConsumer




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

[jira] [Updated] (NIFI-2509) KafkaConsumer results in NPE if check.connection property is not provided

[Oleg Zhurakousky (JIRA)]

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

Oleg Zhurakousky updated NIFI-2509:
---
Fix Version/s: 0.8.0
   1.0.0

> KafkaConsumer results in NPE if check.connection property is not provided
> -
>
> Key: NIFI-2509
> URL: https://issues.apache.org/jira/browse/NIFI-2509
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0-Beta
>Reporter: Arpit Gupta
> Fix For: 1.0.0, 0.8.0
>
>
> If the user does not provide check connection property consume kafka returns 
> a NPE
> {code}
> java.lang.NullPointerException: null
> at 
> org.apache.nifi.processors.kafka.pubsub.ConsumeKafka.buildKafkaResource(ConsumeKafka.java:241)
>  
> {code}



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

[jira] [Updated] (NIFI-2509) KafkaConsumer results in NPE if check.connection property is not provided

[Oleg Zhurakousky (JIRA)]

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

Oleg Zhurakousky updated NIFI-2509:
---
Affects Version/s: (was: 0.8.0)

> KafkaConsumer results in NPE if check.connection property is not provided
> -
>
> Key: NIFI-2509
> URL: https://issues.apache.org/jira/browse/NIFI-2509
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0-Beta
>Reporter: Arpit Gupta
>Assignee: Oleg Zhurakousky
> Fix For: 1.0.0, 0.8.0
>
>
> If the user does not provide check connection property consume kafka returns 
> a NPE
> {code}
> java.lang.NullPointerException: null
> at 
> org.apache.nifi.processors.kafka.pubsub.ConsumeKafka.buildKafkaResource(ConsumeKafka.java:241)
>  
> {code}



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

[jira] [Assigned] (NIFI-2509) KafkaConsumer results in NPE if check.connection property is not provided

[Oleg Zhurakousky (JIRA)]

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

Oleg Zhurakousky reassigned NIFI-2509:
--

Assignee: Oleg Zhurakousky

> KafkaConsumer results in NPE if check.connection property is not provided
> -
>
> Key: NIFI-2509
> URL: https://issues.apache.org/jira/browse/NIFI-2509
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0-Beta
>Reporter: Arpit Gupta
>Assignee: Oleg Zhurakousky
> Fix For: 1.0.0, 0.8.0
>
>
> If the user does not provide check connection property consume kafka returns 
> a NPE
> {code}
> java.lang.NullPointerException: null
> at 
> org.apache.nifi.processors.kafka.pubsub.ConsumeKafka.buildKafkaResource(ConsumeKafka.java:241)
>  
> {code}



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

[jira] [Created] (NIFI-2509) KafkaConsumer results in NPE if check.connection property is not provided

[Arpit Gupta (JIRA)]

Arpit Gupta created NIFI-2509:
-

 Summary: KafkaConsumer results in NPE if check.connection property 
is not provided
 Key: NIFI-2509
 URL: https://issues.apache.org/jira/browse/NIFI-2509
 Project: Apache NiFi
  Issue Type: Bug
  Components: Extensions
Affects Versions: 0.8.0, 1.0.0-Beta
Reporter: Arpit Gupta


If the user does not provide check connection property consume kafka returns a 
NPE

{code}
java.lang.NullPointerException: null
at 
org.apache.nifi.processors.kafka.pubsub.ConsumeKafka.buildKafkaResource(ConsumeKafka.java:241)
 
{code}



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

[jira] [Commented] (NIFI-1148) Add processor to GetEmail supporting IMAP and POP3

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1148:
--

Github user olegz commented on the issue:

https://github.com/apache/nifi/pull/710
  
@mattyb149 your comments are addressed in the last commit. Thanks for 
reviewing 


> Add processor to GetEmail supporting IMAP and POP3
> --
>
> Key: NIFI-1148
> URL: https://issues.apache.org/jira/browse/NIFI-1148
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Joseph Witt
>Assignee: Oleg Zhurakousky
> Fix For: 1.0.0
>
>
> It is fairly common that users want to be able to acquire data via email.  
> This means both IMAP and POP3.  POP3 is easier as it is a sort of fire/forget 
> model whereas IMAP involves more state handling.  But in any event both modes 
> are important to support.



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

[GitHub] nifi issue #710: NIFI-1148 added IMAP/POP3 support

[olegz]

Github user olegz commented on the issue:

https://github.com/apache/nifi/pull/710
  
@mattyb149 your comments are addressed in the last commit. Thanks for 
reviewing 


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

[jira] [Commented] (NIFI-1148) Add processor to GetEmail supporting IMAP and POP3

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1148:
--

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

https://github.com/apache/nifi/pull/710#discussion_r73805537
  
--- Diff: 
nifi-nar-bundles/nifi-email-bundle/nifi-email-processors/src/main/resources/docs/org.apache.nifi.processors.email.ConsumeIMAP/additionalDetails.html
 ---
@@ -0,0 +1,60 @@
+
+
+
+
+
+ConsumeIMAP
+
+
+
+
+   
+   Description:
+   This Processors consumes email messages via IMAP protocol and
+   sends the content of an email message as content of the 
FlowFile.
+   Content of the incoming email message is written as raw bytes 
to the
+   content of the outgoing Flow File.
+
+
+   Since different serves may require different Java Mail
+   properties such properties could be provided via dynamic 
properties.
+   For example, below is a sample configuration for GMail:
+   
+   
+   Processor's static properties:
+   
+   Host Name - imap.gmail.com
+   Port - 993
+   User Name - [your user name]
+   Password - [your password]
+   Folder - INBOX
+   
+   Processor's dynamic properties:
+   
+   mail.imap.socketFactory.class - 
javax.net.ssl.SSLSocketFactory
+   mail.imap.socketFactory.fallback - false
+   mail.store.protocol - imaps
--- End diff --

Additionally as you have learned there is some provider work that needs to 
happen as well. For example with GMail you first have to enable IMAP and POP3 
in your settings and then set additional security preferences to enable it.
Basically my point is that for these processors to work most of the 
information should be supplied by the email server administrator.


> Add processor to GetEmail supporting IMAP and POP3
> --
>
> Key: NIFI-1148
> URL: https://issues.apache.org/jira/browse/NIFI-1148
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Joseph Witt
>Assignee: Oleg Zhurakousky
> Fix For: 1.0.0
>
>
> It is fairly common that users want to be able to acquire data via email.  
> This means both IMAP and POP3.  POP3 is easier as it is a sort of fire/forget 
> model whereas IMAP involves more state handling.  But in any event both modes 
> are important to support.



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

[GitHub] nifi pull request #710: NIFI-1148 added IMAP/POP3 support

[olegz]

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

https://github.com/apache/nifi/pull/710#discussion_r73805537
  
--- Diff: 
nifi-nar-bundles/nifi-email-bundle/nifi-email-processors/src/main/resources/docs/org.apache.nifi.processors.email.ConsumeIMAP/additionalDetails.html
 ---
@@ -0,0 +1,60 @@
+
+
+
+
+
+ConsumeIMAP
+
+
+
+
+   
+   Description:
+   This Processors consumes email messages via IMAP protocol and
+   sends the content of an email message as content of the 
FlowFile.
+   Content of the incoming email message is written as raw bytes 
to the
+   content of the outgoing Flow File.
+
+
+   Since different serves may require different Java Mail
+   properties such properties could be provided via dynamic 
properties.
+   For example, below is a sample configuration for GMail:
+   
+   
+   Processor's static properties:
+   
+   Host Name - imap.gmail.com
+   Port - 993
+   User Name - [your user name]
+   Password - [your password]
+   Folder - INBOX
+   
+   Processor's dynamic properties:
+   
+   mail.imap.socketFactory.class - 
javax.net.ssl.SSLSocketFactory
+   mail.imap.socketFactory.fallback - false
+   mail.store.protocol - imaps
--- End diff --

Additionally as you have learned there is some provider work that needs to 
happen as well. For example with GMail you first have to enable IMAP and POP3 
in your settings and then set additional security preferences to enable it.
Basically my point is that for these processors to work most of the 
information should be supplied by the email server administrator.


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

[jira] [Commented] (NIFI-1148) Add processor to GetEmail supporting IMAP and POP3

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1148:
--

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

https://github.com/apache/nifi/pull/710#discussion_r73805385
  
--- Diff: 
nifi-nar-bundles/nifi-email-bundle/nifi-email-processors/src/main/resources/docs/org.apache.nifi.processors.email.ConsumeIMAP/additionalDetails.html
 ---
@@ -0,0 +1,60 @@
+
+
+
+
+
+ConsumeIMAP
+
+
+
+
+   
+   Description:
+   This Processors consumes email messages via IMAP protocol and
+   sends the content of an email message as content of the 
FlowFile.
+   Content of the incoming email message is written as raw bytes 
to the
+   content of the outgoing Flow File.
+
+
+   Since different serves may require different Java Mail
+   properties such properties could be provided via dynamic 
properties.
+   For example, below is a sample configuration for GMail:
+   
+   
+   Processor's static properties:
+   
+   Host Name - imap.gmail.com
+   Port - 993
+   User Name - [your user name]
+   Password - [your password]
+   Folder - INBOX
+   
+   Processor's dynamic properties:
+   
+   mail.imap.socketFactory.class - 
javax.net.ssl.SSLSocketFactory
+   mail.imap.socketFactory.fallback - false
+   mail.store.protocol - imaps
--- End diff --

Unfortunately we can't do that, for reasons that there are no sensible 
defaults for protocols, only for providers. So if we ever get to something like 
ConsumeGmailViaIMAP, then we could eliminate most of not all dynamic 
properties, but unless we get into provider specific processors we have to stay 
pure to protocols and APIs.


> Add processor to GetEmail supporting IMAP and POP3
> --
>
> Key: NIFI-1148
> URL: https://issues.apache.org/jira/browse/NIFI-1148
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Joseph Witt
>Assignee: Oleg Zhurakousky
> Fix For: 1.0.0
>
>
> It is fairly common that users want to be able to acquire data via email.  
> This means both IMAP and POP3.  POP3 is easier as it is a sort of fire/forget 
> model whereas IMAP involves more state handling.  But in any event both modes 
> are important to support.



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

[GitHub] nifi pull request #710: NIFI-1148 added IMAP/POP3 support

[olegz]

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

https://github.com/apache/nifi/pull/710#discussion_r73805385
  
--- Diff: 
nifi-nar-bundles/nifi-email-bundle/nifi-email-processors/src/main/resources/docs/org.apache.nifi.processors.email.ConsumeIMAP/additionalDetails.html
 ---
@@ -0,0 +1,60 @@
+
+
+
+
+
+ConsumeIMAP
+
+
+
+
+   
+   Description:
+   This Processors consumes email messages via IMAP protocol and
+   sends the content of an email message as content of the 
FlowFile.
+   Content of the incoming email message is written as raw bytes 
to the
+   content of the outgoing Flow File.
+
+
+   Since different serves may require different Java Mail
+   properties such properties could be provided via dynamic 
properties.
+   For example, below is a sample configuration for GMail:
+   
+   
+   Processor's static properties:
+   
+   Host Name - imap.gmail.com
+   Port - 993
+   User Name - [your user name]
+   Password - [your password]
+   Folder - INBOX
+   
+   Processor's dynamic properties:
+   
+   mail.imap.socketFactory.class - 
javax.net.ssl.SSLSocketFactory
+   mail.imap.socketFactory.fallback - false
+   mail.store.protocol - imaps
--- End diff --

Unfortunately we can't do that, for reasons that there are no sensible 
defaults for protocols, only for providers. So if we ever get to something like 
ConsumeGmailViaIMAP, then we could eliminate most of not all dynamic 
properties, but unless we get into provider specific processors we have to stay 
pure to protocols and APIs.


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

[jira] [Updated] (NIFI-2508) Revert to using getKeyStorePassword() for key-password in AbstractKafkaProcessor

[Oleg Zhurakousky (JIRA)]

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

Oleg Zhurakousky updated NIFI-2508:
---
Status: Patch Available  (was: Open)

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



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

[jira] [Commented] (NIFI-2508) Revert to using getKeyStorePassword() for key-password in AbstractKafkaProcessor

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2508:
--

GitHub user olegz opened a pull request:

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

NIFI-2508 fixed compilation errors in AbstractKafkaProcessor

NOTE: This is for 0.x only

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

$ git pull https://github.com/olegz/nifi NIFI-2508

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

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


commit 16f5faf7e7cafafef8bed875d97884ea33d4e678
Author: Oleg Zhurakousky 
Date:   2016-08-07T15:45:20Z

NIFI-2508 fixed compilation errors in AbstractKafkaProcessor




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



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

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

[olegz]

GitHub user olegz opened a pull request:

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

NIFI-2508 fixed compilation errors in AbstractKafkaProcessor

NOTE: This is for 0.x only

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

$ git pull https://github.com/olegz/nifi NIFI-2508

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

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


commit 16f5faf7e7cafafef8bed875d97884ea33d4e678
Author: Oleg Zhurakousky 
Date:   2016-08-07T15:45:20Z

NIFI-2508 fixed compilation errors in AbstractKafkaProcessor




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

[jira] [Created] (NIFI-2508) Revert to using getKeyStorePassword() for key-password in AbstractKafkaProcessor

[Oleg Zhurakousky (JIRA)]

Oleg Zhurakousky created NIFI-2508:
--

 Summary: Revert to using getKeyStorePassword() for key-password in 
AbstractKafkaProcessor
 Key: NIFI-2508
 URL: https://issues.apache.org/jira/browse/NIFI-2508
 Project: Apache NiFi
  Issue Type: Bug
Reporter: Oleg Zhurakousky
Assignee: Oleg Zhurakousky
Priority: Blocker
 Fix For: 0.8.0


Current NIFI build for 0.x is broken due to the SSL changes in Kafka processors 
where it is using an _getKeyPassword()_ operation only available in 1.0. We 
need to fall back on _getKeyStorePassword()_.



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

[jira] [Updated] (NIFI-1971) Create a batch capable pseudo-whois ("netcat") enrichment Processor

[Andre (JIRA)]

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

Andre updated NIFI-1971:

Affects Version/s: 1.0.0
   0.7.0

> Create a batch capable pseudo-whois ("netcat") enrichment Processor
> ---
>
> Key: NIFI-1971
> URL: https://issues.apache.org/jira/browse/NIFI-1971
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 1.0.0, 0.7.0
>Reporter: Andre
>Assignee: Andre
> Fix For: 1.1.0
>
>
> While the QueryDNS created can be used on low to medium volume enrichment and 
> to licensed DNS based lookups (e.g. commercial use of SpamHaus) many 
> enrichment providers prefer the use of bulk queries using pseudo whois API 
> (a.k.a. netcat interface).
> as documented 
> [here|https://www.shadowserver.org/wiki/pmwiki.php/Services/IP-BGP#toc6] the 
> bulk interfaces work by connecting to port 43/TCP and sending a payload like:
> {code}
> begin origin
> 4.5.4.3
> 17.112.152.32
> 208.77.188.166
> end
> {code}



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

[jira] [Updated] (NIFI-1971) Create a batch capable pseudo-whois ("netcat") enrichment Processor

[Andre (JIRA)]

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

Andre updated NIFI-1971:

Fix Version/s: 1.1.0

> Create a batch capable pseudo-whois ("netcat") enrichment Processor
> ---
>
> Key: NIFI-1971
> URL: https://issues.apache.org/jira/browse/NIFI-1971
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 1.0.0, 0.7.0
>Reporter: Andre
>Assignee: Andre
> Fix For: 1.1.0
>
>
> While the QueryDNS created can be used on low to medium volume enrichment and 
> to licensed DNS based lookups (e.g. commercial use of SpamHaus) many 
> enrichment providers prefer the use of bulk queries using pseudo whois API 
> (a.k.a. netcat interface).
> as documented 
> [here|https://www.shadowserver.org/wiki/pmwiki.php/Services/IP-BGP#toc6] the 
> bulk interfaces work by connecting to port 43/TCP and sending a payload like:
> {code}
> begin origin
> 4.5.4.3
> 17.112.152.32
> 208.77.188.166
> end
> {code}



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

[jira] [Updated] (NIFI-2374) IdentifyMimeType documentation is misleading

[Andre (JIRA)]

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

Andre updated NIFI-2374:

Fix Version/s: 1.0.0

> IdentifyMimeType documentation is misleading
> 
>
> Key: NIFI-2374
> URL: https://issues.apache.org/jira/browse/NIFI-2374
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 1.0.0, 0.7.0
>Reporter: Andre
>Assignee: Andre
>Priority: Minor
> Fix For: 1.0.0
>
>
> The current documentation of IdentifyMimeType mentions the processor is 
> capable of identifying a reasonably small range of file types.
> However, upon inspecting the code, it becomes evident that the processor 
> employs Apache Tike detectors and parsers (required to distinguish a ZIP file 
> from a JAR).
> This means the list of File(MIME) types detected is the same as the one 
> present in Tika's DefaultDetector.
>  



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

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

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1965:
--

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/496
  
@pvillard31 let me know if you have any other comments as I am waiting for 
this to be merged to submit a PR covering NIFI-1971 as well 

Cheers


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



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

[GitHub] nifi issue #496: NIFI-1965 - Implement QueryDNS Processor

[trixpan]

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/496
  
@pvillard31 let me know if you have any other comments as I am waiting for 
this to be merged to submit a PR covering NIFI-1971 as well 

Cheers


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

[jira] [Assigned] (NIFI-1971) Create a batch capable pseudo-whois ("netcat") enrichment Processor

[Andre (JIRA)]

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

Andre reassigned NIFI-1971:
---

Assignee: Andre

> Create a batch capable pseudo-whois ("netcat") enrichment Processor
> ---
>
> Key: NIFI-1971
> URL: https://issues.apache.org/jira/browse/NIFI-1971
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Andre
>Assignee: Andre
>
> While the QueryDNS created can be used on low to medium volume enrichment and 
> to licensed DNS based lookups (e.g. commercial use of SpamHaus) many 
> enrichment providers prefer the use of bulk queries using pseudo whois API 
> (a.k.a. netcat interface).
> as documented 
> [here|https://www.shadowserver.org/wiki/pmwiki.php/Services/IP-BGP#toc6] the 
> bulk interfaces work by connecting to port 43/TCP and sending a payload like:
> {code}
> begin origin
> 4.5.4.3
> 17.112.152.32
> 208.77.188.166
> end
> {code}



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