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 <jsk...@gmail.com>
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.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
