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

Karl Wright commented on CONNECTORS-840:
----------------------------------------

Fixed that problem, ran into another one when doing "ant 
run-tests-solr-connector":

{code}
run-tests:
    [mkdir] Created dir: C:\wip\mcf\CONNECTORS-840\connectors\solr\test-output
    [junit] Testsuite: org.apache.manifoldcf.agents.output.solr.HttpPosterTest
    [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0.09 sec
    [junit]
    [junit] Testcase: testIndexPost(org.apache.manifoldcf.agents.output.solr.Htt
pPosterTest):   Caused an ERROR
    [junit] org/noggit/JSONWriter$Writable
    [junit] java.lang.NoClassDefFoundError: org/noggit/JSONWriter$Writable
    [junit]     at java.lang.ClassLoader.defineClass1(Native Method)
    [junit]     at java.lang.ClassLoader.defineClass(ClassLoader.java:792)
    [junit]     at java.security.SecureClassLoader.defineClass(SecureClassLoader
.java:142)
    [junit]     at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
    [junit]     at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
    [junit]     at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
    [junit]     at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
    [junit]     at java.security.AccessController.doPrivileged(Native Method)
    [junit]     at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
    [junit]     at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
    [junit]     at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)

    [junit]     at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
    [junit]     at org.apache.manifoldcf.agents.output.solr.HttpPoster.<init>(Ht
tpPoster.java:150)
    [junit]     at org.apache.manifoldcf.agents.output.solr.HttpPosterTest.setUp
(HttpPosterTest.java:85)
    [junit] Caused by: java.lang.ClassNotFoundException: org.noggit.JSONWriter$W
ritable
    [junit]     at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
    [junit]     at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
    [junit]     at java.security.AccessController.doPrivileged(Native Method)
    [junit]     at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
    [junit]     at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
    [junit]     at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)

    [junit]     at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
    [junit]
    [junit]
{code}

Looks like we are still missing a dependency.


> 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