[
https://issues.apache.org/jira/browse/NIFI-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15201674#comment-15201674
]
Joe Skora commented on NIFI-1118:
---------------------------------
[~joewitt], as Mark pointed out, it is not deprecation but feature removal.
Sorry for any confusion, what I was incorrectly referring to as "deprecation"
is leaving the property in place but invalidating the processor if it is set,
as you suggested last week, so flows that need to be adjusted will be
highlighted by the invalid processor.
I don't think we should release 0.6.0 with the known data loss bug in the
current SplitText processor. I think it would be better to either release the
new version which may require some flows to be adjusted if "Remove Trailing
Newlines" is set, or postpone release of 0.6.0 until the old version can be
fixed to eliminate possible 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)
