Thanks for your answers.
I've made some test, the singleton is correctly shared between handlers
in the same core, but not between cores, while putting connection pool
jar (and its dependencies) inside the war, make it works as it should
(but that doesn't look like a solution to me).
It seems to me
Allow configurable class loader sharing between cores
-
Key: SOLR-409
URL: https://issues.apache.org/jira/browse/SOLR-409
Project: Solr
Issue Type: Sub-task
Affects Versions: 1.3
[
https://issues.apache.org/jira/browse/SOLR-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Biestro updated SOLR-409:
---
Attachment: solr-409.patch
initial drop
> Allow configurable class loader sharing between cores
>
Created solr-409 as a sub-task of solr-215 to track and post patch.
I took the shareable library directory path (ie you can specify the library
directory used by a given core and whether it is shared or not); if 2 cores
specify the same directory and they are shared, there will be only one
instan
ryantxu wrote:
>
> Is the patch ready for a serious review? or are you still working on it?
>
Not sure if this I'm supposed to answer but anyway, I was expecting comments
before 'generalizing' the patch. Right now, it only applies to filter &
tokenizer factories. The foundation should be soli
[
https://issues.apache.org/jira/browse/SOLR-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541762
]
Walter Ferrara commented on SOLR-409:
-
Thanks very much!
a) In order to apply the patch, I've locally modified it t
[
https://issues.apache.org/jira/browse/SOLR-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541771
]
Henri Biestro commented on SOLR-409:
Sorry about the non-regular patch, my bad, I should've documented that.
I like
[
https://issues.apache.org/jira/browse/SOLR-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Biestro updated SOLR-409:
---
Attachment: solr-409.patch
> Allow configurable class loader sharing between cores
> --
[
https://issues.apache.org/jira/browse/SOLR-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Biestro updated SOLR-409:
---
Attachment: solr-350_409.patch
solr 350 & solr 409 mixed together
> Allow configurable class loader sh
[
https://issues.apache.org/jira/browse/SOLR-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541785
]
Henri Biestro commented on SOLR-281:
Not sure process-wise whether votes/watchers got a say, my apologies if not; +
[
https://issues.apache.org/jira/browse/SOLR-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541786
]
Yonik Seeley commented on SOLR-281:
---
I'm checking out the latest version now...
> Search Components (plugins)
>
With a multicore.xml that looks like:
it seems to work fine.
Just a tip:
libDir is somehow not relative to configdir. Maybe making it relative to
cfgDir, like:
libDir=cfgdir+libDir;
@ row 83 of MultiCore.java could make it more intuitive. (ie.
libDir="lib" vs. libDir="solr/lib")
I will te
: Created solr-409 as a sub-task of solr-215 to track and post patch.
: I took the shareable library directory path (ie you can specify the library
: directory used by a given core and whether it is shared or not); if 2 cores
: specify the same directory and they are shared, there will be only one
[
https://issues.apache.org/jira/browse/SOLR-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-394.
---
Resolution: Fixed
I just committed a fix for this.
> Ruby response writer emits invalid integers for n
My apologies for generating confusion.
The original solr-215 has a small blurb about its intentions that still
remain true today that I'll try to beef up and make more comprehensible (in
solr-350 most probably). There are 2 functional axis; one axis is about
easing deployment in IT constrained e
[
https://issues.apache.org/jira/browse/SOLR-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Biestro updated SOLR-409:
---
Attachment: solr-350_409.patch
lib dir is now relative to multicore dir;
started servlet update for sol
[
https://issues.apache.org/jira/browse/SOLR-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541879
]
Eric Pugh commented on SOLR-284:
Juri,
Thanks for the vote on the issue! The next time I update this patch to work
w
[
https://issues.apache.org/jira/browse/SOLR-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541786
]
[EMAIL PROTECTED] edited comment on SOLR-281 at 11/12/07 10:48 AM:
--
> How do you feel abou
[
https://issues.apache.org/jira/browse/SOLR-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-176.
Resolution: Fixed
Committed as part of SOLR-281
> Add detailed timing data to query response output
[
https://issues.apache.org/jira/browse/SOLR-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-281:
---
Component/s: search
Fix Version/s: 1.3
Assignee: Ryan McKinley
Affects Ve
[
https://issues.apache.org/jira/browse/SOLR-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-110.
Resolution: Fixed
SOLR-281 moves common search operation into reusable 'components'
> Factor out com
Audit the new ResponseBuilder class
---
Key: SOLR-410
URL: https://issues.apache.org/jira/browse/SOLR-410
Project: Solr
Issue Type: Improvement
Components: search
Affects Versions: 1.3
[
https://issues.apache.org/jira/browse/SOLR-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-281.
Resolution: Fixed
Lets track ResponseBuilder issues with SOLR-410
> Search Components (plugins)
> --
[
https://issues.apache.org/jira/browse/SOLR-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541938
]
Yonik Seeley commented on SOLR-410:
---
Ongoing review + changes also applies to search components in general
(SearchCo
Yonik Seeley commented on SOLR-410:
---
Ongoing review + changes also applies to search components in general
(SearchComponent class, etc).
Yes, of course!
What is your thought on resolving vs keeping open issues that need
further review/changes?
Keeping S
On Nov 12, 2007 3:34 PM, Ryan McKinley <[EMAIL PROTECTED]> wrote:
> What is your thought on resolving vs keeping open issues that need
> further review/changes?
If we know that changes need to be made (as is the case here), I think
it's OK to leave it open.
Committing things before they are "done"
[
https://issues.apache.org/jira/browse/SOLR-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tricia Williams updated SOLR-386:
-
Attachment: SOLR-386-SolrHighlighter.patch
SOLR-281 was recently commited. Formerly those changes
: My apologies for generating confusion.
oh please don't ... some confusion is bound to be a by-product of active
experimentation and forward thinking change ... we just need to make sure
that we periodicly take stock, and double check that we know where we are
going.
: Hopes this makes the m
28 matches
Mail list logo
