[
https://issues.apache.org/jira/browse/MINIFICPP-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16198742#comment-16198742
]
marco polo commented on MINIFICPP-256:
--------------------------------------
[~fstakem] The problem that PR addresses is in the move of the file from input
to /processing, so process.py can access it. When I run this no OSX, RHEL7, and
ubuntu16 I see the following lines in minifi-app.log.
Can you validate that you also have these lines?
[2017-10-10 14:17:37.530] [org::apache::nifi::minifi::core::ProcessGroup]
[debug] Starting ExecuteProcess
[2017-10-10 14:17:37.530] [org::apache::nifi::minifi::ThreadedSchedulingAgent]
[info] Scheduled thread 1 concurrent workers for for process ExecuteProcess
[2017-10-10 14:17:37.530] [org::apache::nifi::minifi::SchedulingAgent] [debug]
Triggering ExecuteProcess
[2017-10-10 14:17:37.530]
[org::apache::nifi::minifi::processors::ExecuteProcess] [info] Execute Command
python /home/fstakem/tmp/nifi_test/process.py
When I shut down I see the following lines that indicate the sleep is being
honored.
[2017-10-10 14:18:10.738] [org::apache::nifi::minifi::ThreadedSchedulingAgent]
[info] Shutting down threads for processor
ExecuteProcess/c48096de-adc5-11e7-848b-1250849c08b8
[2017-10-10 14:18:10.741]
[org::apache::nifi::minifi::processors::ExecuteProcess] [info] Execute Command
Complete python status 1 pid 5352
If you could pass along your minifi-app.log or at least the ExecuteProcess
portions I can offer more help. The fix I provided should get you to have the
correct data for ExecuteProcess, at which point my systems are not experiencing
the same issue, so there is hopefully some info in your log that may be able to
help.
> ExecuteProcess script uses wrong path
> -------------------------------------
>
> Key: MINIFICPP-256
> URL: https://issues.apache.org/jira/browse/MINIFICPP-256
> Project: NiFi MiNiFi C++
> Issue Type: Bug
> Reporter: Fredrick Stakem
> Assignee: marco polo
> Attachments: 1.csv, 2.csv, basic_minifi_test.xml, config.yml,
> process.py
>
>
> I am running a test using nifi to create a flow and then import this flow
> into minifi c++. The flow seems to work as expected on nifi.
> The flow takes a file from input directory and places it into the processing
> directory. In the background another ExectureProcess processor runs a simple
> python script to look at the processing directory, get any files, parse the
> files, and export to an output directory.
> As stated before everything works as expected nifi, but in minifi c++ the
> files end up in the root folder of minifi c++ and not the output directory.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
