[
https://issues.apache.org/jira/browse/NIFI-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15201508#comment-15201508
]
Joseph Witt commented on NIFI-1118:
-----------------------------------
mark,
Flow behavior change: I think if we do it before 1.0 the deprecated property
should still be supported as is. I know i suggested to make it invalid. That
is what i'm saying i was wrong about. I was not considering well enough just
how extensive the use of this is and how disruptive it would be on upgrades.
We should then explain in the docs that the property is deprecated (but not
removed) and that it will actually be removed later. This is more in-line with
the spirit of deprecation.
If we do it after 1.0 i think we can go ahead and change the behavior, document
it well in a transition guide, and we should be good to go.
Again, I apologize for waffling on the reasonableness of just making it invalid
but as i mentioned i now feel like that was too disruptive to users. You can
probably keep the work done as work slated for 1.0.
The other features should be able to get incorporated as you had originally
intend "line length and filter header". Just also be cautious about the byte
buffer concern mark raised.
Thanks
Joe
> 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)
