[
https://issues.apache.org/jira/browse/NIFI-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14379028#comment-14379028
]
Bryan Bende commented on NIFI-461:
----------------------------------
Thanks for the quick feedback Mark, all of this makes sense and I'll start
working on some updates. A couple of questions/clarifications....
- For the "Default Collection" property, by having it support expression
language would that mean I no longer need to code the logic of preferring the
FlowFile attribute over the Default Collection value? I'm familiar with EL
conceptually, but haven't done that much with it from an implementation
perspective.
- For the GetSolr processor with regards to the filter query, the [ ] are
inclusive and { } is exclusive for range queries, so I was trying to avoid a
document matching on the exact end date and then matching again on the next
start date.
- I'm leaning towards changing "Content Stream URL" to "Content Stream Path" or
maybe "Update Handler Path" since that might align better with Solr terminology.
- For the request parameters, your suggestion is actually how I wanted it to
work, but I didn't know how to implement it with dynamic user properties. After
looking at the Dev Guide and RouteOnAttribute, I think I see how to make it
work now. Would you recommend some kind of naming convention so that properties
intended to be sent on the request can be identified, for example maybe they
have to start with "solr." ? or I guess any dynamic property can be passed
along?
Thanks.
> 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)
