Hi Shawn,
I'm going to add this to the your JIRA unless you think that it would be
good to open another issue.
The issue for me is that making a ./lib in the instanceDir is documented as
working in several places and has worked in previous versions of Solr, for
example solr 4.1.0.
I make a ./lib directory in Solr Home, all works just fine. However
according to the documentation making a ./lib directory in the instanceDir
should work, and in fact in Solr 4.1.0 it works just fine.
So the question for me is whether making a ./lib directory as documented
in collections1/conf/solrconfig.xml and collections1/README.txt is supposed
to work in Solr 4.4 , but due to a bug it is not working.
If it is not supposed to work, then the documentation needs fixing and
some note needs to be made about upgrading from previous versions of Solr.
Do you think I should open another JIRA and link it to yours or just add
this information (i.e. other scenarios where class loading not working) to
your JIRA?
Details below:
Tom
The documentation in the collections1/conf directory is confusing. For
example the collections1/conf/solrconfig.xml file says you should put a
./lib dir in your instanceDir. (Am I correct that an instanceDir refers to
the core? ) On the other hand the documentation in the
collections1/README.txt is confusing about whether it is talking about the
instanceDir or Solr Home:
For example, In collections1/conf/solrconfig.xml there is this comment:
If a "./lib" directory exists in your instanceDir, all files
found in it are included as if you had used the following
syntax...
<lib dir="./lib" />
Also in collections1/conf/README.txt it is suggested that you use ./lib
but that README.txt file needs editing as it is very confusing about
whether it is talking about Solr Home or the Instance Directory in the text
excerpted below.
I would assume that the conf and data directories have to be subdirectories
of the instanceDir, since I assume they are set per core. So in the
excerpt below the discussion of the sub-directories should apply to the
instanceDir not Solr Home.
"Example SolrCore Instance Directory
=============================
This directory is provided as an example of what an "Instance Directory
should look like for a SolrCore
It's not strictly necessary that you copy all of the files in this
directory when setting up a new SolrCores, but it is recommended.
Basic Directory Structure
-------------------------
The Solr Home directory typically contains the following sub-directorie:
conf/
This directory is mandatory and must contain your solrconfig.xml
and schema.xml. Any other optional configuration files would also
be kept here.
data/
This directory is the default location where Solr will keep your
...
lib/
On Wed, Aug 28, 2013 at 12:11 PM, Shawn Heisey <s...@elyograg.org> wrote:
> On 8/28/2013 9:34 AM, Tom Burton-West wrote:
>
>> I think I am running into the same bug, but the symptoms are a bit
>> different.
>> I'm wondering if it makes sense to file a separate linked bug report.
>>
>> The workaround is to remove sharedLib from solr.xml,
>>>>
>>> The solr.xml that comes out-of-the-box does not have a sharedLib.
>>
>> I am using Solr 4.4. out-of-the-box, with the exception that I set
>> up a
>> lib directory in example/solr/collection1. I did not change solr.xml
>> from
>> the out-of-the-box. There is no mention of "lib" in the out-of-the-box
>> example/solr/solr.xml.
>>
>> I did not change the out-of-the-box solrconfig.xml.
>>
>> According to the README.txt, all that needs to be done is create the
>> collection1/lib directory and put the jars there.
>> However, I am getting the class not found error.
>>
>> Should I open another bug report or comment on the existing report?
>>
>
> I have never heard of using ${instanceDir}/lib for jars. That doesn't
> mean it won't work, but I have never seen it mentioned anywhere.
>
> I have only ever put the lib directory in solr.home, where solr.xml is.
> Did you try that?
>
> If you have seen documentation for collection1/lib, then there may be a
> doc bug, another dimension to the bug already filed, or a new bug. Do you
> see log entries saying your jars in collection/lib are loaded? If you do,
> then I think it's probably another dimension to the existing bug.
>
> Thanks,
> Shawn
>
>
