[
https://issues.apache.org/jira/browse/NIFI-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15195495#comment-15195495
]
ASF GitHub Bot commented on NIFI-1118:
--------------------------------------
GitHub user jskora opened a pull request:
https://github.com/apache/nifi/pull/280
NIFI-1118 Update SplitText Processor - add support for split size limits
and header line markers.
* Add "Maximum Fragment Size" property. A new split file will be created
if the next line to be added to the current split file exceeds this
user-defined maximum file size. In the case where an input line is longer than
the fragment size, this line will be output in a separate split file that will
exceed the maximum fragment size.
* Add "Header Line Marker Character" property. Lines that begin with these
user-defined character(s) will be considered header line(s) rather than a
predetermined number of lines. The existing property "Header Line Count" must
be zero for this new property and behavior to be used.
* Deprecated the "Remove Trailing Newlines" property.
* Fixed conditional that incorrectly suppressed splits where the content
line count equaled the header line count and did not remove empty splits from
the session.
* Minor formatting cleanup.
* Exclude test files from RAT check in pom.xml.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jskora/nifi NIFI-1118
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/280.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #280
----
commit 914c5a2c52b19d153077a89b59f751aa49ddf86c
Author: Joe Skora <[email protected]>
Date: 2016-03-15T14:31:00Z
NIFI-1118 Update SplitText Processor - add support for split size limits
and header line markers.
* Add "Maximum Fragment Size" property. A new split file will be created
if the next line to be added to the current split file exceeds this
user-defined maximum file size. In the case where an input line is longer than
the fragment size, this line will be output in a separate split file that will
exceed the maximum fragment size.
* Add "Header Line Marker Character" property. Lines that begin with these
user-defined character(s) will be considered header line(s) rather than a
predetermined number of lines. The existing property "Header Line Count" must
be zero for this new property and behavior to be used.
* Fixed conditional that incorrectly suppressed splits where the content
line count equaled the header line count and did not remove empty splits from
the session.
* Minor formatting cleanup.
* Exclude test files from RAT check in pom.xml.
----
> 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)
