there is some work in progress on this, but it isn't ready for prime time
yet ... you are welcome to be an early adopter and try out some of
the patches...
https://issues.apache.org/jira/browse/SOLR-139
-Hoss
Hi, everyone!
As we known, solr uses lucene scoring.
This score is the raw score. Scores returned from Hits aren't
necessarily the raw score, however. If the top-scoring document scores
greater than 1.0, all scores are normalized from that score, such that
all scores from Hits are uaranteed to be
I am a new Solr user and wonder if anyone can help me these questions. I used
Solr to index about two million documents and query on it using standard
request handler. I disabled all cache. I found phrase query was substantially
slower than the usual query. The statistic I collected is as
Hi Hoss,
I am sorry about that. I know it was not very polite to do so. I was new to the
community and new to mailing list. I was experimenting how to start a
discussion.
I tried starting the discussion by sending a new email to [EMAIL PROTECTED] and
[EMAIL PROTECTED] But it doesn't seem to
I am a new Solr user and wonder if anyone can help me these questions. I used
Solr to index about two million documents and query on it using standard
request handler. I disabled all cache. I found phrase query was substantially
slower than the usual query. The statistic I collected is as
is it / will it be possible to add priorly non-existing fields to a document
with the upcoming solr-139?
for instance, would something like this work?
add mode=scorex=OVERWRITE
doc
field name=id* type=1318127/field
field name=scorex12/field
/doc
/add
with schema.xml:
...
fields
field
Hiya,
I have set up solr CollectionDistribution between a master and a slave with
postCommit triggering snapshooter, and a cron job (snappuller and
snapinstaller) on the slave accepting and installing updated snapshops every
15 minutes.
Once I delete a record from the master (with java code
Yes, you can add new fields to existing documents with SOLR-139.
As for SOLR-139 status - it's a bit stalled as far as I know. It
would be a wonderful addition to Solr, and hopefully available in
Solr 1.3, but the approach taken in the existing patches is something
I believe will be
Thank Erik,
That fixed the problem.
Cheers!
harry
-Original Message-
From: Erik Hatcher [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 25, 2007 4:41 PM
To: solr-user@lucene.apache.org
Subject: Re: Performance Recommendation
On Oct 25, 2007, at 4:19 PM, Wagner,Harry wrote:
Where is
Solr returns the raw score, not the Lucene Hits normalized one.
It's trivial for the client to normalize if desired - take the top
scoring document, if it's greater than 1.0 then scale all scores
based on that.
Erik
On Oct 26, 2007, at 2:53 AM, zx zhang wrote:
Hi, everyone!
As
Hi All.
We're seeing a really interesting problem when searching by
date range.
We have two fields of type date in our index (they are both
indexed and stored). They are:
content_date
and
created_date
We can run any date-range query we want against content_date
and we get expected results.
Hi David,
I'd start by:
- having a look a the index with Luke (or via some code that just dumps the
content of that created_date field), so I can be 100% sure that the right stuff
is in it to begin with
- 0 results makes me think that index-time and search-time tokenization might
be
Hi Karen,
snappuller and snapinstaller can be run by hand. I'd try that and I'd check
the logs to see what went wrong. Also look at the index directory on the
slaves and make sure that the files there match what you see on the master.
Otis
--
Sematext -- http://sematext.com/ -- Lucene -
Does anyone know of a way to have an index analyzer factory affect the
contents of the actual data (versus the contents of the index)?
Another example would be noting a pattern within a field and then
setting a flag field to a particular value, but wanting that value
to be returned as data
On 10/26/07, Karen Loughran [EMAIL PROTECTED] wrote:
But after distribution of this latest snapshop to the slave the collection
does not show the update (with solr admin query url or via java query client)
UNLESS I restart tomcat ?
Sounds like a config issue with the scripts... pulling the
: It's trivial for the client to normalize if desired - take the top scoring
: document, if it's greater than 1.0 then scale all scores based on that.
this is why doclists include the maxScore in their output as well, to
make it easy to normalize scores even if you are using pagination (or
If you went with the FunctionQuery approach for sorting by distance, would
there be any way to use the output of the FunctionQuery to limit the
documents to those within a certain radius? Or is it just for boosting
documents, not for filtering?
Also, even if you're just using it for boosting,
17 matches
Mail list logo
