[
https://issues.apache.org/jira/browse/CONNECTORS-840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866134#comment-13866134
]
Karl Wright commented on CONNECTORS-840:
----------------------------------------
Addressed that issue - now on to the next problem, to whit:
{code}
[junit] 473 [Thread-0] INFO org.apache.zookeeper.ZooKeeper - Initiating clie
nt connection, connectString=zkHost sessionTimeout=5000 watcher=org.apache.solr.
common.cloud.ConnectionManager@14cff90
[junit] ------------- ---------------- ---------------
[junit] Testcase:
testIndexPost(org.apache.manifoldcf.agents.output.solr.HttpPosterTest):
Caused an ERROR
[junit] java.net.UnknownHostException: zkHost
[junit] java.lang.RuntimeException: java.net.UnknownHostException: zkHost
[junit] at
org.apache.solr.common.cloud.SolrZkClient.<init>(SolrZkClient.java:130)
[junit] at
org.apache.solr.common.cloud.SolrZkClient.<init>(SolrZkClient.java:88)
[junit] at
org.apache.solr.common.cloud.ZkStateReader.<init>(ZkStateReader.java:150)
[junit] at
org.apache.solr.client.solrj.impl.CloudSolrServer.connect(CloudSolrServer.java:240)
[junit] at
org.apache.solr.client.solrj.impl.CloudSolrServer.request(CloudSolrServer.java:501)
[junit] at
org.apache.solr.client.solrj.request.AbstractUpdateRequest.process(AbstractUpdateRequest.java:117)
[junit] at
org.apache.manifoldcf.agents.output.solr.HttpPoster$IngestThread.run(HttpPoster.java:886)
[junit] Caused by: java.net.UnknownHostException: zkHost
[junit] at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
[junit] at
java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:894)
[junit] at
java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1286)
[junit] at java.net.InetAddress.getAllByName0(InetAddress.java:1239)
[junit] at java.net.InetAddress.getAllByName(InetAddress.java:1155)
[junit] at java.net.InetAddress.getAllByName(InetAddress.java:1091)
[junit] at
org.apache.zookeeper.client.StaticHostProvider.<init>(StaticHostProvider.java:60)
[junit] at org.apache.zookeeper.ZooKeeper.<init>(ZooKeeper.java:445)
[junit] at org.apache.zookeeper.ZooKeeper.<init>(ZooKeeper.java:380)
[junit] at
org.apache.solr.common.cloud.SolrZooKeeper.<init>(SolrZooKeeper.java:40)
[junit] at
org.apache.solr.common.cloud.DefaultConnectionStrategy.connect(DefaultConnectionStrategy.java:37)
[junit] at
org.apache.solr.common.cloud.SolrZkClient.<init>(SolrZkClient.java:105)
[junit]
[junit]
{code}
It seems like the test is not working for SolrCloud, when that comes up
randomly.
> 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)
