-
+ ${solr.data.dir:./solr/data}
+
I just ran into something weird with this...
If you set the solr home with JNDI or solr.solr.home, the dataDir still
defaults to "./solr/data" -- not the data directory relative to solr
home. This requires you to *also* set: "solr.data.dir" if you wa
[
https://issues.apache.org/jira/browse/SOLR-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharad Agarwal updated SOLR-256:
Attachment: jmx.patch
-Corrected line wrap to 80 columns
-Used the original LinkedHashMap (when jmx m
Yep, been there done that. Thanks for the reminder.
On 6/11/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
: I'd like to see the solrsharp client library added under source control
for
: solr (http://svn.apache.org/viewvc/lucene/solr/trunk/client/
). Additionally
: I'd like to get read/write
Thanks Ryan - if you have room on your server, that would be great. It
would be nice to have a place to update the codebase (there are a few
changes to the library with the 1.2 release), and having a repository to
upload those would be handy.
thanks,
jeff
On 6/10/07, Ryan McKinley <[EMAIL PROTE
I hate to be a pest... but if anyone gets a change to look at either
of these, that would be great.
The changes are significant enough that I'd like something more then
silence before moving forward...
On 6/7/07, Ryan McKinley <[EMAIL PROTECTED]> wrote:
Has anyone had a chance to look at:
S
[
https://issues.apache.org/jira/browse/SOLR-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-260:
---
Attachment: SOLR-260-PluginLoader.patch
This patch uses a single plugin loader for:
* RequestHandlers
*
[
https://issues.apache.org/jira/browse/SOLR-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503697
]
John Wang commented on SOLR-243:
Are you looking at the right patch?
For 1) at least, they are public.
2) I am using
: Yes, the current JIRA patch uses the FieldCache.
I just ment in contrast with Mike's comment about iterating over all the
stored fields to support the "post-faceting" situation (but frankly i'm
not sure that i undersatnd what the "post-faceting" situation is, so feel
free to ignore me)
: >...
[
https://issues.apache.org/jira/browse/SOLR-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503691
]
Hoss Man commented on SOLR-243:
---
comments on the latest patch..
1) SolrIndexSeacher constructor is still private
2) i b
On 6/11/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
: It seems that the only way to do it would be to collapse the entire
: result set first, which entails loading the stored fields of the
: whole docset.
:
: That doesn't seem particularly feasible to do exactly.
I haven't really been follow
[
https://issues.apache.org/jira/browse/SOLR-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503679
]
Ryan McKinley commented on SOLR-260:
>
> Ryan: FYI but there is currently no patch attached to this issue.
>
i'm
[
https://issues.apache.org/jira/browse/SOLR-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503678
]
Hoss Man commented on SOLR-260:
---
a few more thoughts...
1) instead of DEFAULT_PACAKGES that should really be "String[]
g
: It seems that the only way to do it would be to collapse the entire
: result set first, which entails loading the stored fields of the
: whole docset.
:
: That doesn't seem particularly feasible to do exactly.
I haven't really been following this conversation that closely, but
assuming what you
[
https://issues.apache.org/jira/browse/SOLR-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503673
]
Hoss Man commented on SOLR-260:
---
Ryan: FYI but there is currently no patch attached to this issue.
looking ta the way P
On 11-Jun-07, at 8:10 AM, Will Johnson wrote:
And one other point, one of the reasons why it's hard to find an
example
of post-faceting is that many of the major engines can't do it.
It seems that the only way to do it would be to collapse the entire
result set first, which entails loadin
[
https://issues.apache.org/jira/browse/SOLR-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-225:
---
Attachment: SOLR-225-HighlightingConfig.patch
implemented with the (soon to upload) SOLR-260 PluginLoad
reusable PluginLoader -- helper class to load plugins
-
Key: SOLR-260
URL: https://issues.apache.org/jira/browse/SOLR-260
Project: Solr
Issue Type: New Feature
Reporter: Ryan Mc
On 6/11/07, Yonik Seeley <[EMAIL PROTECTED]> wrote:
On 6/11/07, Ryan McKinley <[EMAIL PROTECTED]> wrote:
> while (not all components done) {
> for (component : List) {
> boolean done = component.process(req,rsp);
> }
> }
> - - - - -
> Yonik, what components do you imagine need to run mult
On 6/11/07, Ryan McKinley <[EMAIL PROTECTED]> wrote:
while (not all components done) {
for (component : List) {
boolean done = component.process(req,rsp);
}
}
- - - - -
Yonik, what components do you imagine need to run multiple times?
Not sure... a component that needs to run both befor
:
: One interesting/difficult part would be the standardization of the
: communication between components.
Communication can be coordinated with things like
SolrQueryRequest.getContext() ... it will have to be fairly loose
communication governed by convetion, but i don't see anyway to avoid tha
[
https://issues.apache.org/jira/browse/SOLR-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503570
]
Hoss Man commented on SOLR-259:
---
FWIW: I just did a quick "grep -C3 -r severeErrors" and verified there are no
other pla
[
https://issues.apache.org/jira/browse/SOLR-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley reassigned SOLR-259:
--
Assignee: Ryan McKinley
> More descriptive text on improperly set solr/home
> ---
[
https://issues.apache.org/jira/browse/SOLR-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-259.
Resolution: Fixed
added in rev 546223. Thanks Will!
> More descriptive text on improperly set solr/
Thanks. He was right.
I've noticed that the HTTPClient has no connection timeout
(http://jakarta.apache.org/commons/httpclient/preference-api.html#HTTP_connection_parameters)
setted, maybe there is a way to set it out-of-the-client (any
suggestion?), but it would help this connection timeout to be
: I'd like to see the solrsharp client library added under source control for
: solr (http://svn.apache.org/viewvc/lucene/solr/trunk/client/). Additionally
: I'd like to get read/write permissions to the library as well.
:
: How do I get this established?
Getting a patch committed just takes int
Sorry, I forgot to turn on my _wild_ideas_ flag before that last post.
That being said, you could build the notion of dependencies into each
stage and have the search logic omputed based on those dependencies,
alternatively you could do pre/post methods for each processing stage
that allow each st
the second hitch is that "docs" only makes sense in ssuedo code ... in
reality there are DocSets and DocLists, and the efficiencies of geting
only one instead of both can be significant, but if the first phase of
processing doesn't know what expectations the later phases have (facet or
not? retu
[
https://issues.apache.org/jira/browse/SOLR-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Will Johnson updated SOLR-259:
--
Attachment: betterSolrHomeError.patch
+import java.util.logging.Level
and a simple
log.log(Level.SEVERE
More descriptive text on improperly set solr/home
-
Key: SOLR-259
URL: https://issues.apache.org/jira/browse/SOLR-259
Project: Solr
Issue Type: Improvement
Affects Versions: 1.2
: for (component : List) {
: // a chance to communicate needs to other components?
: // highlighting needs a Query or terms, and a list of fields
: // faceting needs a base DocSet
: component.prepare(req, rsp);
: }
:
: while (not all components done) {
: for (component : List) {
: bo
: // choose one query method
: docs = Query( req, debug )
:- standard
:- dismax
:- mlt (as input)
there are two small hitches to an approach like this, the first is that
you'd like to reuse more of hte query processing then to just say "go pick
the list of docs basedo nthe reuqest
And one other point, one of the reasons why it's hard to find an example
of post-faceting is that many of the major engines can't do it.
- will
-Original Message-
From: Will Johnson [mailto:[EMAIL PROTECTED]
Sent: Monday, June 11, 2007 11:05 AM
To: solr-dev@lucene.apache.org
Subject: RE
>I assumed they would... I think our signals might be crossed w.r.t.
>the meaning of pre or post collapsing. Faceting "post collapsing" I
>took to mean that the base docset would be restricted to the top "n"
>of each category.
In my view, faceting should occur on the full collapsed result set. I
On 6/11/07, Will Johnson <[EMAIL PROTECTED]> wrote:
Having worked on a number of customer implementations regarding this
feature I can say that the number one requirement is for the facet
counts to be accurate post collapsing. It all comes down to the user
experience. For example, if I run a qu
Having worked on a number of customer implementations regarding this
feature I can say that the number one requirement is for the facet
counts to be accurate post collapsing. It all comes down to the user
experience. For example, if I run a query that get collapsed and has a
facet count for the n
Some thoughts:
One of the most powerful and useful concepts that many of the other
engines (well the good ones) use is the notion of processing pipelines.
For queries this means a series of stages that do things such as:
* faceting
* collapsing
* applying default values
* spell checking
* adding
[
https://issues.apache.org/jira/browse/SOLR-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Keller updated SOLR-236:
-
Description:
This patch include a new feature called "Field collapsing".
"Used in order to c
[
https://issues.apache.org/jira/browse/SOLR-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Keller updated SOLR-236:
-
Attachment: (was: SOLR-236-FieldCollapsing.patch)
> Field collapsing
>
>
>
[
https://issues.apache.org/jira/browse/SOLR-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Keller updated SOLR-236:
-
Attachment: SOLR-236-FieldCollapsing.patch
New release:
- Fieldcollapsing added on DisMaxRequestHan
39 matches
Mail list logo