[
https://issues.apache.org/jira/browse/NIFI-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14551613#comment-14551613
]
ASF GitHub Bot commented on NIFI-446:
-------------------------------------
GitHub user bbende opened a pull request:
https://github.com/apache/incubator-nifi/pull/57
NIFI-446 Adding a Delimiter Strategy to MergeContent
Adds a "Delimiter Strategy" property which allows specifying the Header,
Footer, and Demarcator as filenames, or as text values.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/bbende/incubator-nifi NIFI-446
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-nifi/pull/57.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 #57
----
commit 3cf65261aa141ef116b762d821cc5dbe26bb2bdd
Author: bbende <[email protected]>
Date: 2015-05-20T01:11:50Z
NIFI-446 Adding a Delimiter Strategy to MergeContent
----
> MergeContent should provide "Strategy" property for specifying how Header,
> Footer, and Demarcator properties should be interpreted
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-446
> URL: https://issues.apache.org/jira/browse/NIFI-446
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Bryan Bende
> Priority: Minor
>
> The Header, Footer, and Demarcator currently must be specified as filenames.
> We should add a strategy to allow user to configure the values as filenames
> or just text to insert.
> We would have a property named "Delimiter Strategy" (or something better)
> that provides 2 allowable value: "Text" and "Filename".
> If filename, it should behave as it does now. If text, instead of
> interpreting the header, footer, and demarcator as filenames, the
> user-defined text should be used. This means we should change the "Display
> Name" of these properties from "Header File", "Footer File", and "Demarcator
> File" to simply "Header", "Footer", and "Demarcator", respectively.
> Also will need to implement customValidate, since the validation of these
> properties depends on the strategy.
> Also need to allow for the Expression Language to be used, if not filename.
> If filename, should not allow Expression Language.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
