You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Tricia Jenkins (JIRA)" <ji...@apache.org> on 2013/01/23 18:43:16 UTC
[jira] [Comment Edited] (SOLR-4317) SolrTestCaseJ4: Can't avoid
"collection1" convention
[ https://issues.apache.org/jira/browse/SOLR-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13560050#comment-13560050 ]
Tricia Jenkins edited comment on SOLR-4317 at 1/23/13 5:43 PM:
---------------------------------------------------------------
There is still a problem with jars from a sharedLib directory defined in solr.xml outside of the coreName's dataDir not being available to coreName's TestHarness despite it being logged as added to classpath:
1200 T11 oasc.SolrResourceLoader.replaceClassLoader Adding 'file:/C:/Development/workspace/peel-solr/src/solr.home/lib/my-solrplugins.jar' to classloader
I'm getting: SEVERE Full Import failed:java.lang.RuntimeException: org.apache.solr.handler.dataimport.DataImportHandlerException: Unable to load EntityProcessor implementation for entity:properties Processing Document # 1
Caused by: java.lang.ClassNotFoundException: Unable to load PropertiesEntityProcessor or org.apache.solr.handler.dataimport.PropertiesEntityProcessor
Workaround is to not use sharedLib.
was (Author: pgwillia):
There is still a problem with jars from a sharedLib directory defined in solr.xml outside of the coreName's dataDir not being available to coreName's TestHarness despite it being logged as added to classpath:
1200 T11 oasc.SolrResourceLoader.replaceClassLoader Adding 'file:/C:/Development/workspace/peel-solr/src/solr.home/lib/my-solrplugins.jar' to classloader
I'm getting: SEVERE Full Import failed:java.lang.RuntimeException: org.apache.solr.handler.dataimport.DataImportHandlerException: Unable to load EntityProcessor implementation for entity:properties Processing Document # 1
Caused by: java.lang.ClassNotFoundException: Unable to load MyEntityProcessor or org.apache.solr.handler.dataimport.PropertiesEntityProcessor
Workaround is to not use sharedLib.
> SolrTestCaseJ4: Can't avoid "collection1" convention
> ----------------------------------------------------
>
> Key: SOLR-4317
> URL: https://issues.apache.org/jira/browse/SOLR-4317
> Project: Solr
> Issue Type: Improvement
> Components: Tests
> Affects Versions: 4.0
> Reporter: Tricia Jenkins
> Priority: Minor
> Fix For: 4.2, 5.0
>
> Attachments: SOLR-4317.patch, SOLR-4317.patch
>
>
> There is still an issue after the SOLR-3826 patch was applied for 4.0 [https://issues.apache.org/jira/browse/SOLR-3826] in September 2012. When TestHarness is called from SolrTestCase4J the only available constructors ignore coreName, set coreName = null, and initialize the default 'collection1.'
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org