[GitHub] nifi-minifi-cpp issue #13: MINIFI-109: Add ExecuteProcess

[benqiu2016]

Github user benqiu2016 commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/13
  
@apiri Address the above review comments. Thanks for the review.


---
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-2828) SelectHiveQL and PutHiveQL fail with NoClassDefFoundError when using HTTP transport

[Matt Burgess (JIRA)]

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

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

> SelectHiveQL and PutHiveQL fail with NoClassDefFoundError when using HTTP 
> transport 
> 
>
> Key: NIFI-2828
> URL: https://issues.apache.org/jira/browse/NIFI-2828
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joey Frazee
>Assignee: Matt Burgess
> Fix For: 1.1.0
>
>
> SelectHiveQL and PutHiveQL don't currently work with HTTP transport. There 
> appears to be a class loader problem resulting in 
> java.lang.NoClassDefFoundError: Could not initialize class 
> org.apache.http.conn.ssl.SSLConnectionSocketFactory.
> This looks like a conflict with the Apache commons httpclient version in 
> hadoop-common. Removing the hadoop-libraries .nar dependency and provided 
> scope for hadoop-common appears to fix the issue, but I haven't done any 
> rigorous testing so I'm not sure if there are other consequences or not.



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

[jira] [Commented] (NIFI-2828) SelectHiveQL and PutHiveQL fail with NoClassDefFoundError when using HTTP transport

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2828:
--

GitHub user mattyb149 opened a pull request:

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

NIFI-2828: Fix Hive NAR dependencies

The approach is to remove the parent dependency and put all Hadoop/Hive 
dependencies in the Hive NAR instead of expecting them in a parent classloader.

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

$ git pull https://github.com/mattyb149/nifi NIFI-2828

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

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


commit d245a66f0495d416d556fc2b53cc00c288780ad8
Author: Matt Burgess 
Date:   2016-09-27T23:51:49Z

NIFI-2828: Fix Hive NAR dependencies




> SelectHiveQL and PutHiveQL fail with NoClassDefFoundError when using HTTP 
> transport 
> 
>
> Key: NIFI-2828
> URL: https://issues.apache.org/jira/browse/NIFI-2828
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joey Frazee
>Assignee: Matt Burgess
> Fix For: 1.1.0
>
>
> SelectHiveQL and PutHiveQL don't currently work with HTTP transport. There 
> appears to be a class loader problem resulting in 
> java.lang.NoClassDefFoundError: Could not initialize class 
> org.apache.http.conn.ssl.SSLConnectionSocketFactory.
> This looks like a conflict with the Apache commons httpclient version in 
> hadoop-common. Removing the hadoop-libraries .nar dependency and provided 
> scope for hadoop-common appears to fix the issue, but I haven't done any 
> rigorous testing so I'm not sure if there are other consequences or not.



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

[GitHub] nifi pull request #1075: NIFI-2828: Fix Hive NAR dependencies

[mattyb149]

GitHub user mattyb149 opened a pull request:

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

NIFI-2828: Fix Hive NAR dependencies

The approach is to remove the parent dependency and put all Hadoop/Hive 
dependencies in the Hive NAR instead of expecting them in a parent classloader.

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

$ git pull https://github.com/mattyb149/nifi NIFI-2828

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

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


commit d245a66f0495d416d556fc2b53cc00c288780ad8
Author: Matt Burgess 
Date:   2016-09-27T23:51:49Z

NIFI-2828: Fix Hive NAR 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] [Updated] (NIFI-2673) Add MERGE support on processor ConvertJSONTOSQL

[Paul Gibeault (JIRA)]

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

Paul Gibeault updated NIFI-2673:

Status: Patch Available  (was: Open)

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

> Add MERGE support on processor ConvertJSONTOSQL
> ---
>
> Key: NIFI-2673
> URL: https://issues.apache.org/jira/browse/NIFI-2673
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 1.0.0
>Reporter: Paul Gibeault
>Priority: Minor
>  Labels: features
> Fix For: 1.1.0
>
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> Update ConvertJSONToSQL to add support for ANSI SQL MERGE 
> https://en.wikipedia.org/wiki/Merge_(SQL)
> This would simplify workflows that manage ingestion of slowly changing 
> dimensions.



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

[jira] [Commented] (NIFI-2829) PutSQL assumes all Date and Time values are provided in Epoch

[Paul Gibeault (JIRA)]

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

Paul Gibeault commented on NIFI-2829:
-

Thank you for the help.   A status of "Patch Available" is what I was intending 
to convey.

> PutSQL assumes all Date and Time values are provided in Epoch
> -
>
> Key: NIFI-2829
> URL: https://issues.apache.org/jira/browse/NIFI-2829
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Paul Gibeault
> Fix For: 1.1.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> This bug is the same as NIFI-2576 only extended to data types DATE and TIME.
> https://issues.apache.org/jira/browse/NIFI-2576
> When PutSQL sees a DATE or TIME data type it assumes that it's being provided 
> as a Long in Epoch format.
> This doesn't make much sense since the Query Database tools that return Avro 
> return DATES and TIME values as strings; and thus following the 
> Avro->JSON->JSON To SQL Route leads to DATE and TIME fields as being strings.



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

[jira] [Updated] (NIFI-2826) GetEventHubProcessor Support Enqueue Time

[Joseph Niemiec (JIRA)]

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

Joseph Niemiec updated NIFI-2826:
-
Status: Patch Available  (was: In Progress)

> GetEventHubProcessor Support Enqueue Time
> -
>
> Key: NIFI-2826
> URL: https://issues.apache.org/jira/browse/NIFI-2826
> Project: Apache NiFi
>  Issue Type: Improvement
> Environment: centos6, jdk1.8, nifi 1.0.0
>Reporter: Joseph Niemiec
>Assignee: Joseph Niemiec
>Priority: Minor
> Fix For: 1.1.0
>
> Attachments: 
> 0001-NIFI-2826-Adding-enqueue-time-to-GetAzureEventHub-pr.patch, patch.1
>
>
> The current GetEventHubProcessor should support allowing an enqueue time like 
> eventhubs to read messages from the past. This would also support reading 
> messages missed during downtime. Today the behaviour is for the processor to 
> start at the enqueue of when it was started by the user missing any past 
> messages. 



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

[jira] [Updated] (NIFI-2826) GetEventHubProcessor Support Enqueue Time

[Joseph Niemiec (JIRA)]

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

Joseph Niemiec updated NIFI-2826:
-
Attachment: 0001-NIFI-2826-Adding-enqueue-time-to-GetAzureEventHub-pr.patch

attached patch + added test.

> GetEventHubProcessor Support Enqueue Time
> -
>
> Key: NIFI-2826
> URL: https://issues.apache.org/jira/browse/NIFI-2826
> Project: Apache NiFi
>  Issue Type: Improvement
> Environment: centos6, jdk1.8, nifi 1.0.0
>Reporter: Joseph Niemiec
>Assignee: Joseph Niemiec
>Priority: Minor
> Fix For: 1.1.0
>
> Attachments: 
> 0001-NIFI-2826-Adding-enqueue-time-to-GetAzureEventHub-pr.patch, patch.1
>
>
> The current GetEventHubProcessor should support allowing an enqueue time like 
> eventhubs to read messages from the past. This would also support reading 
> messages missed during downtime. Today the behaviour is for the processor to 
> start at the enqueue of when it was started by the user missing any past 
> messages. 



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

[jira] [Commented] (NIFI-2831) "Auto-terminate" should be used consistently in Settings tab

[Rob Moran (JIRA)]

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

Rob Moran commented on NIFI-2831:
-

Yes I'd like to maintain use of title case for these labels (text-transform: 
capitalize).

What I would actually recommend is to change the phrase "auto-terminate" to 
"automatically terminate." I think impact in the UI will be fine. [~andrewmlim] 
what about in documentation, can a simple find/replace be done? I assume 
there'd be some screenshots to update as well...



> "Auto-terminate" should be used consistently in Settings tab
> 
>
> Key: NIFI-2831
> URL: https://issues.apache.org/jira/browse/NIFI-2831
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0, 0.7.0
>Reporter: Andrew Lim
>Assignee: Scott Aslan
>Priority: Trivial
> Attachments: 0.7.0_auto-Terminate.png, 1.0.0_autoTerminate.png
>
>
> As shown in the attached screenshots of the Settings tab (0.7.0 and 1.0.0) 
> when configuring a processor:
> *The text "Auto terminate relationships" is displayed. This should be changed 
> to "Auto-terminate relationships"
> *In the Configuration error, should change "Cannot Auto-Terminate" to 
> "Cannot Auto-terminate"
> These changes would make references to auto-terminate functionality 
> consistent in the application and with the documentation 
> (https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#settings-tab).



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

[jira] [Commented] (NIFI-2832) State management should be part of the documentation/usage

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2832:
---

[~pvillard] just want to say i think this is a *great* idea and really glad to 
see you and others highlighting and thinking through our opportunity to better 
engage and assist end users!  Thanks

> State management should be part of the documentation/usage
> --
>
> Key: NIFI-2832
> URL: https://issues.apache.org/jira/browse/NIFI-2832
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Reporter: Pierre Villard
>Assignee: Pierre Villard
>Priority: Minor
>  Labels: documentation
> Fix For: 1.1.0
>
>
> At the moment, ``@Stateful`` annotation if only used in the 'View State' 
> panel. This may not be intuitive for users (NIFI-2705) and this information 
> should be part of the documentation (in the 'Usage' panel and the web 
> documentation as well).



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

[jira] [Assigned] (NIFI-2764) JdbcCommon Avro Can't Process Java Short Types

[Peter Wicks (JIRA)]

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

Peter Wicks reassigned NIFI-2764:
-

Assignee: Peter Wicks

> JdbcCommon Avro Can't Process Java Short Types
> --
>
> Key: NIFI-2764
> URL: https://issues.apache.org/jira/browse/NIFI-2764
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Peter Wicks
>Assignee: Peter Wicks
>
> Microsoft SQL Server returns TINYINT values as Java Short's.  Avro is unable 
> to write datum's of this type and throws an exception when trying to.
> This currently breaks QueryDatabaseTable at the very least when querying MS 
> SQL Server with TINYINT's in the ResultSet.



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

[jira] [Updated] (NIFI-2832) State management should be part of the documentation/usage

[Pierre Villard (JIRA)]

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

Pierre Villard updated NIFI-2832:
-
Fix Version/s: 1.1.0
   Status: Patch Available  (was: Open)

> State management should be part of the documentation/usage
> --
>
> Key: NIFI-2832
> URL: https://issues.apache.org/jira/browse/NIFI-2832
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Reporter: Pierre Villard
>Assignee: Pierre Villard
>Priority: Minor
>  Labels: documentation
> Fix For: 1.1.0
>
>
> At the moment, ``@Stateful`` annotation if only used in the 'View State' 
> panel. This may not be intuitive for users (NIFI-2705) and this information 
> should be part of the documentation (in the 'Usage' panel and the web 
> documentation as well).



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

[jira] [Assigned] (NIFI-2646) Allow for generic data type to data type conversions

[Peter Wicks (JIRA)]

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

Peter Wicks reassigned NIFI-2646:
-

Assignee: Peter Wicks

> Allow for generic data type to data type conversions
> 
>
> Key: NIFI-2646
> URL: https://issues.apache.org/jira/browse/NIFI-2646
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Reporter: Peter Wicks
>Assignee: Peter Wicks
>
> Allow for data sets to be wrapped with an interface.
> Type specific implementations of the interface will allow record 
> reading/writing in an arbitrary fashion.



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

[jira] [Commented] (NIFI-2832) State management should be part of the documentation/usage

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2832:
--

GitHub user pvillard31 opened a pull request:

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

NIFI-2832 State management should be part of the documentation/usage



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

$ git pull https://github.com/pvillard31/nifi statefulinfo

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

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


commit 815b2251388616f3019acdf7abbc2c2eb660fe98
Author: Pierre Villard 
Date:   2016-09-27T21:17:19Z

NIFI-2832 State management should be part of the documentation/usage




> State management should be part of the documentation/usage
> --
>
> Key: NIFI-2832
> URL: https://issues.apache.org/jira/browse/NIFI-2832
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Reporter: Pierre Villard
>Assignee: Pierre Villard
>Priority: Minor
>  Labels: documentation
>
> At the moment, ``@Stateful`` annotation if only used in the 'View State' 
> panel. This may not be intuitive for users (NIFI-2705) and this information 
> should be part of the documentation (in the 'Usage' panel and the web 
> documentation as well).



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

[GitHub] nifi pull request #1074: NIFI-2832 State management should be part of the do...

[pvillard31]

GitHub user pvillard31 opened a pull request:

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

NIFI-2832 State management should be part of the documentation/usage



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

$ git pull https://github.com/pvillard31/nifi statefulinfo

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

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


commit 815b2251388616f3019acdf7abbc2c2eb660fe98
Author: Pierre Villard 
Date:   2016-09-27T21:17:19Z

NIFI-2832 State management should be part of the documentation/usage




---
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-2832) State management should be part of the documentation/usage

[Pierre Villard (JIRA)]

Pierre Villard created NIFI-2832:


 Summary: State management should be part of the documentation/usage
 Key: NIFI-2832
 URL: https://issues.apache.org/jira/browse/NIFI-2832
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Documentation & Website
Reporter: Pierre Villard
Assignee: Pierre Villard
Priority: Minor


At the moment, ``@Stateful`` annotation if only used in the 'View State' panel. 
This may not be intuitive for users (NIFI-2705) and this information should be 
part of the documentation (in the 'Usage' panel and the web documentation as 
well).



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

[jira] [Assigned] (NIFI-2779) Add processor to GetEmail Supporting Exchange Web Services

[Peter Wicks (JIRA)]

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

Peter Wicks reassigned NIFI-2779:
-

Assignee: Peter Wicks

> Add processor to GetEmail Supporting Exchange Web Services
> --
>
> Key: NIFI-2779
> URL: https://issues.apache.org/jira/browse/NIFI-2779
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Peter Wicks
>Assignee: Peter Wicks
>Priority: Minor
>
> NIFI-1148 added support for POP3/IMAP.
> In the comments it was suggested that Exchange Web Services (EWS) support 
> also be added.
> There is a Microsoft created Java API for EWS available in MVN: 
> https://mvnrepository.com/artifact/com.microsoft.ews-java-api/ews-java-api/2.0



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

[jira] [Updated] (NIFI-2779) Add processor to GetEmail Supporting Exchange Web Services

[Michael Moser (JIRA)]

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

Michael Moser updated NIFI-2779:

Issue Type: New Feature  (was: Bug)

> Add processor to GetEmail Supporting Exchange Web Services
> --
>
> Key: NIFI-2779
> URL: https://issues.apache.org/jira/browse/NIFI-2779
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Peter Wicks
>Priority: Minor
>
> NIFI-1148 added support for POP3/IMAP.
> In the comments it was suggested that Exchange Web Services (EWS) support 
> also be added.
> There is a Microsoft created Java API for EWS available in MVN: 
> https://mvnrepository.com/artifact/com.microsoft.ews-java-api/ews-java-api/2.0



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

[jira] [Updated] (NIFI-2793) Add documentation for primary node only scheduling strategy

[Michael Moser (JIRA)]

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

Michael Moser updated NIFI-2793:

Issue Type: Improvement  (was: Bug)

> Add documentation for primary node only scheduling strategy
> ---
>
> Key: NIFI-2793
> URL: https://issues.apache.org/jira/browse/NIFI-2793
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Reporter: Arpit Gupta
>Priority: Minor
> Fix For: 1.1.0
>
>
> https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#scheduling-tab 
> does not cover the primary node only option. This option is only available 
> when user is running in clustered mode.



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

[jira] [Updated] (NIFI-2827) CompressContent should support brotli (MIT) and zstd (BSD + Patent grant)

[Michael Moser (JIRA)]

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

Michael Moser updated NIFI-2827:

Issue Type: New Feature  (was: Bug)

> CompressContent should support brotli (MIT) and zstd (BSD + Patent grant)
> -
>
> Key: NIFI-2827
> URL: https://issues.apache.org/jira/browse/NIFI-2827
> Project: Apache NiFi
>  Issue Type: New Feature
>Reporter: Andre
>
> brotli and zstd are gaining lots of momentum across the IoT sphere and I 
> suspect it would be a nice to have in NiFi to be able to support those two 
> emerging compression algorithms.
> Both brotli and zstd JAVA implementations are JNIs 
> https://github.com/MeteoGroup/jbrotli (ASL 2)
> https://github.com/luben/zstd-jni (3 clause BSD)



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

[jira] [Assigned] (NIFI-1852) NiFi Summary: Process Group results are not being filtered when filtering “by name"

[Scott Aslan (JIRA)]

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

Scott Aslan reassigned NIFI-1852:
-

Assignee: Scott Aslan

> NiFi Summary: Process Group results are not being filtered when filtering “by 
> name"
> ---
>
> Key: NIFI-1852
> URL: https://issues.apache.org/jira/browse/NIFI-1852
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Andrew Lim
>Assignee: Scott Aslan
>Priority: Minor
> Attachments: NIFI-1852_filterProcessGroups.png
>
>
> In the NiFi summary window, when the user tries to filter Process Group 
> results "by name", the displayed results are not filtered at all (see 
> attached screenshot).



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

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

[Michael Moser (JIRA)]

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

Michael Moser commented on NIFI-2429:
-

PR 1072 includes patches from NIFI-2395 and NIFI-2452.

I tried to cherry-pick NIFI-2600 as well, but it did not merge well at all into 
0.x.  Is this one a significant problem?

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



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

[jira] [Updated] (NIFI-2829) PutSQL assumes all Date and Time values are provided in Epoch

[Pierre Villard (JIRA)]

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

Pierre Villard updated NIFI-2829:
-
Status: Patch Available  (was: Reopened)

> PutSQL assumes all Date and Time values are provided in Epoch
> -
>
> Key: NIFI-2829
> URL: https://issues.apache.org/jira/browse/NIFI-2829
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Paul Gibeault
> Fix For: 1.1.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> This bug is the same as NIFI-2576 only extended to data types DATE and TIME.
> https://issues.apache.org/jira/browse/NIFI-2576
> When PutSQL sees a DATE or TIME data type it assumes that it's being provided 
> as a Long in Epoch format.
> This doesn't make much sense since the Query Database tools that return Avro 
> return DATES and TIME values as strings; and thus following the 
> Avro->JSON->JSON To SQL Route leads to DATE and TIME fields as being strings.



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

[jira] [Reopened] (NIFI-2829) PutSQL assumes all Date and Time values are provided in Epoch

[Pierre Villard (JIRA)]

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

Pierre Villard reopened NIFI-2829:
--

> PutSQL assumes all Date and Time values are provided in Epoch
> -
>
> Key: NIFI-2829
> URL: https://issues.apache.org/jira/browse/NIFI-2829
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Paul Gibeault
> Fix For: 1.1.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> This bug is the same as NIFI-2576 only extended to data types DATE and TIME.
> https://issues.apache.org/jira/browse/NIFI-2576
> When PutSQL sees a DATE or TIME data type it assumes that it's being provided 
> as a Long in Epoch format.
> This doesn't make much sense since the Query Database tools that return Avro 
> return DATES and TIME values as strings; and thus following the 
> Avro->JSON->JSON To SQL Route leads to DATE and TIME fields as being strings.



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

[jira] [Resolved] (NIFI-2829) PutSQL assumes all Date and Time values are provided in Epoch

[Paul Gibeault (JIRA)]

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

Paul Gibeault resolved NIFI-2829.
-
Resolution: Fixed

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

> PutSQL assumes all Date and Time values are provided in Epoch
> -
>
> Key: NIFI-2829
> URL: https://issues.apache.org/jira/browse/NIFI-2829
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Paul Gibeault
> Fix For: 1.1.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> This bug is the same as NIFI-2576 only extended to data types DATE and TIME.
> https://issues.apache.org/jira/browse/NIFI-2576
> When PutSQL sees a DATE or TIME data type it assumes that it's being provided 
> as a Long in Epoch format.
> This doesn't make much sense since the Query Database tools that return Avro 
> return DATES and TIME values as strings; and thus following the 
> Avro->JSON->JSON To SQL Route leads to DATE and TIME fields as being strings.



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

[jira] [Commented] (NIFI-2831) "Auto-terminate" should be used consistently in Settings tab

[Scott Aslan (JIRA)]

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

Scott Aslan commented on NIFI-2831:
---

I can update the Configuration error to "Cannot Auto-terminate" but for the 
text "Auto-terminate relationships" [~rmoran] specifically called out that we 
perform a text-transform: capitalization for the .setting-name in 
https://issues.apache.org/jira/browse/NIFI-2468. This will capitalize the first 
letter of each word and thus the text would actually be "Auto-Terminate 
Relationships" (notice the T is capital in Terminate)...If you notice the 
"Penalty Duration", "Bulletin Level", and all other .setting-name text also do 
not match the documentation...

I don't want to undo this until Rob weighs inwhat say you Rob?

> "Auto-terminate" should be used consistently in Settings tab
> 
>
> Key: NIFI-2831
> URL: https://issues.apache.org/jira/browse/NIFI-2831
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0, 0.7.0
>Reporter: Andrew Lim
>Assignee: Scott Aslan
>Priority: Trivial
> Attachments: 0.7.0_auto-Terminate.png, 1.0.0_autoTerminate.png
>
>
> As shown in the attached screenshots of the Settings tab (0.7.0 and 1.0.0) 
> when configuring a processor:
> *The text "Auto terminate relationships" is displayed. This should be changed 
> to "Auto-terminate relationships"
> *In the Configuration error, should change "Cannot Auto-Terminate" to 
> "Cannot Auto-terminate"
> These changes would make references to auto-terminate functionality 
> consistent in the application and with the documentation 
> (https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#settings-tab).



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

[jira] [Commented] (NIFI-2829) PutSQL assumes all Date and Time values are provided in Epoch

[Paul Gibeault (JIRA)]

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

Paul Gibeault commented on NIFI-2829:
-

I just entered this pull request that corrects this bug
https://github.com/apache/nifi/pull/1073

> PutSQL assumes all Date and Time values are provided in Epoch
> -
>
> Key: NIFI-2829
> URL: https://issues.apache.org/jira/browse/NIFI-2829
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Paul Gibeault
> Fix For: 1.1.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> This bug is the same as NIFI-2576 only extended to data types DATE and TIME.
> https://issues.apache.org/jira/browse/NIFI-2576
> When PutSQL sees a DATE or TIME data type it assumes that it's being provided 
> as a Long in Epoch format.
> This doesn't make much sense since the Query Database tools that return Avro 
> return DATES and TIME values as strings; and thus following the 
> Avro->JSON->JSON To SQL Route leads to DATE and TIME fields as being strings.



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

[jira] [Commented] (NIFI-2829) PutSQL assumes all Date and Time values are provided in Epoch

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2829:
--

GitHub user paulgibeault opened a pull request:

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

Nifi 2829

Implemented fix for JIRA 
https://issues.apache.org/jira/browse/NIFI-2829

Provided logic that will attempt to string parse Dates and Time values if 
they do not match LONG_PATTERN.

The parameter sql.args.#.format may be used to provide the Date, Time or 
Timestamp parsing string.

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

$ git pull https://github.com/paulgibeault/nifi NIFI-2829

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

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


commit 5a37e1cf7854edf23fef66a6b7be5e82c9e9f174
Author: Paul Gibeault 
Date:   2016-09-27T18:39:27Z

Implemented changes to address Jira NIFI-2829

Now Date and Time fields can be provided in String or EPOCH (Long) formats
Implemented Unit Tests to validate new functionality

commit 5e2f0c0315bc775dbf0dedc018cb665102a690ed
Author: Paul Gibeault 
Date:   2016-09-27T18:39:27Z

Implemented changes to address Jira NIFI-2829

Now Date and Time fields can be provided in String or EPOCH (Long) formats
Implemented Unit Tests to validate new functionality

commit 234235e23e1625f8cc3c90a8004cbb8e58f2e10c
Author: Paul Gibeault 
Date:   2016-09-27T20:26:43Z

Merge remote-tracking branch 'origin/NIFI-2829' into NIFI-2829




> PutSQL assumes all Date and Time values are provided in Epoch
> -
>
> Key: NIFI-2829
> URL: https://issues.apache.org/jira/browse/NIFI-2829
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Paul Gibeault
> Fix For: 1.1.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> This bug is the same as NIFI-2576 only extended to data types DATE and TIME.
> https://issues.apache.org/jira/browse/NIFI-2576
> When PutSQL sees a DATE or TIME data type it assumes that it's being provided 
> as a Long in Epoch format.
> This doesn't make much sense since the Query Database tools that return Avro 
> return DATES and TIME values as strings; and thus following the 
> Avro->JSON->JSON To SQL Route leads to DATE and TIME fields as being strings.



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

[GitHub] nifi pull request #1073: Nifi 2829

[paulgibeault]

GitHub user paulgibeault opened a pull request:

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

Nifi 2829

Implemented fix for JIRA 
https://issues.apache.org/jira/browse/NIFI-2829

Provided logic that will attempt to string parse Dates and Time values if 
they do not match LONG_PATTERN.

The parameter sql.args.#.format may be used to provide the Date, Time or 
Timestamp parsing string.

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

$ git pull https://github.com/paulgibeault/nifi NIFI-2829

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

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


commit 5a37e1cf7854edf23fef66a6b7be5e82c9e9f174
Author: Paul Gibeault 
Date:   2016-09-27T18:39:27Z

Implemented changes to address Jira NIFI-2829

Now Date and Time fields can be provided in String or EPOCH (Long) formats
Implemented Unit Tests to validate new functionality

commit 5e2f0c0315bc775dbf0dedc018cb665102a690ed
Author: Paul Gibeault 
Date:   2016-09-27T18:39:27Z

Implemented changes to address Jira NIFI-2829

Now Date and Time fields can be provided in String or EPOCH (Long) formats
Implemented Unit Tests to validate new functionality

commit 234235e23e1625f8cc3c90a8004cbb8e58f2e10c
Author: Paul Gibeault 
Date:   2016-09-27T20:26:43Z

Merge remote-tracking branch 'origin/NIFI-2829' into NIFI-2829




---
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-2787) PersistentProvenanceRepository rollover can fail on immense indexed attributes

[Michael Moser (JIRA)]

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

Michael Moser updated NIFI-2787:

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

> PersistentProvenanceRepository rollover can fail on immense indexed attributes
> --
>
> Key: NIFI-2787
> URL: https://issues.apache.org/jira/browse/NIFI-2787
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0, 0.7.0
>Reporter: Michael Moser
>Assignee: Michael Moser
> Fix For: 1.1.0, 0.7.1
>
>
> Accidentally created an immense attribute (36,000 bytes), which I indexed 
> with nifi.provenance.repository.indexed.attributes.  Received this error.
> ERROR [Provenance Repository Rollover Thread-1] 
> o.a.n.p.PersistentProvenanceRepository Failed to rollover Provenance 
> repository due to java.lang.IllegalArgumentException: Document contains at 
> least one immense term in field="FOO" (whose UTF8 encoding is longer than the 
> max length 32766), all of which were skipped. Please correct the analyzer to 
> not produce such terms.
> Perhaps this is as simple as changing 
> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-provenance-repository-bundle/nifi-persistent-provenance-repository/src/main/java/org/apache/nifi/provenance/RepositoryConfiguration.java#L37
>  to 32766 to match Lucene.  Investigation & testing needed.
> For background, this Lucene ticket made exceeding the term size limit an 
> IllegalArgumentException https://issues.apache.org/jira/browse/LUCENE-5472



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

[jira] [Updated] (NIFI-2636) UnpackContent has concurrent thread safety issue, causes flowfiles to fail

[Michael Moser (JIRA)]

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

Michael Moser updated NIFI-2636:

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

> UnpackContent has concurrent thread safety issue, causes flowfiles to fail
> --
>
> Key: NIFI-2636
> URL: https://issues.apache.org/jira/browse/NIFI-2636
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0, 0.7.0
>Reporter: Michael Moser
>Assignee: Michael Moser
> Fix For: 1.1.0, 0.8.0
>
>
> Shortly after merging NIFI-2611 I took a last look at the code and noticed 
> that each onTrigger() call, when the Packaging Format property is set to "use 
> mime.type attribute", that the class instance variable "private Unpacker 
> unpacker" can change.  When UnpackContent is set to > 1 concurrent task, this 
> isn't thread safe.  Thread A can set the unpacker to the TarUnpacker, but 
> before it gets a chance to unpack its tar file, Thread B changes the unpacker 
> to a FlowFileUnpackagerV3 which causes Thread A to fail its unpack.



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

[jira] [Assigned] (NIFI-2831) "Auto-terminate" should be used consistently in Settings tab

[Scott Aslan (JIRA)]

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

Scott Aslan reassigned NIFI-2831:
-

Assignee: Scott Aslan

> "Auto-terminate" should be used consistently in Settings tab
> 
>
> Key: NIFI-2831
> URL: https://issues.apache.org/jira/browse/NIFI-2831
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0, 0.7.0
>Reporter: Andrew Lim
>Assignee: Scott Aslan
>Priority: Trivial
> Attachments: 0.7.0_auto-Terminate.png, 1.0.0_autoTerminate.png
>
>
> As shown in the attached screenshots of the Settings tab (0.7.0 and 1.0.0) 
> when configuring a processor:
> *The text "Auto terminate relationships" is displayed. This should be changed 
> to "Auto-terminate relationships"
> *In the Configuration error, should change "Cannot Auto-Terminate" to 
> "Cannot Auto-terminate"
> These changes would make references to auto-terminate functionality 
> consistent in the application and with the documentation 
> (https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#settings-tab).



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

[GitHub] nifi issue #1064: Verifying Controller Service cannot move out of scope

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1064
  
Thanks @JPercivall, I've updated the logic to verify the move is allowed.


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

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

[Michael Moser (JIRA)]

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

Michael Moser commented on NIFI-2429:
-

New PR for this

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


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



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

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

[Michael Moser (JIRA)]

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

Michael Moser updated NIFI-2429:

Status: Patch Available  (was: Open)

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



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

[jira] [Commented] (NIFI-2395) PersistentProvenanceRepository Deadlocks caused by a blocked journal merge

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2395:
--

GitHub user mosermw opened a pull request:

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

Nifi 2429 PersistentProvenanceRepository bug fixes

In this PR I cherry-picked these commits from master into 0.x

cfc8a9613cb071247ef22f8fe4a3abb4e6b83151 NIFI-2395 
PersistentProvenanceRepository deadlock on journal merge and index exception
e9b87dd73436b1659b1fddcc400e7248bc00f1ee NIFI-2452 
PersistentProvenanceRepository index readers can be prematurely closed


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

$ git pull https://github.com/mosermw/nifi NIFI-2429

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

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


commit 29460a724f583119eada146661ab654fc961c185
Author: Mark Payne 
Date:   2016-07-28T14:19:45Z

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

commit bf8d66566c8eee911aea48b0b97942500851cf2c
Author: Mike Moser 
Date:   2016-09-26T20:22:50Z

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

commit fba761508d0b1fd39e8d27e3e80a6d6e8e22c0cc
Author: Mark Payne 
Date:   2016-08-01T18:51:02Z

NIFI-2452: Ensure that we do not close Index Readers that are still in use




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

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

[mosermw]

GitHub user mosermw opened a pull request:

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

Nifi 2429 PersistentProvenanceRepository bug fixes

In this PR I cherry-picked these commits from master into 0.x

cfc8a9613cb071247ef22f8fe4a3abb4e6b83151 NIFI-2395 
PersistentProvenanceRepository deadlock on journal merge and index exception
e9b87dd73436b1659b1fddcc400e7248bc00f1ee NIFI-2452 
PersistentProvenanceRepository index readers can be prematurely closed


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

$ git pull https://github.com/mosermw/nifi NIFI-2429

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

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


commit 29460a724f583119eada146661ab654fc961c185
Author: Mark Payne 
Date:   2016-07-28T14:19:45Z

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

commit bf8d66566c8eee911aea48b0b97942500851cf2c
Author: Mike Moser 
Date:   2016-09-26T20:22:50Z

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

commit fba761508d0b1fd39e8d27e3e80a6d6e8e22c0cc
Author: Mark Payne 
Date:   2016-08-01T18:51:02Z

NIFI-2452: Ensure that we do not close Index Readers that are still in use




---
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-1757) If Bulletin Board is opened, the requests keep occurring in the background even after the Bulletin Board is closed

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1757:
--

Github user asfgit closed the pull request at:

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


> If Bulletin Board is opened, the requests keep occurring in the background 
> even after the Bulletin Board is closed
> --
>
> Key: NIFI-1757
> URL: https://issues.apache.org/jira/browse/NIFI-1757
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Mark Payne
>Assignee: Scott Aslan
> Fix For: 1.1.0
>
>
> I clicked to open the Bulletin Board and then closed it. Opening Chrome's 
> Developer Tools, I can see that the requests are still made to retrieve 
> bulletins every few seconds.



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

[jira] [Updated] (NIFI-1757) If Bulletin Board is opened, the requests keep occurring in the background even after the Bulletin Board is closed

[Matt Gilman (JIRA)]

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

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

> If Bulletin Board is opened, the requests keep occurring in the background 
> even after the Bulletin Board is closed
> --
>
> Key: NIFI-1757
> URL: https://issues.apache.org/jira/browse/NIFI-1757
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Mark Payne
>Assignee: Scott Aslan
> Fix For: 1.1.0
>
>
> I clicked to open the Bulletin Board and then closed it. Opening Chrome's 
> Developer Tools, I can see that the requests are still made to retrieve 
> bulletins every few seconds.



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

[jira] [Commented] (NIFI-1757) If Bulletin Board is opened, the requests keep occurring in the background even after the Bulletin Board is closed

[ASF subversion and git services (JIRA)]

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

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

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

[NIFI-1757] remove iframe from shell dialog to prevent reoccurring requests, 
update fill color and label config dialog content margins to fit into their 
respective dialogs. This closes #1069


> If Bulletin Board is opened, the requests keep occurring in the background 
> even after the Bulletin Board is closed
> --
>
> Key: NIFI-1757
> URL: https://issues.apache.org/jira/browse/NIFI-1757
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Mark Payne
>Assignee: Scott Aslan
> Fix For: 1.1.0
>
>
> I clicked to open the Bulletin Board and then closed it. Opening Chrome's 
> Developer Tools, I can see that the requests are still made to retrieve 
> bulletins every few seconds.



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

[jira] [Commented] (NIFI-1757) If Bulletin Board is opened, the requests keep occurring in the background even after the Bulletin Board is closed

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1757:
--

Github user mcgilman commented on the issue:

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


> If Bulletin Board is opened, the requests keep occurring in the background 
> even after the Bulletin Board is closed
> --
>
> Key: NIFI-1757
> URL: https://issues.apache.org/jira/browse/NIFI-1757
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Mark Payne
>Assignee: Scott Aslan
> Fix For: 1.1.0
>
>
> I clicked to open the Bulletin Board and then closed it. Opening Chrome's 
> Developer Tools, I can see that the requests are still made to retrieve 
> bulletins every few seconds.



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

[GitHub] nifi pull request #1069: [NIFI-1757] remove iframe from shell dialog to prev...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1069: [NIFI-1757] remove iframe from shell dialog to prevent reo...

[mcgilman]

Github user mcgilman commented on the issue:

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


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

[jira] [Commented] (NIFI-1757) If Bulletin Board is opened, the requests keep occurring in the background even after the Bulletin Board is closed

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1757:
--

Github user mcgilman commented on the issue:

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


> If Bulletin Board is opened, the requests keep occurring in the background 
> even after the Bulletin Board is closed
> --
>
> Key: NIFI-1757
> URL: https://issues.apache.org/jira/browse/NIFI-1757
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Mark Payne
>Assignee: Scott Aslan
>
> I clicked to open the Bulletin Board and then closed it. Opening Chrome's 
> Developer Tools, I can see that the requests are still made to retrieve 
> bulletins every few seconds.



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

[GitHub] nifi issue #1069: [NIFI-1757] remove iframe from shell dialog to prevent reo...

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1069
  
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] [Updated] (NIFI-2731) MergeContent default max number of flow files and max number of bins should be smaller

[Pierre Villard (JIRA)]

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

Pierre Villard updated NIFI-2731:
-
Fix Version/s: 1.1.0
   Status: Patch Available  (was: Open)

> MergeContent default max number of flow files and max number of bins should 
> be smaller
> --
>
> Key: NIFI-2731
> URL: https://issues.apache.org/jira/browse/NIFI-2731
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Joseph Witt
>Assignee: Pierre Villard
> Fix For: 1.1.0
>
>
> Presently there is no default on max entries.  It should probably be set to 
> 1000 by default.  These are flow files and their objects are read into memory 
> and can add up quickly.  Further, if we have 100 default max bins we could 
> end up with 100s of thousands of flow file objects held in memory during 
> common dataflow scenarios.  Recommend moving to max 5 different bins by 
> default and max 1000 flow files by default.



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

[jira] [Updated] (NIFI-2775) UI - Go To button in Provenance table is not visible in Firefox

[Matt Gilman (JIRA)]

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

Matt Gilman updated NIFI-2775:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> UI - Go To button in Provenance table is not visible in Firefox
> ---
>
> Key: NIFI-2775
> URL: https://issues.apache.org/jira/browse/NIFI-2775
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Scott Aslan
> Fix For: 1.1.0
>
>
> In the Provenance table, the Go To button appears to be wrapping to the next 
> line making the button not visible. Should also verify other buttons in other 
> tables. This is only happening in Firefox.



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

[jira] [Commented] (NIFI-2731) MergeContent default max number of flow files and max number of bins should be smaller

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2731:
--

GitHub user pvillard31 opened a pull request:

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

NIFI-2731 MergeContent default max number of flow files and max number of 
bins should be smaller



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

$ git pull https://github.com/pvillard31/nifi NIFI-2731

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

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


commit 5745a1e6224f1b852071b29b7710d0b5f13f0024
Author: Pierre Villard 
Date:   2016-09-27T19:09:51Z

NIFI-2731 MergeContent default max number of flow files and max number of 
bins should be smaller




> MergeContent default max number of flow files and max number of bins should 
> be smaller
> --
>
> Key: NIFI-2731
> URL: https://issues.apache.org/jira/browse/NIFI-2731
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Joseph Witt
>
> Presently there is no default on max entries.  It should probably be set to 
> 1000 by default.  These are flow files and their objects are read into memory 
> and can add up quickly.  Further, if we have 100 default max bins we could 
> end up with 100s of thousands of flow file objects held in memory during 
> common dataflow scenarios.  Recommend moving to max 5 different bins by 
> default and max 1000 flow files by default.



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

[jira] [Commented] (NIFI-2775) UI - Go To button in Provenance table is not visible in Firefox

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2775:
--

Github user asfgit closed the pull request at:

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


> UI - Go To button in Provenance table is not visible in Firefox
> ---
>
> Key: NIFI-2775
> URL: https://issues.apache.org/jira/browse/NIFI-2775
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Scott Aslan
> Fix For: 1.1.0
>
>
> In the Provenance table, the Go To button appears to be wrapping to the next 
> line making the button not visible. Should also verify other buttons in other 
> tables. This is only happening in Firefox.



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

[GitHub] nifi pull request #1071: NIFI-2731 MergeContent default max number of flow f...

[pvillard31]

GitHub user pvillard31 opened a pull request:

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

NIFI-2731 MergeContent default max number of flow files and max number of 
bins should be smaller



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

$ git pull https://github.com/pvillard31/nifi NIFI-2731

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

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


commit 5745a1e6224f1b852071b29b7710d0b5f13f0024
Author: Pierre Villard 
Date:   2016-09-27T19:09:51Z

NIFI-2731 MergeContent default max number of flow files and max number of 
bins should be smaller




---
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-2775) UI - Go To button in Provenance table is not visible in Firefox

[ASF subversion and git services (JIRA)]

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

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

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

[NIFI-2775] update Provenance table GoTo button visibility in FF. This closes 
#1040


> UI - Go To button in Provenance table is not visible in Firefox
> ---
>
> Key: NIFI-2775
> URL: https://issues.apache.org/jira/browse/NIFI-2775
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Scott Aslan
> Fix For: 1.1.0
>
>
> In the Provenance table, the Go To button appears to be wrapping to the next 
> line making the button not visible. Should also verify other buttons in other 
> tables. This is only happening in Firefox.



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

[GitHub] nifi pull request #1040: [NIFI-2775] update Provenance table GoTo button vis...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2831) "Auto-terminate" should be used consistently in Settings tab

[Andrew Lim (JIRA)]

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

Andrew Lim updated NIFI-2831:
-
Attachment: 0.7.0_auto-Terminate.png
1.0.0_autoTerminate.png

> "Auto-terminate" should be used consistently in Settings tab
> 
>
> Key: NIFI-2831
> URL: https://issues.apache.org/jira/browse/NIFI-2831
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0, 0.7.0
>Reporter: Andrew Lim
>Priority: Trivial
> Attachments: 0.7.0_auto-Terminate.png, 1.0.0_autoTerminate.png
>
>
> As shown in the attached screenshots of the Settings tab (0.7.0 and 1.0.0) 
> when configuring a processor:
> *The text "Auto terminate relationships" is displayed. This should be changed 
> to "Auto-terminate relationships"
> *In the Configuration error, should change "Cannot Auto-Terminate" to 
> "Cannot Auto-terminate"
> These changes would make references to auto-terminate functionality 
> consistent in the application and with the documentation 
> (https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#settings-tab).



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

[jira] [Updated] (NIFI-2831) "Auto-terminate" be used consistently in Settings tab

[Andrew Lim (JIRA)]

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

Andrew Lim updated NIFI-2831:
-
Summary: "Auto-terminate" be used consistently in Settings tab  (was: 
"Auto-terminate" not used consistently in Settings tab)

> "Auto-terminate" be used consistently in Settings tab
> -
>
> Key: NIFI-2831
> URL: https://issues.apache.org/jira/browse/NIFI-2831
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0, 0.7.0
>Reporter: Andrew Lim
>Priority: Trivial
>
> As shown in the attached screenshots of the Settings tab (0.7.0 and 1.0.0) 
> when configuring a processor:
> *The text "Auto terminate relationships" is displayed. This should be changed 
> to "Auto-terminate relationships"
> *In the Configuration error, should change "Cannot Auto-Terminate" to 
> "Cannot Auto-terminate"
> These changes would make references to auto-terminate functionality 
> consistent in the application and with the documentation 
> (https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#settings-tab).



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

[jira] [Updated] (NIFI-2831) "Auto-terminate" should be used consistently in Settings tab

[Andrew Lim (JIRA)]

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

Andrew Lim updated NIFI-2831:
-
Summary: "Auto-terminate" should be used consistently in Settings tab  
(was: "Auto-terminate" be used consistently in Settings tab)

> "Auto-terminate" should be used consistently in Settings tab
> 
>
> Key: NIFI-2831
> URL: https://issues.apache.org/jira/browse/NIFI-2831
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0, 0.7.0
>Reporter: Andrew Lim
>Priority: Trivial
>
> As shown in the attached screenshots of the Settings tab (0.7.0 and 1.0.0) 
> when configuring a processor:
> *The text "Auto terminate relationships" is displayed. This should be changed 
> to "Auto-terminate relationships"
> *In the Configuration error, should change "Cannot Auto-Terminate" to 
> "Cannot Auto-terminate"
> These changes would make references to auto-terminate functionality 
> consistent in the application and with the documentation 
> (https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#settings-tab).



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

[jira] [Created] (NIFI-2831) "Auto-terminate" not used consistently in Settings tab

[Andrew Lim (JIRA)]

Andrew Lim created NIFI-2831:


 Summary: "Auto-terminate" not used consistently in Settings tab
 Key: NIFI-2831
 URL: https://issues.apache.org/jira/browse/NIFI-2831
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core UI
Affects Versions: 0.7.0, 1.0.0
Reporter: Andrew Lim
Priority: Trivial


As shown in the attached screenshots of the Settings tab (0.7.0 and 1.0.0) when 
configuring a processor:

*The text "Auto terminate relationships" is displayed. This should be changed 
to "Auto-terminate relationships"
*In the Configuration error, should change "Cannot Auto-Terminate" to 
"Cannot Auto-terminate"

These changes would make references to auto-terminate functionality consistent 
in the application and with the documentation 
(https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#settings-tab).



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

[jira] [Created] (NIFI-2830) Template UUIDs out of sync in cluster

[Aldrin Piri (JIRA)]

Aldrin Piri created NIFI-2830:
-

 Summary: Template UUIDs out of sync in cluster
 Key: NIFI-2830
 URL: https://issues.apache.org/jira/browse/NIFI-2830
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core Framework
Affects Versions: 1.0.0
Reporter: Aldrin Piri


I uploaded a template to a clustered instance of NiFi which presented me with a 
success dialog.  This, and subsequent actions, were performed through a node, 
nifi1.  Upon trying to add this template to the canvas, I received a message 
that

{code}
Node nifi2:8443 is unable to fulfill this request due to: Unable to locate 
template with id '76c907b3-2664-30e4-987b-e9021ebcc844'.
{code}

Upon performing an inspection on several of the nodes in the cluster, I saw 
that all but nifi2 had the above listed UUID, but nifi2 had a different UUID.  
Upon trying to delete the template, I was presented with the same error.  This 
behavior, inclusive of the error message was the same when performing the same 
actions on nifi2.

Re-uploading the template with a different name, everything worked as 
anticipated.

There was nothing of note in nifi-app or nifi-user logs beyond the information 
provided in the error dialog.  Of possible note is that the node in question 
was possibly having some intermittent network issues but was listed as 
continuously connected on the node I was accessing.



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

[jira] [Created] (NIFI-2829) PutSQL assumes all Date and Time values are provided in Epoch

[Paul Gibeault (JIRA)]

Paul Gibeault created NIFI-2829:
---

 Summary: PutSQL assumes all Date and Time values are provided in 
Epoch
 Key: NIFI-2829
 URL: https://issues.apache.org/jira/browse/NIFI-2829
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core Framework
Affects Versions: 1.0.0
Reporter: Paul Gibeault
 Fix For: 1.1.0


This bug is the same as NIFI-2576 only extended to data types DATE and TIME.
https://issues.apache.org/jira/browse/NIFI-2576

When PutSQL sees a DATE or TIME data type it assumes that it's being provided 
as a Long in Epoch format.
This doesn't make much sense since the Query Database tools that return Avro 
return DATES and TIME values as strings; and thus following the 
Avro->JSON->JSON To SQL Route leads to DATE and TIME fields as being strings.




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

[jira] [Assigned] (NIFI-2496) UI - Zoom Fit does not account for an open palette

[Scott Aslan (JIRA)]

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

Scott Aslan reassigned NIFI-2496:
-

Assignee: Scott Aslan

> UI - Zoom Fit does not account for an open palette
> --
>
> Key: NIFI-2496
> URL: https://issues.apache.org/jira/browse/NIFI-2496
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Scott Aslan
>Priority: Minor
> Fix For: 1.1.0
>
>
> When using zoom fit, the viewport calculation does not account for whether 
> the palette(s) are open. This is also true for entering a Process Group for 
> the first time (which simply calls the zoom fit method).



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

[GitHub] nifi issue #1064: Verifying Controller Service cannot move out of scope

[JPercivall]

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/1064
  
@mcgilman this properly prevents the processor from being moved up to a 
parent group but it also prevents moving the processor to a child process 
group. Also when I tried moving a processor up a level (but it would still have 
visibility of the CS) I got this NPE in the user logs:


2016-09-27 13:55:39,497 INFO [NiFi Web Server-20] 
org.apache.nifi.web.filter.RequestLogger Attempting request for (anonymous) PUT 
http://localhost:8080/nifi-api/snippets/01571004-5208-1cc8-3233-d96e50118e45 
(source ip: 127.0.0.1)
2016-09-27 13:55:39,506 ERROR [NiFi Web Server-20] 
o.a.nifi.web.api.config.ThrowableMapper An unexpected error has occurred: 
java.lang.NullPointerException. Returning Internal Server Error response.
java.lang.NullPointerException: null
at 
org.apache.nifi.groups.StandardProcessGroup.verifyCanMove(StandardProcessGroup.java:2484)
 ~[nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.web.dao.impl.StandardSnippetDAO.verifyUpdateSnippetComponent(StandardSnippetDAO.java:224)
 ~[classes/:na]
at 
org.apache.nifi.web.dao.impl.StandardSnippetDAO.updateSnippetComponents(StandardSnippetDAO.java:231)
 ~[classes/:na]
at 
org.apache.nifi.web.dao.impl.StandardSnippetDAO$$FastClassBySpringCGLIB$$a44196f0.invoke()
 ~[classes/:na]
at 
org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) 
~[spring-core-4.2.4.RELEASE.jar:4.2.4.RELEASE]
at 
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:720)
 ~[spring-aop-4.2.4.RELEASE.jar:4.2.4.RELEASE]
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
 ~[spring-aop-4.2.4.RELEASE.jar:4.2.4.RELEASE]
at 
org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:85)
 ~[spring-aop-4.2.4.RELEASE.jar:4.2.4.RELEASE]
at 
org.apache.nifi.audit.SnippetAuditor.updateSnippetAdvice(SnippetAuditor.java:264)
 ~[classes/:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
~[na:1.8.0_74]
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
~[na:1.8.0_74]
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 ~[na:1.8.0_74]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_74]
at 
org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621)
 ~[spring-aop-4.2.4.RELEASE.jar:4.2.4.RELEASE]
at 
org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610)
 ~[spring-aop-4.2.4.RELEASE.jar:4.2.4.RELEASE]
at 
org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:68)
 ~[spring-aop-4.2.4.RELEASE.jar:4.2.4.RELEASE]
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:168)
 ~[spring-aop-4.2.4.RELEASE.jar:4.2.4.RELEASE]
at 
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92)
 ~[spring-aop-4.2.4.RELEASE.jar:4.2.4.RELEASE]
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
 ~[spring-aop-4.2.4.RELEASE.jar:4.2.4.RELEASE]
at 
org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:655)
 ~[spring-aop-4.2.4.RELEASE.jar:4.2.4.RELEASE]
at 
org.apache.nifi.web.dao.impl.StandardSnippetDAO$$EnhancerBySpringCGLIB$$e100c2a.updateSnippetComponents()
 ~[classes/:na]
at 
org.apache.nifi.web.StandardNiFiServiceFacade$2.update(StandardNiFiServiceFacade.java:639)
 ~[classes/:1.1.0-SNAPSHOT]
at 
org.apache.nifi.web.revision.NaiveRevisionManager.updateRevision(NaiveRevisionManager.java:121)
 ~[nifi-web-optimistic-locking-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.web.StandardNiFiServiceFacade.updateSnippet(StandardNiFiServiceFacade.java:635)
 ~[classes/:1.1.0-SNAPSHOT]
at 
org.apache.nifi.web.StandardNiFiServiceFacade$$FastClassBySpringCGLIB$$358780e0.invoke()
 ~[classes/:1.1.0-SNAPSHOT]
at 
org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) 
~[spring-core-4.2.4.RELEASE.jar:4.2.4.RELEASE]
at 
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:720)
 ~[spring-aop-4.2.4.RELEASE.jar:4.2.4.RELEASE]
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
 ~[spring-aop-4.2.4.RELEASE.jar:4.2.4.RELEASE]
at 

[jira] [Updated] (NIFI-1459) Scroll bar in the properties tab of processor Config appears behind allowable values dropdown

[Scott Aslan (JIRA)]

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

Scott Aslan updated NIFI-1459:
--
Status: Patch Available  (was: In Progress)

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

> Scroll bar in the properties tab of processor Config appears behind allowable 
> values dropdown
> -
>
> Key: NIFI-1459
> URL: https://issues.apache.org/jira/browse/NIFI-1459
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 0.4.1
> Environment: OSX 10.10.15 with "Show scroll bars" option set to "When 
> scrolling" and using Google Chrome version 48.0.2564.97 (64-bit)
>Reporter: Joseph Percivall
>Assignee: Scott Aslan
>Priority: Trivial
> Attachments: Screen Shot 2016-02-02 at 11.23.46 AM.png
>
>
> In processors with many properties, one of them being a dropdown of allowable 
> values,  when the value for the property is select (bringing up the pop-up) 
> the scroll bar will overlap the box.



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

[jira] [Updated] (NIFI-1757) If Bulletin Board is opened, the requests keep occurring in the background even after the Bulletin Board is closed

[Scott Aslan (JIRA)]

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

Scott Aslan updated NIFI-1757:
--
Status: Patch Available  (was: In Progress)

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

> If Bulletin Board is opened, the requests keep occurring in the background 
> even after the Bulletin Board is closed
> --
>
> Key: NIFI-1757
> URL: https://issues.apache.org/jira/browse/NIFI-1757
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Mark Payne
>Assignee: Scott Aslan
>
> I clicked to open the Bulletin Board and then closed it. Opening Chrome's 
> Developer Tools, I can see that the requests are still made to retrieve 
> bulletins every few seconds.



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

[jira] [Commented] (NIFI-1459) Scroll bar in the properties tab of processor Config appears behind allowable values dropdown

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1459:
--

GitHub user scottyaslan opened a pull request:

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

[NIFI-1459] add css translate3d to properties table editors in order …

…to move the element along the z-axis of the 3D space and allow the 
scrollbars to properly be poistioned

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

$ git pull https://github.com/scottyaslan/nifi NIFI-1459

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

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


commit bb415e7b05c0d2dcd7e52bbaae6b32b816842a16
Author: Scott Aslan 
Date:   2016-09-27T17:48:49Z

[NIFI-1459] add css translate3d to properties table editors in order to 
move the element along the z-axis of the 3D space and allow the scrollbars to 
properly be poistioned




> Scroll bar in the properties tab of processor Config appears behind allowable 
> values dropdown
> -
>
> Key: NIFI-1459
> URL: https://issues.apache.org/jira/browse/NIFI-1459
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 0.4.1
> Environment: OSX 10.10.15 with "Show scroll bars" option set to "When 
> scrolling" and using Google Chrome version 48.0.2564.97 (64-bit)
>Reporter: Joseph Percivall
>Assignee: Scott Aslan
>Priority: Trivial
> Attachments: Screen Shot 2016-02-02 at 11.23.46 AM.png
>
>
> In processors with many properties, one of them being a dropdown of allowable 
> values,  when the value for the property is select (bringing up the pop-up) 
> the scroll bar will overlap the box.



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

[GitHub] nifi pull request #1070: [NIFI-1459] add css translate3d to properties table...

[scottyaslan]

GitHub user scottyaslan opened a pull request:

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

[NIFI-1459] add css translate3d to properties table editors in order …

…to move the element along the z-axis of the 3D space and allow the 
scrollbars to properly be poistioned

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

$ git pull https://github.com/scottyaslan/nifi NIFI-1459

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

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


commit bb415e7b05c0d2dcd7e52bbaae6b32b816842a16
Author: Scott Aslan 
Date:   2016-09-27T17:48:49Z

[NIFI-1459] add css translate3d to properties table editors in order to 
move the element along the z-axis of the 3D space and allow the scrollbars to 
properly be poistioned




---
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-2288) Authorization: Start and Stop buttons in Operate pallette are active for a user that only has view privileges to process group

[Andrew Lim (JIRA)]

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

Andrew Lim resolved NIFI-2288.
--
Resolution: Cannot Reproduce

Closing.  Unable to reproduce in 1.0.0.

> Authorization:  Start and Stop buttons in Operate pallette are active for a 
> user that only has view privileges to process group
> ---
>
> Key: NIFI-2288
> URL: https://issues.apache.org/jira/browse/NIFI-2288
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Scott Aslan
>Priority: Minor
>  Labels: UI
>
> A non-administrator user only has view privileges to a process group, however 
> the Start and Stop buttons in the Operate pallete are active and clickable, 
> when they should be inactive.
> Clicking the Start and Stop buttons doesn't do anything, which is why I 
> marked as Minor priority, but this is still confusing to the user.



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

[jira] [Assigned] (NIFI-1459) Scroll bar in the properties tab of processor Config appears behind allowable values dropdown

[Scott Aslan (JIRA)]

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

Scott Aslan reassigned NIFI-1459:
-

Assignee: Scott Aslan

> Scroll bar in the properties tab of processor Config appears behind allowable 
> values dropdown
> -
>
> Key: NIFI-1459
> URL: https://issues.apache.org/jira/browse/NIFI-1459
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 0.4.1
> Environment: OSX 10.10.15 with "Show scroll bars" option set to "When 
> scrolling" and using Google Chrome version 48.0.2564.97 (64-bit)
>Reporter: Joseph Percivall
>Assignee: Scott Aslan
>Priority: Trivial
> Attachments: Screen Shot 2016-02-02 at 11.23.46 AM.png
>
>
> In processors with many properties, one of them being a dropdown of allowable 
> values,  when the value for the property is select (bringing up the pop-up) 
> the scroll bar will overlap the box.



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

[GitHub] nifi issue #1064: Verifying Controller Service cannot move out of scope

[JPercivall]

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/1064
  
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-2288) Authorization: Start and Stop buttons in Operate pallette are active for a user that only has view privileges to process group

[Scott Aslan (JIRA)]

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

Scott Aslan commented on NIFI-2288:
---

[~andrewmlim] I believe this ticket can also be closed. Can you please verify?

> Authorization:  Start and Stop buttons in Operate pallette are active for a 
> user that only has view privileges to process group
> ---
>
> Key: NIFI-2288
> URL: https://issues.apache.org/jira/browse/NIFI-2288
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Scott Aslan
>Priority: Minor
>  Labels: UI
>
> A non-administrator user only has view privileges to a process group, however 
> the Start and Stop buttons in the Operate pallete are active and clickable, 
> when they should be inactive.
> Clicking the Start and Stop buttons doesn't do anything, which is why I 
> marked as Minor priority, but this is still confusing to the user.



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

[jira] [Commented] (NIFI-2828) SelectHiveQL and PutHiveQL fail with NoClassDefFoundError when using HTTP transport

[Andrew Grande (JIRA)]

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

Andrew Grande commented on NIFI-2828:
-

I saw the same stacktrace for the PutHiveQL processor when connecting to Hive 
over HTTP.

> SelectHiveQL and PutHiveQL fail with NoClassDefFoundError when using HTTP 
> transport 
> 
>
> Key: NIFI-2828
> URL: https://issues.apache.org/jira/browse/NIFI-2828
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joey Frazee
>Assignee: Matt Burgess
> Fix For: 1.1.0
>
>
> SelectHiveQL and PutHiveQL don't currently work with HTTP transport. There 
> appears to be a class loader problem resulting in 
> java.lang.NoClassDefFoundError: Could not initialize class 
> org.apache.http.conn.ssl.SSLConnectionSocketFactory.
> This looks like a conflict with the Apache commons httpclient version in 
> hadoop-common. Removing the hadoop-libraries .nar dependency and provided 
> scope for hadoop-common appears to fix the issue, but I haven't done any 
> rigorous testing so I'm not sure if there are other consequences or not.



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

[jira] [Commented] (NIFI-2828) SelectHiveQL and PutHiveQL fail with NoClassDefFoundError when using HTTP transport

[Matt Burgess (JIRA)]

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

Matt Burgess commented on NIFI-2828:


Initial tests appear to only increase the size of the Hive NAR by 10-12 MB

> SelectHiveQL and PutHiveQL fail with NoClassDefFoundError when using HTTP 
> transport 
> 
>
> Key: NIFI-2828
> URL: https://issues.apache.org/jira/browse/NIFI-2828
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joey Frazee
>Assignee: Matt Burgess
>
> SelectHiveQL and PutHiveQL don't currently work with HTTP transport. There 
> appears to be a class loader problem resulting in 
> java.lang.NoClassDefFoundError: Could not initialize class 
> org.apache.http.conn.ssl.SSLConnectionSocketFactory.
> This looks like a conflict with the Apache commons httpclient version in 
> hadoop-common. Removing the hadoop-libraries .nar dependency and provided 
> scope for hadoop-common appears to fix the issue, but I haven't done any 
> rigorous testing so I'm not sure if there are other consequences or not.



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

[jira] [Commented] (NIFI-2828) SelectHiveQL and PutHiveQL fail with NoClassDefFoundError when using HTTP transport

[Matt Burgess (JIRA)]

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

Matt Burgess commented on NIFI-2828:


There are definitely issues with Hadoop versions between the 
nifi-hadoop-libraries-nar (usually the parent), nifi-hdfs-processors, 
nifi-hive-nar, HBase stuff, etc.  For Hive it seems fairly picky about its 
dependencies, so my suggested fix is to remove the dependency from the Hive NAR 
on the Hadoop Libraries NAR, remove any "provided" scopes, and remove all 
exclusions. This should involve complete regression testing of the Hive 
components in NiFi.

> SelectHiveQL and PutHiveQL fail with NoClassDefFoundError when using HTTP 
> transport 
> 
>
> Key: NIFI-2828
> URL: https://issues.apache.org/jira/browse/NIFI-2828
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joey Frazee
>
> SelectHiveQL and PutHiveQL don't currently work with HTTP transport. There 
> appears to be a class loader problem resulting in 
> java.lang.NoClassDefFoundError: Could not initialize class 
> org.apache.http.conn.ssl.SSLConnectionSocketFactory.
> This looks like a conflict with the Apache commons httpclient version in 
> hadoop-common. Removing the hadoop-libraries .nar dependency and provided 
> scope for hadoop-common appears to fix the issue, but I haven't done any 
> rigorous testing so I'm not sure if there are other consequences or not.



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

[jira] [Assigned] (NIFI-2828) SelectHiveQL and PutHiveQL fail with NoClassDefFoundError when using HTTP transport

[Matt Burgess (JIRA)]

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

Matt Burgess reassigned NIFI-2828:
--

Assignee: Matt Burgess

> SelectHiveQL and PutHiveQL fail with NoClassDefFoundError when using HTTP 
> transport 
> 
>
> Key: NIFI-2828
> URL: https://issues.apache.org/jira/browse/NIFI-2828
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joey Frazee
>Assignee: Matt Burgess
>
> SelectHiveQL and PutHiveQL don't currently work with HTTP transport. There 
> appears to be a class loader problem resulting in 
> java.lang.NoClassDefFoundError: Could not initialize class 
> org.apache.http.conn.ssl.SSLConnectionSocketFactory.
> This looks like a conflict with the Apache commons httpclient version in 
> hadoop-common. Removing the hadoop-libraries .nar dependency and provided 
> scope for hadoop-common appears to fix the issue, but I haven't done any 
> rigorous testing so I'm not sure if there are other consequences or not.



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

[jira] [Updated] (NIFI-2828) SelectHiveQL and PutHiveQL fail with NoClassDefFoundError when using HTTP transport

[Joey Frazee (JIRA)]

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

Joey Frazee updated NIFI-2828:
--
Description: 
SelectHiveQL and PutHiveQL don't currently work with HTTP transport. There 
appears to be a class loader problem resulting in 
java.lang.NoClassDefFoundError: Could not initialize class 
org.apache.http.conn.ssl.SSLConnectionSocketFactory.

This looks like a conflict with the Apache commons httpclient version in 
hadoop-common. Removing the hadoop-libraries .nar dependency and provided scope 
for hadoop-common appears to fix the issue, but I haven't done any rigorous 
testing so I'm not sure if there are other consequences or not.

  was:
SelectHiveQL and PutHiveQL don't currently work with HTTP transport. There 
appears to be a class loader problem resulting in 
java.lang.NoClassDefFoundError: Could not initialize class 
org.apache.http.conn.ssl.SSLConnectionSocketFactory.

This looks like a conflict with the Apache commons httpclient version in 
hadoop-common. Removing the provided scope for hadoop-common appears to fix the 
issue, but I haven't done any rigorous testing so I'm not sure if there are 
other consequences or not.


> SelectHiveQL and PutHiveQL fail with NoClassDefFoundError when using HTTP 
> transport 
> 
>
> Key: NIFI-2828
> URL: https://issues.apache.org/jira/browse/NIFI-2828
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joey Frazee
>
> SelectHiveQL and PutHiveQL don't currently work with HTTP transport. There 
> appears to be a class loader problem resulting in 
> java.lang.NoClassDefFoundError: Could not initialize class 
> org.apache.http.conn.ssl.SSLConnectionSocketFactory.
> This looks like a conflict with the Apache commons httpclient version in 
> hadoop-common. Removing the hadoop-libraries .nar dependency and provided 
> scope for hadoop-common appears to fix the issue, but I haven't done any 
> rigorous testing so I'm not sure if there are other consequences or not.



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

[jira] [Commented] (NIFI-2795) Enhance Cluster UI with System Diagnostics

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2795:
--

Github user jvwing commented on the issue:

https://github.com/apache/nifi/pull/1042
  
Thank you, @mcgilman.


> Enhance Cluster UI with System Diagnostics
> --
>
> Key: NIFI-2795
> URL: https://issues.apache.org/jira/browse/NIFI-2795
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: James Wing
>Assignee: James Wing
>Priority: Minor
> Fix For: 1.1.0
>
> Attachments: cluster-01-nodes.png, cluster-02-system.png, 
> cluster-03-jvm.png, cluster-04-flowfile-store.png, 
> cluster-05-content-store.png
>
>
> The Cluster UI currently provides some basic information on each node in the 
> cluster and options for connecting and disconnecting nodes. I propose to add 
> system diagnostics information in tables, contained in multiple tabs.  
> Roughly, the tabs should cover the same content as the System Diagnostics 
> dialog already in the System UI, but in a tabular format for comparing across 
> nodes.



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

[jira] [Commented] (NIFI-2795) Enhance Cluster UI with System Diagnostics

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2795:
--

Github user jvwing closed the pull request at:

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


> Enhance Cluster UI with System Diagnostics
> --
>
> Key: NIFI-2795
> URL: https://issues.apache.org/jira/browse/NIFI-2795
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: James Wing
>Assignee: James Wing
>Priority: Minor
> Fix For: 1.1.0
>
> Attachments: cluster-01-nodes.png, cluster-02-system.png, 
> cluster-03-jvm.png, cluster-04-flowfile-store.png, 
> cluster-05-content-store.png
>
>
> The Cluster UI currently provides some basic information on each node in the 
> cluster and options for connecting and disconnecting nodes. I propose to add 
> system diagnostics information in tables, contained in multiple tabs.  
> Roughly, the tabs should cover the same content as the System Diagnostics 
> dialog already in the System UI, but in a tabular format for comparing across 
> nodes.



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

[GitHub] nifi issue #1042: NIFI-2795 Sys Diagnostics in Cluster UI

[jvwing]

Github user jvwing commented on the issue:

https://github.com/apache/nifi/pull/1042
  
Thank you, @mcgilman.


---
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-2828) SelectHiveQL and PutHiveQL fail with NoClassDefFoundError when using HTTP transport

[Joey Frazee (JIRA)]

Joey Frazee created NIFI-2828:
-

 Summary: SelectHiveQL and PutHiveQL fail with NoClassDefFoundError 
when using HTTP transport 
 Key: NIFI-2828
 URL: https://issues.apache.org/jira/browse/NIFI-2828
 Project: Apache NiFi
  Issue Type: Bug
Reporter: Joey Frazee


SelectHiveQL and PutHiveQL don't currently work with HTTP transport. There 
appears to be a class loader problem resulting in 
java.lang.NoClassDefFoundError: Could not initialize class 
org.apache.http.conn.ssl.SSLConnectionSocketFactory.

This looks like a conflict with the Apache commons httpclient version in 
hadoop-common. Removing the provided scope for hadoop-common appears to fix the 
issue, but I haven't done any rigorous testing so I'm not sure if there are 
other consequences or not.



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

[jira] [Resolved] (NIFI-2639) Update graphics in "Apache NiFi In Depth" doc

[Joseph Percivall (JIRA)]

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

Joseph Percivall resolved NIFI-2639.

Resolution: Fixed

> Update graphics in "Apache NiFi In Depth" doc
> -
>
> Key: NIFI-2639
> URL: https://issues.apache.org/jira/browse/NIFI-2639
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 1.0.0
>Reporter: Joseph Percivall
>Assignee: Andrew Lim
>Priority: Minor
> Fix For: 1.1.0
>
>
> There are a number of graphics in the "Apache NiFi In Depth" that are screen 
> shots of a flow that currently are of the 0.x UI. 
> For aesthetics purposes, these should be updated using the new UI .



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

[jira] [Commented] (NIFI-2818) NIFI requires write access to NIFI_HOME/lib upon start

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2818:
--

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/1059
  
not yet ready for review


> NIFI requires write access to NIFI_HOME/lib upon start
> --
>
> Key: NIFI-2818
> URL: https://issues.apache.org/jira/browse/NIFI-2818
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.0.0, 0.7.0
>Reporter: Andre
>Assignee: Andre
> Fix For: 1.1.0
>
>
> As part of NIFI-1500 we noted that NiFi requires what can be described as 
> excessive filesystem privileges to be executed.
> One of the issues identified is that NiFi requires write access to 
> NIFI_HOME/lib as illustrated by the following:
> {code}
> nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-nar-utils/src/main/java/org/apache/nifi/nar/NarUnpacker.java
>  for (Path narLibraryDir : narLibraryDirs) {
> File narDir = narLibraryDir.toFile();
> FileUtils.ensureDirectoryExistAndCanAccess(narDir);
> File[] dirFiles = narDir.listFiles(NAR_FILTER);
> if (dirFiles != null) {
> List fileList = Arrays.asList(dirFiles);
> narFiles.addAll(fileList);
> }
> }
> {code}



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

[GitHub] nifi issue #1059: NIFI-2818 - Minimise fs permission required by NiFi

[trixpan]

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/1059
  
not yet ready for review


---
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-2639) Update graphics in "Apache NiFi In Depth" doc

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2639 Update NiFi In Depth Doc: made text edits and replaced screenshots 
with new UI

This closes #1067

Signed-off-by: jpercivall 


> Update graphics in "Apache NiFi In Depth" doc
> -
>
> Key: NIFI-2639
> URL: https://issues.apache.org/jira/browse/NIFI-2639
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 1.0.0
>Reporter: Joseph Percivall
>Assignee: Andrew Lim
>Priority: Minor
> Fix For: 1.1.0
>
>
> There are a number of graphics in the "Apache NiFi In Depth" that are screen 
> shots of a flow that currently are of the 0.x UI. 
> For aesthetics purposes, these should be updated using the new UI .



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

[jira] [Commented] (NIFI-2639) Update graphics in "Apache NiFi In Depth" doc

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2639:
--

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

https://github.com/apache/nifi/pull/1067#discussion_r80725420
  
--- Diff: nifi-docs/src/main/asciidoc/nifi-in-depth.adoc ---
@@ -34,26 +34,28 @@ There are three repositories that are utilized by NiFi. 
Each exists within the O
 - The Content Repository holds the content for current and past FlowFiles.
 - The Provenance Repository holds the history of FlowFiles.
 
-image::NiFiArchitecture.png["NiFi Architecture Diagram"]
+image::zero-master-node.png["NiFi Architecture Diagram"]
--- End diff --

Rgr, I will remove it, double check it wasn't referenced by anything, amend 
the removal to your commit and push.


> Update graphics in "Apache NiFi In Depth" doc
> -
>
> Key: NIFI-2639
> URL: https://issues.apache.org/jira/browse/NIFI-2639
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 1.0.0
>Reporter: Joseph Percivall
>Assignee: Andrew Lim
>Priority: Minor
> Fix For: 1.1.0
>
>
> There are a number of graphics in the "Apache NiFi In Depth" that are screen 
> shots of a flow that currently are of the 0.x UI. 
> For aesthetics purposes, these should be updated using the new UI .



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

[GitHub] nifi pull request #1067: NIFI-2639 Update NiFi In Depth Doc: made text edits...

[JPercivall]

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

https://github.com/apache/nifi/pull/1067#discussion_r80725420
  
--- Diff: nifi-docs/src/main/asciidoc/nifi-in-depth.adoc ---
@@ -34,26 +34,28 @@ There are three repositories that are utilized by NiFi. 
Each exists within the O
 - The Content Repository holds the content for current and past FlowFiles.
 - The Provenance Repository holds the history of FlowFiles.
 
-image::NiFiArchitecture.png["NiFi Architecture Diagram"]
+image::zero-master-node.png["NiFi Architecture Diagram"]
--- End diff --

Rgr, I will remove it, double check it wasn't referenced by anything, amend 
the removal to your commit and push.


---
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 #1067: NIFI-2639 Update NiFi In Depth Doc: made text edits...

[andrewmlim]

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

https://github.com/apache/nifi/pull/1067#discussion_r80724244
  
--- Diff: nifi-docs/src/main/asciidoc/nifi-in-depth.adoc ---
@@ -34,26 +34,28 @@ There are three repositories that are utilized by NiFi. 
Each exists within the O
 - The Content Repository holds the content for current and past FlowFiles.
 - The Provenance Repository holds the history of FlowFiles.
 
-image::NiFiArchitecture.png["NiFi Architecture Diagram"]
+image::zero-master-node.png["NiFi Architecture Diagram"]
--- End diff --

Good catch.  Yes, let's remove that obsoleted image. Thanks!


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

[jira] [Commented] (NIFI-2639) Update graphics in "Apache NiFi In Depth" doc

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2639:
--

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

https://github.com/apache/nifi/pull/1067#discussion_r80724244
  
--- Diff: nifi-docs/src/main/asciidoc/nifi-in-depth.adoc ---
@@ -34,26 +34,28 @@ There are three repositories that are utilized by NiFi. 
Each exists within the O
 - The Content Repository holds the content for current and past FlowFiles.
 - The Provenance Repository holds the history of FlowFiles.
 
-image::NiFiArchitecture.png["NiFi Architecture Diagram"]
+image::zero-master-node.png["NiFi Architecture Diagram"]
--- End diff --

Good catch.  Yes, let's remove that obsoleted image. Thanks!


> Update graphics in "Apache NiFi In Depth" doc
> -
>
> Key: NIFI-2639
> URL: https://issues.apache.org/jira/browse/NIFI-2639
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 1.0.0
>Reporter: Joseph Percivall
>Assignee: Andrew Lim
>Priority: Minor
> Fix For: 1.1.0
>
>
> There are a number of graphics in the "Apache NiFi In Depth" that are screen 
> shots of a flow that currently are of the 0.x UI. 
> For aesthetics purposes, these should be updated using the new UI .



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

[jira] [Commented] (NIFI-2639) Update graphics in "Apache NiFi In Depth" doc

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2639:
--

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

https://github.com/apache/nifi/pull/1067#discussion_r80723831
  
--- Diff: nifi-docs/src/main/asciidoc/nifi-in-depth.adoc ---
@@ -34,26 +34,28 @@ There are three repositories that are utilized by NiFi. 
Each exists within the O
 - The Content Repository holds the content for current and past FlowFiles.
 - The Provenance Repository holds the history of FlowFiles.
 
-image::NiFiArchitecture.png["NiFi Architecture Diagram"]
+image::zero-master-node.png["NiFi Architecture Diagram"]
--- End diff --

Ah one thing I almost missed, can I remove the NiFiArchitecture.png image? 
I don't see it referenced anywhere else. I can just amend it to your commit.


> Update graphics in "Apache NiFi In Depth" doc
> -
>
> Key: NIFI-2639
> URL: https://issues.apache.org/jira/browse/NIFI-2639
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 1.0.0
>Reporter: Joseph Percivall
>Assignee: Andrew Lim
>Priority: Minor
> Fix For: 1.1.0
>
>
> There are a number of graphics in the "Apache NiFi In Depth" that are screen 
> shots of a flow that currently are of the 0.x UI. 
> For aesthetics purposes, these should be updated using the new UI .



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

[GitHub] nifi pull request #1067: NIFI-2639 Update NiFi In Depth Doc: made text edits...

[JPercivall]

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

https://github.com/apache/nifi/pull/1067#discussion_r80723831
  
--- Diff: nifi-docs/src/main/asciidoc/nifi-in-depth.adoc ---
@@ -34,26 +34,28 @@ There are three repositories that are utilized by NiFi. 
Each exists within the O
 - The Content Repository holds the content for current and past FlowFiles.
 - The Provenance Repository holds the history of FlowFiles.
 
-image::NiFiArchitecture.png["NiFi Architecture Diagram"]
+image::zero-master-node.png["NiFi Architecture Diagram"]
--- End diff --

Ah one thing I almost missed, can I remove the NiFiArchitecture.png image? 
I don't see it referenced anywhere else. I can just amend it to your commit.


---
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-2639) Update graphics in "Apache NiFi In Depth" doc

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2639:
--

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/1067
  
+1

Read through the docs changes, compared old/new images and did a contrib 
check build. Looks good @andrewmlim, thanks! I will merge it in.


> Update graphics in "Apache NiFi In Depth" doc
> -
>
> Key: NIFI-2639
> URL: https://issues.apache.org/jira/browse/NIFI-2639
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 1.0.0
>Reporter: Joseph Percivall
>Assignee: Andrew Lim
>Priority: Minor
> Fix For: 1.1.0
>
>
> There are a number of graphics in the "Apache NiFi In Depth" that are screen 
> shots of a flow that currently are of the 0.x UI. 
> For aesthetics purposes, these should be updated using the new UI .



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

[GitHub] nifi issue #1067: NIFI-2639 Update NiFi In Depth Doc: made text edits and re...

[JPercivall]

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/1067
  
+1

Read through the docs changes, compared old/new images and did a contrib 
check build. Looks good @andrewmlim, thanks! I will merge it in.


---
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 #1068: Ensuring Custom UI requests are correctly replicated when ...

[YolandaMDavis]

Github user YolandaMDavis commented on the issue:

https://github.com/apache/nifi/pull/1068
  
@mcgilman was able to verify that both advanced UIs for UpdateAttributes 
and JoltTransformProcessor were able to save configurations. Tests were 
performed on standalone NiFi as well as cluster mode (with single and multiple 
nodes)

+1

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.
---

[GitHub] nifi-minifi-cpp pull request #13: MINIFI-109: Add ExecuteProcess

[apiri]

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

https://github.com/apache/nifi-minifi-cpp/pull/13#discussion_r80707030
  
--- Diff: inc/ExecuteProcess.h ---
@@ -0,0 +1,112 @@
+/**
+ * @file ExecuteProcess.h
+ * ExecuteProcess class declaration
+ *
+ * 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.
+ */
+#ifndef __EXECUTE_PROCESS_H__
+#define __EXECUTE_PROCESS_H__
+
+#include 
+#include 
+#include 
+#include 
+#include 
+#include 
+#include 
+#include 
+#include 
+#include 
+#include 
+#include "FlowFileRecord.h"
+#include "Processor.h"
+#include "ProcessSession.h"
+
+//! ExecuteProcess Class
+class ExecuteProcess : public Processor
+{
+public:
+   //! Constructor
+   /*!
+* Create a new processor
+*/
+   ExecuteProcess(std::string name, uuid_t uuid = NULL)
+   : Processor(name, uuid)
+   {
+   _logger = Logger::getLogger();
+   _redirectErrorStream = false;
+   _batchDuration = 0;
+   _workingDir = ".";
+   _processRunning = false;
+   _pid = 0;
+   }
+   //! Destructor
+   virtual ~ExecuteProcess()
+   {
+   if (_processRunning && _pid > 0)
+   kill(_pid, SIGTERM);
+   }
+   //! Processor Name
+   static const std::string ProcessorName;
+   //! Supported Properties
+   static Property Command;
+   static Property CommandArgument;
--- End diff --

Would be good to update this to CommandArguments for consistency.


---
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-2341) Create a processor to parse logs formated using CEF

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2341:
--

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

https://github.com/apache/nifi/pull/785#discussion_r80719887
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/pom.xml ---
@@ -254,6 +254,17 @@ language governing permissions and limitations under 
the License. -->
 org.everit.json.schema
 1.4.0
 
+
+com.fluenda
+ParCEFone
--- End diff --

L are areas we must be picky so I wil be happy to address the NOTICE. I 
promise one day I will get this thing right. :smiley: 

I will check if I can upgrade to 3.0.0 so to reduce the amount of 
"paperwork".



> Create a processor to parse logs formated using CEF
> ---
>
> Key: NIFI-2341
> URL: https://issues.apache.org/jira/browse/NIFI-2341
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Andre
>Assignee: Andre
> Fix For: 1.1.0
>
>
> As NiFi continue to increase its abilities to complement SIEM, Splunk and ELK 
> deployments, a number of users will be looking to parse CEF formatted 
> logs[1][2].
> CEF is a format specified by Arcsight (now part of HPE) and is described in 
> detail in here:
> https://www.protect724.hpe.com/docs/DOC-1072
> [1] 
> http://apache-nifi.1125220.n5.nabble.com/Suggestion-of-processors-td9795.html
> [2] 
> https://community.hortonworks.com/questions/43185/which-processor-is-used-to-parse-cef-format-logs.html



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

[GitHub] nifi pull request #785: NIFI-2341 - Introduce ParseCEF processor

[trixpan]

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

https://github.com/apache/nifi/pull/785#discussion_r80719887
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/pom.xml ---
@@ -254,6 +254,17 @@ language governing permissions and limitations under 
the License. -->
 org.everit.json.schema
 1.4.0
 
+
+com.fluenda
+ParCEFone
--- End diff --

L are areas we must be picky so I wil be happy to address the NOTICE. I 
promise one day I will get this thing right. :smiley: 

I will check if I can upgrade to 3.0.0 so to reduce the amount of 
"paperwork".



---
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-2795) Enhance Cluster UI with System Diagnostics

[Matt Gilman (JIRA)]

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

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

> Enhance Cluster UI with System Diagnostics
> --
>
> Key: NIFI-2795
> URL: https://issues.apache.org/jira/browse/NIFI-2795
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: James Wing
>Assignee: James Wing
>Priority: Minor
> Fix For: 1.1.0
>
> Attachments: cluster-01-nodes.png, cluster-02-system.png, 
> cluster-03-jvm.png, cluster-04-flowfile-store.png, 
> cluster-05-content-store.png
>
>
> The Cluster UI currently provides some basic information on each node in the 
> cluster and options for connecting and disconnecting nodes. I propose to add 
> system diagnostics information in tables, contained in multiple tabs.  
> Roughly, the tabs should cover the same content as the System Diagnostics 
> dialog already in the System UI, but in a tabular format for comparing across 
> nodes.



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

[GitHub] nifi issue #1042: NIFI-2795 Sys Diagnostics in Cluster UI

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1042
  
@jvwing Just finished up testing and everything looks good. This has been 
merged to master. I did find another minor issue with sorting the table but I 
updated the sort method accordingly. Thanks!


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

[jira] [Commented] (NIFI-2795) Enhance Cluster UI with System Diagnostics

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2795:
--

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1042
  
@jvwing Just finished up testing and everything looks good. This has been 
merged to master. I did find another minor issue with sorting the table but I 
updated the sort method accordingly. Thanks!


> Enhance Cluster UI with System Diagnostics
> --
>
> Key: NIFI-2795
> URL: https://issues.apache.org/jira/browse/NIFI-2795
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: James Wing
>Assignee: James Wing
>Priority: Minor
> Attachments: cluster-01-nodes.png, cluster-02-system.png, 
> cluster-03-jvm.png, cluster-04-flowfile-store.png, 
> cluster-05-content-store.png
>
>
> The Cluster UI currently provides some basic information on each node in the 
> cluster and options for connecting and disconnecting nodes. I propose to add 
> system diagnostics information in tables, contained in multiple tabs.  
> Roughly, the tabs should cover the same content as the System Diagnostics 
> dialog already in the System UI, but in a tabular format for comparing across 
> nodes.



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

[jira] [Commented] (NIFI-2795) Enhance Cluster UI with System Diagnostics

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2795 Sys Diagnostics in Cluster UI
- Cleaning up tab resize loop
- Pre-authorizing sys diagnostics api calls
- Addressing issues filtering the tables in the cluster table.
- Addressing issues sorting the tables in the cluster page.


> Enhance Cluster UI with System Diagnostics
> --
>
> Key: NIFI-2795
> URL: https://issues.apache.org/jira/browse/NIFI-2795
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: James Wing
>Assignee: James Wing
>Priority: Minor
> Attachments: cluster-01-nodes.png, cluster-02-system.png, 
> cluster-03-jvm.png, cluster-04-flowfile-store.png, 
> cluster-05-content-store.png
>
>
> The Cluster UI currently provides some basic information on each node in the 
> cluster and options for connecting and disconnecting nodes. I propose to add 
> system diagnostics information in tables, contained in multiple tabs.  
> Roughly, the tabs should cover the same content as the System Diagnostics 
> dialog already in the System UI, but in a tabular format for comparing across 
> nodes.



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

[jira] [Commented] (NIFI-2341) Create a processor to parse logs formated using CEF

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2341:
--

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

https://github.com/apache/nifi/pull/785#discussion_r80709952
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/pom.xml ---
@@ -254,6 +254,17 @@ language governing permissions and limitations under 
the License. -->
 org.everit.json.schema
 1.4.0
 
+
+com.fluenda
+ParCEFone
--- End diff --

Sorry to be overly picky. This library uses javax.el-api which is licensed 
under CDDL 1.1, and its NOTICE has been copied to the NiFi overall NOTICE and 
the assembly's NOTICE. However it is not in the standard-nar's notice 
(nifi/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-nar/src/main/resources/META-INF/NOTICE).
 This should have already been included here since the Jolt UI uses it, but 
since it has not been included, do you mind adding it? Just need to add the 
following line to the CDDL 1.1 section of the aforementioned file:

(CDDL 1.1) (GPL2 w/ CPE) Expression Language 2.2.4 API  
(javax.el:javax.el-api:jar:2.2.4 - http://uel-spec.java.net)

Note that the Jolt UI uses el-api version 3.0.0 but your library is using 
2.2.4. This will cause two different versions (in two different areas once 
unpacked, so no eviction or other issues), but as a NAR we would want either 
two entries (one for each version), or perhaps consider upgrading your library 
to use 3.0.0.




> Create a processor to parse logs formated using CEF
> ---
>
> Key: NIFI-2341
> URL: https://issues.apache.org/jira/browse/NIFI-2341
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Andre
>Assignee: Andre
> Fix For: 1.1.0
>
>
> As NiFi continue to increase its abilities to complement SIEM, Splunk and ELK 
> deployments, a number of users will be looking to parse CEF formatted 
> logs[1][2].
> CEF is a format specified by Arcsight (now part of HPE) and is described in 
> detail in here:
> https://www.protect724.hpe.com/docs/DOC-1072
> [1] 
> http://apache-nifi.1125220.n5.nabble.com/Suggestion-of-processors-td9795.html
> [2] 
> https://community.hortonworks.com/questions/43185/which-processor-is-used-to-parse-cef-format-logs.html



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

[GitHub] nifi pull request #785: NIFI-2341 - Introduce ParseCEF processor

[mattyb149]

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

https://github.com/apache/nifi/pull/785#discussion_r80709952
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/pom.xml ---
@@ -254,6 +254,17 @@ language governing permissions and limitations under 
the License. -->
 org.everit.json.schema
 1.4.0
 
+
+com.fluenda
+ParCEFone
--- End diff --

Sorry to be overly picky. This library uses javax.el-api which is licensed 
under CDDL 1.1, and its NOTICE has been copied to the NiFi overall NOTICE and 
the assembly's NOTICE. However it is not in the standard-nar's notice 
(nifi/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-nar/src/main/resources/META-INF/NOTICE).
 This should have already been included here since the Jolt UI uses it, but 
since it has not been included, do you mind adding it? Just need to add the 
following line to the CDDL 1.1 section of the aforementioned file:

(CDDL 1.1) (GPL2 w/ CPE) Expression Language 2.2.4 API  
(javax.el:javax.el-api:jar:2.2.4 - http://uel-spec.java.net)

Note that the Jolt UI uses el-api version 3.0.0 but your library is using 
2.2.4. This will cause two different versions (in two different areas once 
unpacked, so no eviction or other issues), but as a NAR we would want either 
two entries (one for each version), or perhaps consider upgrading your library 
to use 3.0.0.




---
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-2639) Update graphics in "Apache NiFi In Depth" doc

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2639:
--

Github user JPercivall commented on the issue:

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


> Update graphics in "Apache NiFi In Depth" doc
> -
>
> Key: NIFI-2639
> URL: https://issues.apache.org/jira/browse/NIFI-2639
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 1.0.0
>Reporter: Joseph Percivall
>Assignee: Andrew Lim
>Priority: Minor
> Fix For: 1.1.0
>
>
> There are a number of graphics in the "Apache NiFi In Depth" that are screen 
> shots of a flow that currently are of the 0.x UI. 
> For aesthetics purposes, these should be updated using the new UI .



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