Hi everyone,
i have the following problem... i use UTF-8 and my solr is deployed with
the aid of jetty
So far i have no problem with UTF-8 in the sense than i can store
anything and then it is displayed properly the problem is when i want to
retrieve according to a text field which is not encod
Hi,
I wanted to download a newer nightly (because the one I have is.. old.. and I
want to play with faceted search), but each time I try to reach
http://people.apache.org/dist/lucene/solr/nightly/ i get a time-out
Is there a mirror somewhere, or just an ETA for when that server is up and
avail
Hi chaps,
I currently have a lucene app. which is a daemon listening on a port for
XML requests and servicing these. I'm intending to switch to using Solr in
the near(ish) future, but have a question.
In my daemon, for servicing incoming search requests I manage index
Searchers in a cache via the
On Oct 20, 2006, at 2:34 PM, Walter Underwood wrote:
We have a well-developed browsing design, so I'd rather not mix
facets in with that. Two other things work against using facets:
most of our queries are known-item searches, and I think that
facets work best when there is very broad agreement
How can I get a count like I do by using searcher.numDocs(query, docset) but
with it doing an OR operation? I want the number of documents that match a
OR b?
Thanks,
Mike
: want to play with faceted search), but each time I try to reach
: http://people.apache.org/dist/lucene/solr/nightly/ i get a time-out
: Is there a mirror somewhere, or just an ETA for when that server is up and
: available again?
there was some pretty major infrastructure work being done over
There was a big infrastructure move at Apache this weekend. See
http://monitoring.apache.org/status/. Lots of red right now. Table at
the bottom of the page indicates things are supposed to be back up
sometime today.
-Original Message-
From: Morten Fangel [mailto:[EMAIL PROTECTED]
Sent: M
On 10/23/06, Panayiotis Papadopoulos <[EMAIL PROTECTED]> wrote:
Hi everyone,
i have the following problem... i use UTF-8 and my solr is deployed with
the aid of jetty
So far i have no problem with UTF-8 in the sense than i can store
anything and then it is displayed properly the problem is when i
It should hopefully be up by the end of today.
From www.apache.org:
Scheduled Downtime
The Apache Software Foundation will be doing some infrastructure work
that will cause some public services to be innaccessible from
Saturday, October 21st through Monday, October 23rd.
-Yonik
On 10/23/06,
On 10/23/06, Mike Austin <[EMAIL PROTECTED]> wrote:
How can I get a count like I do by using searcher.numDocs(query, docset) but
with it doing an OR operation? I want the number of documents that match a
OR b?
It's not clear to me what you are trying to calculate.
In code, If you just want the
Hi chaps,
I currently have a lucene app. which is a daemon listening on a port for
XML requests and servicing these. I'm intending to switch to using Solr in
the near(ish) future, but have a question.
In my daemon, for servicing incoming search requests I manage index
Searchers in a cache via the
This explains some of it:
http://wiki.apache.org/solr/SolrCaching
So, there is normally only a single searcher handing around.
When a new searcher is opened, it is opened and warmed in the
"background" so there are two searchers for the duration of warming.
A new searcher is only opened on an ex
I want to know... If I have a maindocset with many filters already, how many
more documents would I get if I added one more OR query to the maindocset.
I've been using numDocs to get the count if I wanted to narrow my maindocset
down because numDocs says that it must be in the maindocset AND in t
Yonik Seeley wrote:
> This explains some of it:
> http://wiki.apache.org/solr/SolrCaching
>
> So, there is normally only a single searcher handing around.
> When a new searcher is opened, it is opened and warmed in the
> "background" so there are two searchers for the duration of warming.
>
> A n
On 10/23/06, Paul Waite <[EMAIL PROTECTED]> wrote:
However if I understand the above properly, we should implement a strategy
which at least limits the commit frequency, to prevent the scenario you
describe in the last para above.
Right. If a new news item comes in, you could do a commit immed
Yonik Seeley wrote:
> On 10/23/06, Paul Waite <[EMAIL PROTECTED]> wrote:
> > However if I understand the above properly, we should implement a
strategy
> > which at least limits the commit frequency, to prevent the scenario you
> > describe in the last para above.
>
> Right. If a new news item c
: Is fq documented anywhere??? It's very useful for speeding up complex
i just added it to CommonQueryParameters
-Hoss
: We'll start with "OR", because I think an all-terms default is a really
: bad idea. If someone is searches for "X-Men 3: The Final Battle", we
: need to show them "X-Men 3: The Last Stand".
BooleanQuery.setMinimumNumberShouldMatch can help reduce the cruft with
this approach .. the dismax handl
If I've missed this in the documentation just point me in the right
direction, otherwise ...
I'm interested in ways of tweaking result sets based on criteria
external to the search itself. For example:
user searches for "foo AND bar" in a general "text" search
search returns 100 records
Yonik Seeley wrote:
> On 10/23/06, Paul Waite <[EMAIL PROTECTED]> wrote:
> > However if I understand the above properly, we should implement a
> > strategy which at least limits the commit frequency, to prevent the
> > scenario you describe in the last para above.
> Right. If a new news item c
On 10/23/06, Walter Lewis <[EMAIL PROTECTED]> wrote:
If I've missed this in the documentation just point me in the right
direction, otherwise ...
Tweaking relevance is a lucene question. Solr adds almost nothing to
this--the various documents pertaining to lucene are most relevant.
Note that
On 10/23/06, Paul Waite <[EMAIL PROTECTED]> wrote:
http://wiki.apache.org/solr/SolrConfigXml
In the UpdateHandler section I see:
1
3600
0
So the hard part is already done - the parameters are named! ;-)
Heh. I forgot that stuff was there. F
22 matches
Mail list logo