[
https://issues.apache.org/jira/browse/CONNECTORS-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13541557#comment-13541557
]
Karl Wright commented on CONNECTORS-594:
----------------------------------------
Ok, I've updated the Solr connector in branches/CONNECTORS-594 to use SolrJ.
There are, however, a couple of outstanding questions.
(1) What is the right way to interpret UpdateResponse from an add or delete
operation? Basically, ManifoldCF receives either an UpdateResponse, a
SolrServerException, or an IOException. From that, it needs to decide to
classify the response as one of the following:
- Document was successfully accepted and indexed
- Document failed, but might be accepted if tried later
- Document was rejected, and that will not change if retried in the future
- Document failed sufficiently badly that the whole job should be stopped
immediately
(2) Prior to using SolrJ, the Solr Connector client required a user to specify
the URLs for the following:
- Index (e.g. "/update/extract")
- Deletion (e.g. "/update")
- Status check (e.g. "/admin/ping")
It now seems like only one of these needs to be specified - the index URL. Why
don't I have to specify the others anymore? Are they permanently fixed? I
thought that they could be moved easily by changing solrconfig.xml. How does
SolrJ deal with that?
If I can get answers to these questions, I think I can quickly finish the SolrJ
work up and commit the revised connector to trunk.
> SolrCloud Output Connector
> --------------------------
>
> Key: CONNECTORS-594
> URL: https://issues.apache.org/jira/browse/CONNECTORS-594
> Project: ManifoldCF
> Issue Type: New Feature
> Affects Versions: ManifoldCF 1.0.1
> Reporter: Minoru Osuka
> Assignee: Karl Wright
> Priority: Minor
> Fix For: ManifoldCF 1.1
>
> Attachments: solrcloud-output-connector.tar.gz
>
>
> The Output Connectors doesn't support SolrCloud currently.
> Since the Solr 4.0 released, I think there is a need for support for
> SolrCloud.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
