[
https://issues.apache.org/jira/browse/NIFI-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503912#comment-14503912
]
ASF GitHub Bot commented on NIFI-461:
-------------------------------------
Github user bbende commented on the pull request:
https://github.com/apache/incubator-nifi/pull/43#issuecomment-94590366
Thanks for reviewing Mike.
With regards to the ContentStreamUpdateRequest... I actually hadn't thought
about using it for deletes, but I just did a test and it worked. So it should
work for almost any add/update/delete example in the Solr documentation. It
would just require an upstream processor that was producing the right commands,
where as for the case of adding new documents it seems more likely that you
already have some data (json, csv, etc) that you can just fork into Solr.
I was thinking there eventually might be a use case for another type of
"PutSolr" processor that reads in data in a standard format (maybe avro) and
converted to a SolrInputDocument, but seemed like the ContentStream approach
gave the most flexibility initially.
> 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)
