[
https://issues.apache.org/jira/browse/MINIFICPP-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849251#comment-16849251
]
Christian Porzio commented on MINIFICPP-881:
--------------------------------------------
Goodness... But that *TailFile* is very different from the one reference on
Apache:
[https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.8.0/org.apache.nifi.processors.standard.TailFile/]
The pros is that I do see indeed the delimiter option which is not mentioned in
the _nifi.apache_ but the big cons is that it does not take any file pattern.
I can do away from the sophisticated file regex that the *TailFile* in
_nifi.apache_ can manage but because my log are in a user's folder with names
depending on the running application, I need to be able to use environment
variables and file patterns.
* id: cc39da05-6c73-3541-0000-000000000000
name: TailFile SM Log Files
*{color:#FF0000}class: org.apache.nifi.processors.standard.TailFile{color}*
max concurrent tasks: 1
scheduling strategy: TIMER_DRIVEN
scheduling period: 0 sec
penalization period: 30 sec
yield period: 1 sec
run duration nanos: 0
auto-terminated relationships list: []
Properties:
File Location: Local
{color:#FF0000}*File to Tail: '.*\.log'*{color}
Initial Start Position: Current Time
Rolling Filename Pattern: .*\.log\.1
{color:#FF0000}*tail-base-directory:
${"LOCALAPPDATA":replace('\\','\\\\'):append('\\\\SmartBrowser')}*{color}
tail-mode: Multiple files
tailfile-lookup-frequency: 0 second
tailfile-maximum-age: 24 hours
tailfile-recursive-lookup: 'true'
I am now confused by such a difference. At least this explains the errors I
could observe when my minfi.exe was running. I was about to submit another
issue for those...
With that being said, thank you for looking at my question. Your inputs are
always appreciated.
Cheers!
> SplitText not supported
> -----------------------
>
> Key: MINIFICPP-881
> URL: https://issues.apache.org/jira/browse/MINIFICPP-881
> Project: Apache NiFi MiNiFi C++
> Issue Type: Improvement
> Environment: Windows development
> Reporter: Christian Porzio
> Assignee: Mr TheSegfault
> Priority: Major
>
> I understand minfi-cpp is improving by the days - very much appreciated!!!
> But at the moment without *SplitText*, I am unable to use it. We do have the
> *TailFile* but without a SplitText those multi lines flowfiles are useless.
> I could just send these flowfiles as-is to my NIFI RPG and have all what we
> currently do on the client side performed on the server side but I would like
> to avoid that and use my client processors to lighten a bit the server load.
> 1/ Is there a targeted date for delivering *SplitText*?
> 2/ Or would one suggest a work around in the meantime, for instance ensure
> the TailFile produce one flowfile per line?
> Thank you for your inputs and recommendations
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
