[
https://issues.apache.org/jira/browse/NIFI-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14379044#comment-14379044
]
Mark Payne commented on NIFI-461:
---------------------------------
Bryan,
* For the "Default Collection" property, that's right, you wouldn't need to
prefer an attribute over the default. You'd just let them pick whatever value
they want. They can hardcode it or they can set an attribute... or they can
even put something like ${solrCollection:replaceNull('SOLR')}. This would use
the solrCollection attribute if it exists or use the string "SOLR" if it does
not exist.
As far as implementation, you just need to set the supportsExpressionLanguage
flag to true in the PropertyDescriptor builder and then evaluate it by calling
context.getProperty().evaluateExpressionLanguage(flowFile).getValue()
* I was guessing you knew what you were doing with GetSolr - just wanted to
make sure that wasn't an oversight :)
* For the parameters, I wouldn't recommend any kind of naming convention. I
would just document how the dynamic properties are used with the
@DynamicProperties annotation. (Dan Bress recently finished that up an did a
pretty bang up job there so that'll make life a lot easier for users) :)
Another example to look at here would be the HandleHttpResponse, which does
something similar: user-defined properties become HTTP headers to add to the
response.
Any more questions, fire away! Happy to help however we can.
> Add processors to interact with Apache Solr
> -------------------------------------------
>
> Key: NIFI-461
> URL: https://issues.apache.org/jira/browse/NIFI-461
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Core Framework
> Reporter: Bryan Bende
> Priority: Minor
>
> I'd like to see processors for interacting with Apache Solr.
> Solr has a variety of "update handlers" which allow posting data for
> indexing, and NiFi would be a great framework to provide the data.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
