Closed
Conversation
alopresto
reviewed
May 2, 2017
| === Component Versions | ||
| You have access to information about the version of your Processors, Controller Services, and Reporting Tasks. | ||
| This is especially useful when you are working within a clustered environment with multiple NiFi instances running | ||
| different versions of a component or if you have upgraded to a newer version of a processors. The Add Processor, |
Contributor
There was a problem hiding this comment.
... newer version of a processor ...
andrewmlim
reviewed
May 2, 2017
| === Component Versions | ||
| You have access to information about the version of your Processors, Controller Services, and Reporting Tasks. | ||
| This is especially useful when you are working within a clustered environment with multiple NiFi instances running | ||
| different versions of a component or if you have upgraded to a newer version of a processors. The Add Processor, |
Contributor
There was a problem hiding this comment.
change "processors" to "processor"
alopresto
reviewed
May 2, 2017
| This is especially useful when you are working within a clustered environment with multiple NiFi instances running | ||
| different versions of a component or if you have upgraded to a newer version of a processors. The Add Processor, | ||
| Add Controller Service, and Add Reporting Task dialogs include a column identifying the component version, as well | ||
| as name of the component, the organization or group that created the component, and the NAR bundle that contains |
Contributor
There was a problem hiding this comment.
... as well as the name of the component ...
alopresto
reviewed
May 2, 2017
| ==== Filtering Components | ||
| When you are adding a component, you can filter based on originating source or version number. | ||
|
|
||
| To filter based on version, click the version column to display in ascending or descending version order. |
Contributor
There was a problem hiding this comment.
This seems more like sorting than filtering.
Contributor
There was a problem hiding this comment.
The columns sort, the Source drop-down filters. So maybe change the section to "Sorting and Filtering Components" also.
alopresto
reviewed
May 2, 2017
| ==== Understanding Version Dependencies | ||
| When you are configuring a component, you can also view information about version dependencies. | ||
|
|
||
| . Right-click your component and select Configure to display the Configure dialog for your component |
Contributor
|
Hi @thesolson . @andrewmlim and I made some suggestions. If you are ok with these or have other comments, please add them. I'll then merge this. Thanks for the great contribution. |
andrewmlim
reviewed
May 2, 2017
| ==== Understanding Version Dependencies | ||
| When you are configuring a component, you can also view information about version dependencies. | ||
|
|
||
| . Right-click your component and select Configure to display the Configure dialog for your component |
Contributor
There was a problem hiding this comment.
Add a period at the end of sentence: "...for your component."
Contributor
|
With (out of band) confirmation from @thesolson , I've made the suggested changes and merged this. |
Contributor
Author
|
Thanks Andy, thanks Drew. Changes look good to me! Sarah Olson m: 415 298 5573
On Tuesday, May 2, 2017 2:38 PM, Andy LoPresto <notifications@github.com> wrote:
With (out of band) confirmation from @thesolson , I've made the suggested changes and merged this.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:
For documentation related changes:
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.