OK, this is working now. There were a couple of things going on, but
the net-net was "classloading issues."
The initial "no such core" problem was happening because the cores
weren't initializing properly due
to a NoClassDefFoundError. But after fixing that, I wound up with a
pile of ClassCastEx
On Fri, Jan 6, 2012 at 11:28 AM, Christopher Childs wrote:
> Multicore does work with EmbeddedSolrServer. It's what we use in our
> application.
>
> solr.xml is also relevant for configuring the cores. We do not do it in quite
> the same manner that Phillip is describing, though. Our CoreContain
Multicore does work with EmbeddedSolrServer. It's what we use in our
application.
solr.xml is also relevant for configuring the cores. We do not do it in quite
the same manner that Phillip is describing, though. Our CoreContainer is
initialized by SolrDispatchFilter. After the core container is
On Fri, Jan 6, 2012 at 11:03 AM, Erik Hatcher wrote:
>
> Again, EmbeddedSolrServer (unless I'm gravely mistaken!) doesn't do
> multicore. It's for a single core. If you want multiple cores
> supported... created multiple EmbeddedSolrServer instances. You point the
> instance to the core's "h
2012/1/6 Yury Kats :
>
> That probably means the home is not set properly, so it can't find solr.xml
>
Well, all the docs mention doing is this bit, which I have:
System.setProperty('solr.solr.home',
'/usr/servers/solr/apache-solr-3.5.0/example/heceta');
I've also tried it the other way mentioned
On Jan 6, 2012, at 10:46 , Yury Kats wrote:
> On 1/6/2012 10:19 AM, Phillip Rhodes wrote:
>> 2012/1/6 Yury Kats :
>>>
>>> Have you tried passing core name (collection1) to the c'tor, instead
>>> of the empty string?
>>
>> Yep, but that gives the same error (with the core name appended) such
>>
On 1/6/2012 10:19 AM, Phillip Rhodes wrote:
> 2012/1/6 Yury Kats :
>>
>> Have you tried passing core name (collection1) to the c'tor, instead
>> of the empty string?
>
> Yep, but that gives the same error (with the core name appended) such
> as "no such core: collection1"
That probably means the
2012/1/6 Yury Kats :
>
> Have you tried passing core name (collection1) to the c'tor, instead
> of the empty string?
Yep, but that gives the same error (with the core name appended) such
as "no such core: collection1"
Phil
On 1/6/2012 9:57 AM, Phillip Rhodes wrote:
> On Fri, Jan 6, 2012 at 3:06 AM, Sven Maurmann wrote:
>> Hi,
>>
>> from your snippets the reason is not completely clear. There are a number of
>> reasons for not starting up the
>> server. For example in case of a faulty configuration of the core
>> (
On Fri, Jan 6, 2012 at 8:06 AM, Erik Hatcher wrote:
> Also note that an EmbeddedSolrServer is for a specific core, not for all
> cores (and thus solr.xml is not used). My hunch is that you > need to point
> to the core's home directory, not to the parent of solr.xml.
Oh, interesting. The exam
On Fri, Jan 6, 2012 at 3:06 AM, Sven Maurmann wrote:
> Hi,
>
> from your snippets the reason is not completely clear. There are a number of
> reasons for not starting up the
> server. For example in case of a faulty configuration of the core
> (solrconfig.xml, schema.xml) the core does
> not sta
Also note that an EmbeddedSolrServer is for a specific core, not for all cores
(and thus solr.xml is not used). My hunch is that you need to point to the
core's home directory, not to the parent of solr.xml.
Erik
On Jan 6, 2012, at 03:06 , Sven Maurmann wrote:
> Hi,
>
> from your s
Hi,
from your snippets the reason is not completely clear. There are a number of
reasons for not starting up the
server. For example in case of a faulty configuration of the core
(solrconfig.xml, schema.xml) the core does
not start and you get the reported error.
Best,
Sven
Am 06.01.2012 um
Hi all, I'm having an issue that I hope someone can shed some light on.
I have a Groovy program, using Solr 3.5, where I am attempting to use
EmbeddedSolrServer using the instructions shown here:
http://wiki.apache.org/solr/Solrj#EmbeddedSolrServer
to that end, I have code setup like this:
...
14 matches
Mail list logo