GitHub user jskora opened a pull request:

    https://github.com/apache/nifi/pull/135

    NIFI-1118 Update SplitText Processor - add support for split size lim…

    …its and header line markers.
    
    1) 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.
    2) 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.

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/135.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 #135
    
----
commit ddd394824e3f36429e5b43b755dd8d9df25f05ab
Author: Joe Skora <jsk...@gmail.com>
Date:   2015-12-01T18:32:36Z

    NIFI-1118 Update SplitText Processor - add support for split size limits 
and header line markers.
    1) 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.
    2) 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.

----


---
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.
---

Reply via email to