It seems to me multicore should avoid replicating (or restricting itself to)
features what we can get with multiple web apps; I advocate allowing tighter
couplings between cores in the former which seems to me closer to user
expectations (at least Walter's). If we keep one class loader per core
On Nov 11, 2007 5:51 AM, Henrib [EMAIL PROTECTED] wrote:
It seems to me multicore should avoid replicating (or restricting itself to)
features what we can get with multiple web apps; I advocate allowing tighter
couplings between cores in the former which seems to me closer to user
expectations
I agree we don't want to replicate the servlet container.
If we were to create class loaders not per instance but per 'lib' directory
(not per instance dir as I mentioned earlier but per library directory),
what about the very standard use case where I want to 'reload' a core?
In this case,
[
https://issues.apache.org/jira/browse/SOLR-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-281:
---
Attachment: SOLR-281-SearchComponents.patch
Here is an updated version of your patch that converts the
[
https://issues.apache.org/jira/browse/SOLR-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tricia Williams updated SOLR-380:
-
Attachment: lucene-core-2.3-dev.jar
SOLR-380-XmlPayload.patch
This is a draft.
