On Wednesday 14 November 2007 06:42:56 Mike Klaas wrote:
...
... I was
imagining that it was necessary to embed the filter clauses in the
core to produce an effective implementation. By the time I
finished my response, I had read enough of the relevant Lucene scorer
code (in particular,
ryantxu wrote:
but I fear we are turning the initialization into a jumbled spaghetti of
interface looparounds, callbacks and pending lists
of soon-to-be-initialized stuff.
(not just this patch - but the combination of requirements we have had for
all the plugin stuff)
I agree this is
I'm in a situation where Solr is embedded in a webapp (ie using solr.jar).
Other modules of this app are using log4j and I'm looking for a way to make
the logging configuration consistent (aka through log4.xml).
Can anyone who solved the same kind of issue share his/her experience?
After much
Long on my to-do list has been trying to use sl4j as a bridge to escape the
horrible limitations of JDK1.4 java.util.logging unfortunately cemented into
Solr, enter the fairly peaceful garden of log4j, and avoid the pitfalls of
commons-logging's trying to class-load its way into everyone's
[
https://issues.apache.org/jira/browse/SOLR-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher resolved SOLR-411.
---
Resolution: Fixed
Fix Version/s: 1.3
Thanks Grant!
Solr JAR Packaging Names
[
https://issues.apache.org/jira/browse/SOLR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542520
]
Henri Biestro commented on SOLR-350:
Walter's suggestion is already in solr-409 (with libDir attribute name).
I
[
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
admin webapp is core aware
Allow configurable class loader sharing
[
https://issues.apache.org/jira/browse/SOLR-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542562
]
Walter Ferrara commented on SOLR-409:
-
I ran some test, it seems to work really fine.
I like the way you choose to
XsltWriter does not output UTF-8 by default
---
Key: SOLR-412
URL: https://issues.apache.org/jira/browse/SOLR-412
Project: Solr
Issue Type: Bug
Components: search
Affects Versions: 1.2
[
https://issues.apache.org/jira/browse/SOLR-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542609
]
Hoss Man commented on SOLR-412:
---
i'm confused as to what the fix here would be... what do you think Solr should
do
For people not following:
http://www.nabble.com/SolrConfig.Initializable-tf4665036.html
In looking at how initialization throughout solr, I think the cleanest
and best approach to move forward is to break the existing init() method
for:
1. TokenFilterFactory.init( MapString,String args )
2.
11 matches
Mail list logo