james94 opened a new pull request #763: URL: https://github.com/apache/nifi-minifi-cpp/pull/763
**MiNiFi C++ and H2O Driverless AI Integration** via Custom Python Processors: Integrates MiNiFi C++ with H2O's Driverless AI by Using Driverless AI's Python Scoring Pipeline and MiNiFi's Custom Python Processors. Uses the Python Processors to execute the Python Scoring Pipeline scorer to do batch scoring and real-time scoring for one or more predicted labels on test data in the incoming flow file content. I would like to contribute my processors to MiNiFi C++ as a new feature. **3 custom python processors** created for MiNiFi: **H2oPspScoreRealTime** - Executes H2O Driverless AI's Python Scoring Pipeline to do interactive scoring (real-time) scoring on an individual row or list of test data within each incoming flow file. **H2oPspScoreBatches** - Executes H2O Driverless AI's Python Scoring Pipeline to do batch scoring on a frame of data within each incoming flow file. **ConvertDsToCsv** - Converts data source of incoming flow file to csv. I do have a question about Python Processors, I notice the ExecutePythonProcessor has a Module Directory property for passing in paths to files and/or directories which contain modules required by the script. I am wondering what if there is a "module name" that the user needs to enter in the processor property to update the scripts import "module name" before that line of code is executed? Is that possible? and if so, how would one do that? Is there a place on the repo I can add config-batch-scoring.yml and config-interactive-scoring.yml files to show users how to get started with these processors quickly? Created Jira ticket associated with this PR: https://issues.apache.org/jira/browse/MINIFICPP-1199 - Note: more information about the 3 python processors is available in the Jira link above. Thank you for submitting a contribution to Apache NiFi - MiNiFi C++. 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 MINIFICPP-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 master)? - [ ] Is your initial contribution a single, squashed commit? ### For code 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? - [ ] If applicable, have you updated the NOTICE file? ### 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. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
