THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Contributing to Apache MiNiFi C++
We welcome contributions to the Apache MiNiFi C++ project. We are providing this guide to make contributing easier and increase development. Apache MiNiFi is developed by an open community in which we welcome feedback and questions. You are invited to engage the community with questions at the dev or user list: dev@nifi.apache.org and user@nifi.apache.org.
Filing JIRA tickets
If you experience problems with Apache MiNiFi contact the dev E-mail list, above, or file an Apache JIRA Ticket [1]. Click Create button at the top and provide as much detail as you can to ticket description. Any information you can provide to facilitate replicating the problem is greatly appreciated.
If you wish to suggest new features, regardless if you have the time to provide the fix or implementation, we encourage you to file an Apache JIRA Ticket [1], providing as much detail as possible for the suggested feature.
Providing code or documentation contributions
...
git config --global user.email user.name@email.org
Checkout the '
...
main' or '0.x' branch
git checkout -b master main origin/master will main will create a local, tracking branch named master.
git checkout -b 0.x origin/0.x will create a local, tracking branch named 0.x.
The master main branch currently represents the next major release line (O.x).
...
Developing with MiNiFi C++
System Requirements
For macOS build instructions, see Building MiNiFi on Mac OS X
Utilities
- CMake
- 2.8 or greater
- gcc
- 4.8.4 or greater
- g++
- 4.8.4 or greater
Libraries / Development Headers
- libboost and boost-devel
- 1.48.0 or greater
- libleveldb and libleveldb-devel
- libuuid and uuid-dev
- openssl
- (optional) doxygen
Building
Apache MiNiFi C++ uses CMAKE [3]. To build the project you may run the following command:
mkdir ./build && cd ./build && cmake .. && make && make test && make linter
This will create the necessary build directory, create the CMAKE environment, make the project, run tests, and assess the code style with the provided linter. If your environment does not meet the necessary requirements your build will fail creating the CMAKE environment. E-mail dev@nifi.apache.org for help in installing necessary components.
Dependencies
The thirdparty directory contains some third party libraries used to build MiNiFi. We currently have the following dependencies:
- Catch – This is a C++ unit testing library
- Civetweb – Used for the ListenHTTP process in providing the ability to instantiate a webserver
- LevelDB – a key/value store that provides an ordered mapping of string keys to string values. This is used for the provenance and flow file repositories.
- Uuid – LibUUID provides us the ability to easily interact with UUID objects (RFC 4122 compliant )
- Yaml-CPP – Library that provides the capability to read YAML configuration files.
- Spdlog – C++ logging infrastruction
- OpenSSL – Provides TLS capabilities for communications.
build instructions, refer to README.md.
Devlopment
Apache MiNiFi C++ can be developed in many IDEs, the scope of which are beyond this document. Common cross platform IDEs exist, such as CLion and Eclipse CDT. These IDEs offer the lowest bar of entry and the ability to continue development across platforms when switching environments.
Developing in Eclipse CDT
To import Apache MiNiFi C++ into your Eclipse CDT environment, right click within your Project Explorer tab and import the Apache MiNiFi sub directory as an Existing AutoTools project. Click Browser to locate the existing directory, at which point Eclipse will populate the project name with nifi-minifi-cpp. Click Finish to complete the import process.
...
Click File > Open Project and browser to the directory where you’ve stored the Apache MiNIFi C++ code base. Descend into the root directory of Apache MiNiFi C++ and click “Open.” CLion will auto detect the project. Follow prompts until you’ve imported Apache MiNiFI C++. CLion has a rich CMAKE environment allow you to debug within the environment. It is suggested that you build from the command line before committing to avoid any issues.
General Development Guidelines.
...
The project is structured with a main and libminifi directories. The former contains the MiNiFI C++ main entry point. The latter is a collection of source files that make up the CORE API.
For the include and src directories the following packages indicate the area of responsibility:
...
- Contains the remainder of the classes that deal with scheduling, provenance, and the main object that controls the processing groups (FlowController)
...
Once you are familiar with the layout and have decided where to put your code, verified your tests pass, and the project builds, you can validate that your style matches the expectations of the project by running “make linter.” When code is committed test and the linter will be run in Travis CI, which will provide you a response via E-maila Github Actions workflow. If you only have one development environment, Travis this CI will automatically run tests and the build within Windows, Linux and OSX, providing you confidence that your build works across platforms.
Make linter executes the linter against your project. If you are using Eclipse, you can use the Google Code Style Eclipse Formatter to reduce the number of artifacts generated during development [5]. If you make use of JetBrains CLion, there is both a cpp-lint plugin as well as the ability to you can configure your the editor to use the Google style for your editor (instructions).
...
Since MiNiFi C++ may run on a variety of platforms, please avoid known platform specific inclusions if possible. If you must make these inclusions, take care to use MACROS to avoid failure on platforms for which your code is non-portable.
Testing your changes
- For code changes, ensure that the full suite of tests is executed via
make testviactestwithin the build folder. Please write or update unit tests to verify your changes. - Did your change introduce new dependencies? Are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0? Did you update the LICENSE file?
- For documentation related changes, ensure that format looks appropriate for the output in which it is rendered.
Performing the commit
In the interest of providing traceability, it is helpful to lead off your commit with the associated JIRA issue number (case-sensitive, MiNIFI in uppercase) and a summary of the change this commit is providing. Such an example is:
...
The issue being listed first provides easy access to the supporting ticket and ensures it is not truncated from the varied means in which commits will be viewed.
...
[5] https://github.com/google/styleguide/blob/gh-pages/eclipse-cpp-google-style.xml