Hi,
I would like to customize the lucene scoring to remove the effect of the
"coord()" parameter in Similarity for the number of fields in which the
whole query is found.
First, here's what I'm trying to achieve:
For example, if I have the query "New York" and that the documents have 2
fields: n
Kastern, thanks for the reply.
> IndexReader is thread-save so you don't need a cache.
If it wasn't thread-safe I may need a cache? I think the cache cannot be
used on a non-thread-safe environment since it exposes same instances to
different threads.
> Opening and closing an IndexReader takes
The scaling per machine should be linear. The overhead from the network is
minimal because the Lucene object sizes are not impacting. Google mentions
in one of their early white papers on scaling
http://labs.google.com/papers/googlecluster-ieee.pdf that they have sub
indexes which are now popular
Hi,
for performance reasons I cache Hits for a certain Query in memcached,
for things like pageination etc. My question right now is if it is
possible to re-search such a cached Hits sets. That would be great for
features like live-learch and so on. Does Lucene support that?
Sascha
-
hi Mohsen,
IndexReader is thread-save so you don't need a cache.
Opening and closing an IndexReader takes some time. But I don't now if this is
measurable.
So if you know that you don't want to change a index, let the IndexReader open.
(somebody disagree with me?)
If you want to use your main m
Note that ISOLatin1AccentFilter converts accent characters only from
ISO-8859-1 character set. Which means that if you need to convert
accents of eastern European languages you need to write your own
accent filter.
wojtek
2008/7/16 Petite Abeille <[EMAIL PROTECTED]>:
>
> On Jul 16, 2008, at 10:58
