[
https://issues.apache.org/jira/browse/MINIFICPP-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16874246#comment-16874246
]
Mr TheSegfault commented on MINIFICPP-937:
------------------------------------------
[~bakaid] a quick look shows that it's pretty trivial to fix. Some errors in
the test cases require a little bit more thought and validation. Thanks for
pointing this out. The error looks to be caused when I bunged up a rebase and
didn't run the manual tests after – given that there was no good test coverage
for those features I'm adding that as critical piece to this fix. a simple unit
test would have easily caught this condition.
> TailFile in Single file mode does not work after restoring from state
> ---------------------------------------------------------------------
>
> Key: MINIFICPP-937
> URL: https://issues.apache.org/jira/browse/MINIFICPP-937
> Project: Apache NiFi MiNiFi C++
> Issue Type: Bug
> Reporter: Daniel Bakai
> Assignee: Mr TheSegfault
> Priority: Blocker
> Fix For: 0.7.0
>
> Attachments: config.yml
>
>
> To reproduce:
> * Create a TailFile - LogAttribute pipeline
> * Let it tail a few lines from the file
> * Restart minifi
> * TailFile will stop functioning (does not produce any FlowFiles even though
> there are lines added to the tailed file)
> I think this might be related to the latest rewrite adding multiple modes and
> changing the state file format and parsing.
> There is also a
> {{[2019-06-27 11:30:05.523] [org::apache::nifi::minifi::processors::TailFile]
> [error] store state file failed}}
> line in the log which indicates that the TailFile::storeState is sometimes
> called when state_file_ is empty (I have added extra logging to onTrigger,
> and the state_file_ variable is filled properly, so I don't know where is it
> exactly coming from).
> I have also attached my config.yml: [^config.yml]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
