On 1/16/07, Ryan McKinley [EMAIL PROTECTED] wrote:
...I think a DocumentParser registry is a good way to isolate this top level
task...
With all this talk about plugins, registries etc., /me can't help
thinking that this would be a good time to introduce the Spring IoC
container to manage
[
https://issues.apache.org/jira/browse/SOLR-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465092
]
Bertrand Delacretaz commented on SOLR-69:
-
SOLR-69.patch updated
PATCH:MoreLikeThis support
Factor out common code in our SolrRequestHandler classes
Key: SOLR-110
URL: https://issues.apache.org/jira/browse/SOLR-110
Project: Solr
Issue Type: Improvement
Components:
[
https://issues.apache.org/jira/browse/SOLR-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465114
]
Bertrand Delacretaz commented on SOLR-69:
-
The method used to compute includeScore in MoreLikeThisHelper was
I'm new to solr (working on solrb with Erik). We have some functional
tests that run against a live solr instance, and I'd like the tests
to periodically remove all the documents from the index. This way
tests will have a predictable outcome that is independent on the
state of the index
On 1/16/07, Edward Summers [EMAIL PROTECTED] wrote:
I was thinking I could do a query that pulls back all the document
ids in the index, and then delete each one...
The delete by query feature will do this without requiring an
iteration on the client side, see
I'm new to SOLR and would like to contribute. I think my skills would best
lend themselves to helping with a nice query interface. I'm a java web dev
by profession (couple of the sites/companies I have worked with are below)
www.ptplace.com
www.colinx.com
www.getlocalbiz.com
On 1/16/07, rlawson [EMAIL PROTECTED] wrote:
...I'm new to SOLR and would like to contribute. I think my skills would best
lend themselves to helping with a nice query interface. I'm a java web dev
by profession...
If you mean graphic design of the admin webpages, there are two issues
about
First: Please pardon the cross-post to solr-user for reference. I hope
to continue this thread in solr-dev. Please answer to solr-dev.
1) more documentation (and posisbly some locking configuration options) on
how you can use Solr to access an index generated by the nutch crawler (i
think
Hello! I'm a novice in Lucene technologies, and now only trying to install
Solr.
The main problem is appeared because I have to use Sun Java(bla-bla) web
server as
servlet contaner. So: Who can explain me what means phrase in solr's docs-
Solr now looks in ./solr/conf for config,
I have three instances of Solr on a single machine that I would like
to query as if they were a single instance.
I was wondering if there's a facility, or if anyone has any
recommendations, for searching across multiple instances with a
single query, or merging the results of multiple
Bertrand Delacretaz wrote:
With all this talk about plugins, registries etc., /me can't help
thinking that this would be a good time to introduce the Spring IoC
container to manage this stuff.
More info at http://www.springframework.org/docs/reference/beans.html
for people who are not familiar
On 1/16/07, Alan Burlison [EMAIL PROTECTED] wrote:
Bertrand Delacretaz wrote:
.../me can't help
thinking that this would be a good time to introduce the Spring IoC
container to manage this stuff...
Please, no. I work on a big webapp that uses spring - it's a complete
nightmare to figure
Bertrand Delacretaz wrote:
Using just the IoC container? I'm not talking about full-blown Spring
magic, *just* IoC to assemble plugins.
Spring's IoC is not complicated, and logging statements and debuggers
are here to find out exactly what's happening if needed.
I don't think it'd be more
On 1/16/07, Alan Burlison [EMAIL PROTECTED] wrote:
...I've had *bad*
experiences with apps where people pulled in just about every framework,
component and widget you can think of...
That's what you previous message seemed to imply ;-)
I agree that, if we start using Spring (or another) IoC
On Tue, 2007-01-16 at 16:28 +0100, Eivind Hasle Amundsen wrote:
First: Please pardon the cross-post to solr-user for reference. I hope
to continue this thread in solr-dev. Please answer to solr-dev.
1) more documentation (and posisbly some locking configuration options) on
how you can use
I'm in frantic deadline mode so I'm just going to throw in some (hopefully)
short comments...
At 11:02 PM -0800 1/15/07, Ryan McKinley wrote:
the one thing that still seems missing is those micro-plugins i was
[SNIP]
interface SolrRequestParser {
SolrRequest process( HttpServletRequest
: Solr now looks in ./solr/conf for config, ./solr/data for data
: configurable via solr.solr.home system property...
: ??
:
: Is system property is really system-property ... / tag in web.xml file?
: Or I have to define sime environment var with name solr.solr.home?
it's a system
[
https://issues.apache.org/jira/browse/SOLR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465254
]
Yonik Seeley commented on SOLR-106:
---
Thanks for the info JJ... didn't see your update untill after I committed this
On 1/15/07, Chris Hostetter [EMAIL PROTECTED] wrote:
: The most important issue is to nail down the external HTTP interface.
I'm not sure if i agree with that statement .. i would think that figuring
out the model or how updates should be handled in a generic way, what
all of the Plugin types
[
https://issues.apache.org/jira/browse/SOLR-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465276
]
Hoss Man commented on SOLR-86:
--
regarding Bertrand's comment, i'm not sure if there is any benefit in having
this code
new repsonse classes and connection enhancements
Key: SOLR-111
URL: https://issues.apache.org/jira/browse/SOLR-111
Project: Solr
Issue Type: Improvement
Components: clients - ruby -
[
https://issues.apache.org/jira/browse/SOLR-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ed Summers updated SOLR-111:
Attachment: response_connection_changes.diff
new repsonse classes and connection enhancements
[
https://issues.apache.org/jira/browse/SOLR-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ed Summers updated SOLR-111:
Attachment: response_connection_changes.diff
new repsonse classes and connection enhancements
On 1/16/07, Chris Hostetter [EMAIL PROTECTED] wrote:
: Date: Sat, 13 Jan 2007 19:12:27 -0800 (PST)
: Subject: [jira] Commented: (SOLR-104) SQL Upload Plugin
: 2) download HandlerRefactoring.DRAFT.zip and extract the contents to:
: \solr\src\java\org\apache\solr\handler
:
: (svn patches
(...) http://andaluciajunta.es/aj-sea-.html This
search engine will be based on nutch in the next version. The special
character is that this main portal search engine has to search against
the solr BOJA based indexed. Meaning Nutch will have to search the solr
index and not vice versa.
Looks
On 1/16/07, J.J. Larrea [EMAIL PROTECTED] wrote:
- Revise the XML-based update code (broken out of SolrCore into a
RequestHandler) to use all the above.
+++1, that's been needed forever.
If one has the time, I'd also advocate moving to StAX (via woodstox
for Java5, but it's built into Java6).
[
https://issues.apache.org/jira/browse/SOLR-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher resolved SOLR-111.
---
Resolution: Fixed
Assignee: Erik Hatcher
Applied, except tweaked autocommit to off by default.
On Tue, 2007-01-16 at 15:49 -0500, Yonik Seeley wrote:
On 1/16/07, J.J. Larrea [EMAIL PROTECTED] wrote:
- Revise the XML-based update code (broken out of SolrCore into a
RequestHandler) to use all the above.
+++1, that's been needed forever.
If one has the time, I'd also advocate moving
[
https://issues.apache.org/jira/browse/SOLR-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465327
]
Thorsten Scherler commented on SOLR-86:
---
Yeah, I know what you mean (had a similar problem today).
if
On 1/16/07, Thorsten Scherler [EMAIL PROTECTED] wrote:
I am on 1.5 ATM and using
|-- stax-1.2.0-dev.jar
`-- stax-utils.jar
I don't know where those jars are from, but I guess one would need the
stax API jar, and the implementation (woodstox I would think) jar.
That's two jars instead of one,
[
https://issues.apache.org/jira/browse/SOLR-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-107:
---
Attachment: IterableNamedList.patch
Iterable NamedList with java5 generics
[
https://issues.apache.org/jira/browse/SOLR-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465357
]
Ryan McKinley commented on SOLR-107:
updated patch for 1,2, and 3
Iterable NamedList with java5 generics
On 1/16/07 8:03 PM, Yonik Seeley [EMAIL PROTECTED] wrote:
I think it's a bit soon to move to 1.6 - I don't know how many
platforms it's available for yet.
It is still in early release from IBM for their PowerPC
servers, so requiring 1.6 would be a serious problem for us.
wunder
--
Walter
On 1/17/07, Thorsten Scherler [EMAIL PROTECTED] wrote:
...Should I use 1.6 for a patch or above mentioned libs?...
IMHO moving to 1.6 is way too soon, and if it's only to save two jars
it's not worth it.
-Bertrand
: The number of people writing update plugins will be small compared to
: the number of users using the external HTTP API (the URL + query
: parameters, and the relationship URL-wise between different update
: formats). My main concern is making *that* as nice and utilitarian as
: possible, and
kind of like a binary stream equivilent to the way analyzers
can be customized -- is thta kind of what you had in mind?
exactly.
interface SolrDocumentParser {
public init(NamedList args);
Document parse(SolrParams p, ContentStream content);
}
yes
37 matches
Mail list logo
