[GitHub] nifi-minifi-cpp issue #4: MINIFI-6: Basic C++ implementation for MiNiFi

[apiri]

Github user apiri commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/4
  
Hey @benqiu2016.  I've had the opportunity to review this and scope out the 
functionality with the help of your README and it seems to be working well in 
communicating with the NiFi instance.  To get a bit more granular, I was 
thinking of merging this into the ongoing MINIFI-6 branch so we can continue to 
iterate and evolve and maybe break things down a bit further.

Overall, the functionality has been great and working quite well.  I've had 
success with the code on OS X and a couple distros of Linux.

Let me know your thoughts! 


---
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-2270) Update app splash (loading...) screen

[Scott Aslan (JIRA)]

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

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

> Update app splash (loading...) screen
> -
>
> Key: NIFI-2270
> URL: https://issues.apache.org/jira/browse/NIFI-2270
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Rob Moran
>Assignee: Scott Aslan
> Attachments: nifi-2270_loading-app.png, nifi-drop-splash.svg
>
>
> See attached mockup *nifi-2270_loading-app.png*
> SVG of NiFi drop attached too *nifi-drop-splash.svg*
> ---
> * Page backround-color: #a3b5be
> * SVG image is 80% of viewport height
> * Use angular material progress circular, color #ba554a
> * Image and spinner should be horizontally and vertically centered



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

[GitHub] nifi issue #655: DataDog support added

[irabinovitch]

Github user irabinovitch commented on the issue:

https://github.com/apache/nifi/pull/655
  
Making it configurable makes sense. That being said the recommended method 
would be to submit metrics via metrics-datadog's statsd implementation.  This 
ensures the metrics are emitted asynchronously, and are buffered should 
connectivity between NiFi and Datadog be interrupted any reason.  


---
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 #655: DataDog support added

[irabinovitch]

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

https://github.com/apache/nifi/pull/655#discussion_r71451069
  
--- Diff: 
nifi-nar-bundles/nifi-datadog-bundle/nifi-datadog-reporting-task/src/main/resources/docs/org.apache.nifi.reporting.ambari.AmbariReportingTask/additionalDetails.html
 ---
@@ -0,0 +1,56 @@
+
+
+
+
+
+DataDogReportingTask
+
+
+
+
+DataDogReportingTask
+
+This ReportingTask sends the following metrics to DataDog:
--- End diff --

If we can determine some base metrics that apply to everyone, I'd be happy 
to help you create a default dashboard in the Datadog service.


---
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-2107) Other panels like 'content-viewer' still using old style

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2107:
--

GitHub user scottyaslan opened a pull request:

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

[NIFI-2107] [NIFI-2143] Update content-viewer, error, and login pages…

…. Fix Provenance filter combo text

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

$ git pull https://github.com/scottyaslan/nifi devBranch

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

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


commit 230f46bbc409185d83395148d8121f654b9705b1
Author: Scott Aslan 
Date:   2016-07-19T22:42:45Z

[NIFI-2107] [NIFI-2143] Update content-viewer, error, and login pages. Fix 
Provenance filter combo text




> Other panels like 'content-viewer' still using old style
> 
>
> Key: NIFI-2107
> URL: https://issues.apache.org/jira/browse/NIFI-2107
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Joseph Witt
>Assignee: Scott Aslan
> Fix For: 1.0.0
>
> Attachments: bg-error.png, nifi-2107_content-viewer.png
>
>




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

[jira] [Updated] (NIFI-2107) Other panels like 'content-viewer' still using old style

[Scott Aslan (JIRA)]

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

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

> Other panels like 'content-viewer' still using old style
> 
>
> Key: NIFI-2107
> URL: https://issues.apache.org/jira/browse/NIFI-2107
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Joseph Witt
>Assignee: Scott Aslan
> Fix For: 1.0.0
>
> Attachments: bg-error.png, nifi-2107_content-viewer.png
>
>




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

[jira] [Updated] (NIFI-2143) Provenance "Filter By" drop-down truncates selected value

[Scott Aslan (JIRA)]

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

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

> Provenance "Filter By" drop-down truncates selected value
> -
>
> Key: NIFI-2143
> URL: https://issues.apache.org/jira/browse/NIFI-2143
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Mark Payne
>Assignee: Scott Aslan
>Priority: Minor
> Fix For: 1.0.0
>
>
> When I open the Provenance page, on the left-hand side where I have the 
> option to filter the results, the selected value is "by component n..." 
> instead of "by component name". When I click the drop-down, I do see the full 
> "by component name" but it is truncated when selected.
> Also, I would recommend we change "by type" to "by event type" in order to 
> disambiguate between "by component type" and "by type".



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

[jira] [Assigned] (NIFI-2270) Update app splash (loading...) screen

[Scott Aslan (JIRA)]

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

Scott Aslan reassigned NIFI-2270:
-

Assignee: Scott Aslan

> Update app splash (loading...) screen
> -
>
> Key: NIFI-2270
> URL: https://issues.apache.org/jira/browse/NIFI-2270
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Rob Moran
>Assignee: Scott Aslan
> Attachments: nifi-2270_loading-app.png, nifi-drop-splash.svg
>
>
> See attached mockup *nifi-2270_loading-app.png*
> SVG of NiFi drop attached too *nifi-drop-splash.svg*
> ---
> * Page backround-color: #a3b5be
> * SVG image is 80% of viewport height
> * Use angular material progress circular, color #ba554a
> * Image and spinner should be horizontally and vertically centered



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

[jira] [Commented] (NIFI-1214) Mock Framework should allow order-independent assumptions on FlowFiles

[Joseph Percivall (JIRA)]

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

Joseph Percivall commented on NIFI-1214:


Hey [~Toivo Adams], I see the PR has conflicts with master. Can you resolve 
them or can we punt this to 1.1?

> Mock Framework should allow order-independent assumptions on FlowFiles
> --
>
> Key: NIFI-1214
> URL: https://issues.apache.org/jira/browse/NIFI-1214
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Tools and Build
>Reporter: Mark Payne
>Assignee: Toivo Adams
> Fix For: 1.0.0
>
>
> A common pattern in unit testing is to iterate over all FlowFiles that are 
> output to a Relationship and verify that each FlowFile matches one criteria 
> or another and that all criteria are met. For example, the following code 
> snippet from TestRouteText  verifies that two FlowFiles were output and that 
> Criteria A was met by one of them and Criteria B was met by the other:
> {code}
> final List list = 
> runner.getFlowFilesForRelationship("o");
> boolean found1 = false;
> boolean found2 = false;
> for (final MockFlowFile mff : list) {
> if (mff.getAttribute(RouteText.GROUP_ATTRIBUTE_KEY).equals("1")) {
> mff.assertContentEquals("1,hello\n1,good-bye");
> found1 = true;
> } else {
> mff.assertAttributeEquals(RouteText.GROUP_ATTRIBUTE_KEY, "2");
> mff.assertContentEquals("2,world\n");
> found2 = true;
> }
> }
> assertTrue(found1);
> assertTrue(found2);
> {code}
> This is very verbose, and error-prone. It could be done much more concisely 
> if we have a method like:
> {code}
> TestRunner.assertAllConditionsMet( Relationship relationship, 
> FlowFileVerifier... verifier );
> {code}
> Where FlowFileVerifier is able to verify some condition on a FlowFile. This 
> method would then be responsible for ensuring that each FlowFile that was 
> routed to 'relationship' meets one of the criteria specified by a verifier, 
> and that all of the verifiers were met. For example:
> {code}
> runner.assertAllConditionsMet( "o", 
> { mff -> mff.isAttributeEqual(RouteText.GROUP_ATTRIBUTE_KEY, "1") && 
> mff.isContentEqual("1,hello\n1,good-bye") },
> { mff -> mff.isAttributeEqual(RouteText.GROUP_ATTRIBUTE_KEY, "2") && 
> mff.isContentEqual("2,world\n") }
> );
> {code}



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

[jira] [Created] (NIFI-2325) Add support for LDAPS in authentication provider

[Joseph Witt (JIRA)]

Joseph Witt created NIFI-2325:
-

 Summary: Add support for LDAPS in authentication provider
 Key: NIFI-2325
 URL: https://issues.apache.org/jira/browse/NIFI-2325
 Project: Apache NiFi
  Issue Type: Improvement
Reporter: Joseph Witt


[~mcgilman] [~alopresto] please add thoughts if you have them.

I propose we add support for LDAPS despite StartTLS being the now preferred 
approach.  This offers more flexibility for use with many of the long standing 
LDAP environments out there.




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

[jira] [Assigned] (NIFI-2076) New Inline Controller Service Dialog

[Scott Aslan (JIRA)]

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

Scott Aslan reassigned NIFI-2076:
-

Assignee: Scott Aslan

> New Inline Controller Service Dialog
> 
>
> Key: NIFI-2076
> URL: https://issues.apache.org/jira/browse/NIFI-2076
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Scott Aslan
> Fix For: 1.0.0
>
>
> - is too wide



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

[jira] [Assigned] (NIFI-2143) Provenance "Filter By" drop-down truncates selected value

[Scott Aslan (JIRA)]

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

Scott Aslan reassigned NIFI-2143:
-

Assignee: Scott Aslan

> Provenance "Filter By" drop-down truncates selected value
> -
>
> Key: NIFI-2143
> URL: https://issues.apache.org/jira/browse/NIFI-2143
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Mark Payne
>Assignee: Scott Aslan
>Priority: Minor
> Fix For: 1.0.0
>
>
> When I open the Provenance page, on the left-hand side where I have the 
> option to filter the results, the selected value is "by component n..." 
> instead of "by component name". When I click the drop-down, I do see the full 
> "by component name" but it is truncated when selected.
> Also, I would recommend we change "by type" to "by event type" in order to 
> disambiguate between "by component type" and "by type".



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

[jira] [Assigned] (NIFI-2025) Birdseye does not update when repositioning an existing item on the canvas

[Scott Aslan (JIRA)]

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

Scott Aslan reassigned NIFI-2025:
-

Assignee: Scott Aslan

> Birdseye does not update when repositioning an existing item on the canvas
> --
>
> Key: NIFI-2025
> URL: https://issues.apache.org/jira/browse/NIFI-2025
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Scott Aslan
>Assignee: Scott Aslan
> Fix For: 1.0.0
>
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> Birdseye does not update when repositioning an existing item on the canvas 
> but it does update appropriately when adding/deleting items from the canvas. 
> We need to refresh the birdseye when repositioning items on the canvas.



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

[jira] [Resolved] (NIFI-1782) UI - Refresh NiFi Header to global menu

[Scott Aslan (JIRA)]

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

Scott Aslan resolved NIFI-1782.
---
Resolution: Fixed

> UI - Refresh NiFi Header to global menu
> ---
>
> Key: NIFI-1782
> URL: https://issues.apache.org/jira/browse/NIFI-1782
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Scott Aslan
>Assignee: Scott Aslan
> Fix For: 1.0.0
>
>
> AC:
> -Configure ngMaterial theme to match UX definitions per 
> https://docs.google.com/document/d/1G1g0zNxdbSJUEH8hm_p1asuf8FE4k-nNFNbpPbK-3po/edit#
> -Introduce new flowfonts and font awesome
> -Update User name display
> -Update login/logout display
> -Update Banner display
> -Update search UX
> -Manage Flow status values with angular service and display using angular 
> dual binding
> -Flow status hover menu
> -Bulletins UX
> -Implement new global menu complete with the foillowing actions
> --Summary
> --Counters
> --Bulletin Board
> --Data Provenance
> --Controller Settings
> --Flow Configuration History
> --Users
> --Templates
> --Help
> --About



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

[jira] [Commented] (NIFI-2324) If we reach the maximum number of outstanding HTTP requests, logs should indicate which requests are outstanding

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2324:
--

GitHub user markap14 opened a pull request:

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

NIFI-2324: Log number of requests per URI if we have too many outstan…

…ding requests to replicate

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

$ git pull https://github.com/markap14/nifi NIFI-2324

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

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


commit 4e8e204da8abc0d37922c2ad3ac2f3aa52715f1a
Author: Mark Payne 
Date:   2016-07-19T20:59:14Z

NIFI-2324: Log number of requests per URI if we have too many outstanding 
requests to replicate




> If we reach the maximum number of outstanding HTTP requests, logs should 
> indicate which requests are outstanding
> 
>
> Key: NIFI-2324
> URL: https://issues.apache.org/jira/browse/NIFI-2324
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.0.0
>
>




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

[GitHub] nifi pull request #683: NIFI-2324: Log number of requests per URI if we have...

[markap14]

GitHub user markap14 opened a pull request:

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

NIFI-2324: Log number of requests per URI if we have too many outstan…

…ding requests to replicate

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

$ git pull https://github.com/markap14/nifi NIFI-2324

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

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


commit 4e8e204da8abc0d37922c2ad3ac2f3aa52715f1a
Author: Mark Payne 
Date:   2016-07-19T20:59:14Z

NIFI-2324: Log number of requests per URI if we have too many outstanding 
requests to replicate




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

[jira] [Assigned] (NIFI-2245) Summary Page: Node-wise break down incomplete

[Matt Gilman (JIRA)]

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

Matt Gilman reassigned NIFI-2245:
-

Assignee: Matt Gilman

> Summary Page: Node-wise break down incomplete 
> --
>
> Key: NIFI-2245
> URL: https://issues.apache.org/jira/browse/NIFI-2245
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>Priority: Minor
> Fix For: 1.0.0
>
>
> Node-wise break down is missing some nodes.



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

[jira] [Assigned] (NIFI-2077) Remove old 0.x images that have been replaced in 1.x

[Matt Gilman (JIRA)]

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

Matt Gilman reassigned NIFI-2077:
-

Assignee: Matt Gilman

> Remove old 0.x images that have been replaced in 1.x
> 
>
> Key: NIFI-2077
> URL: https://issues.apache.org/jira/browse/NIFI-2077
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>Priority: Minor
> Fix For: 1.0.0
>
>




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

[GitHub] nifi pull request #682: NiFi 2324 - Log number of requests per URI if we hav...

[markap14]

Github user markap14 closed the pull request at:

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


---
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-1554) Incorporate new Authorizer API

[Matt Gilman (JIRA)]

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

Matt Gilman resolved NIFI-1554.
---
Resolution: Fixed

> Incorporate new Authorizer API
> --
>
> Key: NIFI-1554
> URL: https://issues.apache.org/jira/browse/NIFI-1554
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Matt Gilman
> Fix For: 1.0.0
>
>
> - Introduce checks on user actions using new Authorizer API.



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

[GitHub] nifi pull request #682: NiFi 2324 - Log number of requests per URI if we hav...

[markap14]

GitHub user markap14 opened a pull request:

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

NiFi 2324 - Log number of requests per URI if we have too many outstanding 
requests to replicate



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

$ git pull https://github.com/markap14/nifi NIFI-2324

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

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


commit f3ee623c1e68cf45ee39a7ed58b14ad6e275c014
Author: Mark Payne 
Date:   2016-07-19T19:57:05Z

NIFI-2289: Ensure that we include Node ID's of all nodes when finding 
cluster coordinator, even if the node is currently still connecting or has not 
yet joined the cluster, which ccan be the case if all nodes in the cluster are 
restarting at the same time.

commit 4bcfba1ccc2405f0be4f1b3f405e4f33425687f1
Author: Mark Payne 
Date:   2016-07-19T20:55:55Z

NIFI-2324: Long number of requests per URI if we have too many outstanding 
requests to replicate




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

[jira] [Assigned] (NIFI-2176) Able to create a template without a name

[Matt Gilman (JIRA)]

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

Matt Gilman reassigned NIFI-2176:
-

Assignee: Matt Gilman

> Able to create a template without a name
> 
>
> Key: NIFI-2176
> URL: https://issues.apache.org/jira/browse/NIFI-2176
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Matt Gilman
>  Labels: UI
> Fix For: 1.0.0
>
>
> Select "Create Template" from the Operator palette.  Immediately select 
> "Create" from the "Create Template" dialog leaving the name field blank.  A 
> success message "Template '' was successfully created." is displayed.
> In 0.x, if a user attempted this they would get an error "Template name 
> cannot be blank."



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

[jira] [Created] (NIFI-2324) If we reach the maximum number of outstanding HTTP requests, logs should indicate which requests are outstanding

[Mark Payne (JIRA)]

Mark Payne created NIFI-2324:


 Summary: If we reach the maximum number of outstanding HTTP 
requests, logs should indicate which requests are outstanding
 Key: NIFI-2324
 URL: https://issues.apache.org/jira/browse/NIFI-2324
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core Framework
Reporter: Mark Payne
Assignee: Mark Payne
 Fix For: 1.0.0






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

[jira] [Updated] (NIFI-1949) Group and AccessPolicy should have a "description" field

[Matt Gilman (JIRA)]

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

Matt Gilman updated NIFI-1949:
--
Fix Version/s: (was: 1.0.0)
   1.1.0

> Group and AccessPolicy should have a "description" field
> 
>
> Key: NIFI-1949
> URL: https://issues.apache.org/jira/browse/NIFI-1949
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Jeff Storck
>Priority: Minor
> Fix For: 1.1.0
>
>
> Add a nullable string description field to Group and AccessPolicy objects of 
> the Authorization API.



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

[jira] [Assigned] (NIFI-2242) UI does not render components properly if moving multiple components with mixed permissions

[Matt Gilman (JIRA)]

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

Matt Gilman reassigned NIFI-2242:
-

Assignee: Matt Gilman

> UI does not render components properly if moving multiple components with 
> mixed permissions
> ---
>
> Key: NIFI-2242
> URL: https://issues.apache.org/jira/browse/NIFI-2242
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Mark Payne
>Assignee: Matt Gilman
> Fix For: 1.0.0
>
>
> I selected several processors and connections (a small, disconnected graph) 
> and dragged the components to the right. When I released, I got an error 
> message because I didn't have 'write' permissions to one of the processors. 
> All of the other processors moved, but he one processor did not. As a result, 
> the connections were also not refreshed properly and were not connecting the 
> components visually. Clicking 'refresh' on the graph did cause the 
> connections to be redrawn properly.
> This could be addressed in two different ways. First, we could simply refresh 
> the canvas in this case.
> Secondly, we could use a Flow Snippet to move the components, in which case 
> none of the components would be moved if the user attempted this action 
> because the user does not have sufficient permissions for all components.



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

[jira] [Assigned] (NIFI-2224) Upload template dialog does not show template name selected

[Matt Gilman (JIRA)]

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

Matt Gilman reassigned NIFI-2224:
-

Assignee: Matt Gilman

> Upload template dialog does not show template name selected
> ---
>
> Key: NIFI-2224
> URL: https://issues.apache.org/jira/browse/NIFI-2224
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Affects Versions: 1.0.0
> Environment: Mac OS X; Chrome
>Reporter: Andrew Lim
>Assignee: Matt Gilman
>  Labels: UI
> Fix For: 1.0.0
>
> Attachments: NIFI-2224.mp4
>
>
> Following STRs are shown in the attached video:
> 1. Select Upload Template from operator palette
> 2. Select magnifying glass icon to browse for template
> 3. Select template '1.xml'
> 4. Select open button
> 5. Upload template dialog in NiFi shows '1.xml' as selected
> 6. Select Upload button
> 7. Template uploaded successfully
> 8. Select Upload Template from operator palette
> 9. Select magnifying glass icon to browse for template
> 10 Select template '1.xml' AGAIN
> 11. Select open button
> 12. Upload template dialog in NiFi does NOT show '1.xml' as selected
> Separate bug (NIFI-2223)
> 13.  Select Upload button
> 14. Template uploaded successfully



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

[jira] [Assigned] (NIFI-2295) Replay Permissions bug in unsecure standalone instance

[Matt Gilman (JIRA)]

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

Matt Gilman reassigned NIFI-2295:
-

Assignee: Matt Gilman

> Replay Permissions bug in unsecure standalone instance
> --
>
> Key: NIFI-2295
> URL: https://issues.apache.org/jira/browse/NIFI-2295
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Percivall
>Assignee: Matt Gilman
> Fix For: 1.0.0
>
>
> I have an unsecure default instance. When I go to replay a message I see an 
> unexpected error that says "Unable to perform the desired action due to 
> insufficient permissions. Contact the system administrator." 
> That said, after I see the error when I go back to the canvas and refresh I 
> see the message was properly marked for replay (exists in the queue and I can 
> see the provenance of it getting replayed).



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

[jira] [Updated] (NIFI-2052) Search results

[Matt Gilman (JIRA)]

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

Matt Gilman updated NIFI-2052:
--
Fix Version/s: (was: 1.0.0)
   1.1.0

> Search results
> --
>
> Key: NIFI-2052
> URL: https://issues.apache.org/jira/browse/NIFI-2052
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Scott Aslan
> Fix For: 1.1.0
>
> Attachments: nifi-search-results.png
>
>
> New icons and styles to be applied to the search results container.



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

[jira] [Updated] (NIFI-1963) Cluster - Flow inheritability

[Matt Gilman (JIRA)]

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

Matt Gilman updated NIFI-1963:
--
Fix Version/s: (was: 1.0.0)
   1.1.0

> Cluster - Flow inheritability
> -
>
> Key: NIFI-1963
> URL: https://issues.apache.org/jira/browse/NIFI-1963
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Matt Gilman
> Fix For: 1.1.0
>
>
> I disconnected a node and changed the penalty duration. The attempted to 
> reconnect the node. The node joined successfully with an inconsistent penalty 
> duration.
> Need to reconsider which fields need to belong in the flow fingerprint to 
> ensure consistent configuration throughout the cluster.



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

[jira] [Updated] (NIFI-2053) open/close palettes

[Matt Gilman (JIRA)]

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

Matt Gilman updated NIFI-2053:
--
Fix Version/s: (was: 1.0.0)
   1.1.0

> open/close palettes
> ---
>
> Key: NIFI-2053
> URL: https://issues.apache.org/jira/browse/NIFI-2053
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Scott Aslan
> Fix For: 1.1.0
>
> Attachments: nifi-2053_palette-clickable-area.png
>
>
> Need to alter where the user clicks to open/close palettes. Also may want to 
> make these palettes draggable and resizeable so users can "dock" them 
> anywhere...



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

[jira] [Updated] (NIFI-1870) Restore go to source/destination capability

[Matt Gilman (JIRA)]

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

Matt Gilman updated NIFI-1870:
--
Fix Version/s: (was: 1.0.0)
   1.1.0

> Restore go to source/destination capability
> ---
>
> Key: NIFI-1870
> URL: https://issues.apache.org/jira/browse/NIFI-1870
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Matt Gilman
>Priority: Minor
> Fix For: 1.1.0
>
>




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

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

[Matt Burgess (JIRA)]

Matt Burgess created NIFI-2323:
--

 Summary: Improve handling of Oracle datetime columns in 
QueryDatabaseTable and GenerateTableFetch
 Key: NIFI-2323
 URL: https://issues.apache.org/jira/browse/NIFI-2323
 Project: Apache NiFi
  Issue Type: Improvement
Affects Versions: 0.6.0
Reporter: Matt Burgess


Due to default handling of Oracle columns returned as java.sql.Date types, the 
string literals used to compare against the column values must be in the same 
format as the NLS_DATE_FORMAT setting of the database (often -MM-DD).

I believe when "Oracle" is provided as the database type (formerly known as 
pre-processing strategy), Oracle's Datetime Functions (such as TO_DATE or 
TO_TIMESTAMP) could be leveraged to give more fine-grained maximum-value 
information.



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

[jira] [Updated] (NIFI-1967) nifi.properties conversion for 1.0.0

[Joseph Witt (JIRA)]

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

Joseph Witt updated NIFI-1967:
--
Labels: migration  (was: )

> nifi.properties conversion for 1.0.0
> 
>
> Key: NIFI-1967
> URL: https://issues.apache.org/jira/browse/NIFI-1967
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Configuration, Documentation & Website
>Reporter: Matt Gilman
>Assignee: Andrew Lim
>Priority: Minor
>  Labels: migration
> Fix For: 1.0.0
>
>
> With the properties changing it would be nice to offer an automated way of 
> converting an existing nifi.properties to the 1.0.0 version. Specifically, 
> the clustering properties have changed enough to warrant scripting this for 
> users.



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

[jira] [Updated] (NIFI-2322) ConsumeKafka gets stuck (cannot be stopped)

[Haimo Liu (JIRA)]

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

Haimo Liu updated NIFI-2322:

Fix Version/s: 1.0.0

> ConsumeKafka gets stuck (cannot be stopped)
> ---
>
> Key: NIFI-2322
> URL: https://issues.apache.org/jira/browse/NIFI-2322
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0
>Reporter: Haimo Liu
> Fix For: 1.0.0
>
> Attachments: Screen Shot 2016-07-19 at 2.14.32 PM.png, Screen Shot 
> 2016-07-19 at 2.14.48 PM.png
>
>
> If kafka broker path is invalid or inaccurate, ConsumeKafka processor can get 
> stuck (concurrent tasks cannot be stopped in a clustered mode). Please refer 
> to the images in the attachment. It appears that a configurable timeout 
> property would potentially solve the problem.



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

[jira] [Created] (NIFI-2322) ConsumeKafka gets stuck (cannot be stopped)

[Haimo Liu (JIRA)]

Haimo Liu created NIFI-2322:
---

 Summary: ConsumeKafka gets stuck (cannot be stopped)
 Key: NIFI-2322
 URL: https://issues.apache.org/jira/browse/NIFI-2322
 Project: Apache NiFi
  Issue Type: Bug
  Components: Extensions
Affects Versions: 1.0.0
Reporter: Haimo Liu


If kafka broker path is invalid or inaccurate, ConsumeKafka processor can get 
stuck (concurrent tasks cannot be stopped in a clustered mode). Please refer to 
the images in the attachment. It appears that a configurable timeout property 
would potentially solve the problem.



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

[jira] [Commented] (NIFI-1846) Build requires Git through Bower

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-1846:
---

Is there a particular version of Git needed?  I can update the docs if we know 
this.

> Build requires Git through Bower
> 
>
> Key: NIFI-1846
> URL: https://issues.apache.org/jira/browse/NIFI-1846
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Documentation & Website, Tools and Build
>Reporter: Matt Gilman
>Assignee: Andrew Lim
> Fix For: 1.0.0
>
>
> Investigate build to see if there is an alternative which would not introduce 
> new requirements in our process build. If unable to remove dependency, need 
> to update the getting started/contribution/release helper to indicate that 
> Git is required.



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

[jira] [Resolved] (NIFI-2231) Refresh Content Viewer UI

[Joseph Witt (JIRA)]

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

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

> Refresh Content Viewer UI
> -
>
> Key: NIFI-2231
> URL: https://issues.apache.org/jira/browse/NIFI-2231
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Scott Aslan
>Priority: Blocker
> Fix For: 1.0.0
>
>




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

[jira] [Updated] (NIFI-2297) Describe differences for QueryDatabaseTable between 0.x and 1.0

[Joseph Witt (JIRA)]

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

Joseph Witt updated NIFI-2297:
--
Labels: migration  (was: )

> Describe differences for QueryDatabaseTable between 0.x and 1.0
> ---
>
> Key: NIFI-2297
> URL: https://issues.apache.org/jira/browse/NIFI-2297
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Documentation & Website
>Reporter: Matt Burgess
>Assignee: Andrew Lim
>  Labels: migration
> Fix For: 1.0.0
>
>
> QueryDatabaseTable was refactored to support a common interface 
> (DatabaseAdapter) between some DB-related processors that need to know the 
> "type" of database, either for SQL generation or whatever. Since 
> QueryDatabaseTable exists in 0.7.x, documentation is needed to describe the 
> changes that need to be made between "SQL Preprocessing Strategy" and 
> "Database Type". In the former property the choice is "None" or "Oracle"; in 
> the new system that property is invalid and the new one offers a choice of 
> "Generic" or "Oracle".



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

[jira] [Resolved] (NIFI-2230) Refresh UpdateAttribute Custom UI

[Joseph Witt (JIRA)]

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

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

> Refresh UpdateAttribute Custom UI
> -
>
> Key: NIFI-2230
> URL: https://issues.apache.org/jira/browse/NIFI-2230
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Matt Gilman
>Assignee: Scott Aslan
>Priority: Blocker
> Fix For: 1.0.0
>
>




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

[jira] [Resolved] (NIFI-2284) Remove policies for component upon removal

[Joseph Witt (JIRA)]

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

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

> Remove policies for component upon removal
> --
>
> Key: NIFI-2284
> URL: https://issues.apache.org/jira/browse/NIFI-2284
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Reporter: Matt Gilman
> Fix For: 1.0.0
>
>
> When components are removed, we should remove any corresponding policies for 
> that component.



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

[jira] [Resolved] (NIFI-2290) List Queue not working properly in clustered mode

[Joseph Witt (JIRA)]

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

Joseph Witt resolved NIFI-2290.
---
Resolution: Duplicate

> List Queue not working properly in clustered mode
> -
>
> Key: NIFI-2290
> URL: https://issues.apache.org/jira/browse/NIFI-2290
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework, Core UI
>Affects Versions: 1.0.0
>Reporter: Mark Payne
> Fix For: 1.0.0
>
>
> When I click on a connection and choose List Queue, I am seeing only 20 
> FlowFiles listed, though the connection has 50,000 FlowFiles (across 5 
> nodes). All of the FlowFiles listed come form a single node. When I try to 
> view any of them, I am told that the FlowFile no longer exists in the queue, 
> even though the destination processor is stopped. I do have expiration 
> configured, but none of the FlowFiles have been in the queue long enough to 
> expire.



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

[jira] [Created] (NIFI-2321) Update Getting Started documentation for 1.0 changes

[Andrew Lim (JIRA)]

Andrew Lim created NIFI-2321:


 Summary: Update Getting Started documentation for 1.0 changes
 Key: NIFI-2321
 URL: https://issues.apache.org/jira/browse/NIFI-2321
 Project: Apache NiFi
  Issue Type: Bug
  Components: Documentation & Website
Affects Versions: 1.0.0
Reporter: Andrew Lim


Getting Started guide needs to be updated for the changes in the 1.0 UI.



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

[jira] [Commented] (NIFI-2289) Cluster sometimes gets into state where it always says 'no Cluster Coordinator elected'

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2289:
--

GitHub user markap14 opened a pull request:

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

NIFI-2289: Ensure that we include Node ID's of all nodes when finding…

… cluster coordinator, even if the node is currently still connecting or 
has not yet joined the cluster, which ccan be the case if all nodes in the 
cluster are restarting at the same time.

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

$ git pull https://github.com/markap14/nifi NIFI-2289-PART2

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

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


commit f3ee623c1e68cf45ee39a7ed58b14ad6e275c014
Author: Mark Payne 
Date:   2016-07-19T19:57:05Z

NIFI-2289: Ensure that we include Node ID's of all nodes when finding 
cluster coordinator, even if the node is currently still connecting or has not 
yet joined the cluster, which ccan be the case if all nodes in the cluster are 
restarting at the same time.




> Cluster sometimes gets into state where it always says 'no Cluster 
> Coordinator elected'
> ---
>
> Key: NIFI-2289
> URL: https://issues.apache.org/jira/browse/NIFI-2289
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.0.0
>
>
> When running in clustered mode, occasionally NiFi will get into a state where 
> it indicates for each request that no cluster coordinator exists, even though 
> one is clearly elected.



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

[jira] [Commented] (NIFI-826) Export templates in a deterministic way

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-826:
-

Github user olegz closed the pull request at:

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


> Export templates in a deterministic way
> ---
>
> Key: NIFI-826
> URL: https://issues.apache.org/jira/browse/NIFI-826
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Oleg Zhurakousky
> Fix For: 1.0.0
>
>
> Templates should be exported in a deterministic way so that they can be 
> compared or diff'ed with another. Items to consider...
> - The ordering of components
> - The id's used to identify the components
> - Consider excluding irrelevant items. When components are imported some 
> settings are ignored (run state).



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

[GitHub] nifi pull request #681: NIFI-2289: Ensure that we include Node ID's of all n...

[markap14]

GitHub user markap14 opened a pull request:

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

NIFI-2289: Ensure that we include Node ID's of all nodes when finding…

… cluster coordinator, even if the node is currently still connecting or 
has not yet joined the cluster, which ccan be the case if all nodes in the 
cluster are restarting at the same time.

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

$ git pull https://github.com/markap14/nifi NIFI-2289-PART2

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

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


commit f3ee623c1e68cf45ee39a7ed58b14ad6e275c014
Author: Mark Payne 
Date:   2016-07-19T19:57:05Z

NIFI-2289: Ensure that we include Node ID's of all nodes when finding 
cluster coordinator, even if the node is currently still connecting or has not 
yet joined the cluster, which ccan be the case if all nodes in the cluster are 
restarting at the same time.




---
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 #679: NIFI-826 (part 3)

[olegz]

Github user olegz closed the pull request at:

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


---
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-2289) Cluster sometimes gets into state where it always says 'no Cluster Coordinator elected'

[Mark Payne (JIRA)]

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

Mark Payne commented on NIFI-2289:
--

Re-opened the JIRA because the original solution fixed the problem in most 
cases, but I did identify a corner case where it fails to work properly - will 
submit a new PR to address that case


> Cluster sometimes gets into state where it always says 'no Cluster 
> Coordinator elected'
> ---
>
> Key: NIFI-2289
> URL: https://issues.apache.org/jira/browse/NIFI-2289
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.0.0
>
>
> When running in clustered mode, occasionally NiFi will get into a state where 
> it indicates for each request that no cluster coordinator exists, even though 
> one is clearly elected.



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

[jira] [Reopened] (NIFI-2289) Cluster sometimes gets into state where it always says 'no Cluster Coordinator elected'

[Mark Payne (JIRA)]

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

Mark Payne reopened NIFI-2289:
--

> Cluster sometimes gets into state where it always says 'no Cluster 
> Coordinator elected'
> ---
>
> Key: NIFI-2289
> URL: https://issues.apache.org/jira/browse/NIFI-2289
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.0.0
>
>
> When running in clustered mode, occasionally NiFi will get into a state where 
> it indicates for each request that no cluster coordinator exists, even though 
> one is clearly elected.



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

[jira] [Commented] (NIFI-826) Export templates in a deterministic way

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-826:
-

Github user markap14 commented on the issue:

https://github.com/apache/nifi/pull/679
  
@olegz looks good. Addresses the issue that I was seeing. +1. Merged to 
master.



> Export templates in a deterministic way
> ---
>
> Key: NIFI-826
> URL: https://issues.apache.org/jira/browse/NIFI-826
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Oleg Zhurakousky
> Fix For: 1.0.0
>
>
> Templates should be exported in a deterministic way so that they can be 
> compared or diff'ed with another. Items to consider...
> - The ordering of components
> - The id's used to identify the components
> - Consider excluding irrelevant items. When components are imported some 
> settings are ignored (run state).



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

[jira] [Commented] (NIFI-826) Export templates in a deterministic way

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-826 (part 3)
- fixed ID generation routine that was causing miss-identification of the 
components


> Export templates in a deterministic way
> ---
>
> Key: NIFI-826
> URL: https://issues.apache.org/jira/browse/NIFI-826
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Oleg Zhurakousky
> Fix For: 1.0.0
>
>
> Templates should be exported in a deterministic way so that they can be 
> compared or diff'ed with another. Items to consider...
> - The ordering of components
> - The id's used to identify the components
> - Consider excluding irrelevant items. When components are imported some 
> settings are ignored (run state).



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

[jira] [Assigned] (NIFI-2320) Update screenshot images in Getting Started guide

[Andrew Lim (JIRA)]

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

Andrew Lim reassigned NIFI-2320:


Assignee: Andrew Lim

> Update screenshot images in Getting Started guide
> -
>
> Key: NIFI-2320
> URL: https://issues.apache.org/jira/browse/NIFI-2320
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>
> The screenshots in the documentation need to be updated for the new UI.
> This ticket will cover the images used or added to the Getting Started guide.



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

[jira] [Updated] (NIFI-2320) Update screenshot images in Getting Started guide

[Andrew Lim (JIRA)]

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

Andrew Lim updated NIFI-2320:
-
Description: 
The screenshots in the documentation need to be updated for the new UI.

This ticket is for the images used or added to the Getting Started guide.

  was:
The screenshots in the documentation need to be updated for the new UI.

This ticket will cover the images used or added to the Getting Started guide.


> Update screenshot images in Getting Started guide
> -
>
> Key: NIFI-2320
> URL: https://issues.apache.org/jira/browse/NIFI-2320
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>
> The screenshots in the documentation need to be updated for the new UI.
> This ticket is for the images used or added to the Getting Started guide.



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

[jira] [Created] (NIFI-2320) Update screenshot images in Getting Started guide

[Andrew Lim (JIRA)]

Andrew Lim created NIFI-2320:


 Summary: Update screenshot images in Getting Started guide
 Key: NIFI-2320
 URL: https://issues.apache.org/jira/browse/NIFI-2320
 Project: Apache NiFi
  Issue Type: Bug
  Components: Documentation & Website
Affects Versions: 1.0.0
Reporter: Andrew Lim


The screenshots in the documentation need to be updated for the new UI.

This ticket will cover the images used or added to the Getting Started guide.



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

[jira] [Resolved] (NIFI-929) Ability to generate a 'true' pid file

[Joseph Percivall (JIRA)]

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

Joseph Percivall resolved NIFI-929.
---
Resolution: Fixed

> Ability to generate a 'true' pid file
> -
>
> Key: NIFI-929
> URL: https://issues.apache.org/jira/browse/NIFI-929
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Configuration
>Affects Versions: 0.3.0
>Reporter: Ali Bajwa
>Assignee: Bryan Bende
>Priority: Minor
> Fix For: 1.0.0
>
>
> The nifi pid file does not seem to be a true pid file (it has other info as 
> well). 
> For integration with monitoring tools like Ambari it would be nice to have a 
> true pid file (containing only the pid) created as well (in line with other 
> Hadoop components). This is coming from the Ambari service I put together: I 
> had to parse out the pid from Nifi pidfile and maintain another one



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

[jira] [Commented] (NIFI-929) Ability to generate a 'true' pid file

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-929:
-

Github user asfgit closed the pull request at:

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


> Ability to generate a 'true' pid file
> -
>
> Key: NIFI-929
> URL: https://issues.apache.org/jira/browse/NIFI-929
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Configuration
>Affects Versions: 0.3.0
>Reporter: Ali Bajwa
>Assignee: Bryan Bende
>Priority: Minor
> Fix For: 1.0.0
>
>
> The nifi pid file does not seem to be a true pid file (it has other info as 
> well). 
> For integration with monitoring tools like Ambari it would be nice to have a 
> true pid file (containing only the pid) created as well (in line with other 
> Hadoop components). This is coming from the Ambari service I put together: I 
> had to parse out the pid from Nifi pidfile and maintain another one



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

[GitHub] nifi pull request #677: NIFI-929 Changing permissions of nifi.pid to be read...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2319) When clicking View FlowFiles on a connection, I am seeing only the FlowFiles on the node I'm connected to

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2319:
--

GitHub user markap14 opened a pull request:

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

NIFI-2319: Ensure that when we set cluster node id's and node address…

…es, that we do so only if they are not already populated

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

$ git pull https://github.com/markap14/nifi NIFI-2319

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

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


commit 1070bd59e284938a5be812d07e4128459b046dbf
Author: Mark Payne 
Date:   2016-07-19T19:33:59Z

NIFI-2319: Ensure that when we set cluster node id's and node addresses, 
that we do so only if they are not already populated




> When clicking View FlowFiles on a connection, I am seeing only the FlowFiles 
> on the node I'm connected to
> -
>
> Key: NIFI-2319
> URL: https://issues.apache.org/jira/browse/NIFI-2319
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.0.0
>
>
> When I right-click on a connection and choose View FlowFiles, when running a 
> clustered instance of NiFi, I see only the FlowFiles that are on the node I'm 
> connected to. Unless I am connected to the currently elected cluster 
> coordinator - then I see the correct response, which is the merged result 
> from all nodes.



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

[jira] [Commented] (NIFI-929) Ability to generate a 'true' pid file

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-929:
-

Github user JPercivall commented on the issue:

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

Visually verified code, contrib check build and verified that when created, 
the PID file has read access by group and others (and r/w by owner). Thanks 
@bbende, I will merge it in.


> Ability to generate a 'true' pid file
> -
>
> Key: NIFI-929
> URL: https://issues.apache.org/jira/browse/NIFI-929
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Configuration
>Affects Versions: 0.3.0
>Reporter: Ali Bajwa
>Assignee: Bryan Bende
>Priority: Minor
> Fix For: 1.0.0
>
>
> The nifi pid file does not seem to be a true pid file (it has other info as 
> well). 
> For integration with monitoring tools like Ambari it would be nice to have a 
> true pid file (containing only the pid) created as well (in line with other 
> Hadoop components). This is coming from the Ambari service I put together: I 
> had to parse out the pid from Nifi pidfile and maintain another one



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

[GitHub] nifi issue #677: NIFI-929 Changing permissions of nifi.pid to be readable by...

[JPercivall]

Github user JPercivall commented on the issue:

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

Visually verified code, contrib check build and verified that when created, 
the PID file has read access by group and others (and r/w by owner). Thanks 
@bbende, I will merge it in.


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

[jira] [Updated] (NIFI-2318) Node Events shown in cluster table often indicate that the node's status changed to CONNECTED many times

[Mark Payne (JIRA)]

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

Mark Payne updated NIFI-2318:
-
Status: Patch Available  (was: Open)

> Node Events shown in cluster table often indicate that the node's status 
> changed to CONNECTED many times
> 
>
> Key: NIFI-2318
> URL: https://issues.apache.org/jira/browse/NIFI-2318
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Minor
> Fix For: 1.0.0
>
>




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

[jira] [Updated] (NIFI-2316) After restarting cluster, all nodes sometimes come up with all components stopped

[Mark Payne (JIRA)]

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

Mark Payne updated NIFI-2316:
-
Status: Patch Available  (was: Open)

> After restarting cluster, all nodes sometimes come up with all components 
> stopped
> -
>
> Key: NIFI-2316
> URL: https://issues.apache.org/jira/browse/NIFI-2316
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0
>
>
> When I restart an entire cluster, I see sometimes that all processors, etc. 
> are stopped. Sometimes this can also result in some nodes not being able to 
> join the cluster if they have a root group port, as the run status is not the 
> same across the cluster, so the new node cannot inherit the flow.



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

[jira] [Updated] (NIFI-2017) Root Group Port Transmission Icon is inaccurate

[Mark Payne (JIRA)]

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

Mark Payne updated NIFI-2017:
-
Fix Version/s: (was: 1.0.0)
   1.1.0

> Root Group Port Transmission Icon is inaccurate
> ---
>
> Key: NIFI-2017
> URL: https://issues.apache.org/jira/browse/NIFI-2017
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Matt Gilman
>Priority: Minor
> Fix For: 1.1.0
>
>




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

[jira] [Commented] (NIFI-2017) Root Group Port Transmission Icon is inaccurate

[Mark Payne (JIRA)]

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

Mark Payne commented on NIFI-2017:
--

[~mcgilman] - I believe you are correct, in that this is a 'framework-core' 
issue, not a UI issue. Since it is a 'minor' priority though I'm going to push 
it off to 1.1.0. If anyone has the cycles and wants to tackle it for 1.0.0, 
though, they are welcome to move it back if it's getting worked.

> Root Group Port Transmission Icon is inaccurate
> ---
>
> Key: NIFI-2017
> URL: https://issues.apache.org/jira/browse/NIFI-2017
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Matt Gilman
>Priority: Minor
> Fix For: 1.1.0
>
>




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

[jira] [Commented] (NIFI-826) Export templates in a deterministic way

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-826:
-

GitHub user olegz opened a pull request:

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

NIFI-826 (part 3)

- fixed ID generation routine that was causing miss-identification of the 
components

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

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

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

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


commit b735d6aa7d7450a2d88d444aab73471f3908acd2
Author: Oleg Zhurakousky 
Date:   2016-07-19T19:13:36Z

NIFI-826 (part 3)
- fixed ID generation routine that was causing miss-identification of the 
components




> Export templates in a deterministic way
> ---
>
> Key: NIFI-826
> URL: https://issues.apache.org/jira/browse/NIFI-826
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Oleg Zhurakousky
> Fix For: 1.0.0
>
>
> Templates should be exported in a deterministic way so that they can be 
> compared or diff'ed with another. Items to consider...
> - The ordering of components
> - The id's used to identify the components
> - Consider excluding irrelevant items. When components are imported some 
> settings are ignored (run state).



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

[GitHub] nifi pull request #679: NIFI-826 (part 3)

[olegz]

GitHub user olegz opened a pull request:

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

NIFI-826 (part 3)

- fixed ID generation routine that was causing miss-identification of the 
components

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

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

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

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


commit b735d6aa7d7450a2d88d444aab73471f3908acd2
Author: Oleg Zhurakousky 
Date:   2016-07-19T19:13:36Z

NIFI-826 (part 3)
- fixed ID generation routine that was causing miss-identification of the 
components




---
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-2241) Audit actions on User/Groups/Policies

[Matt Gilman (JIRA)]

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

Matt Gilman resolved NIFI-2241.
---
Resolution: Duplicate

> Audit actions on User/Groups/Policies
> -
>
> Key: NIFI-2241
> URL: https://issues.apache.org/jira/browse/NIFI-2241
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Reporter: Matt Gilman
>Priority: Critical
> Fix For: 1.0.0
>
>




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

[jira] [Resolved] (NIFI-2240) Delete related policies on component removal

[Matt Gilman (JIRA)]

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

Matt Gilman resolved NIFI-2240.
---
Resolution: Duplicate

> Delete related policies on component removal
> 
>
> Key: NIFI-2240
> URL: https://issues.apache.org/jira/browse/NIFI-2240
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Reporter: Matt Gilman
>Priority: Critical
> Fix For: 1.0.0
>
>




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

[jira] [Assigned] (NIFI-1950) Convert 0.x site-to-site access policies when possible

[Bryan Bende (JIRA)]

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

Bryan Bende reassigned NIFI-1950:
-

Assignee: Bryan Bende

> Convert 0.x site-to-site access policies when possible
> --
>
> Key: NIFI-1950
> URL: https://issues.apache.org/jira/browse/NIFI-1950
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Bryan Bende
>Priority: Blocker
> Fix For: 1.0.0
>
>
> In the 0.x baseline access a Remote Port is configurable. These 
> authorizations are stored in the flow.xml. In the 1.0.0 baseline these 
> decisions will be made by a configurable authorizer. When possible, these 
> access policies need to be converted to the authorizer upon starting with a 
> legacy flow.
> Note: This won't be possible when the authorizer is externally managed. When 
> this is the case, we'll need to document that the access policies will need 
> to be manually restored using the external tool the authorizer supports.



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

[jira] [Assigned] (NIFI-2265) Authorization: Able to see hidden processor information in Status History

[Matt Gilman (JIRA)]

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

Matt Gilman reassigned NIFI-2265:
-

Assignee: Matt Gilman

> Authorization: Able to see hidden processor information in Status History
> -
>
> Key: NIFI-2265
> URL: https://issues.apache.org/jira/browse/NIFI-2265
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Matt Gilman
>Priority: Blocker
>  Labels: UI
> Fix For: 1.0.0
>
> Attachments: NIFI-2265_Summary.png, NIFI-2265_statusHistory.png
>
>
> When a user is not privileged to see a processor, on the canvas the Name and 
> Type of the Processor is properly hidden.  But if you right-click on the 
> processor and select "Stats", this information is displayed in the Status 
> History.
> Screenshot attached.



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

[jira] [Commented] (NIFI-2316) After restarting cluster, all nodes sometimes come up with all components stopped

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2316:
--

GitHub user markap14 opened a pull request:

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

NIFI-2316, NIFI-2318: Ensure that we do not save the flow before init…

…ializing the Run Status of components. Clarify the Node Event messages

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

$ git pull https://github.com/markap14/nifi NIFI-2316

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

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


commit d728aa7e4022a70f6aff6b4bfb1184a24f357755
Author: Mark Payne 
Date:   2016-07-19T18:49:38Z

NIFI-2316, NIFI-2318: Ensure that we do not save the flow before 
initializing the Run Status of components. Clarify the Node Event messages




> After restarting cluster, all nodes sometimes come up with all components 
> stopped
> -
>
> Key: NIFI-2316
> URL: https://issues.apache.org/jira/browse/NIFI-2316
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0
>
>
> When I restart an entire cluster, I see sometimes that all processors, etc. 
> are stopped. Sometimes this can also result in some nodes not being able to 
> join the cluster if they have a root group port, as the run status is not the 
> same across the cluster, so the new node cannot inherit the flow.



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

[jira] [Created] (NIFI-2318) Node Events shown in cluster table often indicate that the node's status changed to CONNECTED many times

[Mark Payne (JIRA)]

Mark Payne created NIFI-2318:


 Summary: Node Events shown in cluster table often indicate that 
the node's status changed to CONNECTED many times
 Key: NIFI-2318
 URL: https://issues.apache.org/jira/browse/NIFI-2318
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core Framework
Affects Versions: 1.0.0
Reporter: Mark Payne
Assignee: Mark Payne
Priority: Minor
 Fix For: 1.0.0






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

[jira] [Updated] (NIFI-2308) Create zero-master-cluster-http-access.png

[Rob Moran (JIRA)]

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

Rob Moran updated NIFI-2308:

Attachment: zero-master-cluster-http-access.png

> Create zero-master-cluster-http-access.png
> --
>
> Key: NIFI-2308
> URL: https://issues.apache.org/jira/browse/NIFI-2308
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Documentation & Website
>Reporter: Rob Moran
> Attachments: zero-master-cluster-http-access.png
>
>




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

[jira] [Updated] (NIFI-2212) Update zero-master-cluster.png

[Rob Moran (JIRA)]

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

Rob Moran updated NIFI-2212:

Attachment: zero-master-cluster.png

> Update zero-master-cluster.png
> --
>
> Key: NIFI-2212
> URL: https://issues.apache.org/jira/browse/NIFI-2212
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Documentation & Website
>Reporter: Rob Moran
> Attachments: zero-master-cluster.png
>
>




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

[jira] [Updated] (NIFI-2308) Create zero-master-cluster-http-access.png

[Rob Moran (JIRA)]

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

Rob Moran updated NIFI-2308:

Attachment: (was: zero-master-cluster-http-access.png)

> Create zero-master-cluster-http-access.png
> --
>
> Key: NIFI-2308
> URL: https://issues.apache.org/jira/browse/NIFI-2308
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Documentation & Website
>Reporter: Rob Moran
>




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

[jira] [Updated] (NIFI-2212) Update zero-master-cluster.png

[Rob Moran (JIRA)]

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

Rob Moran updated NIFI-2212:

Attachment: (was: zero-master-cluster.png)

> Update zero-master-cluster.png
> --
>
> Key: NIFI-2212
> URL: https://issues.apache.org/jira/browse/NIFI-2212
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Documentation & Website
>Reporter: Rob Moran
> Attachments: zero-master-cluster.png
>
>




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

[jira] [Commented] (NIFI-929) Ability to generate a 'true' pid file

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-929:
-

GitHub user bbende opened a pull request:

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

NIFI-929 Changing permissions of nifi.pid to be readable by all, writ…

…able only by user

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

$ git pull https://github.com/bbende/nifi NIFI-929-2

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

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


commit b884c57d2d139dc083129199e67248bfbf439a6a
Author: Bryan Bende 
Date:   2016-07-19T17:23:55Z

NIFI-929 Changing permissions of nifi.pid to be readable by all, writable 
only by user




> Ability to generate a 'true' pid file
> -
>
> Key: NIFI-929
> URL: https://issues.apache.org/jira/browse/NIFI-929
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Configuration
>Affects Versions: 0.3.0
>Reporter: Ali Bajwa
>Assignee: Bryan Bende
>Priority: Minor
> Fix For: 1.0.0
>
>
> The nifi pid file does not seem to be a true pid file (it has other info as 
> well). 
> For integration with monitoring tools like Ambari it would be nice to have a 
> true pid file (containing only the pid) created as well (in line with other 
> Hadoop components). This is coming from the Ambari service I put together: I 
> had to parse out the pid from Nifi pidfile and maintain another one



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

[GitHub] nifi pull request #677: NIFI-929 Changing permissions of nifi.pid to be read...

[bbende]

GitHub user bbende opened a pull request:

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

NIFI-929 Changing permissions of nifi.pid to be readable by all, writ…

…able only by user

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

$ git pull https://github.com/bbende/nifi NIFI-929-2

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

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


commit b884c57d2d139dc083129199e67248bfbf439a6a
Author: Bryan Bende 
Date:   2016-07-19T17:23:55Z

NIFI-929 Changing permissions of nifi.pid to be readable by all, writable 
only by user




---
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-2156) Add ListDatabaseTables processor

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2156: Add ListDatabaseTables processor

This closes #642

Signed-off-by: jpercivall 


> Add ListDatabaseTables processor
> 
>
> Key: NIFI-2156
> URL: https://issues.apache.org/jira/browse/NIFI-2156
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Matt Burgess
>Assignee: Matt Burgess
> Fix For: 1.0.0
>
>
> This processor would use a DatabaseConnectionPool controller service, call 
> getTables(), and if the (optional, defaulting-to-false) property "Include Row 
> Count" is set, then a "SELECT COUNT(1) from table" would be issued to the 
> database. The table catalog, schema, name, type, remarks (and its count if 
> specified) will be included as attributes in a zero-content flow file.
> It will also use State Management to only list tables once. If new tables are 
> added (and the processor is running), then the new tables' flow files will be 
> generated. Changing any property that could affect the list of returned 
> tables (such as the DB Connection, catalog, schema pattern, table name 
> pattern, or table types) will reset the state and all tables will be fetched 
> using the new criteria. The state can also be manually cleared using the 
> standard Clear State link on the View State dialog (available on the 
> processor's context menu)



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

[jira] [Updated] (NIFI-2156) Add ListDatabaseTables processor

[Joseph Percivall (JIRA)]

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

Joseph Percivall updated NIFI-2156:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Add ListDatabaseTables processor
> 
>
> Key: NIFI-2156
> URL: https://issues.apache.org/jira/browse/NIFI-2156
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Matt Burgess
>Assignee: Matt Burgess
> Fix For: 1.0.0
>
>
> This processor would use a DatabaseConnectionPool controller service, call 
> getTables(), and if the (optional, defaulting-to-false) property "Include Row 
> Count" is set, then a "SELECT COUNT(1) from table" would be issued to the 
> database. The table catalog, schema, name, type, remarks (and its count if 
> specified) will be included as attributes in a zero-content flow file.
> It will also use State Management to only list tables once. If new tables are 
> added (and the processor is running), then the new tables' flow files will be 
> generated. Changing any property that could affect the list of returned 
> tables (such as the DB Connection, catalog, schema pattern, table name 
> pattern, or table types) will reset the state and all tables will be fetched 
> using the new criteria. The state can also be manually cleared using the 
> standard Clear State link on the View State dialog (available on the 
> processor's context menu)



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

[jira] [Commented] (NIFI-2156) Add ListDatabaseTables processor

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2156:
--

Github user asfgit closed the pull request at:

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


> Add ListDatabaseTables processor
> 
>
> Key: NIFI-2156
> URL: https://issues.apache.org/jira/browse/NIFI-2156
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Matt Burgess
>Assignee: Matt Burgess
> Fix For: 1.0.0
>
>
> This processor would use a DatabaseConnectionPool controller service, call 
> getTables(), and if the (optional, defaulting-to-false) property "Include Row 
> Count" is set, then a "SELECT COUNT(1) from table" would be issued to the 
> database. The table catalog, schema, name, type, remarks (and its count if 
> specified) will be included as attributes in a zero-content flow file.
> It will also use State Management to only list tables once. If new tables are 
> added (and the processor is running), then the new tables' flow files will be 
> generated. Changing any property that could affect the list of returned 
> tables (such as the DB Connection, catalog, schema pattern, table name 
> pattern, or table types) will reset the state and all tables will be fetched 
> using the new criteria. The state can also be manually cleared using the 
> standard Clear State link on the View State dialog (available on the 
> processor's context menu)



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

[GitHub] nifi pull request #642: NIFI-2156: Add ListDatabaseTables processor

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2156) Add ListDatabaseTables processor

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2156:
--

Github user JPercivall commented on the issue:

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

Visually verified code and any comments were addressed. Ran a contrib check 
build and verified functionality in a standalone cluster hitting a MySQL DB. 
Thanks @mattyb149, I will squash and merge


> Add ListDatabaseTables processor
> 
>
> Key: NIFI-2156
> URL: https://issues.apache.org/jira/browse/NIFI-2156
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Matt Burgess
>Assignee: Matt Burgess
> Fix For: 1.0.0
>
>
> This processor would use a DatabaseConnectionPool controller service, call 
> getTables(), and if the (optional, defaulting-to-false) property "Include Row 
> Count" is set, then a "SELECT COUNT(1) from table" would be issued to the 
> database. The table catalog, schema, name, type, remarks (and its count if 
> specified) will be included as attributes in a zero-content flow file.
> It will also use State Management to only list tables once. If new tables are 
> added (and the processor is running), then the new tables' flow files will be 
> generated. Changing any property that could affect the list of returned 
> tables (such as the DB Connection, catalog, schema pattern, table name 
> pattern, or table types) will reset the state and all tables will be fetched 
> using the new criteria. The state can also be manually cleared using the 
> standard Clear State link on the View State dialog (available on the 
> processor's context menu)



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

[GitHub] nifi issue #642: NIFI-2156: Add ListDatabaseTables processor

[JPercivall]

Github user JPercivall commented on the issue:

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

Visually verified code and any comments were addressed. Ran a contrib check 
build and verified functionality in a standalone cluster hitting a MySQL DB. 
Thanks @mattyb149, I will squash and merge


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

[GitHub] nifi pull request #676: Updating PutAzureEventHub processor so that it uses ...

[apsaltis]

GitHub user apsaltis opened a pull request:

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

Updating PutAzureEventHub processor so that it uses a partition id an…

Updating PutAzureEventHub processor so that it uses a partition id and also 
emits that id as a flow attribute so it can be used downstream. 

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

$ git pull https://github.com/apsaltis/nifi nifi-2275

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

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


commit 000a82271aa4acbc89f4f60259280d6933369213
Author: Andrew Psaltis 
Date:   2016-07-19T16:38:29Z

Updating PutAzureEventHub processor so that it uses a partition id and also 
emits that id as a flow attribute so it can be used down stream




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

[jira] [Created] (NIFI-2317) Functionality of StateManager.replace() when prior state is -1 varies between state providers

[Joseph Percivall (JIRA)]

Joseph Percivall created NIFI-2317:
--

 Summary: Functionality of StateManager.replace() when prior state 
is -1 varies between state providers
 Key: NIFI-2317
 URL: https://issues.apache.org/jira/browse/NIFI-2317
 Project: Apache NiFi
  Issue Type: Bug
Reporter: Joseph Percivall
Priority: Minor


Currently there is local and clustered state. Local is provided by the 
WriteAheadLocalStateProvider and cluster is provided by ZooKeeperStateProvider. 
When WriteAheadLocalStateProvider calls replace() with a prior state version of 
-1 it always returns false[1]. When ZooKeeperStateProvider it will update the 
state[2]. The API does not state what should happen[3]. 

Functionality should be consistent and documented in the API. I believe the 
expected behavior is to replace it only if the prior version matches. This 
means if state is not set, and a user passed a state map of version -1, it 
should replace.

[1] 
https://github.com/apache/nifi/blob/8a668fd344f202060d45f0a506f3ab19943f57ee/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/state/providers/local/WriteAheadLocalStateProvider.java#L220-L220
[2] 
https://github.com/apache/nifi/blob/fb7b3fe4b87b8c9f45a43d460a3020947ef55dcc/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/state/providers/zookeeper/ZooKeeperStateProvider.java#L292-L292
[3] 
https://github.com/apache/nifi/blob/d1129706e235548daaf4eecf7001b244300761e9/nifi-framework-api/src/main/java/org/apache/nifi/components/state/StateProvider.java#L93-L93



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

[GitHub] nifi issue #502: Nifi-1972 Apache Ignite Put Cache Processor

[mans2singh]

Github user mans2singh commented on the issue:

https://github.com/apache/nifi/pull/502
  
@pvillard31 - I've squashed the commits into a single one.  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 pull request #642: NIFI-2156: Add ListDatabaseTables processor

[JPercivall]

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

https://github.com/apache/nifi/pull/642#discussion_r71372009
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ListDatabaseTables.java
 ---
@@ -303,8 +303,8 @@ public void onTrigger(ProcessContext context, 
ProcessSession session) throws Pro
 stateMapProperties.put(fqn, 
Long.toString(System.currentTimeMillis()));
 }
 }
-// Update the last time the processor finished successfully
-stateManager.replace(stateMap, stateMapProperties, 
Scope.CLUSTER);
+// Update the timestamps for listed tables
+stateManager.setState(stateMapProperties, Scope.CLUSTER);
--- End diff --

I would not change this to setState. It will overwrite anything that is in 
State. If someone does end up running clustered and not primary Node it will 
blow it away without warnings. 

Instead just check if the prior map version was -1 and do a set instead of 
replace.


---
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-2309) AmbariReportingTask misleading metric name

[Joseph Percivall (JIRA)]

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

Joseph Percivall resolved NIFI-2309.

Resolution: Fixed

> AmbariReportingTask misleading metric name
> --
>
> Key: NIFI-2309
> URL: https://issues.apache.org/jira/browse/NIFI-2309
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Bryan Bende
>Assignee: Bryan Bende
>Priority: Minor
> Fix For: 1.0.0
>
>
> The AmbariReportingTask reports "TotalTaskDurationSeconds" but sends the 
> value as nano-seconds. Sending nano-seconds is fine, but we should rename the 
> metric so it doesn't imply seconds. 



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

[jira] [Commented] (NIFI-2163) Nifi Service does not follow LSB Sevice Spec

[Puspendu Banerjee (JIRA)]

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

Puspendu Banerjee commented on NIFI-2163:
-

Understood.. Looks like I had modified it based on old 0.x release.
So, re-oped a PR for 1.x. at https://github.com/apache/nifi/pull/675
Please review. I shall test it on a box at my side as well.


Thanks & Regards,
Puspendu Banerjee

On Tue, Jul 19, 2016 at 9:55 AM, ASF GitHub Bot (JIRA) 



> Nifi Service does not follow LSB Sevice Spec
> 
>
> Key: NIFI-2163
> URL: https://issues.apache.org/jira/browse/NIFI-2163
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Configuration
>Affects Versions: 1.0.0, 0.7.0
> Environment: Centos
>Reporter: Edgardo Vega
>Assignee: Puspendu Banerjee
>Priority: Critical
>  Labels: platform-consistency
>
> Trying to use the lastest off master with nifi.sh and nifi-env.sh and they do 
> not follow the spec for services, whcih causes some configuration tools not 
> to work as they use the return codes to determine if things are running, 
> dead, or stopped.
> http://refspecs.linuxbase.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html



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

[jira] [Commented] (NIFI-2309) AmbariReportingTask misleading metric name

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2309:
--

Github user JPercivall commented on the issue:

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

Visually verified code and ran a contrib check. Thanks @bbende, I will 
merge it in.


> AmbariReportingTask misleading metric name
> --
>
> Key: NIFI-2309
> URL: https://issues.apache.org/jira/browse/NIFI-2309
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Bryan Bende
>Assignee: Bryan Bende
>Priority: Minor
> Fix For: 1.0.0
>
>
> The AmbariReportingTask reports "TotalTaskDurationSeconds" but sends the 
> value as nano-seconds. Sending nano-seconds is fine, but we should rename the 
> metric so it doesn't imply seconds. 



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

[GitHub] nifi issue #672: NIFI-2309 Correcting AmbariReportingTask so it reports tota...

[JPercivall]

Github user JPercivall commented on the issue:

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

Visually verified code and ran a contrib check. Thanks @bbende, I will 
merge it in.


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

[jira] [Commented] (NIFI-2163) Nifi Service does not follow LSB Sevice Spec

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2163:
--

GitHub user PuspenduBanerjee opened a pull request:

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

LSB Adherence

Fixes https://issues.apache.org/jira/browse/NIFI-2163

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

$ git pull https://github.com/PuspenduBanerjee/nifi NIFI-2163

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

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


commit cf711767caf2dc5e66acb09aa92162fb3e7ec232
Author: puspendu.baner...@gmail.com 
Date:   2016-07-19T16:01:20Z

LSB Adherence




> Nifi Service does not follow LSB Sevice Spec
> 
>
> Key: NIFI-2163
> URL: https://issues.apache.org/jira/browse/NIFI-2163
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Configuration
>Affects Versions: 1.0.0, 0.7.0
> Environment: Centos
>Reporter: Edgardo Vega
>Assignee: Puspendu Banerjee
>Priority: Critical
>  Labels: platform-consistency
>
> Trying to use the lastest off master with nifi.sh and nifi-env.sh and they do 
> not follow the spec for services, whcih causes some configuration tools not 
> to work as they use the return codes to determine if things are running, 
> dead, or stopped.
> http://refspecs.linuxbase.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html



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

[GitHub] nifi pull request #675: LSB Adherence

[PuspenduBanerjee]

GitHub user PuspenduBanerjee opened a pull request:

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

LSB Adherence

Fixes https://issues.apache.org/jira/browse/NIFI-2163

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

$ git pull https://github.com/PuspenduBanerjee/nifi NIFI-2163

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

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


commit cf711767caf2dc5e66acb09aa92162fb3e7ec232
Author: puspendu.baner...@gmail.com 
Date:   2016-07-19T16:01:20Z

LSB Adherence




---
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-2309) AmbariReportingTask misleading metric name

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2309:
--

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/672
  
@JPercivall good catch, just pushed an update to correct the variable names


> AmbariReportingTask misleading metric name
> --
>
> Key: NIFI-2309
> URL: https://issues.apache.org/jira/browse/NIFI-2309
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Bryan Bende
>Assignee: Bryan Bende
>Priority: Minor
> Fix For: 1.0.0
>
>
> The AmbariReportingTask reports "TotalTaskDurationSeconds" but sends the 
> value as nano-seconds. Sending nano-seconds is fine, but we should rename the 
> metric so it doesn't imply seconds. 



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

[GitHub] nifi issue #672: NIFI-2309 Correcting AmbariReportingTask so it reports tota...

[bbende]

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/672
  
@JPercivall good catch, just pushed an update to correct the variable names


---
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-2308) Create zero-master-cluster-http-access.png

[Rob Moran (JIRA)]

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

Rob Moran updated NIFI-2308:

Attachment: (was: zero-master-cluster-http-access.png)

> Create zero-master-cluster-http-access.png
> --
>
> Key: NIFI-2308
> URL: https://issues.apache.org/jira/browse/NIFI-2308
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Documentation & Website
>Reporter: Rob Moran
> Attachments: zero-master-cluster-http-access.png
>
>




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

[jira] [Updated] (NIFI-2212) Update zero-master-cluster.png

[Rob Moran (JIRA)]

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

Rob Moran updated NIFI-2212:

Attachment: zero-master-cluster.png

> Update zero-master-cluster.png
> --
>
> Key: NIFI-2212
> URL: https://issues.apache.org/jira/browse/NIFI-2212
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Documentation & Website
>Reporter: Rob Moran
> Attachments: zero-master-cluster.png
>
>




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

[jira] [Updated] (NIFI-2308) Create zero-master-cluster-http-access.png

[Rob Moran (JIRA)]

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

Rob Moran updated NIFI-2308:

Attachment: zero-master-cluster-http-access.png

> Create zero-master-cluster-http-access.png
> --
>
> Key: NIFI-2308
> URL: https://issues.apache.org/jira/browse/NIFI-2308
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Documentation & Website
>Reporter: Rob Moran
> Attachments: zero-master-cluster-http-access.png
>
>




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

[jira] [Updated] (NIFI-2211) Update zero-master-node.png

[Rob Moran (JIRA)]

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

Rob Moran updated NIFI-2211:

Attachment: zero-master-node.png

> Update zero-master-node.png
> ---
>
> Key: NIFI-2211
> URL: https://issues.apache.org/jira/browse/NIFI-2211
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Documentation & Website
>Reporter: Rob Moran
> Attachments: zero-master-node.png
>
>




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

[jira] [Updated] (NIFI-2211) Update zero-master-node.png

[Rob Moran (JIRA)]

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

Rob Moran updated NIFI-2211:

Attachment: (was: zero-master-node.png)

> Update zero-master-node.png
> ---
>
> Key: NIFI-2211
> URL: https://issues.apache.org/jira/browse/NIFI-2211
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Documentation & Website
>Reporter: Rob Moran
> Attachments: zero-master-node.png
>
>




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