[
https://issues.apache.org/jira/browse/NIFI-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15188505#comment-15188505
]
Joe Skora commented on NIFI-1118:
---------------------------------
My concern is the buggy behavior related to Remove Trailing Newlines. Fixing
it may change behavior that's expected by dependents, but I really don't like
that behavior anyway I think it makes the output less consistent and it makes
processing more complex since it has to wait to find out if the current line is
the last line or not. It makes more sense to me if EVERY line is treated the
same regarding stripping or including the EOL marker, but I may be missing
something that drove the inclusion of that property.
It would be great to get it out in 0.6.0, hopefully we can sort out by Friday
if that can be done safely and well.
> 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.6.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)
