The RAMDirectory uses Java memory, an FSDirectory does not. Holding
Java memory makes garbage collection work harder. The operating system
is very very good at managing disk buffers, and does a better job
using spare memory than Java does.
For real-world sites, RAMDirectory is almost always useles
On 6/17/11 12:29 AM, Itamar Syn-Hershko wrote:
No, that was not what I meant.
I'm not interested in coloring the actual text, but in giving the user
an indication of how relevant the results are. Instead of displaying the
result score, I want to give some visual meter to show that. The highest
No, that was not what I meant.
I'm not interested in coloring the actual text, but in giving the user
an indication of how relevant the results are. Instead of displaying the
result score, I want to give some visual meter to show that. The highest
ranking result will be green if the it is rea
See Highlighter's GradientFormatter
Cheers
Mark
On 16 Jun 2011, at 22:01, Itamar Syn-Hershko wrote:
> Hi all,
>
>
> Interesting question: is it possible to color search results in a web-page
> based on their score? e.g. most relevant results in green, and then different
> shades through ora
Hi all,
Interesting question: is it possible to color search results in a
web-page based on their score? e.g. most relevant results in green, and
then different shades through orange, yellow, red and then white.
Theoretically, one could take the highest score and color based on
proximity /
Great. Thanks!
You have to implement it yourself. Lucene 3.3 will provide some additions to
IndexSearcher to merge TopDocs results from different searchers, but
collecting those results and transferring over the network is your task. Or
simply use Solr (which is an implementation, to exactly do that). This new
AP
Thanks for answering.
If I understand it correctly, I can use IndexSearcher concurrently over many
IndexReaders. But since there's no RemoteIndexReader, I'm still left with
the same basic problem. How to I search across several servers?
Hi Tsadok,
In Lucene 3.1:
"MultiSearcher is deprecated; ParallelMultiSearcher has been absorbed directly
into IndexSearcher "
-Sithu
-Original Message-
From: Israel Tsadok [mailto:itsa...@gmail.com]
Sent: Thursday, June 16, 2011 1:35 AM
To: java-user@lucene.apache.org
Subject: RemoteS
On 6/15/11 7:14 PM, liat oren wrote:
Ok, thanks a lot
On 15 June 2011 11:36, Ian Lea wrote:
Don't think so. The boost info is encoded and stored at index time.
Boosts that you set are multiplied by lengthNorm and then stored as a
coarse-grained float in fieldNorm values. There is a utilit
Hi Elmer
Thanks for the reply.
I now tried giving a NumericRangeQuery.
Something like:
Query qq = NumericRangeQuery.newDoubleRange(field, frompercent, topercent,
true, true);
(As suggested in
http://lucene.apache.org/java/3_0_3/api/core/org/apache/lucene/search/NumericRangeQuery.html
)
However,
In your examples the queries are essentially the same, so getting the
same results is expected, and getting different scores is also
expected since you are boosting in the first and not the second, and
the second is using a filter which doesn't contribute to scoring.
You'll need to be careful of y
To summarize what was said before.
In general, using sharding on single machine does make sense only if using
single lucene instance you could not utilize all the hardware on this machine.
For it's own lucene does a good job in this area, so I think it's very rarely
situation where you really n
13 matches
Mail list logo
