[
https://issues.apache.org/jira/browse/NIFI-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15247868#comment-15247868
]
ASF GitHub Bot commented on NIFI-1118:
--------------------------------------
Github user joewitt commented on the pull request:
https://github.com/apache/nifi/pull/280#issuecomment-211956655
thanks @markobean and @jskora . What do you think about making ignore
newlines only be honored/supported when not using the new features you're
planning to include or only in very specific configurations? I ask because
this, admittedly mistaken, feature is used a lot. Ultimately if that seems to
unwieldy we can punt that feature in 1.0, add your new capabilities, and
support end of line removal on ReplaceText instead. We just need to remember
to document this in the migration guide for 1.0 as this could cause some pretty
funky behavior changes for folks.
What do you think?
> 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.7.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)
