[GitHub] nifi pull request #1979: NIFI-4151: Updated UpdateAttribute to only create J...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1979: NIFI-4151: Updated UpdateAttribute to only create J...

[markap14]

GitHub user markap14 opened a pull request:

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

NIFI-4151: Updated UpdateAttribute to only create JAXB Context once; …

…Minor performance tweaks to standard validators and 
StatusMerge.prettyPrint; updated AbstractConfiguredComponent to not create a 
new ValidationContext each time that validate is called but only when needed; 
updated FlowController, StandardControllerServiceProvider, and 
StandardProcessGroup so that component lookups can be performed using a 
ConcurrentMap at FlowController level instead of having to perform a 
depth-first search through all ProcessGroups when calling findProcessor(), 
findProcessGroup(), findXYZ()

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- where  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/markap14/nifi NIFI-4151

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

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


commit 6d2adbd30719cf43d93c399772c282ca4df5cd4b
Author: Mark Payne 
Date:   2017-07-05T15:24:01Z

NIFI-4151: Updated UpdateAttribute to only create JAXB Context once; Minor 
performance tweaks to standard validators and StatusMerge.prettyPrint; updated 
AbstractConfiguredComponent to not create a new ValidationContext each time 
that validate is called but only when needed; updated FlowController, 
StandardControllerServiceProvider, and StandardProcessGroup so that component 
lookups can be performed using a ConcurrentMap at FlowController level instead 
of having to perform a depth-first search through all ProcessGroups when 
calling findProcessor(), findProcessGroup(), findXYZ()




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