grebtsew opened a new pull request #5517:
URL: https://github.com/apache/nifi/pull/5517
<!--
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.
-->
#### Description of : Adding Hexdump processor to standard bundle
Fixes bug/feature NIFI-3965.
Adds Hexdump processor to the nifi standard processor bundle.
The purpose of this processor is to create hexdumps of arbitrary flowfiles
and send them as output flowfiles or/and custom attribute.
Processor Properties include:
**Mode** : Selectable Mode, describing if the converted Hexdump data should
yield FlowFile data, Attribute or Both.
**Flowfile offset** : Non negative integer offset of Hexdump in FlowFile
output. If offset is out of bounds no data will be transferred. This is only
used if mode is FLOWFILE or BOTH.
**Flowfile length** : Non negative integer describing maximum size of
Hexdump in FlowFile output. 0 = unlimited. This is only used if Mode is
FLOWFILE or BOTH.
**Attribute name** : String Hexdump output attribute name. This is only used
if mode is ATTRIBUTE or BOTH.
**Attribute offset** : Non negative integer offset of attribute Hexdump. If
offset is out of bounds no data will be transferred. This is only used if mode
is ATTRIBUTE or BOTH.
**Attribute length** : Non negative integer maximum size of attribute
Hexdump. This is only used if mode is ATTRIBUTE or BOTH.
Adds 2 files:
HexDump.java
TestHexDump.java
Edits 1 file:
nifi/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/resources/META-INF/services/org.apache.nifi.processor.Processor
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
- [x] 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.
- [x] Has your PR been rebased against the latest commit within the target
branch (typically `main`)?
- [x] 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:
- [x] Have you ensured that the full suite of tests is executed via `mvn
-Pcontrib-check clean install` at the root `nifi` folder?
- [x] Have you written or updated unit tests to verify your changes?
- [ ] Have you verified that the full build is successful on JDK 8?
- [x] Have you verified that the full build is successful on JDK 11?
- [x] 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)?
- [x] If applicable, have you updated the `LICENSE` file, including the main
`LICENSE` file under `nifi-assembly`?
- [x] If applicable, have you updated the `NOTICE` file, including the main
`NOTICE` file found under `nifi-assembly`?
- [x] If adding new Properties, have you added `.displayName` in addition to
.name (programmatic access) for each of the new properties?
### For documentation related changes:
- [x] 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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
