[jira] [Commented] (NIFI-446) MergeContent should provide "Strategy" property for specifying how Header, Footer, and Demarcator properties should be interpreted

["Bryan Bende (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14549629#comment-14549629 ] 

Bryan Bende commented on NIFI-446:
----------------------------------

[~markap14] I'm trying to figure out how to allow expression language based on the strategy that is selected, thoughts? 

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