[jira] [Updated] (NIFI-3671) GenerateFlowFile throws NPE in FileSystemRepository

[Joseph Witt (JIRA)]

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

Joseph Witt updated NIFI-3671:
--
Priority: Major  (was: Critical)

> GenerateFlowFile throws NPE in FileSystemRepository
> ---
>
> Key: NIFI-3671
> URL: https://issues.apache.org/jira/browse/NIFI-3671
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.2.0
> Environment: Ubuntu Linux 14.04.5 LTS, x86, NiFi 1.2.0-SNAPSHOT, Java 
> 1.8.0_102
>Reporter: Joe Skora
> Attachments: flow.xml, genff-npe.log, priority.groovy
>
>
> While volume testing, {{GenerateFlowFile}} is randomly throwing 
> {{NullPointerException}} during startup.  The NPE occurs in 
> {{FileSystemRepository.write()}} called from 
> {{BufferedOutputStream.flushBuffer()}} and results in an Administrative Yield.
> When it happens, the bulletin shows up on the processors immediately after 
> starting them.  Starting them a second time will often succeed, but sometimes 
> it takes a multiple retries.  When the {{GenerateFlowFile}} processors are 
> started for these tests, the graph is typically empty.
> Log entries for an example Thread are attached.  This looks similar to 
> [NIFI-2551|https://issues.apache.org/jira/browse/NIFI-2551], but that is 
> marked as being fixed in 1.0.0.



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

[jira] [Commented] (NIFI-3671) GenerateFlowFile throws NPE in FileSystemRepository

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-3671:
---

restored priority to original and removed fix version until there is traction

> GenerateFlowFile throws NPE in FileSystemRepository
> ---
>
> Key: NIFI-3671
> URL: https://issues.apache.org/jira/browse/NIFI-3671
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.2.0
> Environment: Ubuntu Linux 14.04.5 LTS, x86, NiFi 1.2.0-SNAPSHOT, Java 
> 1.8.0_102
>Reporter: Joe Skora
> Attachments: flow.xml, genff-npe.log, priority.groovy
>
>
> While volume testing, {{GenerateFlowFile}} is randomly throwing 
> {{NullPointerException}} during startup.  The NPE occurs in 
> {{FileSystemRepository.write()}} called from 
> {{BufferedOutputStream.flushBuffer()}} and results in an Administrative Yield.
> When it happens, the bulletin shows up on the processors immediately after 
> starting them.  Starting them a second time will often succeed, but sometimes 
> it takes a multiple retries.  When the {{GenerateFlowFile}} processors are 
> started for these tests, the graph is typically empty.
> Log entries for an example Thread are attached.  This looks similar to 
> [NIFI-2551|https://issues.apache.org/jira/browse/NIFI-2551], but that is 
> marked as being fixed in 1.0.0.



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

[jira] [Updated] (NIFI-3671) GenerateFlowFile throws NPE in FileSystemRepository

[Joseph Witt (JIRA)]

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

Joseph Witt updated NIFI-3671:
--
Fix Version/s: (was: 1.2.0)

> GenerateFlowFile throws NPE in FileSystemRepository
> ---
>
> Key: NIFI-3671
> URL: https://issues.apache.org/jira/browse/NIFI-3671
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.2.0
> Environment: Ubuntu Linux 14.04.5 LTS, x86, NiFi 1.2.0-SNAPSHOT, Java 
> 1.8.0_102
>Reporter: Joe Skora
>Priority: Critical
> Attachments: flow.xml, genff-npe.log, priority.groovy
>
>
> While volume testing, {{GenerateFlowFile}} is randomly throwing 
> {{NullPointerException}} during startup.  The NPE occurs in 
> {{FileSystemRepository.write()}} called from 
> {{BufferedOutputStream.flushBuffer()}} and results in an Administrative Yield.
> When it happens, the bulletin shows up on the processors immediately after 
> starting them.  Starting them a second time will often succeed, but sometimes 
> it takes a multiple retries.  When the {{GenerateFlowFile}} processors are 
> started for these tests, the graph is typically empty.
> Log entries for an example Thread are attached.  This looks similar to 
> [NIFI-2551|https://issues.apache.org/jira/browse/NIFI-2551], but that is 
> marked as being fixed in 1.0.0.



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

[jira] [Commented] (NIFI-2886) Framework doesn't release thread if processor administratively yields

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2886:
---

removed fix version

> Framework doesn't release thread if processor administratively yields
> -
>
> Key: NIFI-2886
> URL: https://issues.apache.org/jira/browse/NIFI-2886
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Reporter: David A. Wynne
>Assignee: Oleg Zhurakousky
>
> If a processor yields due to a exception from onScheduled it doesn't 
> immediately release the thread back to the pool.



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

[jira] [Updated] (NIFI-2886) Framework doesn't release thread if processor administratively yields

[Joseph Witt (JIRA)]

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

Joseph Witt updated NIFI-2886:
--
Fix Version/s: (was: 1.2.0)

> Framework doesn't release thread if processor administratively yields
> -
>
> Key: NIFI-2886
> URL: https://issues.apache.org/jira/browse/NIFI-2886
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Reporter: David A. Wynne
>Assignee: Oleg Zhurakousky
>
> If a processor yields due to a exception from onScheduled it doesn't 
> immediately release the thread back to the pool.



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

[jira] [Resolved] (NIFI-3089) Eliminate any usage of json.org Cat-X License

[Joseph Witt (JIRA)]

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

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

> Eliminate any usage of json.org Cat-X License
> -
>
> Key: NIFI-3089
> URL: https://issues.apache.org/jira/browse/NIFI-3089
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Witt
>Assignee: Joseph Witt
>Priority: Blocker
> Fix For: 1.2.0
>
>
> In NIFI-2991 we did the bulk of the work to eliminate Cat-X usage of the 
> json.org library.
> In a thread on 23 Nov 2016 VP Legal of the ASF approved pre-existing usage of 
> the json.org library provided sufficient NOTICE of usage existed (we have 
> that) until April 2017.
> We must ensure twitter4j changes their usage of this by then or we must find 
> an alternative or we must remove this processor/nar again.
> Will place this on the 1.2 release but it might be later than that.  
> Ultimately this must be done by April.
> Please do NOT remove the fix version.  We must ensure we don't lose track of 
> this issue.



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

[jira] [Updated] (NIFI-1280) Create QueryFlowFile Processor

[Matt Burgess (JIRA)]

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

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

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



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

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

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1280:
--

Github user asfgit closed the pull request at:

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


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



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

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

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1280 added support for RecordSchema in SchemaRegistry

Signed-off-by: Mark Payne 
Signed-off-by: Matt Burgess 

NIFI-1280: Updated SimpleKeyValueSchemaRegistry to make use of new CHOICE 
RecordFieldType - Update Record Readers to use SchemaRegistry controller 
service. Moved SchemaRegistry api into its own maven module and added to 
standard-services-api so that we can properly add dependencies on it. Code 
cleanup and bug fixes

Signed-off-by: Matt Burgess 

NIFI-1280: Fixed checkstyle violations and license exclusions for RAT plugin

Signed-off-by: Matt Burgess 

NIFI-1280: Addressed feedback from PR Review

Signed-off-by: Matt Burgess 

NIFI-1280: Additional changes/doc to support QueryFlowFile and Record 
Readers/Writers

This closes #1652


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



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

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

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1280 added support for RecordSchema in SchemaRegistry

Signed-off-by: Mark Payne 
Signed-off-by: Matt Burgess 

NIFI-1280: Updated SimpleKeyValueSchemaRegistry to make use of new CHOICE 
RecordFieldType - Update Record Readers to use SchemaRegistry controller 
service. Moved SchemaRegistry api into its own maven module and added to 
standard-services-api so that we can properly add dependencies on it. Code 
cleanup and bug fixes

Signed-off-by: Matt Burgess 

NIFI-1280: Fixed checkstyle violations and license exclusions for RAT plugin

Signed-off-by: Matt Burgess 

NIFI-1280: Addressed feedback from PR Review

Signed-off-by: Matt Burgess 

NIFI-1280: Additional changes/doc to support QueryFlowFile and Record 
Readers/Writers

This closes #1652


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



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

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

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1280 added support for RecordSchema in SchemaRegistry

Signed-off-by: Mark Payne 
Signed-off-by: Matt Burgess 

NIFI-1280: Updated SimpleKeyValueSchemaRegistry to make use of new CHOICE 
RecordFieldType - Update Record Readers to use SchemaRegistry controller 
service. Moved SchemaRegistry api into its own maven module and added to 
standard-services-api so that we can properly add dependencies on it. Code 
cleanup and bug fixes

Signed-off-by: Matt Burgess 

NIFI-1280: Fixed checkstyle violations and license exclusions for RAT plugin

Signed-off-by: Matt Burgess 

NIFI-1280: Addressed feedback from PR Review

Signed-off-by: Matt Burgess 

NIFI-1280: Additional changes/doc to support QueryFlowFile and Record 
Readers/Writers

This closes #1652


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



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

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

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1280 added support for RecordSchema in SchemaRegistry

Signed-off-by: Mark Payne 
Signed-off-by: Matt Burgess 

NIFI-1280: Updated SimpleKeyValueSchemaRegistry to make use of new CHOICE 
RecordFieldType - Update Record Readers to use SchemaRegistry controller 
service. Moved SchemaRegistry api into its own maven module and added to 
standard-services-api so that we can properly add dependencies on it. Code 
cleanup and bug fixes

Signed-off-by: Matt Burgess 

NIFI-1280: Fixed checkstyle violations and license exclusions for RAT plugin

Signed-off-by: Matt Burgess 

NIFI-1280: Addressed feedback from PR Review

Signed-off-by: Matt Burgess 

NIFI-1280: Additional changes/doc to support QueryFlowFile and Record 
Readers/Writers

This closes #1652


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



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

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

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1280:
--

Github user mattyb149 commented on the issue:

https://github.com/apache/nifi/pull/1652
  
+1 LGTM ran a full build with unit tests and contrib-check, tried various 
RecordReaders and Writers and QueryFlowFile queries, great work!  Merging to 
master


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



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

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

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1280: Refactoring to make more generic so that other data types can be 
supported; created InputStreams to content on-demand so that multiple passes 
can be made over FlowFile content if required. Created new Controller Services 
for reading and writing specific data types

Signed-off-by: Matt Burgess 


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



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

[GitHub] nifi pull request #1652: NIFI-1280: Renamed FilterCSVColumns to QueryFlowFil...

[asfgit]

Github user asfgit closed the pull request at:

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


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

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1280 added support for RecordSchema in SchemaRegistry

Signed-off-by: Mark Payne 
Signed-off-by: Matt Burgess 

NIFI-1280: Updated SimpleKeyValueSchemaRegistry to make use of new CHOICE 
RecordFieldType - Update Record Readers to use SchemaRegistry controller 
service. Moved SchemaRegistry api into its own maven module and added to 
standard-services-api so that we can properly add dependencies on it. Code 
cleanup and bug fixes

Signed-off-by: Matt Burgess 

NIFI-1280: Fixed checkstyle violations and license exclusions for RAT plugin

Signed-off-by: Matt Burgess 

NIFI-1280: Addressed feedback from PR Review

Signed-off-by: Matt Burgess 

NIFI-1280: Additional changes/doc to support QueryFlowFile and Record 
Readers/Writers

This closes #1652


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



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

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

[ASF subversion and git services (JIRA)]

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

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

Commit 4d5872a38500ed0541d7689107b34daedb5b7e34 in nifi's branch 
refs/heads/master from [~Toivo Adams]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=4d5872a ]

NIFI-1280 Create FilterCSVColumns Processor.

Signed-off-by: Matt Burgess 


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



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

[GitHub] nifi issue #1652: NIFI-1280: Renamed FilterCSVColumns to QueryFlowFile; intr...

[mattyb149]

Github user mattyb149 commented on the issue:

https://github.com/apache/nifi/pull/1652
  
+1 LGTM ran a full build with unit tests and contrib-check, tried various 
RecordReaders and Writers and QueryFlowFile queries, great work!  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] [Updated] (NIFI-3690) nifi-gcp-bundle contains undeclared (L&N) dependencies

[James Wing (JIRA)]

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

James Wing updated NIFI-3690:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> nifi-gcp-bundle contains undeclared (L&N) dependencies
> --
>
> Key: NIFI-3690
> URL: https://issues.apache.org/jira/browse/NIFI-3690
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Joseph Witt
>Assignee: James Wing
>Priority: Blocker
> Fix For: 1.2.0
>
>
> [~gene-telligentdata] [~jameswing] In working NIFI-3089 I found the 
> nifi-gcp-nar. It contained a transitive dependency on org.json library which 
> is Category X for apache so must be removed.  I've got that address in 
> NIFI-3089 and will have a PR for that soon.  
> However, in looking at the L&N for the nar itself there are a ton of 
> dependencies in the nar and they're not referenced in the nar's L&N.  We must 
> resolve this before nifi-gcp-nar can be released w/NiFi.



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

[jira] [Commented] (NIFI-3690) nifi-gcp-bundle contains undeclared (L&N) dependencies

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3690:
--

Github user asfgit closed the pull request at:

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


> nifi-gcp-bundle contains undeclared (L&N) dependencies
> --
>
> Key: NIFI-3690
> URL: https://issues.apache.org/jira/browse/NIFI-3690
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Joseph Witt
>Assignee: James Wing
>Priority: Blocker
> Fix For: 1.2.0
>
>
> [~gene-telligentdata] [~jameswing] In working NIFI-3089 I found the 
> nifi-gcp-nar. It contained a transitive dependency on org.json library which 
> is Category X for apache so must be removed.  I've got that address in 
> NIFI-3089 and will have a PR for that soon.  
> However, in looking at the L&N for the nar itself there are a ton of 
> dependencies in the nar and they're not referenced in the nar's L&N.  We must 
> resolve this before nifi-gcp-nar can be released w/NiFi.



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

[GitHub] nifi pull request #1665: NIFI-3690 updated L&N in nifi-gcp-nar and nifi-asse...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-3690) nifi-gcp-bundle contains undeclared (L&N) dependencies

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-3690 Updated nifi-gcp-nar L&N, cat-x deps

Updated L&N in nifi-gcp-nar and nifi-assembly and fixed nifi-gcp-processors
to avoid jsr305 and json.org cat-x dependencies

Signed-off-by: James Wing 

This closes #1665.


> nifi-gcp-bundle contains undeclared (L&N) dependencies
> --
>
> Key: NIFI-3690
> URL: https://issues.apache.org/jira/browse/NIFI-3690
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Joseph Witt
>Assignee: James Wing
>Priority: Blocker
> Fix For: 1.2.0
>
>
> [~gene-telligentdata] [~jameswing] In working NIFI-3089 I found the 
> nifi-gcp-nar. It contained a transitive dependency on org.json library which 
> is Category X for apache so must be removed.  I've got that address in 
> NIFI-3089 and will have a PR for that soon.  
> However, in looking at the L&N for the nar itself there are a ton of 
> dependencies in the nar and they're not referenced in the nar's L&N.  We must 
> resolve this before nifi-gcp-nar can be released w/NiFi.



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

[jira] [Commented] (NIFI-3690) nifi-gcp-bundle contains undeclared (L&N) dependencies

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3690:
--

Github user jvwing commented on the issue:

https://github.com/apache/nifi/pull/1665
  
@joewitt, the license, notice, and dependency changes look good to me:
* Builds good
* Works good - tested a Google Cloud Storage flow in which put, list, 
fetch, and delete all worked.
* Confirmed that the nifi-gcp-nar contains json using com.tdunning:json 
under ASLv2, not the json.org version.

I will merge shortly.


> nifi-gcp-bundle contains undeclared (L&N) dependencies
> --
>
> Key: NIFI-3690
> URL: https://issues.apache.org/jira/browse/NIFI-3690
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Joseph Witt
>Assignee: James Wing
>Priority: Blocker
> Fix For: 1.2.0
>
>
> [~gene-telligentdata] [~jameswing] In working NIFI-3089 I found the 
> nifi-gcp-nar. It contained a transitive dependency on org.json library which 
> is Category X for apache so must be removed.  I've got that address in 
> NIFI-3089 and will have a PR for that soon.  
> However, in looking at the L&N for the nar itself there are a ton of 
> dependencies in the nar and they're not referenced in the nar's L&N.  We must 
> resolve this before nifi-gcp-nar can be released w/NiFi.



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

[GitHub] nifi issue #1665: NIFI-3690 updated L&N in nifi-gcp-nar and nifi-assembly an...

[jvwing]

Github user jvwing commented on the issue:

https://github.com/apache/nifi/pull/1665
  
@joewitt, the license, notice, and dependency changes look good to me:
* Builds good
* Works good - tested a Google Cloud Storage flow in which put, list, 
fetch, and delete all worked.
* Confirmed that the nifi-gcp-nar contains json using com.tdunning:json 
under ASLv2, not the json.org version.

I will merge shortly.


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

[jira] [Commented] (NIFI-3690) nifi-gcp-bundle contains undeclared (L&N) dependencies

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3690:
--

Github user jvwing commented on the issue:

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


> nifi-gcp-bundle contains undeclared (L&N) dependencies
> --
>
> Key: NIFI-3690
> URL: https://issues.apache.org/jira/browse/NIFI-3690
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Joseph Witt
>Assignee: James Wing
>Priority: Blocker
> Fix For: 1.2.0
>
>
> [~gene-telligentdata] [~jameswing] In working NIFI-3089 I found the 
> nifi-gcp-nar. It contained a transitive dependency on org.json library which 
> is Category X for apache so must be removed.  I've got that address in 
> NIFI-3089 and will have a PR for that soon.  
> However, in looking at the L&N for the nar itself there are a ton of 
> dependencies in the nar and they're not referenced in the nar's L&N.  We must 
> resolve this before nifi-gcp-nar can be released w/NiFi.



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

[GitHub] nifi issue #1665: NIFI-3690 updated L&N in nifi-gcp-nar and nifi-assembly an...

[jvwing]

Github user jvwing commented on the issue:

https://github.com/apache/nifi/pull/1665
  
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-3089) Eliminate any usage of json.org Cat-X License

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-3089:
---

PR for NIFI-3690 is in.  Once that is done i think this is good to go and can 
be closed out too.

> Eliminate any usage of json.org Cat-X License
> -
>
> Key: NIFI-3089
> URL: https://issues.apache.org/jira/browse/NIFI-3089
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Witt
>Assignee: Joseph Witt
>Priority: Blocker
> Fix For: 1.2.0
>
>
> In NIFI-2991 we did the bulk of the work to eliminate Cat-X usage of the 
> json.org library.
> In a thread on 23 Nov 2016 VP Legal of the ASF approved pre-existing usage of 
> the json.org library provided sufficient NOTICE of usage existed (we have 
> that) until April 2017.
> We must ensure twitter4j changes their usage of this by then or we must find 
> an alternative or we must remove this processor/nar again.
> Will place this on the 1.2 release but it might be later than that.  
> Ultimately this must be done by April.
> Please do NOT remove the fix version.  We must ensure we don't lose track of 
> this issue.



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

[jira] [Updated] (NIFI-3690) nifi-gcp-bundle contains undeclared (L&N) dependencies

[Joseph Witt (JIRA)]

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

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

> nifi-gcp-bundle contains undeclared (L&N) dependencies
> --
>
> Key: NIFI-3690
> URL: https://issues.apache.org/jira/browse/NIFI-3690
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Joseph Witt
>Assignee: James Wing
>Priority: Blocker
> Fix For: 1.2.0
>
>
> [~gene-telligentdata] [~jameswing] In working NIFI-3089 I found the 
> nifi-gcp-nar. It contained a transitive dependency on org.json library which 
> is Category X for apache so must be removed.  I've got that address in 
> NIFI-3089 and will have a PR for that soon.  
> However, in looking at the L&N for the nar itself there are a ton of 
> dependencies in the nar and they're not referenced in the nar's L&N.  We must 
> resolve this before nifi-gcp-nar can be released w/NiFi.



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

[jira] [Commented] (NIFI-3690) nifi-gcp-bundle contains undeclared (L&N) dependencies

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-3690:
---

[~jameswing] ok james can you give this a look please?

> nifi-gcp-bundle contains undeclared (L&N) dependencies
> --
>
> Key: NIFI-3690
> URL: https://issues.apache.org/jira/browse/NIFI-3690
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Joseph Witt
>Assignee: Joseph Witt
>Priority: Blocker
> Fix For: 1.2.0
>
>
> [~gene-telligentdata] [~jameswing] In working NIFI-3089 I found the 
> nifi-gcp-nar. It contained a transitive dependency on org.json library which 
> is Category X for apache so must be removed.  I've got that address in 
> NIFI-3089 and will have a PR for that soon.  
> However, in looking at the L&N for the nar itself there are a ton of 
> dependencies in the nar and they're not referenced in the nar's L&N.  We must 
> resolve this before nifi-gcp-nar can be released w/NiFi.



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

[jira] [Assigned] (NIFI-3690) nifi-gcp-bundle contains undeclared (L&N) dependencies

[Joseph Witt (JIRA)]

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

Joseph Witt reassigned NIFI-3690:
-

Assignee: James Wing  (was: Joseph Witt)

> nifi-gcp-bundle contains undeclared (L&N) dependencies
> --
>
> Key: NIFI-3690
> URL: https://issues.apache.org/jira/browse/NIFI-3690
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Joseph Witt
>Assignee: James Wing
>Priority: Blocker
> Fix For: 1.2.0
>
>
> [~gene-telligentdata] [~jameswing] In working NIFI-3089 I found the 
> nifi-gcp-nar. It contained a transitive dependency on org.json library which 
> is Category X for apache so must be removed.  I've got that address in 
> NIFI-3089 and will have a PR for that soon.  
> However, in looking at the L&N for the nar itself there are a ton of 
> dependencies in the nar and they're not referenced in the nar's L&N.  We must 
> resolve this before nifi-gcp-nar can be released w/NiFi.



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

[jira] [Commented] (NIFI-3681) Controller Service for Processor Leader Elections

[Joseph Niemiec (JIRA)]

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

Joseph Niemiec commented on NIFI-3681:
--

So just building out a version of the zookeeper leader queue strategy providing 
this core API. I changed from whoIsLeader to isLeader to avoid having to 
understand any type of addressing when it comes to the core are you the leader 
type functions. In my specific need aliveElectors will help the leader 
partition work, and reassign work should someone leave/join. I have no use 
right now honestly for lastElection, but seemed like an important stat to have, 
I plan to have it return the current leaders znode creation timstim. 

public interface LeaderElectionService  {

public boolean isLeader();

public List aliveElectors();

public Long LastElection();

}


> Controller Service for Processor Leader Elections 
> --
>
> Key: NIFI-3681
> URL: https://issues.apache.org/jira/browse/NIFI-3681
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Joseph Niemiec
>Assignee: Joseph Niemiec
>
> Today I find a need for NiFi Cluster to allow a specific set of processors to 
>  perform a 'LeaderElection' of sorts to allow for a single processor to 
> update the process shared cluster state with assignments (both initial and 
> recovery.) The CS would be responsible for joining a Zookeeper group, the 
> logic itself, performing new elections should an leader die, etc... 
> At its core I envision a simple API provided by the CS
> * String - whoIsLeader
> * List[String] - aliveElectors
> * Long- LastElectionEpoch ? - Not sure about this, but would it be good to 
> detect if an election occurred and the leader did not change but the election 
> occured. Maybe a UUID-4?
> While thinking ZK is best as Clustered NiFi already requires it would there 
> be value in implementing a standalone RAFT or PAXOS that runs at the cluster 
> level? 



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

[jira] [Commented] (NIFI-3690) nifi-gcp-bundle contains undeclared (L&N) dependencies

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3690:
--

GitHub user joewitt opened a pull request:

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

NIFI-3690 updated L&N in nifi-gcp-nar and nifi-assembly and fixed nif…

…i-gcp-processors to avoid jsr305 and json.org cat-x dependencies

Thank you for submitting a contribution to Apache NiFi.

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

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

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

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

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

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

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

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


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

$ git pull https://github.com/joewitt/incubator-nifi NIFI-3690

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

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


commit cf879820c33bd6919abf7c734b786719760176d1
Author: joewitt 
Date:   2017-04-11T20:56:28Z

NIFI-3690 updated L&N in nifi-gcp-nar and nifi-assembly and fixed 
nifi-gcp-processors to avoid jsr305 and json.org cat-x dependencies




> nifi-gcp-bundle contains undeclared (L&N) dependencies
> --
>
> Key: NIFI-3690
> URL: https://issues.apache.org/jira/browse/NIFI-3690
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Joseph Witt
>Assignee: Joseph Witt
>Priority: Blocker
> Fix For: 1.2.0
>
>
> [~gene-telligentdata] [~jameswing] In working NIFI-3089 I found the 
> nifi-gcp-nar. It contained a transitive dependency on org.json library which 
> is Category X for apache so must be removed.  I've got that address in 
> NIFI-3089 and will have a PR for that soon.  
> However, in looking at the L&N for the nar itself there are a ton of 
> dependencies in the nar and they're not referenced in the nar's L&N.  We must 
> resolve this before nifi-gcp-nar can be released w/NiFi.



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

[GitHub] nifi pull request #1665: NIFI-3690 updated L&N in nifi-gcp-nar and nifi-asse...

[joewitt]

GitHub user joewitt opened a pull request:

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

NIFI-3690 updated L&N in nifi-gcp-nar and nifi-assembly and fixed nif…

…i-gcp-processors to avoid jsr305 and json.org cat-x dependencies

Thank you for submitting a contribution to Apache NiFi.

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

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

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

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

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

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

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

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


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

$ git pull https://github.com/joewitt/incubator-nifi NIFI-3690

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

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


commit cf879820c33bd6919abf7c734b786719760176d1
Author: joewitt 
Date:   2017-04-11T20:56:28Z

NIFI-3690 updated L&N in nifi-gcp-nar and nifi-assembly and fixed 
nifi-gcp-processors to avoid jsr305 and json.org cat-x dependencies




---
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-2323) Improve handling of Oracle datetime columns in QueryDatabaseTable and GenerateTableFetch

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2323:
--

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

https://github.com/apache/nifi/pull/1664#discussion_r111008309
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/AbstractDatabaseFetchProcessor.java
 ---
@@ -413,7 +400,7 @@ protected static String getLiteralByType(int type, 
String value, String database
 case TIMESTAMP:
 // Timestamp literals in Oracle need to be cast with 
TO_DATE
 if ("Oracle".equals(databaseType)) {
-return "to_date('" + value + "', '-mm-dd 
HH24:MI:SS')";
+return "timestamp '" + value + "'";
--- End diff --

This probably breaks backwards compatibility if the processor has already 
stored a Date (no time-of-day) into the StateMap. To preserve backwards 
compatibility, we should check if the value is just a Date and use the "date" 
coercion instead of the "timestamp" coercion. If that succeeds, then the next 
maximum value observed should be stored as a full timestamp and the "date" 
coercion should no longer be executed


> Improve handling of Oracle datetime columns in QueryDatabaseTable and 
> GenerateTableFetch
> 
>
> Key: NIFI-2323
> URL: https://issues.apache.org/jira/browse/NIFI-2323
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 0.6.0
>Reporter: Matt Burgess
>Assignee: Matt Burgess
>
> Due to default handling of Oracle columns returned as java.sql.Date types, 
> the string literals used to compare against the column values must be in the 
> same format as the NLS_DATE_FORMAT setting of the database (often -MM-DD).
> I believe when "Oracle" is provided as the database type (formerly known as 
> pre-processing strategy), Oracle's Datetime Functions (such as TO_DATE or 
> TO_TIMESTAMP) could be leveraged to give more fine-grained maximum-value 
> information.



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

[GitHub] nifi pull request #1664: NIFI-2323: Fixed Oracle timestamp handling in DB fe...

[mattyb149]

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

https://github.com/apache/nifi/pull/1664#discussion_r111008309
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/AbstractDatabaseFetchProcessor.java
 ---
@@ -413,7 +400,7 @@ protected static String getLiteralByType(int type, 
String value, String database
 case TIMESTAMP:
 // Timestamp literals in Oracle need to be cast with 
TO_DATE
 if ("Oracle".equals(databaseType)) {
-return "to_date('" + value + "', '-mm-dd 
HH24:MI:SS')";
+return "timestamp '" + value + "'";
--- End diff --

This probably breaks backwards compatibility if the processor has already 
stored a Date (no time-of-day) into the StateMap. To preserve backwards 
compatibility, we should check if the value is just a Date and use the "date" 
coercion instead of the "timestamp" coercion. If that succeeds, then the next 
maximum value observed should be stored as a full timestamp and the "date" 
coercion should no longer be executed


---
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-3688) Create extended groovy scripting processor

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3688:
--

Github user joewitt commented on the issue:

https://github.com/apache/nifi/pull/1662
  
The commit which removed the properties/skip javadoc/src does need to be in 
the nar bundle itself.  We dont want src/javadocs for the nar bundle.  Also, 
the processor needs a name that follows the pattern of VerbSubject instead of 
GroovyX.

We will definitely need unit tests for this.  There are references to 
Oracle things in there or at least in the screenshot.  The LICENSE and NOTICE 
appears to have a lot of copy/paste from other nars.  Are all those 
dependencies really there?


> Create extended groovy scripting processor
> --
>
> Key: NIFI-3688
> URL: https://issues.apache.org/jira/browse/NIFI-3688
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Dmitry Lukyanov
>Priority: Minor
>
> The idea is to simplify groovy scripting.
> Main targets:
> - to be compatible with existing groovy scripting
> - simplify read/write attributes
> - simplify read/write content
> - avoid closure casting to nifi types like `StreamCallback`
> - simplify and provide visibility when accessing to controller services from 
> script



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

[GitHub] nifi issue #1662: NIFI-3688 Extended Groovy Nifi Processor

[joewitt]

Github user joewitt commented on the issue:

https://github.com/apache/nifi/pull/1662
  
The commit which removed the properties/skip javadoc/src does need to be in 
the nar bundle itself.  We dont want src/javadocs for the nar bundle.  Also, 
the processor needs a name that follows the pattern of VerbSubject instead of 
GroovyX.

We will definitely need unit tests for this.  There are references to 
Oracle things in there or at least in the screenshot.  The LICENSE and NOTICE 
appears to have a lot of copy/paste from other nars.  Are all those 
dependencies really there?


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

[jira] [Commented] (NIFI-3688) Create extended groovy scripting processor

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3688:
--

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

https://github.com/apache/nifi/pull/1662#discussion_r110994393
  
--- Diff: 
nifi-nar-bundles/nifi-groovyx-bundle/nifi-groovyx-processors/src/main/java/org/apache/nifi/processors/groovyx/GroovyMethods.java
 ---
@@ -0,0 +1,266 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.groovyx;
+
+import groovy.lang.Closure;
+import groovy.lang.DelegatingMetaClass;
+import groovy.lang.GroovySystem;
+import groovy.lang.MetaClass;
+import groovy.lang.Writable;
+
+import org.apache.nifi.processors.groovyx.flow.ProcessSessionWrap;
+import org.apache.nifi.processors.groovyx.flow.SessionFile;
+
+import org.apache.nifi.processor.Relationship;
+import org.apache.nifi.processor.FlowFileFilter;
+import org.apache.nifi.processor.FlowFileFilter.FlowFileFilterResult;
+//import org.apache.nifi.processor.ProcessSession;
--- End diff --

please remove


> Create extended groovy scripting processor
> --
>
> Key: NIFI-3688
> URL: https://issues.apache.org/jira/browse/NIFI-3688
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Dmitry Lukyanov
>Priority: Minor
>
> The idea is to simplify groovy scripting.
> Main targets:
> - to be compatible with existing groovy scripting
> - simplify read/write attributes
> - simplify read/write content
> - avoid closure casting to nifi types like `StreamCallback`
> - simplify and provide visibility when accessing to controller services from 
> script



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

[jira] [Commented] (NIFI-3688) Create extended groovy scripting processor

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3688:
--

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

https://github.com/apache/nifi/pull/1662#discussion_r110994314
  
--- Diff: 
nifi-nar-bundles/nifi-groovyx-bundle/nifi-groovyx-nar/src/main/resources/META-INF/NOTICE
 ---
@@ -0,0 +1,123 @@
+nifi-groovyx-nar
+Copyright 2014-2017 The Apache Software Foundation
+
+This product includes software developed at
+The Apache Software Foundation (http://www.apache.org/).
+
+**
+Apache Software License v2
+**
+
+The following binary components are provided under the Apache Software 
License v2
+
+  (ASLv2) Apache Commons IO
+The following NOTICE information applies:
+  Apache Commons IO
+  Copyright 2002-2016 The Apache Software Foundation
+
+  (ASLv2) Apache Commons Email
+The following NOTICE information applies:
+  Apache Commons Email
+  Copyright 2002-2016 The Apache Software Foundation
+
+  (ASLv2) Apache Commons Lang
+The following NOTICE information applies:
+  Apache Commons Lang
+  Copyright 2001-2015 The Apache Software Foundation
+
+  This product includes software from the Spring Framework,
+  under the Apache License 2.0 (see: StringUtils.containsWhitespace())
+
+  (ASLv2) Apache Commons Logging
+The following NOTICE information applies:
+  Apache Commons Logging
+  Copyright 2003-2016 The Apache Software Foundation
+
+  (ASLv2) Apache HttpComponents
+The following NOTICE information applies:
+  Apache HttpClient
+  Copyright 1999-2015 The Apache Software Foundation
+
+  Apache HttpCore
+  Copyright 2005-2015 The Apache Software Foundation
+
+  Apache HttpMime
+  Copyright 1999-2013 The Apache Software Foundation
+
+  This project contains annotations derived from JCIP-ANNOTATIONS
+  Copyright (c) 2005 Brian Goetz and Tim Peierls. See 
http://www.jcip.net
+
+  (ASLv2) Spring Framework
+The following NOTICE information applies:
+  Spring Framework
+  Copyright 2002-2016 
+  
+  (ASLv2) SubEthaSMTP - A SMTP mail server
+The following NOTICE information applies:
+  Spring Framework
+  Copyright 2006-2007
+
+  (ASLv2) Apache POI
+The following NOTICE information applies:
+
+This product contains parts that were originally based on software 
from BEA.
+Copyright (c) 2000-2003, BEA Systems, .
+
+This product contains W3C XML Schema documents. Copyright 2001-2003 (c)
+World Wide Web Consortium (Massachusetts Institute of Technology, 
European
+Research Consortium for Informatics and Mathematics, Keio University)
+
+This product contains the Piccolo XML Parser for Java
+(http://piccolo.sourceforge.net/). Copyright 2002 Yuval Oren.
+
+This product contains the chunks_parse_cmds.tbl file from the vsdump 
program.
+Copyright (C) 2006-2007 Valek Filippov (f...@df.ru)
+
+This product contains parts of the eID Applet project
+(http://eid-applet.googlecode.com). Copyright (c) 2009-2014
+FedICT (federal ICT department of Belgium), e-Contract.be BVBA 
(https://www.e-contract.be),
+Bart Hanssens from FedICT
+
+CurvesAIP is BSD-licensed software ( 
https://github.com/virtuald/curvesapi/)
+Copyright (c) 2005, Graph Builder
+
+  (ASLv2) Joda Time
+The following NOTICE information applies:
+  This product includes software developed by
+  Joda.org (http://www.joda.org/).
+
+
+
+Common Development and Distribution License 1.1
+
+
+The following binary components are provided under the Common Development 
and Distribution License 1.1. See project link for details.
+
+(CDDL 1.1) (GPL2 w/ CPE) JavaMail API (compat) 
(javax.mail:mail:jar:1.5.6 - https://java.net/projects/javamail/pages/Home)
+
+
+Common Development and Distribution License 1.0
+
+
+The following binary components are provided under the Common Development 
and Distribution License 1.0.  See project link for details.
+
+(CDDL 1.0) JavaBeans Activation Framework (JAF) 
(javax.activation:activation:jar:1.1 - 
http://java.sun.com/products/javabeans/jaf/index.jsp)
+
+
+The MIT License
+
+
+The following binary components ar

[GitHub] nifi pull request #1662: NIFI-3688 Extended Groovy Nifi Processor

[joewitt]

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

https://github.com/apache/nifi/pull/1662#discussion_r110994314
  
--- Diff: 
nifi-nar-bundles/nifi-groovyx-bundle/nifi-groovyx-nar/src/main/resources/META-INF/NOTICE
 ---
@@ -0,0 +1,123 @@
+nifi-groovyx-nar
+Copyright 2014-2017 The Apache Software Foundation
+
+This product includes software developed at
+The Apache Software Foundation (http://www.apache.org/).
+
+**
+Apache Software License v2
+**
+
+The following binary components are provided under the Apache Software 
License v2
+
+  (ASLv2) Apache Commons IO
+The following NOTICE information applies:
+  Apache Commons IO
+  Copyright 2002-2016 The Apache Software Foundation
+
+  (ASLv2) Apache Commons Email
+The following NOTICE information applies:
+  Apache Commons Email
+  Copyright 2002-2016 The Apache Software Foundation
+
+  (ASLv2) Apache Commons Lang
+The following NOTICE information applies:
+  Apache Commons Lang
+  Copyright 2001-2015 The Apache Software Foundation
+
+  This product includes software from the Spring Framework,
+  under the Apache License 2.0 (see: StringUtils.containsWhitespace())
+
+  (ASLv2) Apache Commons Logging
+The following NOTICE information applies:
+  Apache Commons Logging
+  Copyright 2003-2016 The Apache Software Foundation
+
+  (ASLv2) Apache HttpComponents
+The following NOTICE information applies:
+  Apache HttpClient
+  Copyright 1999-2015 The Apache Software Foundation
+
+  Apache HttpCore
+  Copyright 2005-2015 The Apache Software Foundation
+
+  Apache HttpMime
+  Copyright 1999-2013 The Apache Software Foundation
+
+  This project contains annotations derived from JCIP-ANNOTATIONS
+  Copyright (c) 2005 Brian Goetz and Tim Peierls. See 
http://www.jcip.net
+
+  (ASLv2) Spring Framework
+The following NOTICE information applies:
+  Spring Framework
+  Copyright 2002-2016 
+  
+  (ASLv2) SubEthaSMTP - A SMTP mail server
+The following NOTICE information applies:
+  Spring Framework
+  Copyright 2006-2007
+
+  (ASLv2) Apache POI
+The following NOTICE information applies:
+
+This product contains parts that were originally based on software 
from BEA.
+Copyright (c) 2000-2003, BEA Systems, .
+
+This product contains W3C XML Schema documents. Copyright 2001-2003 (c)
+World Wide Web Consortium (Massachusetts Institute of Technology, 
European
+Research Consortium for Informatics and Mathematics, Keio University)
+
+This product contains the Piccolo XML Parser for Java
+(http://piccolo.sourceforge.net/). Copyright 2002 Yuval Oren.
+
+This product contains the chunks_parse_cmds.tbl file from the vsdump 
program.
+Copyright (C) 2006-2007 Valek Filippov (f...@df.ru)
+
+This product contains parts of the eID Applet project
+(http://eid-applet.googlecode.com). Copyright (c) 2009-2014
+FedICT (federal ICT department of Belgium), e-Contract.be BVBA 
(https://www.e-contract.be),
+Bart Hanssens from FedICT
+
+CurvesAIP is BSD-licensed software ( 
https://github.com/virtuald/curvesapi/)
+Copyright (c) 2005, Graph Builder
+
+  (ASLv2) Joda Time
+The following NOTICE information applies:
+  This product includes software developed by
+  Joda.org (http://www.joda.org/).
+
+
+
+Common Development and Distribution License 1.1
+
+
+The following binary components are provided under the Common Development 
and Distribution License 1.1. See project link for details.
+
+(CDDL 1.1) (GPL2 w/ CPE) JavaMail API (compat) 
(javax.mail:mail:jar:1.5.6 - https://java.net/projects/javamail/pages/Home)
+
+
+Common Development and Distribution License 1.0
+
+
+The following binary components are provided under the Common Development 
and Distribution License 1.0.  See project link for details.
+
+(CDDL 1.0) JavaBeans Activation Framework (JAF) 
(javax.activation:activation:jar:1.1 - 
http://java.sun.com/products/javabeans/jaf/index.jsp)
+
+
+The MIT License
+
+
+The following binary components are provided under the MIT License.  See 
project link for details.
+
+  (MIT License) EWS Java API
--- End diff --

You don't need to reference CategoryA deps in the NOTICE which are already 
covered in the LICENSE.  This MIT dep and 

[GitHub] nifi pull request #1662: NIFI-3688 Extended Groovy Nifi Processor

[joewitt]

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

https://github.com/apache/nifi/pull/1662#discussion_r110994393
  
--- Diff: 
nifi-nar-bundles/nifi-groovyx-bundle/nifi-groovyx-processors/src/main/java/org/apache/nifi/processors/groovyx/GroovyMethods.java
 ---
@@ -0,0 +1,266 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.groovyx;
+
+import groovy.lang.Closure;
+import groovy.lang.DelegatingMetaClass;
+import groovy.lang.GroovySystem;
+import groovy.lang.MetaClass;
+import groovy.lang.Writable;
+
+import org.apache.nifi.processors.groovyx.flow.ProcessSessionWrap;
+import org.apache.nifi.processors.groovyx.flow.SessionFile;
+
+import org.apache.nifi.processor.Relationship;
+import org.apache.nifi.processor.FlowFileFilter;
+import org.apache.nifi.processor.FlowFileFilter.FlowFileFilterResult;
+//import org.apache.nifi.processor.ProcessSession;
--- End diff --

please remove


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

[jira] [Resolved] (NIFI-3692) Use hbc-core instead of hbc-twitter4j in social-media bundle to resolve org.json cat-x

[Joseph Witt (JIRA)]

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

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

Tested it and still works!  +1 merged to master.

> Use hbc-core instead of hbc-twitter4j in social-media bundle to resolve 
> org.json cat-x
> --
>
> Key: NIFI-3692
> URL: https://issues.apache.org/jira/browse/NIFI-3692
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Joey Frazee
>Assignee: Joseph Witt
> Fix For: 1.2.0
>
>
> The GetTwitter processor in the social-media bundle is (unnecessarily) using 
> hbc-twitter4j to consume the Twitter stream, which means it pulls in 
> Twitter4j binary, creating a problem for the org.json cat-x decision. 
> GetTwitter does not make use of any Twitter4j classes or helpers though so 
> it's completely unnecessary and we can back off to using hbc-core instead.



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

[jira] [Commented] (NIFI-3692) Use hbc-core instead of hbc-twitter4j in social-media bundle to resolve org.json cat-x

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3692:
--

Github user asfgit closed the pull request at:

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


> Use hbc-core instead of hbc-twitter4j in social-media bundle to resolve 
> org.json cat-x
> --
>
> Key: NIFI-3692
> URL: https://issues.apache.org/jira/browse/NIFI-3692
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Joey Frazee
>Assignee: Joseph Witt
> Fix For: 1.2.0
>
>
> The GetTwitter processor in the social-media bundle is (unnecessarily) using 
> hbc-twitter4j to consume the Twitter stream, which means it pulls in 
> Twitter4j binary, creating a problem for the org.json cat-x decision. 
> GetTwitter does not make use of any Twitter4j classes or helpers though so 
> it's completely unnecessary and we can back off to using hbc-core instead.



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

[jira] [Commented] (NIFI-3692) Use hbc-core instead of hbc-twitter4j in social-media bundle to resolve org.json cat-x

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-3692 This closes #1663. Use hbc-core instead of hbc-twitter4j in 
social-media bundle to resolve org.json cat-x

Signed-off-by: joewitt 


> Use hbc-core instead of hbc-twitter4j in social-media bundle to resolve 
> org.json cat-x
> --
>
> Key: NIFI-3692
> URL: https://issues.apache.org/jira/browse/NIFI-3692
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Joey Frazee
>Assignee: Joseph Witt
> Fix For: 1.2.0
>
>
> The GetTwitter processor in the social-media bundle is (unnecessarily) using 
> hbc-twitter4j to consume the Twitter stream, which means it pulls in 
> Twitter4j binary, creating a problem for the org.json cat-x decision. 
> GetTwitter does not make use of any Twitter4j classes or helpers though so 
> it's completely unnecessary and we can back off to using hbc-core instead.



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

[GitHub] nifi pull request #1663: NIFI-3692 Use hbc-core instead of hbc-twitter4j in ...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #78: MINIFI-265: Add conditional statement for ...

[asfgit]

Github user asfgit closed the pull request at:

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


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

[GitHub] nifi-minifi-cpp issue #78: MINIFI-265: Add conditional statement for doc gen...

[apiri]

Github user apiri commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/78
  
Looks good.  Thanks!  Will merge.


---
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-3690) nifi-gcp-bundle contains undeclared (L&N) dependencies

[Joseph Witt (JIRA)]

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

Joseph Witt reassigned NIFI-3690:
-

Assignee: Joseph Witt

> nifi-gcp-bundle contains undeclared (L&N) dependencies
> --
>
> Key: NIFI-3690
> URL: https://issues.apache.org/jira/browse/NIFI-3690
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Joseph Witt
>Assignee: Joseph Witt
>Priority: Blocker
> Fix For: 1.2.0
>
>
> [~gene-telligentdata] [~jameswing] In working NIFI-3089 I found the 
> nifi-gcp-nar. It contained a transitive dependency on org.json library which 
> is Category X for apache so must be removed.  I've got that address in 
> NIFI-3089 and will have a PR for that soon.  
> However, in looking at the L&N for the nar itself there are a ton of 
> dependencies in the nar and they're not referenced in the nar's L&N.  We must 
> resolve this before nifi-gcp-nar can be released w/NiFi.



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

[jira] [Commented] (NIFI-3690) nifi-gcp-bundle contains undeclared (L&N) dependencies

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-3690:
---

Had a chance to sync with [~jameswing] off list and made a deal with him.  I'll 
listen to pandora, have a drink, and get the L&N updated.  He'll then test and 
make sure it is still ok with the ted dunning json lib in there instead of the 
other one.  If we're good then we can merge it in.

> nifi-gcp-bundle contains undeclared (L&N) dependencies
> --
>
> Key: NIFI-3690
> URL: https://issues.apache.org/jira/browse/NIFI-3690
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Joseph Witt
>Priority: Blocker
> Fix For: 1.2.0
>
>
> [~gene-telligentdata] [~jameswing] In working NIFI-3089 I found the 
> nifi-gcp-nar. It contained a transitive dependency on org.json library which 
> is Category X for apache so must be removed.  I've got that address in 
> NIFI-3089 and will have a PR for that soon.  
> However, in looking at the L&N for the nar itself there are a ton of 
> dependencies in the nar and they're not referenced in the nar's L&N.  We must 
> resolve this before nifi-gcp-nar can be released w/NiFi.



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

[GitHub] nifi-minifi-cpp pull request #78: MINIFI-265: Add conditional statement for ...

[phrocker]

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

https://github.com/apache/nifi-minifi-cpp/pull/78#discussion_r110975952
  
--- Diff: docs/Doxyfile ---
@@ -0,0 +1,2474 @@
+# Doxyfile 1.8.13
--- End diff --

Cool Updated. Thanks!


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

[GitHub] nifi issue #1663: NIFI-3692 Use hbc-core instead of hbc-twitter4j in social-...

[joewitt]

Github user joewitt commented on the issue:

https://github.com/apache/nifi/pull/1663
  
@jfrazee we can remove it from the assembly notice too.  I took out the 
flume twitter source on the 1.x line already.  That NIFI-3018 JIRA is for the 
0.x line.


---
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-3692) Use hbc-core instead of hbc-twitter4j in social-media bundle to resolve org.json cat-x

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3692:
--

Github user joewitt commented on the issue:

https://github.com/apache/nifi/pull/1663
  
@jfrazee we can remove it from the assembly notice too.  I took out the 
flume twitter source on the 1.x line already.  That NIFI-3018 JIRA is for the 
0.x line.


> Use hbc-core instead of hbc-twitter4j in social-media bundle to resolve 
> org.json cat-x
> --
>
> Key: NIFI-3692
> URL: https://issues.apache.org/jira/browse/NIFI-3692
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Joey Frazee
>Assignee: Joseph Witt
> Fix For: 1.2.0
>
>
> The GetTwitter processor in the social-media bundle is (unnecessarily) using 
> hbc-twitter4j to consume the Twitter stream, which means it pulls in 
> Twitter4j binary, creating a problem for the org.json cat-x decision. 
> GetTwitter does not make use of any Twitter4j classes or helpers though so 
> it's completely unnecessary and we can back off to using hbc-core instead.



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

[jira] [Updated] (NIFI-3692) Use hbc-core instead of hbc-twitter4j in social-media bundle to resolve org.json cat-x

[Joseph Witt (JIRA)]

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

Joseph Witt updated NIFI-3692:
--
Fix Version/s: 1.2.0

> Use hbc-core instead of hbc-twitter4j in social-media bundle to resolve 
> org.json cat-x
> --
>
> Key: NIFI-3692
> URL: https://issues.apache.org/jira/browse/NIFI-3692
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Joey Frazee
>Assignee: Joseph Witt
> Fix For: 1.2.0
>
>
> The GetTwitter processor in the social-media bundle is (unnecessarily) using 
> hbc-twitter4j to consume the Twitter stream, which means it pulls in 
> Twitter4j binary, creating a problem for the org.json cat-x decision. 
> GetTwitter does not make use of any Twitter4j classes or helpers though so 
> it's completely unnecessary and we can back off to using hbc-core instead.



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

[jira] [Commented] (NIFI-1833) Add support for Azure Blob Storage and Table Storage

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1833:
--

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

https://github.com/apache/nifi/pull/1636#discussion_r110950968
  
--- Diff: 
nifi-nar-bundles/nifi-azure-bundle/nifi-azure-processors/src/main/resources/docs/org.apache.nifi.processors.azure.storage.FetchAzureBlobStorage/additionalDetails.html
 ---
@@ -0,0 +1,39 @@
+
+
+
+
+
+FetchAzureBlobStorage Processor
+
+
+
+
+
+Apache NiFi Azure Processors
+
+Important Security Note
--- End diff --

Since these are important security notices, should they be presented in the 
main documentation of the processor, rather than additional details?


> Add support for Azure Blob Storage and Table Storage
> 
>
> Key: NIFI-1833
> URL: https://issues.apache.org/jira/browse/NIFI-1833
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.6.1
>Reporter: Simon Elliston Ball
>Priority: Minor
>
> It would be useful to have an Azure equivalent of the current S3 capability. 
> Azure also provides a Table storage mechanism, providing simple key value 
> storage. Since the Azure SDKs are Apache Licensed, this should be reasonably 
> straightforward. A first cut is available as an addition to the existing 
> azure bundle.



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

[jira] [Commented] (NIFI-1833) Add support for Azure Blob Storage and Table Storage

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1833:
--

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

https://github.com/apache/nifi/pull/1636#discussion_r110950260
  
--- Diff: 
nifi-nar-bundles/nifi-azure-bundle/nifi-azure-processors/src/main/java/org/apache/nifi/processors/azure/storage/ListAzureBlobStorage.java
 ---
@@ -0,0 +1,180 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.azure.storage;
+
+import java.io.IOException;
+import java.net.URISyntaxException;
+import java.security.InvalidKeyException;
+import java.util.ArrayList;
+import java.util.Arrays;
+import java.util.Collections;
+import java.util.EnumSet;
+import java.util.HashMap;
+import java.util.List;
+import java.util.Map;
+
+import org.apache.nifi.annotation.behavior.InputRequirement;
+import org.apache.nifi.annotation.behavior.InputRequirement.Requirement;
+import org.apache.nifi.annotation.behavior.Stateful;
+import org.apache.nifi.annotation.behavior.TriggerSerially;
+import org.apache.nifi.annotation.behavior.WritesAttribute;
+import org.apache.nifi.annotation.behavior.WritesAttributes;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.SeeAlso;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.components.state.Scope;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.util.StandardValidators;
+import org.apache.nifi.processors.azure.AzureConstants;
+import org.apache.nifi.processors.azure.storage.utils.BlobInfo;
+import org.apache.nifi.processors.azure.storage.utils.BlobInfo.Builder;
+import org.apache.nifi.processors.standard.AbstractListProcessor;
+
+import com.microsoft.azure.storage.CloudStorageAccount;
+import com.microsoft.azure.storage.StorageException;
+import com.microsoft.azure.storage.StorageUri;
+import com.microsoft.azure.storage.blob.BlobListingDetails;
+import com.microsoft.azure.storage.blob.BlobProperties;
+import com.microsoft.azure.storage.blob.CloudBlob;
+import com.microsoft.azure.storage.blob.CloudBlobClient;
+import com.microsoft.azure.storage.blob.CloudBlobContainer;
+import com.microsoft.azure.storage.blob.CloudBlockBlob;
+import com.microsoft.azure.storage.blob.ListBlobItem;
+
+@TriggerSerially
+@Tags({ "azure", "microsoft", "cloud", "storage", "blob" })
+@SeeAlso({ FetchAzureBlobStorage.class, PutAzureBlobStorage.class })
+@CapabilityDescription("Lists blobs in an Azure Storage container. Listing 
details are attached to an empty FlowFile for use with FetchAzureBlobStorage")
--- End diff --

Container should be capitalized here, flowfile lowercased?


> Add support for Azure Blob Storage and Table Storage
> 
>
> Key: NIFI-1833
> URL: https://issues.apache.org/jira/browse/NIFI-1833
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.6.1
>Reporter: Simon Elliston Ball
>Priority: Minor
>
> It would be useful to have an Azure equivalent of the current S3 capability. 
> Azure also provides a Table storage mechanism, providing simple key value 
> storage. Since the Azure SDKs are Apache Licensed, this should be reasonably 
> straightforward. A first cut is available as an addition to the existing 
> azure bundle.



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

[jira] [Commented] (NIFI-1833) Add support for Azure Blob Storage and Table Storage

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1833:
--

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

https://github.com/apache/nifi/pull/1636#discussion_r110950578
  
--- Diff: 
nifi-nar-bundles/nifi-azure-bundle/nifi-azure-processors/src/main/java/org/apache/nifi/processors/azure/storage/PutAzureBlobStorage.java
 ---
@@ -0,0 +1,116 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.azure.storage;
+
+import java.io.BufferedInputStream;
+import java.io.IOException;
+import java.io.InputStream;
+import java.net.URISyntaxException;
+import java.util.HashMap;
+import java.util.Map;
+import java.util.concurrent.TimeUnit;
+
+import org.apache.nifi.annotation.behavior.InputRequirement;
+import org.apache.nifi.annotation.behavior.InputRequirement.Requirement;
+import org.apache.nifi.annotation.behavior.WritesAttribute;
+import org.apache.nifi.annotation.behavior.WritesAttributes;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.SeeAlso;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.ProcessSession;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processors.azure.AbstractAzureBlobProcessor;
+import org.apache.nifi.processors.azure.AzureConstants;
+
+import com.microsoft.azure.storage.CloudStorageAccount;
+import com.microsoft.azure.storage.StorageException;
+import com.microsoft.azure.storage.blob.BlobProperties;
+import com.microsoft.azure.storage.blob.CloudBlob;
+import com.microsoft.azure.storage.blob.CloudBlobClient;
+import com.microsoft.azure.storage.blob.CloudBlobContainer;
+
+@Tags({ "azure", "microsoft", "cloud", "storage", "blob" })
+@SeeAlso({ ListAzureBlobStorage.class, FetchAzureBlobStorage.class })
+@CapabilityDescription("Puts content into an Azure Storage Blob")
--- End diff --

Should this be changed to say "Azure Storage Container"?



> Add support for Azure Blob Storage and Table Storage
> 
>
> Key: NIFI-1833
> URL: https://issues.apache.org/jira/browse/NIFI-1833
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.6.1
>Reporter: Simon Elliston Ball
>Priority: Minor
>
> It would be useful to have an Azure equivalent of the current S3 capability. 
> Azure also provides a Table storage mechanism, providing simple key value 
> storage. Since the Azure SDKs are Apache Licensed, this should be reasonably 
> straightforward. A first cut is available as an addition to the existing 
> azure bundle.



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

[jira] [Commented] (NIFI-1833) Add support for Azure Blob Storage and Table Storage

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1833:
--

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

https://github.com/apache/nifi/pull/1636#discussion_r110949965
  
--- Diff: 
nifi-nar-bundles/nifi-azure-bundle/nifi-azure-processors/src/main/java/org/apache/nifi/processors/azure/storage/FetchAzureBlobStorage.java
 ---
@@ -0,0 +1,112 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.azure.storage;
+
+import java.io.IOException;
+import java.net.URISyntaxException;
+import java.util.Arrays;
+import java.util.Collections;
+import java.util.HashMap;
+import java.util.List;
+import java.util.Map;
+import java.util.concurrent.TimeUnit;
+
+import org.apache.nifi.annotation.behavior.InputRequirement;
+import org.apache.nifi.annotation.behavior.WritesAttribute;
+import org.apache.nifi.annotation.behavior.InputRequirement.Requirement;
+import org.apache.nifi.annotation.behavior.WritesAttributes;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.SeeAlso;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.ProcessSession;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processors.azure.AbstractAzureBlobProcessor;
+import org.apache.nifi.processors.azure.AzureConstants;
+
+import com.microsoft.azure.storage.CloudStorageAccount;
+import com.microsoft.azure.storage.StorageException;
+import com.microsoft.azure.storage.blob.CloudBlob;
+import com.microsoft.azure.storage.blob.CloudBlobClient;
+import com.microsoft.azure.storage.blob.CloudBlobContainer;
+
+@Tags({ "azure", "microsoft", "cloud", "storage", "blob" })
+@CapabilityDescription("Retrieves contents of an Azure Storage Blob, 
writing the contents to the content of the FlowFile")
--- End diff --

Should this be changed to say "Retrieves contents of a blob from an Azure 
Storage Container..."?


> Add support for Azure Blob Storage and Table Storage
> 
>
> Key: NIFI-1833
> URL: https://issues.apache.org/jira/browse/NIFI-1833
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.6.1
>Reporter: Simon Elliston Ball
>Priority: Minor
>
> It would be useful to have an Azure equivalent of the current S3 capability. 
> Azure also provides a Table storage mechanism, providing simple key value 
> storage. Since the Azure SDKs are Apache Licensed, this should be reasonably 
> straightforward. A first cut is available as an addition to the existing 
> azure bundle.



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

[GitHub] nifi pull request #1636: NIFI-1833 - Azure Storage processors

[jtstorck]

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

https://github.com/apache/nifi/pull/1636#discussion_r110949965
  
--- Diff: 
nifi-nar-bundles/nifi-azure-bundle/nifi-azure-processors/src/main/java/org/apache/nifi/processors/azure/storage/FetchAzureBlobStorage.java
 ---
@@ -0,0 +1,112 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.azure.storage;
+
+import java.io.IOException;
+import java.net.URISyntaxException;
+import java.util.Arrays;
+import java.util.Collections;
+import java.util.HashMap;
+import java.util.List;
+import java.util.Map;
+import java.util.concurrent.TimeUnit;
+
+import org.apache.nifi.annotation.behavior.InputRequirement;
+import org.apache.nifi.annotation.behavior.WritesAttribute;
+import org.apache.nifi.annotation.behavior.InputRequirement.Requirement;
+import org.apache.nifi.annotation.behavior.WritesAttributes;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.SeeAlso;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.ProcessSession;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processors.azure.AbstractAzureBlobProcessor;
+import org.apache.nifi.processors.azure.AzureConstants;
+
+import com.microsoft.azure.storage.CloudStorageAccount;
+import com.microsoft.azure.storage.StorageException;
+import com.microsoft.azure.storage.blob.CloudBlob;
+import com.microsoft.azure.storage.blob.CloudBlobClient;
+import com.microsoft.azure.storage.blob.CloudBlobContainer;
+
+@Tags({ "azure", "microsoft", "cloud", "storage", "blob" })
+@CapabilityDescription("Retrieves contents of an Azure Storage Blob, 
writing the contents to the content of the FlowFile")
--- End diff --

Should this be changed to say "Retrieves contents of a blob from an Azure 
Storage Container..."?


---
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 #1636: NIFI-1833 - Azure Storage processors

[jtstorck]

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

https://github.com/apache/nifi/pull/1636#discussion_r110950968
  
--- Diff: 
nifi-nar-bundles/nifi-azure-bundle/nifi-azure-processors/src/main/resources/docs/org.apache.nifi.processors.azure.storage.FetchAzureBlobStorage/additionalDetails.html
 ---
@@ -0,0 +1,39 @@
+
+
+
+
+
+FetchAzureBlobStorage Processor
+
+
+
+
+
+Apache NiFi Azure Processors
+
+Important Security Note
--- End diff --

Since these are important security notices, should they be presented in the 
main documentation of the processor, rather than additional details?


---
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 #1636: NIFI-1833 - Azure Storage processors

[jtstorck]

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

https://github.com/apache/nifi/pull/1636#discussion_r110950578
  
--- Diff: 
nifi-nar-bundles/nifi-azure-bundle/nifi-azure-processors/src/main/java/org/apache/nifi/processors/azure/storage/PutAzureBlobStorage.java
 ---
@@ -0,0 +1,116 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.azure.storage;
+
+import java.io.BufferedInputStream;
+import java.io.IOException;
+import java.io.InputStream;
+import java.net.URISyntaxException;
+import java.util.HashMap;
+import java.util.Map;
+import java.util.concurrent.TimeUnit;
+
+import org.apache.nifi.annotation.behavior.InputRequirement;
+import org.apache.nifi.annotation.behavior.InputRequirement.Requirement;
+import org.apache.nifi.annotation.behavior.WritesAttribute;
+import org.apache.nifi.annotation.behavior.WritesAttributes;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.SeeAlso;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.ProcessSession;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processors.azure.AbstractAzureBlobProcessor;
+import org.apache.nifi.processors.azure.AzureConstants;
+
+import com.microsoft.azure.storage.CloudStorageAccount;
+import com.microsoft.azure.storage.StorageException;
+import com.microsoft.azure.storage.blob.BlobProperties;
+import com.microsoft.azure.storage.blob.CloudBlob;
+import com.microsoft.azure.storage.blob.CloudBlobClient;
+import com.microsoft.azure.storage.blob.CloudBlobContainer;
+
+@Tags({ "azure", "microsoft", "cloud", "storage", "blob" })
+@SeeAlso({ ListAzureBlobStorage.class, FetchAzureBlobStorage.class })
+@CapabilityDescription("Puts content into an Azure Storage Blob")
--- End diff --

Should this be changed to say "Azure Storage Container"?



---
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 #1636: NIFI-1833 - Azure Storage processors

[jtstorck]

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

https://github.com/apache/nifi/pull/1636#discussion_r110950260
  
--- Diff: 
nifi-nar-bundles/nifi-azure-bundle/nifi-azure-processors/src/main/java/org/apache/nifi/processors/azure/storage/ListAzureBlobStorage.java
 ---
@@ -0,0 +1,180 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.azure.storage;
+
+import java.io.IOException;
+import java.net.URISyntaxException;
+import java.security.InvalidKeyException;
+import java.util.ArrayList;
+import java.util.Arrays;
+import java.util.Collections;
+import java.util.EnumSet;
+import java.util.HashMap;
+import java.util.List;
+import java.util.Map;
+
+import org.apache.nifi.annotation.behavior.InputRequirement;
+import org.apache.nifi.annotation.behavior.InputRequirement.Requirement;
+import org.apache.nifi.annotation.behavior.Stateful;
+import org.apache.nifi.annotation.behavior.TriggerSerially;
+import org.apache.nifi.annotation.behavior.WritesAttribute;
+import org.apache.nifi.annotation.behavior.WritesAttributes;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.SeeAlso;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.components.state.Scope;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.util.StandardValidators;
+import org.apache.nifi.processors.azure.AzureConstants;
+import org.apache.nifi.processors.azure.storage.utils.BlobInfo;
+import org.apache.nifi.processors.azure.storage.utils.BlobInfo.Builder;
+import org.apache.nifi.processors.standard.AbstractListProcessor;
+
+import com.microsoft.azure.storage.CloudStorageAccount;
+import com.microsoft.azure.storage.StorageException;
+import com.microsoft.azure.storage.StorageUri;
+import com.microsoft.azure.storage.blob.BlobListingDetails;
+import com.microsoft.azure.storage.blob.BlobProperties;
+import com.microsoft.azure.storage.blob.CloudBlob;
+import com.microsoft.azure.storage.blob.CloudBlobClient;
+import com.microsoft.azure.storage.blob.CloudBlobContainer;
+import com.microsoft.azure.storage.blob.CloudBlockBlob;
+import com.microsoft.azure.storage.blob.ListBlobItem;
+
+@TriggerSerially
+@Tags({ "azure", "microsoft", "cloud", "storage", "blob" })
+@SeeAlso({ FetchAzureBlobStorage.class, PutAzureBlobStorage.class })
+@CapabilityDescription("Lists blobs in an Azure Storage container. Listing 
details are attached to an empty FlowFile for use with FetchAzureBlobStorage")
--- End diff --

Container should be capitalized here, flowfile lowercased?


---
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 #78: MINIFI-265: Add conditional statement for ...

[apiri]

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

https://github.com/apache/nifi-minifi-cpp/pull/78#discussion_r110945727
  
--- Diff: docs/Doxyfile ---
@@ -0,0 +1,2474 @@
+# Doxyfile 1.8.13
--- End diff --

Will need Apache License on this file


---
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-2323) Improve handling of Oracle datetime columns in QueryDatabaseTable and GenerateTableFetch

[Matt Burgess (JIRA)]

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

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

> Improve handling of Oracle datetime columns in QueryDatabaseTable and 
> GenerateTableFetch
> 
>
> Key: NIFI-2323
> URL: https://issues.apache.org/jira/browse/NIFI-2323
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 0.6.0
>Reporter: Matt Burgess
>Assignee: Matt Burgess
>
> Due to default handling of Oracle columns returned as java.sql.Date types, 
> the string literals used to compare against the column values must be in the 
> same format as the NLS_DATE_FORMAT setting of the database (often -MM-DD).
> I believe when "Oracle" is provided as the database type (formerly known as 
> pre-processing strategy), Oracle's Datetime Functions (such as TO_DATE or 
> TO_TIMESTAMP) could be leveraged to give more fine-grained maximum-value 
> information.



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

[jira] [Commented] (NIFI-2323) Improve handling of Oracle datetime columns in QueryDatabaseTable and GenerateTableFetch

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2323:
--

GitHub user mattyb149 opened a pull request:

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

NIFI-2323: Fixed Oracle timestamp handling in DB fetch processors

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/mattyb149/nifi NIFI-2323

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

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


commit 5d163b7061e4d12269db7c514fa15052df4553ad
Author: Matt Burgess 
Date:   2017-04-11T16:00:31Z

NIFI-2323: Fixed Oracle timestamp handling in DB fetch processors




> Improve handling of Oracle datetime columns in QueryDatabaseTable and 
> GenerateTableFetch
> 
>
> Key: NIFI-2323
> URL: https://issues.apache.org/jira/browse/NIFI-2323
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 0.6.0
>Reporter: Matt Burgess
>Assignee: Matt Burgess
>
> Due to default handling of Oracle columns returned as java.sql.Date types, 
> the string literals used to compare against the column values must be in the 
> same format as the NLS_DATE_FORMAT setting of the database (often -MM-DD).
> I believe when "Oracle" is provided as the database type (formerly known as 
> pre-processing strategy), Oracle's Datetime Functions (such as TO_DATE or 
> TO_TIMESTAMP) could be leveraged to give more fine-grained maximum-value 
> information.



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

[GitHub] nifi pull request #1664: NIFI-2323: Fixed Oracle timestamp handling in DB fe...

[mattyb149]

GitHub user mattyb149 opened a pull request:

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

NIFI-2323: Fixed Oracle timestamp handling in DB fetch processors

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/mattyb149/nifi NIFI-2323

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

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


commit 5d163b7061e4d12269db7c514fa15052df4553ad
Author: Matt Burgess 
Date:   2017-04-11T16:00:31Z

NIFI-2323: Fixed Oracle timestamp handling in DB fetch processors




---
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-3690) nifi-gcp-bundle contains undeclared (L&N) dependencies

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-3690:
---

[~jameswing] i am ok with you pulling it out.  However, the JSON thing is easy 
to workaround ( i believe) because we will do a binary exclusion of the 
offending artifact and pull in a new cleanroom one that should work.

As for the other dependencies yes we need to make sure the binary artifact L&N 
of the nar itself (and if anything needing rollup) is covered.  There are a 
very large number of dependencies in here.  Not sure if all are L&N friendly or 
not but we need to check every one of them and update the L&N as appropriate.

If you decide to pull it out for now so that can get done on a less tight 
timeline we'll be good that way too.

Thanks
Joe

> nifi-gcp-bundle contains undeclared (L&N) dependencies
> --
>
> Key: NIFI-3690
> URL: https://issues.apache.org/jira/browse/NIFI-3690
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Joseph Witt
>Priority: Blocker
> Fix For: 1.2.0
>
>
> [~gene-telligentdata] [~jameswing] In working NIFI-3089 I found the 
> nifi-gcp-nar. It contained a transitive dependency on org.json library which 
> is Category X for apache so must be removed.  I've got that address in 
> NIFI-3089 and will have a PR for that soon.  
> However, in looking at the L&N for the nar itself there are a ton of 
> dependencies in the nar and they're not referenced in the nar's L&N.  We must 
> resolve this before nifi-gcp-nar can be released w/NiFi.



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

[jira] [Commented] (NIFI-3692) Use hbc-core instead of hbc-twitter4j in social-media bundle to resolve org.json cat-x

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-3692:
---

assinging to myself - will review.  THANKS JOEY!

> Use hbc-core instead of hbc-twitter4j in social-media bundle to resolve 
> org.json cat-x
> --
>
> Key: NIFI-3692
> URL: https://issues.apache.org/jira/browse/NIFI-3692
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Joey Frazee
>Assignee: Joseph Witt
>
> The GetTwitter processor in the social-media bundle is (unnecessarily) using 
> hbc-twitter4j to consume the Twitter stream, which means it pulls in 
> Twitter4j binary, creating a problem for the org.json cat-x decision. 
> GetTwitter does not make use of any Twitter4j classes or helpers though so 
> it's completely unnecessary and we can back off to using hbc-core instead.



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

[jira] [Assigned] (NIFI-3692) Use hbc-core instead of hbc-twitter4j in social-media bundle to resolve org.json cat-x

[Joseph Witt (JIRA)]

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

Joseph Witt reassigned NIFI-3692:
-

Assignee: Joseph Witt  (was: Joey Frazee)

> Use hbc-core instead of hbc-twitter4j in social-media bundle to resolve 
> org.json cat-x
> --
>
> Key: NIFI-3692
> URL: https://issues.apache.org/jira/browse/NIFI-3692
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Joey Frazee
>Assignee: Joseph Witt
>
> The GetTwitter processor in the social-media bundle is (unnecessarily) using 
> hbc-twitter4j to consume the Twitter stream, which means it pulls in 
> Twitter4j binary, creating a problem for the org.json cat-x decision. 
> GetTwitter does not make use of any Twitter4j classes or helpers though so 
> it's completely unnecessary and we can back off to using hbc-core instead.



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

[jira] [Assigned] (NIFI-2323) Improve handling of Oracle datetime columns in QueryDatabaseTable and GenerateTableFetch

[Matt Burgess (JIRA)]

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

Matt Burgess reassigned NIFI-2323:
--

Assignee: Matt Burgess

> Improve handling of Oracle datetime columns in QueryDatabaseTable and 
> GenerateTableFetch
> 
>
> Key: NIFI-2323
> URL: https://issues.apache.org/jira/browse/NIFI-2323
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 0.6.0
>Reporter: Matt Burgess
>Assignee: Matt Burgess
>
> Due to default handling of Oracle columns returned as java.sql.Date types, 
> the string literals used to compare against the column values must be in the 
> same format as the NLS_DATE_FORMAT setting of the database (often -MM-DD).
> I believe when "Oracle" is provided as the database type (formerly known as 
> pre-processing strategy), Oracle's Datetime Functions (such as TO_DATE or 
> TO_TIMESTAMP) could be leveraged to give more fine-grained maximum-value 
> information.



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

[jira] [Commented] (NIFI-3690) nifi-gcp-bundle contains undeclared (L&N) dependencies

[James Wing (JIRA)]

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

James Wing commented on NIFI-3690:
--

[~joewitt], to clarify, this ticket is about the incomplete recognition of 
transitive dependencies in the nifi-gcp-nar LICENSE and NOTICE.  It can be 
resolved by expanding on the LICENSE and NOTICE.  Is that correct?

But isn't the transitive JSON.org dependency a hard obstacle?  I do not 
understand what you will resolve in NIFI-3089 with a PR.

The obvious immediate resolution to both issues is to un-merge the nifi-gcp-nar 
until we are comfortable with it, and so it will not constrain a 1.2.0 release. 
 I plan to do this unless you are looking for a different resolution.

> nifi-gcp-bundle contains undeclared (L&N) dependencies
> --
>
> Key: NIFI-3690
> URL: https://issues.apache.org/jira/browse/NIFI-3690
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Joseph Witt
>Priority: Blocker
> Fix For: 1.2.0
>
>
> [~gene-telligentdata] [~jameswing] In working NIFI-3089 I found the 
> nifi-gcp-nar. It contained a transitive dependency on org.json library which 
> is Category X for apache so must be removed.  I've got that address in 
> NIFI-3089 and will have a PR for that soon.  
> However, in looking at the L&N for the nar itself there are a ton of 
> dependencies in the nar and they're not referenced in the nar's L&N.  We must 
> resolve this before nifi-gcp-nar can be released w/NiFi.



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

[GitHub] nifi pull request #1663: NIFI-3692 Use hbc-core instead of hbc-twitter4j in ...

[jfrazee]

GitHub user jfrazee opened a pull request:

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

NIFI-3692 Use hbc-core instead of hbc-twitter4j in social-media bundle to 
resolve org.json cat-x

Note: We can't remove Twitter4j from nifi-assembly/NOTICE until 
[NIFI-3018](https://issues.apache.org/jira/browse/NIFI-3018) is complete. 

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

$ git pull https://github.com/jfrazee/nifi NIFI-3692

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

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


commit 2c3a1215ccee9edd213a55dba0d78a9407b36413
Author: Joey Frazee 
Date:   2017-04-11T15:19:44Z

NIFI-3692 Use hbc-core instead of hbc-twitter4j in social-media bundle to 
resolve org.json cat-x




---
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-3692) Use hbc-core instead of hbc-twitter4j in social-media bundle to resolve org.json cat-x

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3692:
--

GitHub user jfrazee opened a pull request:

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

NIFI-3692 Use hbc-core instead of hbc-twitter4j in social-media bundle to 
resolve org.json cat-x

Note: We can't remove Twitter4j from nifi-assembly/NOTICE until 
[NIFI-3018](https://issues.apache.org/jira/browse/NIFI-3018) is complete. 

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

$ git pull https://github.com/jfrazee/nifi NIFI-3692

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

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


commit 2c3a1215ccee9edd213a55dba0d78a9407b36413
Author: Joey Frazee 
Date:   2017-04-11T15:19:44Z

NIFI-3692 Use hbc-core instead of hbc-twitter4j in social-media bundle to 
resolve org.json cat-x




> Use hbc-core instead of hbc-twitter4j in social-media bundle to resolve 
> org.json cat-x
> --
>
> Key: NIFI-3692
> URL: https://issues.apache.org/jira/browse/NIFI-3692
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Joey Frazee
>Assignee: Joey Frazee
>
> The GetTwitter processor in the social-media bundle is (unnecessarily) using 
> hbc-twitter4j to consume the Twitter stream, which means it pulls in 
> Twitter4j binary, creating a problem for the org.json cat-x decision. 
> GetTwitter does not make use of any Twitter4j classes or helpers though so 
> it's completely unnecessary and we can back off to using hbc-core instead.



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

[GitHub] nifi-minifi-cpp pull request #78: MINIFI-265: Add conditional statement for ...

[phrocker]

GitHub user phrocker opened a pull request:

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

MINIFI-265: Add conditional statement for doc generatin

If Doxygen is installed you can run make docs to generate
HTML and LaTeX output.

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

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

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

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

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

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

### For code changes:
- [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the LICENSE file?
- [ ] If applicable, have you updated the NOTICE file?

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

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


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

$ git pull https://github.com/phrocker/nifi-minifi-cpp MINIFI-265

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

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


commit a4ccfe88be01844f4e4941f5a5aca990e53dfc63
Author: Marc Parisi 
Date:   2017-04-11T15:13:58Z

MINIFI-265: Add conditional statement for doc generatin

If Doxygen is installed you can run make docs to generate
HTML and LaTeX output.




---
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-3692) Use hbc-core instead of hbc-twitter4j in social-media bundle to resolve org.json cat-x

[Joey Frazee (JIRA)]

Joey Frazee created NIFI-3692:
-

 Summary: Use hbc-core instead of hbc-twitter4j in social-media 
bundle to resolve org.json cat-x
 Key: NIFI-3692
 URL: https://issues.apache.org/jira/browse/NIFI-3692
 Project: Apache NiFi
  Issue Type: Improvement
Reporter: Joey Frazee
Assignee: Joey Frazee


The GetTwitter processor in the social-media bundle is (unnecessarily) using 
hbc-twitter4j to consume the Twitter stream, which means it pulls in Twitter4j 
binary, creating a problem for the org.json cat-x decision. 

GetTwitter does not make use of any Twitter4j classes or helpers though so it's 
completely unnecessary and we can back off to using hbc-core instead.



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

[jira] [Resolved] (NIFIREG-2) Design logo for Registry

[Rob Moran (JIRA)]

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

Rob Moran resolved NIFIREG-2.
-
Resolution: Done

> Design logo for Registry
> 
>
> Key: NIFIREG-2
> URL: https://issues.apache.org/jira/browse/NIFIREG-2
> Project: NiFi Registry
>  Issue Type: Task
>Reporter: Rob Moran
>Assignee: Rob Moran
>Priority: Minor
> Attachments: registry-logo-horizontal.png, 
> registry-logo-horizontal-small.png, registry-logo-mark.png, 
> registry-logo-mark-small.png, registry-logo.png, registry-logo-samples.png, 
> registry-logo-source-file.zip, registry-site-header-logo.svg
>
>
> The attached image contains the proposed logo design for Registry. The points 
> below describe some of the thinking behind it:
> * Relationship to NiFi and MiNiFi through the use of the same color palette, 
> typeface, and block elements representing bits of data
> * For Registry these blocks also represent the storage/organization aspect 
> through their even distribution and arrangement
> * The 3 gradated blocks across the top – forming the terminal part of a 
> lowercase *r* – represent movement (e.g., a versioned flow being saved to 
> NiFi or imported to NiFi from the registry)
> * Relating back to the original water/flow concept of NiFi, the curved line 
> integrated into the gradated blocks represent the continuous motion of 
> flowing water
> * The light gray block helps with idea of storage as previously mentioned, 
> but also alludes to unused storage/free space
> * The gray block also helps establish the strong diagonal slicing through it 
> and the lowest green block. Again this helps with the idea of movement, but 
> more so speaks to how Registry operates in the background, tucked away, 
> largely unseen by NiFi operators as it facilitates deployment tasks



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

[jira] [Updated] (NIFIREG-2) Design logo for Registry

[Rob Moran (JIRA)]

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

Rob Moran updated NIFIREG-2:

Attachment: registry-logo-source-file.zip

I've also attached the source file (Adobe Illustrator CC _.ai_ file)

> Design logo for Registry
> 
>
> Key: NIFIREG-2
> URL: https://issues.apache.org/jira/browse/NIFIREG-2
> Project: NiFi Registry
>  Issue Type: Task
>Reporter: Rob Moran
>Assignee: Rob Moran
>Priority: Minor
> Attachments: registry-logo-horizontal.png, 
> registry-logo-horizontal-small.png, registry-logo-mark.png, 
> registry-logo-mark-small.png, registry-logo.png, registry-logo-samples.png, 
> registry-logo-source-file.zip, registry-site-header-logo.svg
>
>
> The attached image contains the proposed logo design for Registry. The points 
> below describe some of the thinking behind it:
> * Relationship to NiFi and MiNiFi through the use of the same color palette, 
> typeface, and block elements representing bits of data
> * For Registry these blocks also represent the storage/organization aspect 
> through their even distribution and arrangement
> * The 3 gradated blocks across the top – forming the terminal part of a 
> lowercase *r* – represent movement (e.g., a versioned flow being saved to 
> NiFi or imported to NiFi from the registry)
> * Relating back to the original water/flow concept of NiFi, the curved line 
> integrated into the gradated blocks represent the continuous motion of 
> flowing water
> * The light gray block helps with idea of storage as previously mentioned, 
> but also alludes to unused storage/free space
> * The gray block also helps establish the strong diagonal slicing through it 
> and the lowest green block. Again this helps with the idea of movement, but 
> more so speaks to how Registry operates in the background, tucked away, 
> largely unseen by NiFi operators as it facilitates deployment tasks



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

[jira] [Updated] (NIFIREG-2) Design logo for Registry

[Rob Moran (JIRA)]

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

Rob Moran updated NIFIREG-2:

Attachment: registry-site-header-logo.svg
registry-logo.png
registry-logo-samples.png
registry-logo-mark.png
registry-logo-mark-small.png
registry-logo-horizontal.png
registry-logo-horizontal-small.png

I've finalized the logo and created multiple variations to best suit how they 
are displayed. Refer to _registry-logo-samples.png_ for details.

[~andrewmlim] there is an SVG attached for use in the header of the website.

> Design logo for Registry
> 
>
> Key: NIFIREG-2
> URL: https://issues.apache.org/jira/browse/NIFIREG-2
> Project: NiFi Registry
>  Issue Type: Task
>Reporter: Rob Moran
>Assignee: Rob Moran
>Priority: Minor
> Attachments: registry-logo-horizontal.png, 
> registry-logo-horizontal-small.png, registry-logo-mark.png, 
> registry-logo-mark-small.png, registry-logo.png, registry-logo-samples.png, 
> registry-site-header-logo.svg
>
>
> The attached image contains the proposed logo design for Registry. The points 
> below describe some of the thinking behind it:
> * Relationship to NiFi and MiNiFi through the use of the same color palette, 
> typeface, and block elements representing bits of data
> * For Registry these blocks also represent the storage/organization aspect 
> through their even distribution and arrangement
> * The 3 gradated blocks across the top – forming the terminal part of a 
> lowercase *r* – represent movement (e.g., a versioned flow being saved to 
> NiFi or imported to NiFi from the registry)
> * Relating back to the original water/flow concept of NiFi, the curved line 
> integrated into the gradated blocks represent the continuous motion of 
> flowing water
> * The light gray block helps with idea of storage as previously mentioned, 
> but also alludes to unused storage/free space
> * The gray block also helps establish the strong diagonal slicing through it 
> and the lowest green block. Again this helps with the idea of movement, but 
> more so speaks to how Registry operates in the background, tucked away, 
> largely unseen by NiFi operators as it facilitates deployment tasks



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

[jira] [Updated] (NIFIREG-2) Design logo for Registry

[Rob Moran (JIRA)]

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

Rob Moran updated NIFIREG-2:

Attachment: (was: registry-logo-concept_2017-03-27.png)

> Design logo for Registry
> 
>
> Key: NIFIREG-2
> URL: https://issues.apache.org/jira/browse/NIFIREG-2
> Project: NiFi Registry
>  Issue Type: Task
>Reporter: Rob Moran
>Assignee: Rob Moran
>Priority: Minor
>
> The attached image contains the proposed logo design for Registry. The points 
> below describe some of the thinking behind it:
> * Relationship to NiFi and MiNiFi through the use of the same color palette, 
> typeface, and block elements representing bits of data
> * For Registry these blocks also represent the storage/organization aspect 
> through their even distribution and arrangement
> * The 3 gradated blocks across the top – forming the terminal part of a 
> lowercase *r* – represent movement (e.g., a versioned flow being saved to 
> NiFi or imported to NiFi from the registry)
> * Relating back to the original water/flow concept of NiFi, the curved line 
> integrated into the gradated blocks represent the continuous motion of 
> flowing water
> * The light gray block helps with idea of storage as previously mentioned, 
> but also alludes to unused storage/free space
> * The gray block also helps establish the strong diagonal slicing through it 
> and the lowest green block. Again this helps with the idea of movement, but 
> more so speaks to how Registry operates in the background, tucked away, 
> largely unseen by NiFi operators as it facilitates deployment tasks



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

[jira] [Updated] (NIFIREG-2) Design logo for Registry

[Rob Moran (JIRA)]

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

Rob Moran updated NIFIREG-2:

Attachment: (was: registry-logo-concept_2017-03-30.png)

> Design logo for Registry
> 
>
> Key: NIFIREG-2
> URL: https://issues.apache.org/jira/browse/NIFIREG-2
> Project: NiFi Registry
>  Issue Type: Task
>Reporter: Rob Moran
>Assignee: Rob Moran
>Priority: Minor
>
> The attached image contains the proposed logo design for Registry. The points 
> below describe some of the thinking behind it:
> * Relationship to NiFi and MiNiFi through the use of the same color palette, 
> typeface, and block elements representing bits of data
> * For Registry these blocks also represent the storage/organization aspect 
> through their even distribution and arrangement
> * The 3 gradated blocks across the top – forming the terminal part of a 
> lowercase *r* – represent movement (e.g., a versioned flow being saved to 
> NiFi or imported to NiFi from the registry)
> * Relating back to the original water/flow concept of NiFi, the curved line 
> integrated into the gradated blocks represent the continuous motion of 
> flowing water
> * The light gray block helps with idea of storage as previously mentioned, 
> but also alludes to unused storage/free space
> * The gray block also helps establish the strong diagonal slicing through it 
> and the lowest green block. Again this helps with the idea of movement, but 
> more so speaks to how Registry operates in the background, tucked away, 
> largely unseen by NiFi operators as it facilitates deployment tasks



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

[jira] [Commented] (NIFI-3035) URL to display a particular process group in UI

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3035:
--

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

https://github.com/apache/nifi/pull/1659#discussion_r110898619
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/src/main/webapp/js/nf/canvas/nf-canvas-utils.js
 ---
@@ -412,9 +412,9 @@
 
 // create object whose keys are the parameter name and the 
values are the parameter values
 var paramsObject = {};
-params.forEach(function (v, k) {
-paramsObject[k] = v;
-});
+for(var pair of params.entries()) {
--- End diff --

:)


> URL to display a particular process group in UI
> ---
>
> Key: NIFI-3035
> URL: https://issues.apache.org/jira/browse/NIFI-3035
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Core UI
>Reporter: Christine Draper
>Assignee: Scott Aslan
> Fix For: 1.2.0
>
>
> Our use case has multiple teams of users working on specific process groups. 
> We would like to be able to give them a URL that will launch the UI on the 
> specific group they are working on, rather than them having to navigate to it 
> from the root group.



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

[GitHub] nifi pull request #1659: [NIFI-3035] use URLSearchParams .toString() to upda...

[scottyaslan]

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

https://github.com/apache/nifi/pull/1659#discussion_r110898619
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/src/main/webapp/js/nf/canvas/nf-canvas-utils.js
 ---
@@ -412,9 +412,9 @@
 
 // create object whose keys are the parameter name and the 
values are the parameter values
 var paramsObject = {};
-params.forEach(function (v, k) {
-paramsObject[k] = v;
-});
+for(var pair of params.entries()) {
--- End diff --

:)


---
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 #76: MINIFI-261: Allow std::string to be used f...

[asfgit]

Github user asfgit closed the pull request at:

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


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

[GitHub] nifi-minifi-cpp issue #76: MINIFI-261: Allow std::string to be used for log ...

[apiri]

Github user apiri commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/76
  
changes and tests look good.  definitely like the convenience.  will get 
this merged.


---
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-3691) Provide utility to verify configured security settings and certificates

[Aldrin Piri (JIRA)]

Aldrin Piri created NIFI-3691:
-

 Summary: Provide utility to verify configured security settings 
and certificates
 Key: NIFI-3691
 URL: https://issues.apache.org/jira/browse/NIFI-3691
 Project: Apache NiFi
  Issue Type: Sub-task
  Components: Configuration
Reporter: Aldrin Piri


It would be helpful to provide a utility that could analyze 
keystores/truststores to verify compatibility and expected behavior with 
configured security settings such as two way SSL (right hostname, alias, etc).  
The idea is that as a diagnostic tool, we could provide users with some help to 
verify and troubleshoot any issues that may exist with certificates outside of 
more expensive change/restart loops with NiFi.  As a follow-on, it would be 
helpful to get a listing of key properties about the configured 
keystore/truststore or files provided.  An extension of this might additionally 
setup a client/server test with the utility between instances, again, to verify 
correct operation without doing so in NiFi itself as suggested by the parent 
ticket.

It would be nice to provide this as part of the NiFi release and accessible via 
nifi.sh.  By extension, the functionality could also appear in the TLS toolkit. 
 



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

[jira] [Resolved] (NIFI-3561) JettyWebSocketServer uses original requested port, instead of the forwarded port

[Andre F de Miranda (JIRA)]

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

Andre F de Miranda resolved NIFI-3561.
--
Resolution: Fixed

> JettyWebSocketServer uses original requested port, instead of the forwarded 
> port
> 
>
> Key: NIFI-3561
> URL: https://issues.apache.org/jira/browse/NIFI-3561
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.1.0
>Reporter: Edgar Orendain
>Assignee: Koji Kawamura
>  Labels: jetty, websocket
> Fix For: 1.2.0
>
>
> Situation:
> We have port forwarding set up in such a way where port 25000 is forwarded to 
> port 15000.  ListenWebSocket processor listens on this 15000 port.
> Requests that hit the JettyWebSocketServer are considered as attempting to 
> connect to the original port (25000) rather than the forwarded port of 15000. 
>  The same was reproduced with different ports and on different forwarding 
> layers (i.e. NAT and iptables).  I've included a stack trace below.
> From Koji:
> -I think it's more of a Jetty side issue, after it upgrade HTTP connection to 
> TCP, it still uses the original requested port (which is a port forwarding 
> request to the real port) to find a request handler assigned to that port.-
> (updated) Excuse me, but I was wrong about this diagnose. It's a problem in 
> NiFi JettyWebSocketServer I wrote. The ControllerService lookups server 
> instance by a port number that the CS listens to. When a request made through 
> port forwarding, a port passed by ServletUpgradeRequest is different than CS 
> is bounded to. Then it fails to lookup a server instance. I will check if 
> original port can be retrieved from a request, if not, I will add a 
> configuration property to the CS to specify forwarding port numbers.
> java.lang.RuntimeException: No controller service is bound with port: 25000
> at 
> org.apache.nifi.websocket.jetty.JettyWebSocketServer$JettyWebSocketServlet.createWebSocket(JettyWebSocketServer.java:134)
>  ~[nifi-websocket-services-jetty-1.1.0.2.1.2.0-10.jar:1.1.0.2.1.2.0-10]
> at 
> org.eclipse.jetty.websocket.server.WebSocketServerFactory.acceptWebSocket(WebSocketServerFactory.java:187)
>  ~[websocket-server-9.3.13.v20161014.jar:9.3.13.v20161014]
> at 
> org.eclipse.jetty.websocket.server.WebSocketServerFactory.acceptWebSocket(WebSocketServerFactory.java:172)
>  ~[websocket-server-9.3.13.v20161014.jar:9.3.13.v20161014]
> at 
> org.eclipse.jetty.websocket.servlet.WebSocketServlet.service(WebSocketServlet.java:155)
>  ~[websocket-servlet-9.3.13.v20161014.jar:9.3.13.v20161014]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) 
> ~[javax.servlet-api-3.1.0.jar:3.1.0]
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845) 
> ~[jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583) 
> [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1174)
>  [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511) 
> [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1106)
>  [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) 
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213)
>  [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
>  [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.server.Server.handle(Server.java:524) 
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:319) 
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:253) 
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)
>  [jetty-io-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95) 
> [jetty-io-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)
>  [jetty-io-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)
>  [jetty-util-9.3.9.v2016051

[jira] [Commented] (NIFI-3561) JettyWebSocketServer uses original requested port, instead of the forwarded port

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3561:
--

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/1568
  
@ijokarumawak thanks for fixing this. merged


> JettyWebSocketServer uses original requested port, instead of the forwarded 
> port
> 
>
> Key: NIFI-3561
> URL: https://issues.apache.org/jira/browse/NIFI-3561
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.1.0
>Reporter: Edgar Orendain
>Assignee: Koji Kawamura
>  Labels: jetty, websocket
> Fix For: 1.2.0
>
>
> Situation:
> We have port forwarding set up in such a way where port 25000 is forwarded to 
> port 15000.  ListenWebSocket processor listens on this 15000 port.
> Requests that hit the JettyWebSocketServer are considered as attempting to 
> connect to the original port (25000) rather than the forwarded port of 15000. 
>  The same was reproduced with different ports and on different forwarding 
> layers (i.e. NAT and iptables).  I've included a stack trace below.
> From Koji:
> -I think it's more of a Jetty side issue, after it upgrade HTTP connection to 
> TCP, it still uses the original requested port (which is a port forwarding 
> request to the real port) to find a request handler assigned to that port.-
> (updated) Excuse me, but I was wrong about this diagnose. It's a problem in 
> NiFi JettyWebSocketServer I wrote. The ControllerService lookups server 
> instance by a port number that the CS listens to. When a request made through 
> port forwarding, a port passed by ServletUpgradeRequest is different than CS 
> is bounded to. Then it fails to lookup a server instance. I will check if 
> original port can be retrieved from a request, if not, I will add a 
> configuration property to the CS to specify forwarding port numbers.
> java.lang.RuntimeException: No controller service is bound with port: 25000
> at 
> org.apache.nifi.websocket.jetty.JettyWebSocketServer$JettyWebSocketServlet.createWebSocket(JettyWebSocketServer.java:134)
>  ~[nifi-websocket-services-jetty-1.1.0.2.1.2.0-10.jar:1.1.0.2.1.2.0-10]
> at 
> org.eclipse.jetty.websocket.server.WebSocketServerFactory.acceptWebSocket(WebSocketServerFactory.java:187)
>  ~[websocket-server-9.3.13.v20161014.jar:9.3.13.v20161014]
> at 
> org.eclipse.jetty.websocket.server.WebSocketServerFactory.acceptWebSocket(WebSocketServerFactory.java:172)
>  ~[websocket-server-9.3.13.v20161014.jar:9.3.13.v20161014]
> at 
> org.eclipse.jetty.websocket.servlet.WebSocketServlet.service(WebSocketServlet.java:155)
>  ~[websocket-servlet-9.3.13.v20161014.jar:9.3.13.v20161014]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) 
> ~[javax.servlet-api-3.1.0.jar:3.1.0]
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845) 
> ~[jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583) 
> [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1174)
>  [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511) 
> [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1106)
>  [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) 
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213)
>  [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
>  [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.server.Server.handle(Server.java:524) 
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:319) 
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:253) 
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)
>  [jetty-io-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95) 
> [jetty-io-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)
>  [jetty-io-9.3.9.v20160517.jar:

[GitHub] nifi issue #1568: NIFI-3561: Fix WS port forwarding

[trixpan]

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/1568
  
@ijokarumawak thanks for fixing this. merged


---
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] [Reopened] (NIFI-3561) JettyWebSocketServer uses original requested port, instead of the forwarded port

[Andre F de Miranda (JIRA)]

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

Andre F de Miranda reopened NIFI-3561:
--

> JettyWebSocketServer uses original requested port, instead of the forwarded 
> port
> 
>
> Key: NIFI-3561
> URL: https://issues.apache.org/jira/browse/NIFI-3561
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.1.0
>Reporter: Edgar Orendain
>Assignee: Koji Kawamura
>  Labels: jetty, websocket
> Fix For: 1.2.0
>
>
> Situation:
> We have port forwarding set up in such a way where port 25000 is forwarded to 
> port 15000.  ListenWebSocket processor listens on this 15000 port.
> Requests that hit the JettyWebSocketServer are considered as attempting to 
> connect to the original port (25000) rather than the forwarded port of 15000. 
>  The same was reproduced with different ports and on different forwarding 
> layers (i.e. NAT and iptables).  I've included a stack trace below.
> From Koji:
> -I think it's more of a Jetty side issue, after it upgrade HTTP connection to 
> TCP, it still uses the original requested port (which is a port forwarding 
> request to the real port) to find a request handler assigned to that port.-
> (updated) Excuse me, but I was wrong about this diagnose. It's a problem in 
> NiFi JettyWebSocketServer I wrote. The ControllerService lookups server 
> instance by a port number that the CS listens to. When a request made through 
> port forwarding, a port passed by ServletUpgradeRequest is different than CS 
> is bounded to. Then it fails to lookup a server instance. I will check if 
> original port can be retrieved from a request, if not, I will add a 
> configuration property to the CS to specify forwarding port numbers.
> java.lang.RuntimeException: No controller service is bound with port: 25000
> at 
> org.apache.nifi.websocket.jetty.JettyWebSocketServer$JettyWebSocketServlet.createWebSocket(JettyWebSocketServer.java:134)
>  ~[nifi-websocket-services-jetty-1.1.0.2.1.2.0-10.jar:1.1.0.2.1.2.0-10]
> at 
> org.eclipse.jetty.websocket.server.WebSocketServerFactory.acceptWebSocket(WebSocketServerFactory.java:187)
>  ~[websocket-server-9.3.13.v20161014.jar:9.3.13.v20161014]
> at 
> org.eclipse.jetty.websocket.server.WebSocketServerFactory.acceptWebSocket(WebSocketServerFactory.java:172)
>  ~[websocket-server-9.3.13.v20161014.jar:9.3.13.v20161014]
> at 
> org.eclipse.jetty.websocket.servlet.WebSocketServlet.service(WebSocketServlet.java:155)
>  ~[websocket-servlet-9.3.13.v20161014.jar:9.3.13.v20161014]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) 
> ~[javax.servlet-api-3.1.0.jar:3.1.0]
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845) 
> ~[jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583) 
> [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1174)
>  [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511) 
> [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1106)
>  [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) 
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213)
>  [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
>  [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.server.Server.handle(Server.java:524) 
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:319) 
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:253) 
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)
>  [jetty-io-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95) 
> [jetty-io-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)
>  [jetty-io-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)
>  [jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517]

[jira] [Commented] (NIFI-3561) JettyWebSocketServer uses original requested port, instead of the forwarded port

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3561:
--

Github user asfgit closed the pull request at:

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


> JettyWebSocketServer uses original requested port, instead of the forwarded 
> port
> 
>
> Key: NIFI-3561
> URL: https://issues.apache.org/jira/browse/NIFI-3561
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.1.0
>Reporter: Edgar Orendain
>Assignee: Koji Kawamura
>  Labels: jetty, websocket
> Fix For: 1.2.0
>
>
> Situation:
> We have port forwarding set up in such a way where port 25000 is forwarded to 
> port 15000.  ListenWebSocket processor listens on this 15000 port.
> Requests that hit the JettyWebSocketServer are considered as attempting to 
> connect to the original port (25000) rather than the forwarded port of 15000. 
>  The same was reproduced with different ports and on different forwarding 
> layers (i.e. NAT and iptables).  I've included a stack trace below.
> From Koji:
> -I think it's more of a Jetty side issue, after it upgrade HTTP connection to 
> TCP, it still uses the original requested port (which is a port forwarding 
> request to the real port) to find a request handler assigned to that port.-
> (updated) Excuse me, but I was wrong about this diagnose. It's a problem in 
> NiFi JettyWebSocketServer I wrote. The ControllerService lookups server 
> instance by a port number that the CS listens to. When a request made through 
> port forwarding, a port passed by ServletUpgradeRequest is different than CS 
> is bounded to. Then it fails to lookup a server instance. I will check if 
> original port can be retrieved from a request, if not, I will add a 
> configuration property to the CS to specify forwarding port numbers.
> java.lang.RuntimeException: No controller service is bound with port: 25000
> at 
> org.apache.nifi.websocket.jetty.JettyWebSocketServer$JettyWebSocketServlet.createWebSocket(JettyWebSocketServer.java:134)
>  ~[nifi-websocket-services-jetty-1.1.0.2.1.2.0-10.jar:1.1.0.2.1.2.0-10]
> at 
> org.eclipse.jetty.websocket.server.WebSocketServerFactory.acceptWebSocket(WebSocketServerFactory.java:187)
>  ~[websocket-server-9.3.13.v20161014.jar:9.3.13.v20161014]
> at 
> org.eclipse.jetty.websocket.server.WebSocketServerFactory.acceptWebSocket(WebSocketServerFactory.java:172)
>  ~[websocket-server-9.3.13.v20161014.jar:9.3.13.v20161014]
> at 
> org.eclipse.jetty.websocket.servlet.WebSocketServlet.service(WebSocketServlet.java:155)
>  ~[websocket-servlet-9.3.13.v20161014.jar:9.3.13.v20161014]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) 
> ~[javax.servlet-api-3.1.0.jar:3.1.0]
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845) 
> ~[jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583) 
> [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1174)
>  [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511) 
> [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1106)
>  [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) 
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213)
>  [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
>  [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.server.Server.handle(Server.java:524) 
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:319) 
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:253) 
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)
>  [jetty-io-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95) 
> [jetty-io-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)
>  [jetty-io-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.util.t

[jira] [Commented] (NIFI-3561) JettyWebSocketServer uses original requested port, instead of the forwarded port

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-3561: Fix WS port forwarding

Fixed service instance lookup to use local port so that it works when
it is accessed through port forwarding.

This fixes: #1568

Signed-off-by: Andre F de Miranda 


> JettyWebSocketServer uses original requested port, instead of the forwarded 
> port
> 
>
> Key: NIFI-3561
> URL: https://issues.apache.org/jira/browse/NIFI-3561
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.1.0
>Reporter: Edgar Orendain
>Assignee: Koji Kawamura
>  Labels: jetty, websocket
> Fix For: 1.2.0
>
>
> Situation:
> We have port forwarding set up in such a way where port 25000 is forwarded to 
> port 15000.  ListenWebSocket processor listens on this 15000 port.
> Requests that hit the JettyWebSocketServer are considered as attempting to 
> connect to the original port (25000) rather than the forwarded port of 15000. 
>  The same was reproduced with different ports and on different forwarding 
> layers (i.e. NAT and iptables).  I've included a stack trace below.
> From Koji:
> -I think it's more of a Jetty side issue, after it upgrade HTTP connection to 
> TCP, it still uses the original requested port (which is a port forwarding 
> request to the real port) to find a request handler assigned to that port.-
> (updated) Excuse me, but I was wrong about this diagnose. It's a problem in 
> NiFi JettyWebSocketServer I wrote. The ControllerService lookups server 
> instance by a port number that the CS listens to. When a request made through 
> port forwarding, a port passed by ServletUpgradeRequest is different than CS 
> is bounded to. Then it fails to lookup a server instance. I will check if 
> original port can be retrieved from a request, if not, I will add a 
> configuration property to the CS to specify forwarding port numbers.
> java.lang.RuntimeException: No controller service is bound with port: 25000
> at 
> org.apache.nifi.websocket.jetty.JettyWebSocketServer$JettyWebSocketServlet.createWebSocket(JettyWebSocketServer.java:134)
>  ~[nifi-websocket-services-jetty-1.1.0.2.1.2.0-10.jar:1.1.0.2.1.2.0-10]
> at 
> org.eclipse.jetty.websocket.server.WebSocketServerFactory.acceptWebSocket(WebSocketServerFactory.java:187)
>  ~[websocket-server-9.3.13.v20161014.jar:9.3.13.v20161014]
> at 
> org.eclipse.jetty.websocket.server.WebSocketServerFactory.acceptWebSocket(WebSocketServerFactory.java:172)
>  ~[websocket-server-9.3.13.v20161014.jar:9.3.13.v20161014]
> at 
> org.eclipse.jetty.websocket.servlet.WebSocketServlet.service(WebSocketServlet.java:155)
>  ~[websocket-servlet-9.3.13.v20161014.jar:9.3.13.v20161014]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) 
> ~[javax.servlet-api-3.1.0.jar:3.1.0]
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845) 
> ~[jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583) 
> [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1174)
>  [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511) 
> [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1106)
>  [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) 
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213)
>  [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
>  [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.server.Server.handle(Server.java:524) 
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:319) 
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:253) 
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)
>  [jetty-io-9.3.9.v20160517

[jira] [Updated] (NIFI-3561) JettyWebSocketServer uses original requested port, instead of the forwarded port

[Andre F de Miranda (JIRA)]

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

Andre F de Miranda updated NIFI-3561:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> JettyWebSocketServer uses original requested port, instead of the forwarded 
> port
> 
>
> Key: NIFI-3561
> URL: https://issues.apache.org/jira/browse/NIFI-3561
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.1.0
>Reporter: Edgar Orendain
>Assignee: Koji Kawamura
>  Labels: jetty, websocket
> Fix For: 1.2.0
>
>
> Situation:
> We have port forwarding set up in such a way where port 25000 is forwarded to 
> port 15000.  ListenWebSocket processor listens on this 15000 port.
> Requests that hit the JettyWebSocketServer are considered as attempting to 
> connect to the original port (25000) rather than the forwarded port of 15000. 
>  The same was reproduced with different ports and on different forwarding 
> layers (i.e. NAT and iptables).  I've included a stack trace below.
> From Koji:
> -I think it's more of a Jetty side issue, after it upgrade HTTP connection to 
> TCP, it still uses the original requested port (which is a port forwarding 
> request to the real port) to find a request handler assigned to that port.-
> (updated) Excuse me, but I was wrong about this diagnose. It's a problem in 
> NiFi JettyWebSocketServer I wrote. The ControllerService lookups server 
> instance by a port number that the CS listens to. When a request made through 
> port forwarding, a port passed by ServletUpgradeRequest is different than CS 
> is bounded to. Then it fails to lookup a server instance. I will check if 
> original port can be retrieved from a request, if not, I will add a 
> configuration property to the CS to specify forwarding port numbers.
> java.lang.RuntimeException: No controller service is bound with port: 25000
> at 
> org.apache.nifi.websocket.jetty.JettyWebSocketServer$JettyWebSocketServlet.createWebSocket(JettyWebSocketServer.java:134)
>  ~[nifi-websocket-services-jetty-1.1.0.2.1.2.0-10.jar:1.1.0.2.1.2.0-10]
> at 
> org.eclipse.jetty.websocket.server.WebSocketServerFactory.acceptWebSocket(WebSocketServerFactory.java:187)
>  ~[websocket-server-9.3.13.v20161014.jar:9.3.13.v20161014]
> at 
> org.eclipse.jetty.websocket.server.WebSocketServerFactory.acceptWebSocket(WebSocketServerFactory.java:172)
>  ~[websocket-server-9.3.13.v20161014.jar:9.3.13.v20161014]
> at 
> org.eclipse.jetty.websocket.servlet.WebSocketServlet.service(WebSocketServlet.java:155)
>  ~[websocket-servlet-9.3.13.v20161014.jar:9.3.13.v20161014]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) 
> ~[javax.servlet-api-3.1.0.jar:3.1.0]
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845) 
> ~[jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583) 
> [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1174)
>  [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511) 
> [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1106)
>  [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) 
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213)
>  [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
>  [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.server.Server.handle(Server.java:524) 
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:319) 
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:253) 
> [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)
>  [jetty-io-9.3.9.v20160517.jar:9.3.9.v20160517]
> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95) 
> [jetty-io-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)
>  [jetty-io-9.3.9.v20160517.jar:9.3.9.v20160517]
> at 
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduce

[GitHub] nifi-minifi-cpp issue #76: MINIFI-261: Allow std::string to be used for log ...

[apiri]

Github user apiri commented on the issue:

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


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

[GitHub] nifi pull request #1568: NIFI-3561: Fix WS port forwarding

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-3277) StandardProcessSession.isSpuriousRouteEvent() performance

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3277:
--

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/1390
  
@brosander sorry for the delay but now it seems like this PR has merge 
conflicts. 


> StandardProcessSession.isSpuriousRouteEvent() performance
> -
>
> Key: NIFI-3277
> URL: https://issues.apache.org/jira/browse/NIFI-3277
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
>Priority: Minor
>
> StandardProcessSession.isSpuriousRouteEvent() currently creates a 
> Relationship from a builder and loops over all checkpoint records for every 
> route provenance event generated by the processor.
> This takes nontrivial time and can be mitigated by caching the Relationships 
> and creating a uuid -> StandardFlowFileRecord map on-demand.



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

[GitHub] nifi issue #1390: NIFI-3277 - StandardProcessSession.isSpuriousRouteEvent() ...

[trixpan]

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/1390
  
@brosander sorry for the delay but now it seems like this PR has merge 
conflicts. 


---
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-2860) Use different properties for JVM Heap Max and Min values

[Andre F de Miranda (JIRA)]

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

Andre F de Miranda updated NIFI-2860:
-
   Resolution: Fixed
Fix Version/s: 1.2.0
   Status: Resolved  (was: Patch Available)

> Use different properties for JVM Heap Max and Min values
> 
>
> Key: NIFI-2860
> URL: https://issues.apache.org/jira/browse/NIFI-2860
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Configuration
>Affects Versions: 0.6.1
>Reporter: Andrew Festa
>Assignee: Pierre Villard
> Fix For: 1.2.0
>
>
> In the bootstrap.conf, the JVM memory settings are using maven filtering to 
> set the default values.  Currently the JVM memory settings (java.arg.2 and 
> java.arg.3) are using the same property.  These should be using different 
> values so we can override them to different values.
> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-resources/src/main/resources/conf/bootstrap.conf#L35-L36



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

[jira] [Commented] (NIFI-2860) Use different properties for JVM Heap Max and Min values

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2860 Use different properties for JVM Heap Max and Min values

This closes: #1382

Signed-off-by: Andre F de Miranda 


> Use different properties for JVM Heap Max and Min values
> 
>
> Key: NIFI-2860
> URL: https://issues.apache.org/jira/browse/NIFI-2860
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Configuration
>Affects Versions: 0.6.1
>Reporter: Andrew Festa
>Assignee: Pierre Villard
>
> In the bootstrap.conf, the JVM memory settings are using maven filtering to 
> set the default values.  Currently the JVM memory settings (java.arg.2 and 
> java.arg.3) are using the same property.  These should be using different 
> values so we can override them to different values.
> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-resources/src/main/resources/conf/bootstrap.conf#L35-L36



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

[jira] [Commented] (NIFI-2860) Use different properties for JVM Heap Max and Min values

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2860:
--

Github user asfgit closed the pull request at:

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


> Use different properties for JVM Heap Max and Min values
> 
>
> Key: NIFI-2860
> URL: https://issues.apache.org/jira/browse/NIFI-2860
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Configuration
>Affects Versions: 0.6.1
>Reporter: Andrew Festa
>Assignee: Pierre Villard
>
> In the bootstrap.conf, the JVM memory settings are using maven filtering to 
> set the default values.  Currently the JVM memory settings (java.arg.2 and 
> java.arg.3) are using the same property.  These should be using different 
> values so we can override them to different values.
> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-resources/src/main/resources/conf/bootstrap.conf#L35-L36



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

[GitHub] nifi pull request #1382: NIFI-2860 Use different properties for JVM Heap Max...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-1856) ExecuteStreamCommand Needs to Consume Standard Error

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1856:
--

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/1364
  
@brosander are you still planning to review this at some stage? Happy to 
try to help if needed.

Cheers!


> ExecuteStreamCommand Needs to Consume Standard Error
> 
>
> Key: NIFI-1856
> URL: https://issues.apache.org/jira/browse/NIFI-1856
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Alan Jackoway
>Assignee: Karthik Narayanan
>
> I was using ExecuteStreamProcess to run certain hdfs commands that are tricky 
> to write in nifi but easy in bash (e.g. {{hadoop fs -rm -r 
> /data/*/2014/05/05}})
> However, my larger commands kept hanging even though when I run them from the 
> command line they finish quickly.
> Based on 
> http://www.javaworld.com/article/2071275/core-java/when-runtime-exec---won-t.html
>  I believe that ExecuteStreamCommand and possibly other processors need to 
> consume the standard error stream to prevent the processes from blocking when 
> standard error gets filled.
> To reproduce. Create this as ~/write.py
> {code:python}
> import sys
> count = int(sys.argv[1])
> for x in range(count):
> sys.stderr.write("ERROR %d\n" % x)
> sys.stdout.write("OUTPUT %d\n" % x)
> {code}
> Create a flow that goes 
> # GenerateFlowFile - 5 minutes schedule 0 bytes size 
> # ExecuteStreamCommand - Command arguments /Users/alanj/write.py;100 Command 
> Path python
> # PutFile - /tmp/write/
> routing output stream of ExecuteStreamCommand to PutFile
> When you turn everything on, you get 100 lines (not 200) of just the standard 
> output in /tmp/write.
> Next, change the command arguments to /Users/alanj/write.py;10 and turn 
> everything on again. The command will hang.
> I believe that whenever you execute a process the way ExecuteStreamCommand is 
> doing, you need to consume the standard error stream to keep it from 
> blocking. This may also affect things like ExecuteProcess and ExecuteScript 
> as well.



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