[
https://issues.apache.org/jira/browse/NIFI-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228305#comment-15228305
]
Joseph Witt commented on NIFI-1118:
-----------------------------------
I am fine with removing that property from this processor because it
muddies/complicates its pure function. However, there are absolutely use cases
for being able to remove trailing newlines and I just watched a NiFi
(commercial) user doing exactly this so they could remerge that and other data
with a normalized demarcator. This by the way was exactly why it was done in
the first place. Multiple sources of each of which using slightly different
end of line markings and this allowed those to be removed and normalized to a
specific one. That said, it is better to get that out of this processor and
put that into another most likely. So yeah I am fine with removing it
personally. We should do that in 1.0 because it is the default. People are
using it even when they did not really need it or perhaps even want it. That
was a mistake obviously on our part in choosing that as a default.
> Enable SplitText processor to limit line length and filter header lines
> -----------------------------------------------------------------------
>
> Key: NIFI-1118
> URL: https://issues.apache.org/jira/browse/NIFI-1118
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Mark Bean
> Assignee: Joe Skora
> Fix For: 0.7.0
>
>
> Include the following functionality to the SplitText processor:
> 1) Maximum size limit of the split file(s)
> A new split file will be created if the next line to be added to the current
> split file exceeds a user-defined maximum file size
> 2) Header line marker
> User-defined character(s) can be used to identify the header line(s) of the
> data file rather than a predetermined number of lines
> These changes are additions, not a replacement of any property or behavior.
> In the case of header line marker, the existing property "Header Line Count"
> must be zero for the new property and behavior to be used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
