[
https://issues.apache.org/jira/browse/NIFI-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15189293#comment-15189293
]
Joseph Witt commented on NIFI-1118:
-----------------------------------
Well we should really try to avoid changing the behavior with the user knowing
it. So one option if you'd like to remove this property altogether, and I for
one am fine with that, is to leave the property there but if set to true have
the processor be invalid. It could be optional or dynamically supported and
that way if used then we can leave the processor in an invalid state thus
ensuring the user will be alerted to the behavior change without the flow
simply moving on.
This processor is one of those extremely heavily used ones so we should just be
really careful.
In short, let's clean it up. If it is broke and fixing it will prove too risky
or problematic then let's punt that feature but alert the user. It will have
to occur on an at least minor version bump.
Let's be sure to sync on this again tomorrow or Monday. If it cannot be in
this 0.6.0 release that is ok because whenever we change this it needs time for
testing for sure.
Appreciate that you are digging into the details and thinking through it
carefully.
> 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)
