You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by GitBox <gi...@apache.org> on 2021/08/13 15:15:10 UTC
[GitHub] [nifi] tpalfy opened a new pull request #5306: NIFI-8650 Flow Analysis
tpalfy opened a new pull request #5306:
URL: https://github.com/apache/nifi/pull/5306
Created new component: FlowAnalyisRule.
Added new framework functionality: analyze flow.
FlowAnalysisRules can be managed from the UI: hamburger-menu -> Controller Settings -> Flow Analysis Rules
Flow analysis is run by the framework:
-For the whole flow (starting at the root process group), scheduled every 5 seconds (similar to validation)
-For each components individually, during their validation
-For a process group (can be root), when requested asynchronously through REST interface (not from UI as of yet)
Flow analysis may produce rule violations as a result. These are stored in memory and are not persisted.
They
-Can be requested through REST interface (not from UI as of yet)
-In case of POLICY rules, invalidate the corresponding components
Currently FlowAnalysisRule implementations are directly provided either
-a component (currently supported Processors and ControllerServices) as VersionedComponent instances. Concrete type should be determined by the rule.
-a process group as a VersionedProcessGroup.
Indirectly they can analyze other components accessible from the directly provided components.
Added one FlowAnalyisRule implementation: DisallowComponentType.
It can be configured with the (simple) name of a type.
Produces a rule violation for each supported component (currently controller servie and processor) instances of that type.
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
### 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 `main`)?
- [ ] Is your initial contribution a single, squashed commit? _Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not `squash` or use `--force` when pushing to allow for clean monitoring of changes._
### 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?
- [ ] Have you verified that the full build is successful on JDK 8?
- [ ] Have you verified that the full build is successful on JDK 11?
- [ ] 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 GitHub Actions CI for build issues and submit an update to your PR as soon as possible.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@nifi.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [nifi] github-actions[bot] commented on pull request #5306: NIFI-8650 Flow Analysis
Posted by GitBox <gi...@apache.org>.
github-actions[bot] commented on pull request #5306:
URL: https://github.com/apache/nifi/pull/5306#issuecomment-1028476075
We're marking this PR as stale due to lack of updates in the past few months. If after another couple of weeks the stale label has not been removed this PR will be closed. This stale marker and eventual auto close does not indicate a judgement of the PR just lack of reviewer bandwidth and helps us keep the PR queue more manageable. If you would like this PR re-opened you can do so and a committer can remove the stale tag. Or you can open a new PR. Try to help review other PRs to increase PR review bandwidth which in turn helps yours.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@nifi.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org