lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan Ernst (JIRA)" <>
Subject [jira] [Commented] (SOLR-4652) Resource loader has broken behavior for solr.xml plugins (basically ShardHandlerFactory)
Date Wed, 03 Apr 2013 01:04:14 GMT


Ryan Ernst commented on SOLR-4652:

Thanks Uwe!

I've disabled the "auto reorder imports" feature from IntelliJ, so that should be better in
future patches.  I will also make sure to figure out the svn revision or use an svn checkout.
 Sorry about the hassle!

I'm hoping to tackle refactoring of the shard handler factory stuff next, but then coming
back to classloader chaining is a possibility.  As I said before, I did start down that
is just a doozy.  It is pretty straightforward until you get to ZkSolrResourceLoader, then
it seemed to get complicated (I stopped there, so I am not sure if there is an easy path there).
> Resource loader has broken behavior for solr.xml plugins (basically ShardHandlerFactory)
> ----------------------------------------------------------------------------------------
>                 Key: SOLR-4652
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 4.2
>            Reporter: Ryan Ernst
>            Assignee: Uwe Schindler
>             Fix For: 4.3, 5.0
>         Attachments: SOLR-4652.patch, SOLR-4652.patch, SOLR-4652.patch
> I have the following scenario:
> MyShardHandlerFactory is plugged in via solr.xml.  The jar containing MyShardHandlerFactory
is in the shared lib dir.  There are a couple issues:
> 1. From within a per core handler (that is loaded within the core's lib dir), you grab
the ShardHandlerFactory from CoreContainer, casting to MyShardHandlerFactory will results
in a ClassCastException with a message like "cannot cast instance of MyShardHandlerFactory
to MyShardHandlerFactory".
> 2. Adding a custom dir for shared lib (for example "mylib") does not work.  The ShardHandlerFactory
is initialized before sharedLib is loaded.
> I've been pouring through the code on this and I don't see an easy fix.  I'll keep looking
at it, but I wanted to get this up so hopefully others have some thoughts on how best to fix.
 IMO, it seems like there needs to be a clear chain of resource loaders (one for loading solr.xml,
a child for loading the lib dir, used for solr.xml plugins, a grandchild for per core config,
and a great grandchild for per core lib dir based plugins).  Right now there are some siblings,
because any place a SolrResourceLoader is created with a null parent classloader, it gets
the jetty thread's classloader as the parent.

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:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message