[
https://issues.apache.org/jira/browse/NIFI-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15201602#comment-15201602
]
Joe Skora commented on NIFI-1118:
---------------------------------
[~joewitt]
(Sorry, I've been having computer issues this morning or I'd have replied
sooner.)
I really hate to see this pushed out further. It was re-worked based on the
discussion last week and has close to 99% code coverage. The byte buffer is
suppressed when possible, but it seems a necessary evil to provide line
granularity when splitting on total file size instead of line count.
Since the existing version has a verifiable bug with the "Remove Trailing
Newlines" logic that can result in data loss, to me the new version seems safer
for users. The deprecation will only invalidate flows that are currently at
risk of silent data loss.
> 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)
