[ 
https://issues.apache.org/jira/browse/CONNECTORS-840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13865363#comment-13865363
 ] 

Karl Wright edited comment on CONNECTORS-840 at 1/8/14 12:18 PM:
-----------------------------------------------------------------

The missing classes are mockito classes, e.g.:

{code}
[javac] 
C:\wip\mcf\CONNECTORS-840\connectors\solr\connector\src\test\java\org\apache\manifoldcf\agents\output\solr\HttpPosterTest.java:43:
 error: package org.mockito does not exist
    [javac] import org.mockito.Mockito;
    [javac]                   ^
{code}

The powermock jars include no classes from org.mockito.*.  I suspect mockito is 
a dependency of powermock which is not being included.  Until it is included, 
the tests will not run under ant.



was (Author: [email protected]):
The powermock jars include no classes from org.mockito.*.  I suspect mockito is 
a dependency of powermock which is not being included.  Until it is included, 
the tests will not run under ant.


> 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)

Reply via email to