[
https://issues.apache.org/jira/browse/NIFI-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15201481#comment-15201481
]
Joseph Witt commented on NIFI-1118:
-----------------------------------
In my opinion it is not ready and should be moved to 0.7.0 or 1.0 - whatever is
next. It has some clear benefits and is moving in the right direction. I even
do support dropping the end of line thing. But we need to do that probably at
the 1.0 release and with great user guided explanation to help them with the
change. Because this processor is really old and really heavily used.
[~markap14] also noted in the review a byte buffer issue that could impact
memory on some large lines (and we see that all the time).
In short, I request we move this off of this release. It is important work but
it is not ready and 0.6.0 is primed.
> 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)
