[jira] [Updated] (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 updated NIFI-2496:
--
Status: Patch Available  (was: In Progress)

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

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

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2496:
--

GitHub user scottyaslan opened a pull request:

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

[NIFI-2496] Zoom Fit now accounts for an open palette as well as the …

…breadcrumb bar

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

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

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

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


commit 58decaae9d9cdc6bda3d1a69336874fd4dd0bf5a
Author: Scott Aslan 
Date:   2016-09-30T01:15:04Z

[NIFI-2496] Zoom Fit now accounts for an open palette as well as the 
breadcrumb bar




> 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 pull request #1082: [NIFI-2496] Zoom Fit now accounts for an open palet...

[scottyaslan]

GitHub user scottyaslan opened a pull request:

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

[NIFI-2496] Zoom Fit now accounts for an open palette as well as the …

…breadcrumb bar

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

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

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

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


commit 58decaae9d9cdc6bda3d1a69336874fd4dd0bf5a
Author: Scott Aslan 
Date:   2016-09-30T01:15:04Z

[NIFI-2496] Zoom Fit now accounts for an open palette as well as the 
breadcrumb bar




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

[GitHub] nifi-minifi-cpp issue #15: MINIFI-111 Providing explicit inclusion of cstrin...

[apiri]

Github user apiri commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/15
  
@randerzander good deal, glad to hear it.  I was inspired when you 
mentioned this earlier and also have some work in progress to get travis up and 
running.  have some library/distro versioning issues to sort through, but 
should have some automated testing covering our environments shortly.  thanks 
for bringing this to our attention!


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

[GitHub] nifi-minifi-cpp issue #15: MINIFI-111 Providing explicit inclusion of cstrin...

[randerzander]

Github user randerzander commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/15
  
awesome, thanks @apiri worked for me too.


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

[GitHub] nifi-minifi-cpp issue #15: MINIFI-111 Providing explicit inclusion of cstrin...

[apiri]

Github user apiri commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/15
  
@randerzander this fixed things for me on my CentOS system


---
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 #15: MINIFI-111 Providing explicit inclusion of...

[apiri]

GitHub user apiri opened a pull request:

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

MINIFI-111 Providing explicit inclusion of cstring in ExecuteProcess

MINIFI-111 Providing explicit inclusion of cstring in ExecuteProcess.

This takes care of correcting the build issue on gcc based build systems 
from the inclusion of a new processor in #13 

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

$ git pull https://github.com/apiri/nifi-minifi-cpp minifi-111

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

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


commit 37981ab78a9b941f3dc340dd16ad983eda1ce7aa
Author: Aldrin Piri 
Date:   2016-09-29T23:27:06Z

MINIFI-111 Providing explicit inclusion of cstring in ExecuteProcess needed 
by gcc environments.




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

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

[apiri]

Github user apiri commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/13
  
@randerzander Great, thanks!


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

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

[randerzander]

Github user randerzander commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/13
  
I have opened https://issues.apache.org/jira/browse/MINIFI-111


---
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-2800) GetFile Processor Appends overrides last slash in filename to always be \

[Michael Moser (JIRA)]

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

Michael Moser commented on NIFI-2800:
-

I suppose we could have used File.separator here, but what would happen if 
attributes captured on Windows with backslashes is then sent over to a NIFI 
running on a Linux box?  Both Windows and Linux systems work (in Java) with the 
forward slash, so we chose to just go with that.

This decision was made long before ExecuteStreamProcess was built.  Would need 
a bit of consensus before just changing this as if it was a mistake.

> GetFile Processor Appends overrides last slash in filename to always be \
> -
>
> Key: NIFI-2800
> URL: https://issues.apache.org/jira/browse/NIFI-2800
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.0.0
> Environment: This was discovered on a windows machine running nifi 
> server locally
>Reporter: Christopher Gambino
>Priority: Minor
>
> When using the GetFile processor all flowfiles created have an 
> "Absolute.Path" attribute.  This absolute path is taken from the directory 
> field of the GetFile configuration.  The last slash in the directory is 
> always over-ridden to be '/' even when the user puts "\" in the directory 
> structure. 
> Example:
> Configuraton - "Directory": "C:\Samplepath\SampleFolder\"
> Output Flowfile - "Absolute.Path": "C:\Samplepath\SampleFolder/"
> I believe the intended function of this should not replace the last \ with a 
> /.  This creates issues when using the attribute in later stages with other 
> processors such as ExecuteStreamProcess.



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

[jira] [Updated] (NIFI-2847) In NiFi Cluster window, filtering "by status" or "by address" do not work as expected

[Andrew Lim (JIRA)]

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

Andrew Lim updated NIFI-2847:
-
Description: 
Attaching a screenshot of what this window displays when no filters are applied 
to the displayed results for a 3 node cluster.

When filtering "by status":
-If I enter "CONNECTED", all 3 results are shown.
-But if I enter "CONNECTED,"  or "COORDINATOR", no results are shown.  I 
expected this to filter out all nodes except the cluster coordinator.

When filtering "by address":
-if I enter "localhost", all 3 results are shown.
-But if I enter "localhost:" or any of the ports (9443, for example), no 
results are shown.  I think it is a very common use case to filter by port.

  was:
Attaching a screenshot of what this window displays when no filters are applied 
to the displayed results.

When filtering "by status":
-If I enter "CONNECTED", all 3 results are shown.
-But if I enter "CONNECTED,"  or "COORDINATOR", no results are shown.  I 
expected this to filter out all nodes except the cluster coordinator.

When filtering "by address":
-if I enter "localhost", all 3 results are shown.
-But if I enter "localhost:" or any of the ports (9443, for example), no 
results are shown.  I think it is a very common use case to filter by port.


> In NiFi Cluster window, filtering "by status" or "by address" do not work as 
> expected
> -
>
> Key: NIFI-2847
> URL: https://issues.apache.org/jira/browse/NIFI-2847
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
> Attachments: NIFI-2847_NiFiClusterFilter.png
>
>
> Attaching a screenshot of what this window displays when no filters are 
> applied to the displayed results for a 3 node cluster.
> When filtering "by status":
> -If I enter "CONNECTED", all 3 results are shown.
> -But if I enter "CONNECTED,"  or "COORDINATOR", no results are shown.  I 
> expected this to filter out all nodes except the cluster coordinator.
> When filtering "by address":
> -if I enter "localhost", all 3 results are shown.
> -But if I enter "localhost:" or any of the ports (9443, for example), no 
> results are shown.  I think it is a very common use case to filter by port.



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

[jira] [Updated] (NIFI-2847) In NiFi Cluster window, filtering "by status" or "by address" do not work as expected

[Andrew Lim (JIRA)]

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

Andrew Lim updated NIFI-2847:
-
Attachment: NIFI-2847_NiFiClusterFilter.png

> In NiFi Cluster window, filtering "by status" or "by address" do not work as 
> expected
> -
>
> Key: NIFI-2847
> URL: https://issues.apache.org/jira/browse/NIFI-2847
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
> Attachments: NIFI-2847_NiFiClusterFilter.png
>
>
> Attaching a screenshot of what this window displays when no filters are 
> applied to the displayed results.
> When filtering "by status":
> -If I enter "CONNECTED", all 3 results are shown.
> -But if I enter "CONNECTED,"  or "COORDINATOR", no results are shown.  I 
> expected this to filter out all nodes except the cluster coordinator.
> When filtering "by address":
> -if I enter "localhost", all 3 results are shown.
> -But if I enter "localhost:" or any of the ports (9443, for example), no 
> results are shown.  I think it is a very common use case to filter by port.



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

[jira] [Updated] (NIFI-2840) Not clear how templates are ordered when adding to canvas

[Andrew Lim (JIRA)]

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

Andrew Lim updated NIFI-2840:
-
Attachment: (was: NIFI-2840_NiFiClusterFilter.png)

> Not clear how templates are ordered when adding to canvas
> -
>
> Key: NIFI-2840
> URL: https://issues.apache.org/jira/browse/NIFI-2840
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Priority: Minor
>  Labels: UI
> Attachments: NIFI-2840_addTemplateOrder.png
>
>
> As shown in the attached screenshot, the ordering of the templates is not 
> alphabetical.  It is also not ordered by time of import.
> If there is an ordering being applied, it should be made more 
> transparent/obvious to the user.
> My personal preference is for the ordering to be done by last imported.  So 
> the top-most available selection is the most recently imported template, 
> which would seem logical.  I'm assuming if a user has imported a template, 
> he/she would like to then immediately add it to the flow.



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

[jira] [Updated] (NIFI-2840) Not clear how templates are ordered when adding to canvas

[Andrew Lim (JIRA)]

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

Andrew Lim updated NIFI-2840:
-
Attachment: NIFI-2840_NiFiClusterFilter.png

> Not clear how templates are ordered when adding to canvas
> -
>
> Key: NIFI-2840
> URL: https://issues.apache.org/jira/browse/NIFI-2840
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Priority: Minor
>  Labels: UI
> Attachments: NIFI-2840_NiFiClusterFilter.png, 
> NIFI-2840_addTemplateOrder.png
>
>
> As shown in the attached screenshot, the ordering of the templates is not 
> alphabetical.  It is also not ordered by time of import.
> If there is an ordering being applied, it should be made more 
> transparent/obvious to the user.
> My personal preference is for the ordering to be done by last imported.  So 
> the top-most available selection is the most recently imported template, 
> which would seem logical.  I'm assuming if a user has imported a template, 
> he/she would like to then immediately add it to the flow.



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

[jira] [Created] (NIFI-2847) In NiFi Cluster window, filtering "by status" or "by address" do not work as expected

[Andrew Lim (JIRA)]

Andrew Lim created NIFI-2847:


 Summary: In NiFi Cluster window, filtering "by status" or "by 
address" do not work as expected
 Key: NIFI-2847
 URL: https://issues.apache.org/jira/browse/NIFI-2847
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core UI
Affects Versions: 1.0.0
Reporter: Andrew Lim


Attaching a screenshot of what this window displays when no filters are applied 
to the displayed results.

When filtering "by status":
-If I enter "CONNECTED", all 3 results are shown.
-But if I enter "CONNECTED,"  or "COORDINATOR", no results are shown.  I 
expected this to filter out all nodes except the cluster coordinator.

When filtering "by address":
-if I enter "localhost", all 3 results are shown.
-But if I enter "localhost:" or any of the ports (9443, for example), no 
results are shown.  I think it is a very common use case to filter by port.



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

[jira] [Commented] (NIFI-2783) Command line site-to-site client in toolkit would be useful

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2783:
--

Github user brosander commented on the issue:

https://github.com/apache/nifi/pull/1056
  
@bbende I didn't notice the settings were that low, bumped them up a bit


> Command line site-to-site client in toolkit would be useful
> ---
>
> Key: NIFI-2783
> URL: https://issues.apache.org/jira/browse/NIFI-2783
> Project: Apache NiFi
>  Issue Type: New Feature
>Reporter: Bryan Rosander
>
> A command line site-to-site client in the toolkit would be beneficial in 
> several scenarios:
> 1. Easily pipe data into, out of NiFi flows using command line utilities or 
> other (non-java) programs makes integrating other tools with NiFi trivial
> 2. Easier to debug site-to-site issues when only one NiFi instance is 
> involved in the troubleshooting process
> 3. Dev testing site-to-site is easier command line reproduction of 
> issues/validation of functionality



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

[GitHub] nifi issue #1056: NIFI-2783 - Site-to-site command line client

[brosander]

Github user brosander commented on the issue:

https://github.com/apache/nifi/pull/1056
  
@bbende I didn't notice the settings were that low, bumped them up a bit


---
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-1912) PutEmail doesn't send formatted email when there is an attachment with the message

[Pierre Villard (JIRA)]

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

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

> PutEmail doesn't send formatted email when there is an attachment with the 
> message
> --
>
> Key: NIFI-1912
> URL: https://issues.apache.org/jira/browse/NIFI-1912
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 0.6.1
>Reporter: Ravi Bhushan Ratnakar
>Assignee: Pierre Villard
>Priority: Critical
> Fix For: 1.1.0
>
>
> When I am trying to send formatted email with an attachment using PutEmail 
> processor, all the html tags are displayed as it is like a text(This).
> After going through the code what i observed that when there is an 
> attachment, in that case content type is hard coded to 'text/plain'. Below 
> code  snippet from PutEmail 
> if (context.getProperty(ATTACH_FILE).asBoolean()) {
> final MimeBodyPart mimeText = new 
> PreencodedMimeBodyPart("base64");
> mimeText.setDataHandler(new DataHandler(new 
> ByteArrayDataSource(
> Base64.encodeBase64(messageText.getBytes("UTF-8")), 
> "text/plain; charset=\"utf-8\"")));



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

[jira] [Commented] (NIFI-1912) PutEmail doesn't send formatted email when there is an attachment with the message

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1912:
--

GitHub user pvillard31 opened a pull request:

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

NIFI-1912 - PutEmail fixed format when attachment

Correction as suggested by users in JIRA.
+ adding a unit test to check attachments.

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

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

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

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


commit 007430f706a936e4e46b013aa7e30b11ed7bd0af
Author: Pierre Villard 
Date:   2016-09-29T20:47:04Z

NIFI-1912 - PutEmail fixed format when attachment

Correction as suggested by users in JIRA.
+ adding a unit test to check attachments.




> PutEmail doesn't send formatted email when there is an attachment with the 
> message
> --
>
> Key: NIFI-1912
> URL: https://issues.apache.org/jira/browse/NIFI-1912
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 0.6.1
>Reporter: Ravi Bhushan Ratnakar
>Priority: Critical
> Fix For: 1.1.0
>
>
> When I am trying to send formatted email with an attachment using PutEmail 
> processor, all the html tags are displayed as it is like a text(This).
> After going through the code what i observed that when there is an 
> attachment, in that case content type is hard coded to 'text/plain'. Below 
> code  snippet from PutEmail 
> if (context.getProperty(ATTACH_FILE).asBoolean()) {
> final MimeBodyPart mimeText = new 
> PreencodedMimeBodyPart("base64");
> mimeText.setDataHandler(new DataHandler(new 
> ByteArrayDataSource(
> Base64.encodeBase64(messageText.getBytes("UTF-8")), 
> "text/plain; charset=\"utf-8\"")));



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

[GitHub] nifi pull request #1081: NIFI-1912 - PutEmail fixed format when attachment

[pvillard31]

GitHub user pvillard31 opened a pull request:

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

NIFI-1912 - PutEmail fixed format when attachment

Correction as suggested by users in JIRA.
+ adding a unit test to check attachments.

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

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

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

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


commit 007430f706a936e4e46b013aa7e30b11ed7bd0af
Author: Pierre Villard 
Date:   2016-09-29T20:47:04Z

NIFI-1912 - PutEmail fixed format when attachment

Correction as suggested by users in JIRA.
+ adding a unit test to check attachments.




---
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 #914: Adding support for Binary Row Keys

[a-aravindan]

Github user a-aravindan commented on the issue:

https://github.com/apache/nifi/pull/914
  
Hi All,
This nifi-**-nar-0.6.1.nar created for this request is not working with HDP 
2.3.4. It is throwing the ERROR "failed to process due to 
java.lang.NoSuchMethodError: org.apache.nifi.hbase.put.PutColumn."
nar files used:
nifi-standard-services-api-nar-0.6.1.nar 
nifi-hbase-nar-0.6.1.nar 
nifi-hbase_1_1_2-client-service-nar-0.6.1.nar

Thanks
Aravind


---
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-2838) In the Advanced UI, if the Rule name is very long, the "x" to delete the rule becomes unavailable

[Andrew Lim (JIRA)]

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

Andrew Lim updated NIFI-2838:
-
Attachment: NIFI-2838_twoXicons.png

> In the Advanced UI, if the Rule name is very long, the "x" to delete the rule 
> becomes unavailable
> -
>
> Key: NIFI-2838
> URL: https://issues.apache.org/jira/browse/NIFI-2838
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Priority: Minor
>  Labels: UI
> Attachments: NIFI-2838_noDeleteIcon.png, NIFI-2838_twoXicons.png
>
>
> As shown in the attached screenshot, when the rule name is very long it 
> extends the whole width of the bar, so the "x" to delete the rule is no 
> longer selectable.
> Note: There is also a scroll bar that appears in this part of the UI, which I 
> thought would possibly reveal the "x", but the scroll bar doesn't appear to 
> add any value.  The width of the rule name bar doesn't extend the width of 
> the space.



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

[jira] [Updated] (NIFI-2838) In the Advanced UI, if the Rule name is very long, the "x" to delete the rule becomes unavailable

[Andrew Lim (JIRA)]

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

Andrew Lim updated NIFI-2838:
-
Attachment: (was: NIFI-2838_twoXicons.png)

> In the Advanced UI, if the Rule name is very long, the "x" to delete the rule 
> becomes unavailable
> -
>
> Key: NIFI-2838
> URL: https://issues.apache.org/jira/browse/NIFI-2838
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Priority: Minor
>  Labels: UI
> Attachments: NIFI-2838_noDeleteIcon.png, NIFI-2838_twoXicons.png
>
>
> As shown in the attached screenshot, when the rule name is very long it 
> extends the whole width of the bar, so the "x" to delete the rule is no 
> longer selectable.
> Note: There is also a scroll bar that appears in this part of the UI, which I 
> thought would possibly reveal the "x", but the scroll bar doesn't appear to 
> add any value.  The width of the rule name bar doesn't extend the width of 
> the space.



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

[jira] [Commented] (NIFI-2838) In the Advanced UI, if the Rule name is very long, the "x" to delete the rule becomes unavailable

[Andrew Lim (JIRA)]

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

Andrew Lim commented on NIFI-2838:
--

Also just noticing that if you add/select another rule below the long named 
rule, two "x" icons appear.  See attached screenshot.

> In the Advanced UI, if the Rule name is very long, the "x" to delete the rule 
> becomes unavailable
> -
>
> Key: NIFI-2838
> URL: https://issues.apache.org/jira/browse/NIFI-2838
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Priority: Minor
>  Labels: UI
> Attachments: NIFI-2838_noDeleteIcon.png, NIFI-2838_twoXicons.png
>
>
> As shown in the attached screenshot, when the rule name is very long it 
> extends the whole width of the bar, so the "x" to delete the rule is no 
> longer selectable.
> Note: There is also a scroll bar that appears in this part of the UI, which I 
> thought would possibly reveal the "x", but the scroll bar doesn't appear to 
> add any value.  The width of the rule name bar doesn't extend the width of 
> the space.



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

[jira] [Updated] (NIFI-2838) In the Advanced UI, if the Rule name is very long, the "x" to delete the rule becomes unavailable

[Andrew Lim (JIRA)]

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

Andrew Lim updated NIFI-2838:
-
Attachment: NIFI-2838_twoXicons.png

> In the Advanced UI, if the Rule name is very long, the "x" to delete the rule 
> becomes unavailable
> -
>
> Key: NIFI-2838
> URL: https://issues.apache.org/jira/browse/NIFI-2838
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Priority: Minor
>  Labels: UI
> Attachments: NIFI-2838_noDeleteIcon.png, NIFI-2838_twoXicons.png
>
>
> As shown in the attached screenshot, when the rule name is very long it 
> extends the whole width of the bar, so the "x" to delete the rule is no 
> longer selectable.
> Note: There is also a scroll bar that appears in this part of the UI, which I 
> thought would possibly reveal the "x", but the scroll bar doesn't appear to 
> add any value.  The width of the rule name bar doesn't extend the width of 
> the space.



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

[jira] [Updated] (NIFI-2838) In the Advanced UI, if the Rule name is very long, the "x" to delete the rule becomes unavailable

[Andrew Lim (JIRA)]

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

Andrew Lim updated NIFI-2838:
-
Priority: Minor  (was: Major)

> In the Advanced UI, if the Rule name is very long, the "x" to delete the rule 
> becomes unavailable
> -
>
> Key: NIFI-2838
> URL: https://issues.apache.org/jira/browse/NIFI-2838
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Priority: Minor
>  Labels: UI
> Attachments: NIFI-2838_noDeleteIcon.png
>
>
> As shown in the attached screenshot, when the rule name is very long it 
> extends the whole width of the bar, so the "x" to delete the rule is no 
> longer selectable.
> Note: There is also a scroll bar that appears in this part of the UI, which I 
> thought would possibly reveal the "x", but the scroll bar doesn't appear to 
> add any value.  The width of the rule name bar doesn't extend the width of 
> the space.



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

[jira] [Commented] (NIFI-2838) In the Advanced UI, if the Rule name is very long, the "x" to delete the rule becomes unavailable

[Andrew Lim (JIRA)]

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

Andrew Lim commented on NIFI-2838:
--

I just noticed that the "x" to delete the rule can become visible if you resize 
the browser window enough to reveal the entire rule name.  However, this is 
still a problem though for a really long rule name, where even resizing doesn't 
help.

> In the Advanced UI, if the Rule name is very long, the "x" to delete the rule 
> becomes unavailable
> -
>
> Key: NIFI-2838
> URL: https://issues.apache.org/jira/browse/NIFI-2838
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>  Labels: UI
> Attachments: NIFI-2838_noDeleteIcon.png
>
>
> As shown in the attached screenshot, when the rule name is very long it 
> extends the whole width of the bar, so the "x" to delete the rule is no 
> longer selectable.
> Note: There is also a scroll bar that appears in this part of the UI, which I 
> thought would possibly reveal the "x", but the scroll bar doesn't appear to 
> add any value.  The width of the rule name bar doesn't extend the width of 
> the space.



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

[jira] [Updated] (NIFI-2838) In the Advanced UI, if the Rule name is very long, the "x" to delete the rule becomes unavailable

[Andrew Lim (JIRA)]

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

Andrew Lim updated NIFI-2838:
-
Attachment: NIFI-2838_noDeleteIcon.png

> In the Advanced UI, if the Rule name is very long, the "x" to delete the rule 
> becomes unavailable
> -
>
> Key: NIFI-2838
> URL: https://issues.apache.org/jira/browse/NIFI-2838
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>  Labels: UI
> Attachments: NIFI-2838_noDeleteIcon.png
>
>
> As shown in the attached screenshot, when the rule name is very long it 
> extends the whole width of the bar, so the "x" to delete the rule is no 
> longer selectable.
> Note: There is also a scroll bar that appears in this part of the UI, which I 
> thought would possibly reveal the "x", but the scroll bar doesn't appear to 
> add any value.  The width of the rule name bar doesn't extend the width of 
> the space.



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

[jira] [Updated] (NIFI-2840) Not clear how templates are ordered when adding to canvas

[Andrew Lim (JIRA)]

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

Andrew Lim updated NIFI-2840:
-
Attachment: NIFI-2840_addTemplateOrder.png

> Not clear how templates are ordered when adding to canvas
> -
>
> Key: NIFI-2840
> URL: https://issues.apache.org/jira/browse/NIFI-2840
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Priority: Minor
>  Labels: UI
> Attachments: NIFI-2840_addTemplateOrder.png
>
>
> As shown in the attached screenshot, the ordering of the templates is not 
> alphabetical.  It is also not ordered by time of import.
> If there is an ordering being applied, it should be made more 
> transparent/obvious to the user.
> My personal preference is for the ordering to be done by last imported.  So 
> the top-most available selection is the most recently imported template, 
> which would seem logical.  I'm assuming if a user has imported a template, 
> he/she would like to then immediately add it to the flow.



--
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=15533918#comment-15533918
 ] 

ASF GitHub Bot commented on NIFI-2832:
--

Github user mcgilman commented on the issue:

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


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

[GitHub] nifi issue #1074: NIFI-2832 State management should be part of the documenta...

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1074
  
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] [Resolved] (NIFI-2846) Align text in Global Menu

[Andrew Lim (JIRA)]

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

Andrew Lim resolved NIFI-2846.
--
Resolution: Duplicate

Dupe of https://issues.apache.org/jira/browse/NIFI-2788 which addressed this 
issue.

> Align text in Global Menu
> -
>
> Key: NIFI-2846
> URL: https://issues.apache.org/jira/browse/NIFI-2846
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Priority: Minor
> Attachments: NIFI-2846_globalMenuText.png
>
>
> As shown in the attached screenshot, the text of the selections available in 
> the Global Menu are not aligned.  "Cluster" is the most obvious.



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

[jira] [Updated] (NIFI-2846) Align text in Global Menu

[Andrew Lim (JIRA)]

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

Andrew Lim updated NIFI-2846:
-
Attachment: NIFI-2846_globalMenuText.png

> Align text in Global Menu
> -
>
> Key: NIFI-2846
> URL: https://issues.apache.org/jira/browse/NIFI-2846
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Priority: Minor
> Attachments: NIFI-2846_globalMenuText.png
>
>
> As shown in the attached screenshot, the text of the selections available in 
> the Global Menu are not aligned.  "Cluster" is the most obvious.



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

[jira] [Created] (NIFI-2846) Align text in Global Menu

[Andrew Lim (JIRA)]

Andrew Lim created NIFI-2846:


 Summary: Align text in Global Menu
 Key: NIFI-2846
 URL: https://issues.apache.org/jira/browse/NIFI-2846
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Core UI
Affects Versions: 1.0.0
Reporter: Andrew Lim
Priority: Minor


As shown in the attached screenshot, the text of the selections available in 
the Global Menu are not aligned.  "Cluster" is the most obvious.



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

[jira] [Created] (NIFI-2845) Add help text to JoltTransformJSON advanced UI

[Sarah Olson (JIRA)]

Sarah Olson created NIFI-2845:
-

 Summary: Add help text to JoltTransformJSON advanced UI
 Key: NIFI-2845
 URL: https://issues.apache.org/jira/browse/NIFI-2845
 Project: Apache NiFi
  Issue Type: Bug
Affects Versions: 1.0.0
Reporter: Sarah Olson
Priority: Minor


To address a few questions about how to use the JoltTransformJSON advanced UI, 
I suggest adding some help text between the top and bottom halves of the UI. 
Something similar to:

Test your Jolt specification below



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

[jira] [Assigned] (NIFI-2843) UI - Process Group Context Menu

[Matt Gilman (JIRA)]

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

Matt Gilman reassigned NIFI-2843:
-

Assignee: Matt Gilman

> UI - Process Group Context Menu
> ---
>
> Key: NIFI-2843
> URL: https://issues.apache.org/jira/browse/NIFI-2843
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>Priority: Minor
>
> The context menu for the Process Group lists both Configure and View 
> Configuration menu items. Investigate possibly removing the view 
> configuration dialog as the Configure dialog supports read-only mode when the 
> user does not have permissions.



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

[jira] [Commented] (NIFI-2783) Command line site-to-site client in toolkit would be useful

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2783:
--

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/1056
  
@brosander this is really cool! Been playing with it and seems to be 
working well. 

I noticed in the scripts that we set the max heap to 24mb, I was wondering 
if there is any concern about that being too low. For the most part the 
input/output is streaming so I guess we would only have to worry about a single 
DataPacket coming in that was greater than 24mb? 


> Command line site-to-site client in toolkit would be useful
> ---
>
> Key: NIFI-2783
> URL: https://issues.apache.org/jira/browse/NIFI-2783
> Project: Apache NiFi
>  Issue Type: New Feature
>Reporter: Bryan Rosander
>
> A command line site-to-site client in the toolkit would be beneficial in 
> several scenarios:
> 1. Easily pipe data into, out of NiFi flows using command line utilities or 
> other (non-java) programs makes integrating other tools with NiFi trivial
> 2. Easier to debug site-to-site issues when only one NiFi instance is 
> involved in the troubleshooting process
> 3. Dev testing site-to-site is easier command line reproduction of 
> issues/validation of functionality



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

[GitHub] nifi issue #1056: NIFI-2783 - Site-to-site command line client

[bbende]

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/1056
  
@brosander this is really cool! Been playing with it and seems to be 
working well. 

I noticed in the scripts that we set the max heap to 24mb, I was wondering 
if there is any concern about that being too low. For the most part the 
input/output is streaming so I guess we would only have to worry about a single 
DataPacket coming in that was greater than 24mb? 


---
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-2115) Enhanced About Box Version Information

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2115:
--

Github user jvwing commented on the issue:

https://github.com/apache/nifi/pull/583
  
I pushed another update to rebase on the latest master, and add a Versions 
tab to the Cluster UI using the version-enriched system diagnostics data.


> Enhanced About Box Version Information
> --
>
> Key: NIFI-2115
> URL: https://issues.apache.org/jira/browse/NIFI-2115
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI, Tools and Build
>Affects Versions: 1.0.0
>Reporter: James Wing
>Assignee: James Wing
>Priority: Minor
> Attachments: screenshot-1-of-4-about-expands.png, 
> screenshot-2-of-4-git-build.png, screenshot-3-of-4-release-build.png, 
> screenshot-4-of-4-source-build.png
>
>
> The UI's About dialog and underlying API provide the version of NiFi, like 
> "0.7.0-SNAPSHOT".  For many bug reports and troubleshooting requests, this is 
> not very precise, especially around rapidly changing code or 
> platform-dependent behavior.  It would help if NiFi captured and displayed 
> additional information:  
> * NiFi build commit hash
> * NiFi build branch
> * NiFi build date/time
> * Java Version
> * Java Vendor (Oracle, OpenJDK)
> * OS
> Then a simple copy/paste from the about box would provide very specific 
> information about a particular NiFi installation and which code it was 
> derived from.



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

[GitHub] nifi issue #583: NIFI-2115 Detailed Version Info for About Box

[jvwing]

Github user jvwing commented on the issue:

https://github.com/apache/nifi/pull/583
  
I pushed another update to rebase on the latest master, and add a Versions 
tab to the Cluster UI using the version-enriched system diagnostics data.


---
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 #12: Minifi 109

[benqiu2016]

Github user benqiu2016 closed the pull request at:

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


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

[GitHub] nifi-minifi-cpp issue #12: Minifi 109

[benqiu2016]

Github user benqiu2016 commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/12
  
Close as Aldrin suggested.


---
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-2844) The icon for the component is cut-off in the Cluster Summary window.

[Andrew Lim (JIRA)]

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

Andrew Lim commented on NIFI-2844:
--

Also, consider making the icons and text larger if possible to improve 
readability.

> The icon for the component is cut-off in the Cluster  Summary 
> window.
> 
>
> Key: NIFI-2844
> URL: https://issues.apache.org/jira/browse/NIFI-2844
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Priority: Minor
> Attachments: NIFI-2844_connection.png, NIFI-2844_inputPort.png, 
> NIFI-2844_outputPort.png, NIFI-2844_processor.png
>
>
> In a clustered environment, select "Summary" from the Global Menu.
> As an example, in the Processors tab, select "View processor details" icon 
> (the 3 cube cluster icon) for one of the processors.  The icon shown for the 
> processor is cut-off at the top.
> This also occurs for the following components:
> -Input Ports
> -Output Ports
> -Connections
> Screenshots attached.



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

[jira] [Updated] (NIFI-1851) NiFi summary filter displays wrong number of total results for Process Groups after refresh

[Scott Aslan (JIRA)]

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

Scott Aslan updated NIFI-1851:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> NiFi summary filter displays wrong number of total results for Process Groups 
> after refresh
> ---
>
> Key: NIFI-1851
> URL: https://issues.apache.org/jira/browse/NIFI-1851
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 0.6.0
>Reporter: Andrew Lim
>Assignee: Scott Aslan
>Priority: Minor
> Attachments: NIFI-1851_zeroResultsProcessGroup.png
>
>
> Pre-conditions:
> Flow that has multiple process groups
> Steps to Reproduce:
> 1. Go to NiFi Summary Page
> 2. Select Process Groups tab
> 3. Note the numbers displayed next to the Filter ie. Displaying 5 of 5
> 4. Select the "Refresh" icon next to the Process Groups tab
> 5.  The numbers displayed will now be "Displaying x of 0"   (see attached 
> screenshot)



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

[jira] [Updated] (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 updated NIFI-2831:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> "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] [Updated] (NIFI-2844) The icon for the component is cut-off in the Cluster Summary window.

[Andrew Lim (JIRA)]

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

Andrew Lim updated NIFI-2844:
-
Attachment: NIFI-2844_processor.png
NIFI-2844_outputPort.png
NIFI-2844_inputPort.png
NIFI-2844_connection.png

> The icon for the component is cut-off in the Cluster  Summary 
> window.
> 
>
> Key: NIFI-2844
> URL: https://issues.apache.org/jira/browse/NIFI-2844
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Priority: Minor
> Attachments: NIFI-2844_connection.png, NIFI-2844_inputPort.png, 
> NIFI-2844_outputPort.png, NIFI-2844_processor.png
>
>
> In a clustered environment, select "Summary" from the Global Menu.
> As an example, in the Processors tab, select "View processor details" icon 
> (the 3 cube cluster icon) for one of the processors.  The icon shown for the 
> processor is cut-off at the top.
> This also occurs for the following components:
> -Input Ports
> -Output Ports
> -Connections
> Screenshots attached.



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

[jira] [Updated] (NIFI-2833) Increase font-size and line-height for message text in small dialogs

[Scott Aslan (JIRA)]

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

Scott Aslan updated NIFI-2833:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Increase font-size and line-height for message text in small dialogs
> 
>
> Key: NIFI-2833
> URL: https://issues.apache.org/jira/browse/NIFI-2833
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Rob Moran
>Assignee: Scott Aslan
>Priority: Minor
> Attachments: current.png, proposed.png
>
>
> In small dialogs where error and various messages are communicated to the 
> user, the text is quite small. I'd recommend increasing the size and line 
> spacing to:
> font-size: 13px;
> line-height: 1.3;
> See attached screenshots for a current example and the proposed change.



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

[jira] [Commented] (NIFI-2844) The icon for the component is cut-off in the Cluster Summary window.

[Andrew Lim (JIRA)]

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

Andrew Lim commented on NIFI-2844:
--

Note:  For processors, the icon itself is incorrect.  The Data Provenance icon 
is used instead of the Processor icon.   I can create a separate Jira for this 
if necessary.

> The icon for the component is cut-off in the Cluster  Summary 
> window.
> 
>
> Key: NIFI-2844
> URL: https://issues.apache.org/jira/browse/NIFI-2844
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Priority: Minor
>
> In a clustered environment, select "Summary" from the Global Menu.
> As an example, in the Processors tab, select "View processor details" icon 
> (the 3 cube cluster icon) for one of the processors.  The icon shown for the 
> processor is cut-off at the top.
> This also occurs for the following components:
> -Input Ports
> -Output Ports
> -Connections
> Screenshots attached.



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

[jira] [Created] (NIFI-2844) The icon for the component is cut-off in the Cluster Summary window.

[Andrew Lim (JIRA)]

Andrew Lim created NIFI-2844:


 Summary: The icon for the component is cut-off in the Cluster 
 Summary window.
 Key: NIFI-2844
 URL: https://issues.apache.org/jira/browse/NIFI-2844
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core UI
Affects Versions: 1.0.0
Reporter: Andrew Lim
Priority: Minor


In a clustered environment, select "Summary" from the Global Menu.

As an example, in the Processors tab, select "View processor details" icon (the 
3 cube cluster icon) for one of the processors.  The icon shown for the 
processor is cut-off at the top.

This also occurs for the following components:
-Input Ports
-Output Ports
-Connections

Screenshots attached.



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

[jira] [Created] (NIFI-2843) UI - Process Group Context Menu

[Matt Gilman (JIRA)]

Matt Gilman created NIFI-2843:
-

 Summary: UI - Process Group Context Menu
 Key: NIFI-2843
 URL: https://issues.apache.org/jira/browse/NIFI-2843
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core UI
Reporter: Matt Gilman
Priority: Minor


The context menu for the Process Group lists both Configure and View 
Configuration menu items. Investigate possibly removing the view configuration 
dialog as the Configure dialog supports read-only mode when the user does not 
have permissions.



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

[jira] [Updated] (NIFI-2841) SplitAvro Processor is Broken

[Bryan Bende (JIRA)]

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

Bryan Bende updated NIFI-2841:
--
Attachment: NIFI-2841.patch

The attached patch should avoid making two consecutive calls to 
reader.hasNext(), although I would really like to reproduce the problem to know 
for sure that this solves it. Existing unit tests still pass.

I know there has been one other change to SplitAvro after the 1.0.0 release, so 
if you wanted to try this out you could apply this patch to master and do a 
build of that, and then take the updated Avro NAR.

> SplitAvro Processor is Broken
> -
>
> Key: NIFI-2841
> URL: https://issues.apache.org/jira/browse/NIFI-2841
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: David Hicks
>Priority: Critical
> Attachments: NIFI-2841.patch
>
>
> This is largely the fault of the Avro DataFileStream reader, but it's making 
> the processor unusable.  The problem appears to occur when you make the 
> following series of calls (which happens because of the splitSize comparison):
> reader.next() -> returns last element
> reader.hasNext() -> returns false
> reader.hasNext() -> returns true
> reader.next() -> EOFException
> org.apache.nifi.processor.exception.ProcessException: IOException thrown from 
> SplitAvro[id=22e03ca4-0151-4474-92fc-040e1fe12ab9]: java.io.EOFException
>   at 
> org.apache.nifi.controller.repository.StandardProcessSession.write(StandardProcessSession.java:2013)
>  ~[na:na]
>   at 
> org.apache.nifi.processors.avro.SplitAvro$RecordSplitter$1.process(SplitAvro.java:250)
>  ~[nifi-avro-processors-0.7.0.jar:0.7.0]
>   at 
> org.apache.nifi.controller.repository.StandardProcessSession.read(StandardProcessSession.java:1851)
>  ~[na:na]
>   at 
> org.apache.nifi.controller.repository.StandardProcessSession.read(StandardProcessSession.java:1822)
>  ~[na:na]
>   at 
> org.apache.nifi.processors.avro.SplitAvro$RecordSplitter.split(SplitAvro.java:236)
>  ~[nifi-avro-processors-0.7.0.jar:0.7.0]
>   at 
> org.apache.nifi.processors.avro.SplitAvro.onTrigger(SplitAvro.java:202) 
> ~[nifi-avro-processors-0.7.0.jar:0.7.0]
>   at 
> org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
>  [nifi-api-0.7.0.jar:0.7.0]
>   at 
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1054)
>  [nifi-framework-core-0.7.0.jar:0.7.0]
>   at 
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136)
>  [nifi-framework-core-0.7.0.jar:0.7.0]
>   at 
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
>  [nifi-framework-core-0.7.0.jar:0.7.0]
>   at 
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:127)
>  [nifi-framework-core-0.7.0.jar:0.7.0]
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [na:1.8.0_101]
>   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
> [na:1.8.0_101]
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>  [na:1.8.0_101]
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>  [na:1.8.0_101]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [na:1.8.0_101]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [na:1.8.0_101]
>   at java.lang.Thread.run(Thread.java:745) [na:1.8.0_101]
> Caused by: java.io.EOFException: null
>   at 
> org.apache.avro.io.BinaryDecoder.ensureBounds(BinaryDecoder.java:473) 
> ~[avro-1.7.7.jar:1.7.7]
>   at org.apache.avro.io.BinaryDecoder.readInt(BinaryDecoder.java:128) 
> ~[avro-1.7.7.jar:1.7.7]
>   at org.apache.avro.io.BinaryDecoder.readString(BinaryDecoder.java:259) 
> ~[avro-1.7.7.jar:1.7.7]
>   at 
> org.apache.avro.io.ResolvingDecoder.readString(ResolvingDecoder.java:201) 
> ~[avro-1.7.7.jar:1.7.7]
>   at 
> org.apache.avro.generic.GenericDatumReader.readString(GenericDatumReader.java:363)
>  ~[avro-1.7.7.jar:1.7.7]
>   at 
> org.apache.avro.generic.GenericDatumReader.readString(GenericDatumReader.java:355)
>  ~[avro-1.7.7.jar:1.7.7]
>   at 
> org.apache.avro.generic.GenericDatumReader.read(GenericDatumReader.java:157) 
> ~[avro-1.7.7.jar:1.7.7]
>   at 
> org.apache.avro.generic.GenericDatumReader.readField(GenericDatumReader.java:193)
>  ~[avro-1.7.7.jar:1.7.7]
>   at 
> org.apache.avro.generic.GenericDatumReader.readRecord(GenericDatumReader.java:183)
>  ~[avro-1.7.7.jar:1.7.7]
>   at 
> 

[jira] [Commented] (NIFI-1851) NiFi summary filter displays wrong number of total results for Process Groups after refresh

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1851:
--

Github user asfgit closed the pull request at:

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


> NiFi summary filter displays wrong number of total results for Process Groups 
> after refresh
> ---
>
> Key: NIFI-1851
> URL: https://issues.apache.org/jira/browse/NIFI-1851
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 0.6.0
>Reporter: Andrew Lim
>Assignee: Scott Aslan
>Priority: Minor
> Attachments: NIFI-1851_zeroResultsProcessGroup.png
>
>
> Pre-conditions:
> Flow that has multiple process groups
> Steps to Reproduce:
> 1. Go to NiFi Summary Page
> 2. Select Process Groups tab
> 3. Note the numbers displayed next to the Filter ie. Displaying 5 of 5
> 4. Select the "Refresh" icon next to the Process Groups tab
> 5.  The numbers displayed will now be "Displaying x of 0"   (see attached 
> screenshot)



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

[GitHub] nifi pull request #1079: [NIFI-1851] correctly display number of total proce...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1079: [NIFI-1851] correctly display number of total process grou...

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1079
  
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-1851) NiFi summary filter displays wrong number of total results for Process Groups after refresh

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1851:
--

Github user mcgilman commented on the issue:

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


> NiFi summary filter displays wrong number of total results for Process Groups 
> after refresh
> ---
>
> Key: NIFI-1851
> URL: https://issues.apache.org/jira/browse/NIFI-1851
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 0.6.0
>Reporter: Andrew Lim
>Assignee: Scott Aslan
>Priority: Minor
> Attachments: NIFI-1851_zeroResultsProcessGroup.png
>
>
> Pre-conditions:
> Flow that has multiple process groups
> Steps to Reproduce:
> 1. Go to NiFi Summary Page
> 2. Select Process Groups tab
> 3. Note the numbers displayed next to the Filter ie. Displaying 5 of 5
> 4. Select the "Refresh" icon next to the Process Groups tab
> 5.  The numbers displayed will now be "Displaying x of 0"   (see attached 
> screenshot)



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

[GitHub] nifi issue #1079: [NIFI-1851] correctly display number of total process grou...

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1079
  
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-2831) "Auto-terminate" should be used consistently in Settings tab

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2831:
--

Github user asfgit closed the pull request at:

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


> "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 pull request #1077: [NIFI-2831] update auto terminate messages

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1077: [NIFI-2831] update auto terminate messages

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1077
  
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-2759) TestListDatabaseTables.testListTablesMultipleRefresh consistently failing

[Joe Skora (JIRA)]

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

Joe Skora commented on NIFI-2759:
-

I think this is timing related.  I noticed that the test fails when running the 
project test suite, but that if running just for the 
{{nifi-standard-processors}} module it passes.  It may just need adjustment of 
the refresh interval or sleep period in the test.

> TestListDatabaseTables.testListTablesMultipleRefresh consistently failing
> -
>
> Key: NIFI-2759
> URL: https://issues.apache.org/jira/browse/NIFI-2759
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Joe Skora
>Priority: Critical
>
> Running this test repeatedly produces errors.
> {code}
> Running org.apache.nifi.processors.standard.TestListDatabaseTables
> Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 13.114 sec 
> <<< FAILURE! - in org.apache.nifi.processors.standard.TestListDatabaseTables
> testListTablesMultipleRefresh(org.apache.nifi.processors.standard.TestListDatabaseTables)
>   Time elapsed: 0.794 sec  <<< FAILURE!
> java.lang.AssertionError: expected:<1> but was:<2>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:645)
> at org.junit.Assert.assertEquals(Assert.java:631)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.assertTransferCount(StandardProcessorTestRunner.java:318)
> at 
> org.apache.nifi.processors.standard.TestListDatabaseTables.testListTablesMultipleRefresh(TestListDatabaseTables.java:216)
> {code}
> followed by 
> {code}
> Failed tests:
>   TestListDatabaseTables.testListTablesMultipleRefresh:216 expected:<1> but 
> was:<2>
> {code}
> I tried removing the 
> [runner.clearTransferState();|https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/test/java/org/apache/nifi/processors/standard/TestListDatabaseTables.java#L210]
>  thinking the reset was causing both tables to show but that did not make a 
> difference.



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

[jira] [Updated] (NIFI-2824) Errors encountered when saving from Advanced UI (UpdateAttribute, JoltTransformProcessor)

[Yolanda M. Davis (JIRA)]

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

Yolanda M. Davis updated NIFI-2824:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

PR merged

> Errors encountered when saving from Advanced UI (UpdateAttribute, 
> JoltTransformProcessor)
> -
>
> Key: NIFI-2824
> URL: https://issues.apache.org/jira/browse/NIFI-2824
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Yolanda M. Davis
>Assignee: Matt Gilman
> Fix For: 1.1.0
>
>
> When attempting to save configuration changes using the Advanced UI for 
> UpdateAttributes or JoltTransformProcessor the following example exception 
> stack trace was encountered in a secured clustered environment (e.g. 
> Transaction already in progress):
> Received a status of 409 from ydavis-ldap-nifi-demo-1.openstacklocal:9091 for 
> request PUT /nifi-api/processors/66ce1842-0157-1000--7e910d9e when 
> performing first stage of two-stage commit. The action will not occur. Node 
> explanation: Transaction d12cd676-5140-4f1a-95c3-5e44689f2b37 is already in 
> progress.
> 2016-09-26 16:07:43,445 ERROR [NiFi Web Server-22] 
> c.s.j.spi.container.ContainerResponse The RuntimeException could not be 
> mapped to a response, re-throwing to the HTTP container
> org.apache.nifi.cluster.manager.exception.IllegalClusterStateException: Node 
> ydavis-ldap-nifi-demo-1.openstacklocal:9091 is unable to fulfill this request 
> due to: Transaction d12cd676-5140-4f1a-95c3-5e44689f2b37 is already in 
> progress.
>   at 
> org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$2.onCompletion(ThreadPoolRequestReplicator.java:473)
>  ~[na:na]
>   at 
> org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$NodeHttpRequest.run(ThreadPoolRequestReplicator.java:729)
>  ~[na:na]
>   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> ~[na:1.8.0_77]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[na:1.8.0_77]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  ~[na:1.8.0_77]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  ~[na:1.8.0_77]
>   at java.lang.Thread.run(Thread.java:745) [na:1.8.0_77]
> 2016-09-26 16:07:43,454 WARN [NiFi Web Server-22] 
> org.eclipse.jetty.servlet.ServletHandler 
> /nifi-jolt-transform-json-ui-1.1.0-SNAPSHOT/api/standard/processor/properties
> org.apache.nifi.cluster.manager.exception.IllegalClusterStateException: Node 
> ydavis-ldap-nifi-demo-1.openstacklocal:9091 is unable to fulfill this request 
> due to: Transaction d12cd676-5140-4f1a-95c3-5e44689f2b37 is already in 
> progress.
>   at 
> org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$2.onCompletion(ThreadPoolRequestReplicator.java:473)
>  ~[na:na]
>   at 
> org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$NodeHttpRequest.run(ThreadPoolRequestReplicator.java:729)
>  ~[na:na]
>   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> ~[na:1.8.0_77]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[na:1.8.0_77]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  ~[na:1.8.0_77]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  ~[na:1.8.0_77]
>   at java.lang.Thread.run(Thread.java:745) [na:1.8.0_77]



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

[jira] [Commented] (NIFI-2833) Increase font-size and line-height for message text in small dialogs

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2833:
--

Github user mcgilman commented on the issue:

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


> Increase font-size and line-height for message text in small dialogs
> 
>
> Key: NIFI-2833
> URL: https://issues.apache.org/jira/browse/NIFI-2833
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Rob Moran
>Assignee: Scott Aslan
>Priority: Minor
> Attachments: current.png, proposed.png
>
>
> In small dialogs where error and various messages are communicated to the 
> user, the text is quite small. I'd recommend increasing the size and line 
> spacing to:
> font-size: 13px;
> line-height: 1.3;
> See attached screenshots for a current example and the proposed change.



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

[jira] [Commented] (NIFI-2833) Increase font-size and line-height for message text in small dialogs

[ASF subversion and git services (JIRA)]

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

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

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

[NIFI-2833] Increase font size and line height for small dialogs. This closes 
#1078


> Increase font-size and line-height for message text in small dialogs
> 
>
> Key: NIFI-2833
> URL: https://issues.apache.org/jira/browse/NIFI-2833
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Rob Moran
>Assignee: Scott Aslan
>Priority: Minor
> Attachments: current.png, proposed.png
>
>
> In small dialogs where error and various messages are communicated to the 
> user, the text is quite small. I'd recommend increasing the size and line 
> spacing to:
> font-size: 13px;
> line-height: 1.3;
> See attached screenshots for a current example and the proposed change.



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

[jira] [Commented] (NIFI-2833) Increase font-size and line-height for message text in small dialogs

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2833:
--

Github user asfgit closed the pull request at:

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


> Increase font-size and line-height for message text in small dialogs
> 
>
> Key: NIFI-2833
> URL: https://issues.apache.org/jira/browse/NIFI-2833
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Rob Moran
>Assignee: Scott Aslan
>Priority: Minor
> Attachments: current.png, proposed.png
>
>
> In small dialogs where error and various messages are communicated to the 
> user, the text is quite small. I'd recommend increasing the size and line 
> spacing to:
> font-size: 13px;
> line-height: 1.3;
> See attached screenshots for a current example and the proposed change.



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

[GitHub] nifi issue #1078: [NIFI-2833] Increase font size and line height for small d...

[mcgilman]

Github user mcgilman commented on the issue:

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

[GitHub] nifi pull request #1078: [NIFI-2833] Increase font size and line height for ...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1080: NIFI-766 Added icon on connection when backpressure is ena...

[mcgilman]

Github user mcgilman commented on the issue:

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


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

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

[apiri]

Github user apiri commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/13
  
Thanks!  Just makes it a little easier to cover as that one was closed out. 
 Much appreciated.  Was able to reproduce on a Linux environment.


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

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2429:
--

Github user mosermw commented on the issue:

https://github.com/apache/nifi/pull/1072
  
@markap14 any interest or time to review this?


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

[GitHub] nifi issue #1072: NIFI-2429 PersistentProvenanceRepository bug fixes

[mosermw]

Github user mosermw commented on the issue:

https://github.com/apache/nifi/pull/1072
  
@markap14 any interest or time to review this?


---
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-1768) Add SSL Support for Solr Processors

[Bryan Bende (JIRA)]

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

Bryan Bende updated NIFI-1768:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Add SSL Support for Solr Processors
> ---
>
> Key: NIFI-1768
> URL: https://issues.apache.org/jira/browse/NIFI-1768
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Bryan Bende
>Assignee: Bryan Bende
>Priority: Minor
> Fix For: 1.1.0
>
>
> Currently the Solr processors do not support communicating with a Solr 
> instance that is secured with SSL. 
> We should be able to add the SSLContextService to the processor and pass an 
> SSLContext to the underlying HttpClient used by the SolrClient in the 
> SolrProcessor base class.



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

[jira] [Updated] (NIFI-1980) Add 'commit within' value to PutSolrContentStream

[Bryan Bende (JIRA)]

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

Bryan Bende updated NIFI-1980:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Add 'commit within' value to PutSolrContentStream
> -
>
> Key: NIFI-1980
> URL: https://issues.apache.org/jira/browse/NIFI-1980
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.6.1
> Environment: Solr 6.0.1 in **standalone** mode (in a docker 
> container).
>Reporter: Andrew Grande
>Assignee: Bryan Bende
>Priority: Minor
> Fix For: 1.1.0
>
>
> Here's a default docker image for Solr with some instructions to create a 
> core: https://github.com/docker-solr/docker-solr
> Have NiFi send to that Solr instance. Everything seems ok, but the number of 
> documents in the core never increases, no commit happens. *Commit Within* 
> must be configured (number of milliseconds) in case of a standalone Solr.
> Often Solr server is configured with auto-commit, but apparently not this 
> default docker image.
> Proposal: update the processor to have a default value for Commit Within 
> (e.g. match Solr's default of 15 seconds or less). Update its description to 
> hint the user to remove the value in case they configure auto-commit in Solr.



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

[jira] [Updated] (NIFI-2568) Add Kerberos Support to Solr Processors

[Bryan Bende (JIRA)]

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

Bryan Bende updated NIFI-2568:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Add Kerberos Support to Solr Processors
> ---
>
> Key: NIFI-2568
> URL: https://issues.apache.org/jira/browse/NIFI-2568
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 1.0.0, 0.7.0
>Reporter: Bryan Bende
>Assignee: Bryan Bende
>Priority: Minor
> Fix For: 1.1.0
>
>
> We should add support to the Solr processors for interacting with a 
> kerberized Solr cloud instance. The following pages described how Kerberos 
> works in Solr:
> https://cwiki.apache.org/confluence/display/solr/Kerberos+Authentication+Plugin
> From a client perspective it says you need the following:
> {code}
> System.setProperty("java.security.auth.login.config", 
> "/home/foo/jaas-client.conf");
> HttpClientUtil.setConfigurer(new Krb5HttpClientConfigurer());
> {code}



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

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

[randerzander]

Github user randerzander commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/13
  
Will do. I assumed you would have considered it part of the original
ExecuteProcess jira. Will reply here shortly

On Sep 29, 2016 9:21 AM, "Aldrin Piri"  wrote:

hey @randerzander  would you mind please
opening a ticket in JIRA to report this so we can track appropriately?
https://issues.apache.org/jira/browse/MINIFI

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
,
or mute the thread


.



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

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

[apiri]

Github user apiri commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/13
  
hey @randerzander would you mind please opening a ticket in JIRA to report 
this so we can track appropriately?  
https://issues.apache.org/jira/browse/MINIFI


---
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-2709) Email processors with Exchange don't output to RFC2822 format

[Andre (JIRA)]

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

Andre commented on NIFI-2709:
-

[~bende] I think this is the same issue the folk at the community experienced.

> Email processors with Exchange don't output to RFC2822 format
> -
>
> Key: NIFI-2709
> URL: https://issues.apache.org/jira/browse/NIFI-2709
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0
> Environment: Ubuntu 16.04 LTS with openjdk-8-jre-headless
>Reporter: Emil Frank
>Priority: Minor
> Attachments: screenshot-1.png
>
>
> When using the new ConsumeIMAP and ConsumePOP3 processors with a Microsoft 
> Exchange 2013 IMAP server the flowfiles which are produced are simple HTML 
> messages with no RFC2822 headers. I have also tried setting Exchange to force 
> emails to be text only, sadly only the body with some Content-Type: fields 
> are outputed.
> This mean that ExtractEmailHeaders and ExtractEmailAttachments cannot be used 
> directly with these processors.
> In Python, I can force Exchange to output the headers by specify RFC822 in 
> the connection settings:
> - https://docs.python.org/3/library/imaplib.html#imap4-example
> Is a similar option available for the spring mail framework?



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

[jira] [Commented] (NIFI-2841) SplitAvro Processor is Broken

[David Hicks (JIRA)]

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

David Hicks commented on NIFI-2841:
---

Ah, you're right.  I shouldn't have included the bit about any and all files.  
I removed it from the description.  I'm dealing with a sensitive data set, so I 
can't just send the file.  I'm trying to track down how my files are created so 
I can send you one.

> SplitAvro Processor is Broken
> -
>
> Key: NIFI-2841
> URL: https://issues.apache.org/jira/browse/NIFI-2841
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: David Hicks
>Priority: Critical
>
> This is largely the fault of the Avro DataFileStream reader, but it's making 
> the processor unusable.  The problem appears to occur when you make the 
> following series of calls (which happens because of the splitSize comparison):
> reader.next() -> returns last element
> reader.hasNext() -> returns false
> reader.hasNext() -> returns true
> reader.next() -> EOFException
> org.apache.nifi.processor.exception.ProcessException: IOException thrown from 
> SplitAvro[id=22e03ca4-0151-4474-92fc-040e1fe12ab9]: java.io.EOFException
>   at 
> org.apache.nifi.controller.repository.StandardProcessSession.write(StandardProcessSession.java:2013)
>  ~[na:na]
>   at 
> org.apache.nifi.processors.avro.SplitAvro$RecordSplitter$1.process(SplitAvro.java:250)
>  ~[nifi-avro-processors-0.7.0.jar:0.7.0]
>   at 
> org.apache.nifi.controller.repository.StandardProcessSession.read(StandardProcessSession.java:1851)
>  ~[na:na]
>   at 
> org.apache.nifi.controller.repository.StandardProcessSession.read(StandardProcessSession.java:1822)
>  ~[na:na]
>   at 
> org.apache.nifi.processors.avro.SplitAvro$RecordSplitter.split(SplitAvro.java:236)
>  ~[nifi-avro-processors-0.7.0.jar:0.7.0]
>   at 
> org.apache.nifi.processors.avro.SplitAvro.onTrigger(SplitAvro.java:202) 
> ~[nifi-avro-processors-0.7.0.jar:0.7.0]
>   at 
> org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
>  [nifi-api-0.7.0.jar:0.7.0]
>   at 
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1054)
>  [nifi-framework-core-0.7.0.jar:0.7.0]
>   at 
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136)
>  [nifi-framework-core-0.7.0.jar:0.7.0]
>   at 
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
>  [nifi-framework-core-0.7.0.jar:0.7.0]
>   at 
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:127)
>  [nifi-framework-core-0.7.0.jar:0.7.0]
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [na:1.8.0_101]
>   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
> [na:1.8.0_101]
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>  [na:1.8.0_101]
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>  [na:1.8.0_101]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [na:1.8.0_101]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [na:1.8.0_101]
>   at java.lang.Thread.run(Thread.java:745) [na:1.8.0_101]
> Caused by: java.io.EOFException: null
>   at 
> org.apache.avro.io.BinaryDecoder.ensureBounds(BinaryDecoder.java:473) 
> ~[avro-1.7.7.jar:1.7.7]
>   at org.apache.avro.io.BinaryDecoder.readInt(BinaryDecoder.java:128) 
> ~[avro-1.7.7.jar:1.7.7]
>   at org.apache.avro.io.BinaryDecoder.readString(BinaryDecoder.java:259) 
> ~[avro-1.7.7.jar:1.7.7]
>   at 
> org.apache.avro.io.ResolvingDecoder.readString(ResolvingDecoder.java:201) 
> ~[avro-1.7.7.jar:1.7.7]
>   at 
> org.apache.avro.generic.GenericDatumReader.readString(GenericDatumReader.java:363)
>  ~[avro-1.7.7.jar:1.7.7]
>   at 
> org.apache.avro.generic.GenericDatumReader.readString(GenericDatumReader.java:355)
>  ~[avro-1.7.7.jar:1.7.7]
>   at 
> org.apache.avro.generic.GenericDatumReader.read(GenericDatumReader.java:157) 
> ~[avro-1.7.7.jar:1.7.7]
>   at 
> org.apache.avro.generic.GenericDatumReader.readField(GenericDatumReader.java:193)
>  ~[avro-1.7.7.jar:1.7.7]
>   at 
> org.apache.avro.generic.GenericDatumReader.readRecord(GenericDatumReader.java:183)
>  ~[avro-1.7.7.jar:1.7.7]
>   at 
> org.apache.avro.generic.GenericDatumReader.read(GenericDatumReader.java:151) 
> ~[avro-1.7.7.jar:1.7.7]
>   at 
> org.apache.avro.generic.GenericDatumReader.read(GenericDatumReader.java:142) 
> ~[avro-1.7.7.jar:1.7.7]
>   at 

[jira] [Updated] (NIFI-2841) SplitAvro Processor is Broken

[David Hicks (JIRA)]

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

David Hicks updated NIFI-2841:
--
Description: 
This is largely the fault of the Avro DataFileStream reader, but it's making 
the processor unusable.  The problem appears to occur when you make the 
following series of calls (which happens because of the splitSize comparison):
reader.next() -> returns last element
reader.hasNext() -> returns false
reader.hasNext() -> returns true
reader.next() -> EOFException

org.apache.nifi.processor.exception.ProcessException: IOException thrown from 
SplitAvro[id=22e03ca4-0151-4474-92fc-040e1fe12ab9]: java.io.EOFException
at 
org.apache.nifi.controller.repository.StandardProcessSession.write(StandardProcessSession.java:2013)
 ~[na:na]
at 
org.apache.nifi.processors.avro.SplitAvro$RecordSplitter$1.process(SplitAvro.java:250)
 ~[nifi-avro-processors-0.7.0.jar:0.7.0]
at 
org.apache.nifi.controller.repository.StandardProcessSession.read(StandardProcessSession.java:1851)
 ~[na:na]
at 
org.apache.nifi.controller.repository.StandardProcessSession.read(StandardProcessSession.java:1822)
 ~[na:na]
at 
org.apache.nifi.processors.avro.SplitAvro$RecordSplitter.split(SplitAvro.java:236)
 ~[nifi-avro-processors-0.7.0.jar:0.7.0]
at 
org.apache.nifi.processors.avro.SplitAvro.onTrigger(SplitAvro.java:202) 
~[nifi-avro-processors-0.7.0.jar:0.7.0]
at 
org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
 [nifi-api-0.7.0.jar:0.7.0]
at 
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1054)
 [nifi-framework-core-0.7.0.jar:0.7.0]
at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136)
 [nifi-framework-core-0.7.0.jar:0.7.0]
at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
 [nifi-framework-core-0.7.0.jar:0.7.0]
at 
org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:127)
 [nifi-framework-core-0.7.0.jar:0.7.0]
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
[na:1.8.0_101]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
[na:1.8.0_101]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
 [na:1.8.0_101]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
 [na:1.8.0_101]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
[na:1.8.0_101]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
[na:1.8.0_101]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_101]
Caused by: java.io.EOFException: null
at 
org.apache.avro.io.BinaryDecoder.ensureBounds(BinaryDecoder.java:473) 
~[avro-1.7.7.jar:1.7.7]
at org.apache.avro.io.BinaryDecoder.readInt(BinaryDecoder.java:128) 
~[avro-1.7.7.jar:1.7.7]
at org.apache.avro.io.BinaryDecoder.readString(BinaryDecoder.java:259) 
~[avro-1.7.7.jar:1.7.7]
at 
org.apache.avro.io.ResolvingDecoder.readString(ResolvingDecoder.java:201) 
~[avro-1.7.7.jar:1.7.7]
at 
org.apache.avro.generic.GenericDatumReader.readString(GenericDatumReader.java:363)
 ~[avro-1.7.7.jar:1.7.7]
at 
org.apache.avro.generic.GenericDatumReader.readString(GenericDatumReader.java:355)
 ~[avro-1.7.7.jar:1.7.7]
at 
org.apache.avro.generic.GenericDatumReader.read(GenericDatumReader.java:157) 
~[avro-1.7.7.jar:1.7.7]
at 
org.apache.avro.generic.GenericDatumReader.readField(GenericDatumReader.java:193)
 ~[avro-1.7.7.jar:1.7.7]
at 
org.apache.avro.generic.GenericDatumReader.readRecord(GenericDatumReader.java:183)
 ~[avro-1.7.7.jar:1.7.7]
at 
org.apache.avro.generic.GenericDatumReader.read(GenericDatumReader.java:151) 
~[avro-1.7.7.jar:1.7.7]
at 
org.apache.avro.generic.GenericDatumReader.read(GenericDatumReader.java:142) 
~[avro-1.7.7.jar:1.7.7]
at org.apache.avro.file.DataFileStream.next(DataFileStream.java:233) 
~[avro-1.7.7.jar:1.7.7]
at 
org.apache.nifi.processors.avro.SplitAvro$RecordSplitter$1$1.process(SplitAvro.java:259)
 ~[nifi-avro-processors-0.7.0.jar:0.7.0]
at 
org.apache.nifi.controller.repository.StandardProcessSession.write(StandardProcessSession.java:1998)
 ~[na:na]
... 17 common frames omitted


  was:
This is largely the fault of the Avro DataFileStream reader, but it's making 
the processor unusable.  The problem appears to occur when you make the 
following series of calls (which happens because of the splitSize comparison):
reader.next() -> returns last element
reader.hasNext() -> returns false
reader.hasNext() ->