commit | 63d2358d3a37dcd44415ae764c028f72f64355e3 | [log] [tgz] |
---|---|---|
author | Aldrin Piri <aldrin@apache.org> | Thu Jul 14 09:13:34 2016 -0700 |
committer | Aldrin Piri <aldrin@apache.org> | Wed Aug 03 09:07:39 2016 -0400 |
tree | 67708d7736537b659bb002a15285ac1b48de16dc | |
parent | b3848a3192f349023ef209b943519f7812e3faca [diff] |
MINIFI-68 Adding yaml-cpp source and updating LICENSE to reflect its inclusion. Adding a Makefile for yaml-cpp and incorporating its library build as part of the overall process. Providing parsing of config.yml to establish a processing graph as well as providing configuration for FlowController to handle XML and YAML. Ignoring SIGPIPE signal. Adjusting Makefile to correct assembly packages not being generated. Providing includes for yaml-cpp build Makefile and having top level Makefile build libuuid regardless. Removing generated tst_uuid binary from uuid thirdprty dependency. Adding Google Test LICENSE information as it is bundled with yaml-cpp
MiNiFi is a child project effort of Apache NiFi. This repository is for a native implementation in C++.
Except as otherwise noted this software is licensed under the Apache License, Version 2.0
Licensed 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.
Build application, it will build minifi exe under build and copy over to target directory
$ make
Clean
$ make clean
Running application
$ ./target/minifi
The Native MiNiFi example flow.xml is in target/conf It show cases a Native MiNiFi client which can generate flowfile, log flowfile and push it to the NiFi server. Also it can pull flowfile from NiFi server and log the flowfile. The NiFi server config is target/conf/flow_Site2SiteServer.xml
For trial command control protocol between Native MiNiFi and NiFi Server, please see the example NiFi Server implementation in test/Server.cpp The command control protocol is not finalized yet.
Caveat: 1) Add new propery HostName and Port into RemoteProcessGroup InputOutput port for remote Site2Site hostname and port 8f3b248f-d493-4269-b317-36f85719f480 NiFi Flow http://localhost:8081/nifi 30 sec 1 sec true 471deef6-2a6e-4a7d-912a-81cc17e3a204 From Node A RUNNING 1 false Host Name localhost Port 10001 2) Add new proerties into minifi.properties for command control
nifi.server.name=localhost nifi.server.port=9000 nifi.server.report.interval=1000 ms