adamdebreceni commented on a change in pull request #1138:
URL: https://github.com/apache/nifi-minifi-cpp/pull/1138#discussion_r691886386
##########
File path: conf/minifi.properties
##########
@@ -20,6 +20,9 @@ nifi.administrative.yield.duration=30 sec
# If a component has no work to do (is "bored"), how long should we wait
before checking again for work?
nifi.bored.yield.duration=100 millis
+# Comma separated path for the extension libraries. Relative path is relative
to the minifi executable.
+nifi.extension.path=../extensions/*
Review comment:
regarding the second point: you would need to move the compiled
extensions to `MINIFI_HOME/extensions`, I wouldn't call that "without extra
effort", but you could specify `nifi.extension.path=*` and it would use the
freshly built extensions while `${MINIFI_HOME}/extensions/*` would achieve the
other use-case
I don't think we can reference the `EXE_DIR` from the configuration file, so
if someone decides to use the extension relative to the exe they would have to
hard code the exe dir
--
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-unsubscr...@nifi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
