Sorry everybody, please ignore my last message. Gmail protects from
accidental reply-alls, but not replies to mailing lists :).
(Thanks to the developers for all the fantastic work on Solr, btw.
Saving us a tonne of work.)
-Jeff
On 4/21/07, Jeff Kavanagh <[EMAIL PROTECTED]> wrote:
You might w
You might want to have a look at this patch in case it breaks stuff for us
On 4/20/07, Henrib <[EMAIL PROTECTED]> wrote:
Updated (forgot the patch for Servlet).
http://www.nabble.com/file/7996/solr-trunk-src.patch solr-trunk-src.patch
The change should still be compatible with the trunk it is
Updated (forgot the patch for Servlet).
http://www.nabble.com/file/7996/solr-trunk-src.patch solr-trunk-src.patch
The change should still be compatible with the trunk it is based upon.
Henrib wrote:
>
> Following up on a previous thread in the Solr-User list, here is a patch
> that allows ma
I'm sorry to say I am *way* behind on my patch reading (and moving into my
new place this weekend where i have no net access isn't going to help) so
i can't comment on the technique (or even style) of this patch ... but if
you could do peopel a favor and open a Jira issue and post it there for
peo
There is still only one solr.home instance used to load the various classes
which is used as the one 'root'.
>From there, you can have multiple solrconfig*.xml & schema*.xml (even
absolute pathes); calling new SolrCore(name_of_core, path_to_solrconfig,
path_to_schema) creates a named core that you
This sounds like a great idea, and potentially very useful for my company.
Can you explain a bit about how you would configure the various solr/home
paths, and how the different indexes would be accessed by clients?
Thanks!
- Michael
--
View this message in context:
http://www.nabble.com/Mult