[jira] [Commented] (NIFI-4576) "Available Processors" rewording

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4576:
--------------------------------------

GitHub user pvillard31 opened a pull request:

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

    NIFI-4576 - rewording processors / cores

    After changes:
    
    <img width="795" alt="screen shot 2017-11-10 at 8 12 32 pm" 
src="https://user-images.githubusercontent.com/11541012/32674500-d27c7506-c653-11e7-827a-b3c1d8dc9a0d.png";>
    <img width="590" alt="screen shot 2017-11-10 at 8 12 56 pm" 
src="https://user-images.githubusercontent.com/11541012/32674501-d293a42e-c653-11e7-84d0-4d7b7281caac.png";>
    
    
    Thank you for submitting a contribution to Apache NiFi.
    
    In order to streamline the review of the contribution we ask you
    to ensure the following steps have been taken:
    
    ### For all changes:
    - [ ] Is there a JIRA ticket associated with this PR? Is it referenced 
         in the commit message?
    
    - [ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number 
you are trying to resolve? Pay particular attention to the hyphen "-" character.
    
    - [ ] Has your PR been rebased against the latest commit within the target 
branch (typically master)?
    
    - [ ] Is your initial contribution a single, squashed commit?
    
    ### For code changes:
    - [ ] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?
    - [ ] Have you written or updated unit tests to verify your changes?
    - [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
    - [ ] If applicable, have you updated the LICENSE file, including the main 
LICENSE file under nifi-assembly?
    - [ ] If applicable, have you updated the NOTICE file, including the main 
NOTICE file found under nifi-assembly?
    - [ ] If adding new Properties, have you added .displayName in addition to 
.name (programmatic access) for each of the new properties?
    
    ### For documentation related changes:
    - [ ] Have you ensured that format looks appropriate for the output in 
which it is rendered?
    
    ### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.


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

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

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

    https://github.com/apache/nifi/pull/2267.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 #2267
    
----
commit a4c889e2fd847d65bfd3e9356623b7eb58a70f2d
Author: Pierre Villard <pierre.villard...@gmail.com>
Date:   2017-11-10T19:14:00Z

    NIFI-4576 - rewording processors / cores

----


> "Available Processors" rewording
> --------------------------------
>
>                 Key: NIFI-4576
>                 URL: https://issues.apache.org/jira/browse/NIFI-4576
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core UI
>            Reporter: Pierre Villard
>            Priority: Trivial
>
> In few places, we're using "available processors" to indicate how much cores 
> are available for NiFi. I believe this can be confusing and should be 
> reworded differently. "Available Cores" is an option but maybe there is 
> another wording to better reflect what would be the value in an 
> hyper-threaded environment / docker container / virtual machine, etc.
> I believe there are at least two places to update:
> - Summary / System Diagnostics / System tab
> - Cluster view / System tab



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)