[
https://issues.apache.org/jira/browse/CONNECTORS-840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866143#comment-13866143
]
Karl Wright commented on CONNECTORS-840:
----------------------------------------
When I change the zkhost parameter to "localhost", then we get this:
{code}
[junit] ------------- ---------------- ---------------
[junit] Testcase: testIndexPost(org.apache.manifoldcf.agents.output.solr.Htt
pPosterTest): Caused an ERROR
[junit] java.util.concurrent.TimeoutException: Could not connect to ZooKeepe
r localhost within 500 ms
[junit] java.lang.RuntimeException: java.util.concurrent.TimeoutException: C
ould not connect to ZooKeeper localhost within 500 ms
[junit] at org.apache.solr.common.cloud.SolrZkClient.<init>(SolrZkClient
.java:142)
[junit] at org.apache.solr.common.cloud.SolrZkClient.<init>(SolrZkClient
.java:88)
[junit] at org.apache.solr.common.cloud.ZkStateReader.<init>(ZkStateRead
er.java:150)
[junit] at org.apache.solr.client.solrj.impl.CloudSolrServer.connect(Clo
udSolrServer.java:240)
[junit] at org.apache.solr.client.solrj.impl.CloudSolrServer.request(Clo
udSolrServer.java:501)
[junit] at org.apache.solr.client.solrj.request.AbstractUpdateRequest.pr
ocess(AbstractUpdateRequest.java:117)
[junit] at org.apache.manifoldcf.agents.output.solr.HttpPoster$IngestThr
ead.run(HttpPoster.java:886)
[junit] Caused by: java.util.concurrent.TimeoutException: Could not connect
to ZooKeeper localhost within 500 ms
[junit] at org.apache.solr.common.cloud.ConnectionManager.waitForConnect
ed(ConnectionManager.java:169)
[junit] at org.apache.solr.common.cloud.SolrZkClient.<init>(SolrZkClient
.java:134)
[junit]
[junit]
{code}
So clearly the test is not bringing up a ZooKeeper instance to talk to. How
could this ever have worked?
> Job - Solr Mapping Improvement
> ------------------------------
>
> Key: CONNECTORS-840
> URL: https://issues.apache.org/jira/browse/CONNECTORS-840
> Project: ManifoldCF
> Issue Type: Improvement
> Components: Lucene/SOLR connector
> Affects Versions: ManifoldCF 1.4.1
> Reporter: Alessandro Benedetti
> Assignee: Karl Wright
> Priority: Minor
> Labels: field, mapping, request, solr, update
> Fix For: ManifoldCF 1.5
>
> Attachments: CONNECTORS-840.patch
>
>
> "When you configure a job to use a Solr-type output connection, the Solr
> connection type provides a tab called "Field Mapping". The purpose of this
> tab is to allow you to map metadata fields as fetched by the job's connection
> type to fields that Solr is set up to receive. This is necessary because the
> names of the metadata items are often determined by the repository, with no
> alignment to fields defined in the Solr schema. You may also suppress
> specific metadata items from being sent to the index using this tab.
> Add a new mapping by filling in the "source" with the name of the metadata
> item from the repository, and "target" as the name of the output field in
> Solr, and click the "Add" button. Leaving the "target" field blank will
> result in all metadata items of that name not being sent to Solr."
> In my opinion we should change the way a metadata field is suppressed.
> The most natural way is that we express only the mappings of the metadata
> fields we want to keep.
> All the missing params will not be sent to Solr.
> The improvement will be :
> - same interface with a boolean flag in addition, this flag will specify if
> the missing metadata fields not expressed should be sent to Solr with the
> original names or not sent at all.
> In this way if we want to keep 3/100 metadata fields, we don't have to write
> 100 mapping entries , 97 empty but simply 3 entries and activate the flag.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
