nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Payne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NIFI-446) MergeContent should provide "Strategy" property for specifying how Header, Footer, and Demarcator properties should be interpreted
Date Tue, 19 May 2015 01:42:00 GMT

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

Mark Payne commented on NIFI-446:
---------------------------------

[~bbende] I think I would just always allow Expression Language. If it's interpreted as a
filename, the Expression Language will be interpreted without the FlowFile attributes, though.
Still would allow you to specify JVM and System Properties. I.e., you'd call context.getProperty(...).evaluateAttributeExpressions().getValue();

If the "Text" strategy is used, it would interpret the value for each FlowFile instead.

Does that make sense? It does in my head, but I'm not sure that I'm articulating it well at
all right now :)

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

Mime
View raw message