[
https://issues.apache.org/jira/browse/NIFI-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15201761#comment-15201761
]
Mark Bean commented on NIFI-1118:
---------------------------------
This depends entirely on what you mean by "fix". I propose the only fix is to
prevent the possible data loss when the number of blank lines exceeds the line
split count. Go no further (unless it happens conveniently and naturally as a
result of the fix.) I believe that to make the feature behave correctly and
consistently will require buffering and possible performance impacts.
Additionally, it should be noted that any change which affect how this feature
operates - even if it is for consistency sake - is changing behavior. This will
have an impact on users equally as much as forcing the feature to be disabled.
> 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)
