[
https://issues.apache.org/jira/browse/NIFI-8214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17618906#comment-17618906
]
Chris Sampson commented on NIFI-8214:
-------------------------------------
[~rti1979] thanks for the reply. What your describing (whether I;d ever take
the same approach aside) sounds like a more general thing for the NiFi
Framework than just the Elasticsearch processors.
Suggest, if this is something you (or others in future) think would be useful,
then it would be sensible to start a discussion in the [Developer Mailing
List](https://nifi.apache.org/mailing_lists.html), that way it's a bit more of
a general discussion and someone can decide if/how NiFi could take that forward
in future - it doesn't feel like the right approach to change processors
piecemeal to support such an approach and I'd imagine comments in a single Jira
ticket aren't likely to catch the attention of the people most likely to make
such changes.
Note that Parameters can (I believe) be used in pretty much every
processor/controller property field, but they're different to taking values out
of a FlowFile's content/attributes (as you're describing in your use case).
> Extend PutElasticsearchHttp / Elastic URL to take ff-Attributes
> ---------------------------------------------------------------
>
> Key: NIFI-8214
> URL: https://issues.apache.org/jira/browse/NIFI-8214
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 1.12.1
> Reporter: ROGIER TIMMERMANS
> Priority: Minor
>
> The PutElasticsearchHttp processor's URL field only allows Variable Registry
> scope; this makes it less flexible than ea. InvokeHttp as this allows ff
> attributes as well.
> Suggesting a minor improvement/enhancement here.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
