: Thanks for the reply. And sorry for sounding impatient -
: I've been working in the weekend and I wasn't sure if I expressed
: my question well, hence why the second email :)
yeah .. my apologies as well, i realize now i didn't answer your question
very well at all ... i've been sick and it's
Hello Chris,
Thanks for the reply. And sorry for sounding impatient -
I've been working in the weekend and I wasn't sure if I expressed
my question well, hence why the second email :)
I understand I can url-encode the space. My question, which I failed
to mention in my first email, is that, what
first off, please have a little patience when sending mai lto the mailing
list ... 17 hours between "reposting" isn't relaly a lot ... especially on
a weekend, when many people are out of hte country for a confrence, and
i'm sick :)
On to your question...
: fq=+popularity:[10 TO *] +section:0
:
: when solr is processing the fields to figure out where to put the doc in the
: tree, it proccesses the indexable fields and removes the stops words. This
: stripped down set of keyword is passed to some other function which places
: it in the correct part of the search tree.
:
: I would like to h
Could anyone please explain a bit about the line below?
No spaces is allowed in a URL so I suppose this needs
to be quoted, but, what if there is space in the fq value field,
which will create ambiguity between fq field boundary and
term boundary?
fq=+popularity:[10 TO *] +section:0
> I'm not su
It may not be easy or even possible without major changes, but having
global collection statistics would allow scores to be compared across
searchers. To do this, the master indexes would need to be able to
communicate with each other.
An other approach to merging across searchers is describe
On 4/11/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
A custom Similaity class with simplified tf, idf, and queryNorm functions
might also help you get scores from the Explain method that are more
easily manageable since you'll have predictible query structures hard
coded into your application
Hello ,
I'm not sure if I understand how to specify multiple fq in
CommonQueryParameters, which is described in this page
http://wiki.apache.org/solr/CommonQueryParameters
It says:
--- cut -
fq=+popularity:[10 TO *] +section:0
is equivalent to
fq=popularity:[10 TO *]&fq=section:0
