With local indices, it is enough to reopen the IndexSearcher by calling
close() and then renew the IndexSearcher object. How about RemoteSearchers?
Is it necessary to re-initialize remote search server?
--jaf
On 7/12/07, Erick Erickson [EMAIL PROTECTED] wrote:
In general, searchers cannot
Hi folks,
- I am wondering whether there is any mechanism to specify the sorting
direction (i.e. ascending/descending) without being obliged to make a custom
Sorter. I add a timeOfIndexing field in order that I can retrive results
based ob recentness later. But the sorter sorts in an ascending
How about this idea:
- a special Identifier field.
- A DocumentHash class which calculates a hash value from a Document.
- A query on Identifier before inserting new Documents to check if it
already exists.
--jaf
On 5/10/07, STEFANOS STEFANOS [EMAIL PROTECTED] wrote:
Hello,
I would
Hi Chris,
Can you explain how? I know the source is available but perhaps a short
summary would be very useful for the list readers.
--jaf
On 4/24/07, Chris Lu [EMAIL PROTECTED] wrote:
Hi, Saurabh,
It's just one query and returns both hits and
categorized counts.
Chris
--- Saurabh Dani
examined.
I've just got to ask... Why do you (jafarim) want to fiddle with the
threshold? How is this going to benefit the user over and above
just getting the first N 100 docs from a Hits object? They're
sorted already in relevancy order. Yonik's point that scores aren't
comparable across
Hi list.
I am trying to implement some TopScoreHitCollector class; a kind of
TopDocCollector which collects the documents the score of which is higher
than a threshold. The threshold will be configurable in the constructor of
the class. There is seemingly a document starvation about
Be aware that
score thresholds don't work well in general since scores aren't really
comparable from one query to another.
What is I normalize the scores in such a manner that they become between 0
and 1?
--jaf
hi list,
I am using a ParallelMultiSearcher in order to search a number of indices.
As the rate of input to the index is very high I have to check
indexSearcher.isCurrent quite often and have to reopen the index. There are
however to issues:
- In order to have a current version of a searcher, do
Hi
I wonder why there is not setter method for the lazy member variable in
Field class. Does that mean the propoerty is nominal and setting it does not
have any effect, or am I missing some point?
Any way, is there any way to tell lucene that a field is to be lazy-loaded,
from the very beginning
So, what's the usage of this propoerty in the Field class?
On 4/4/07, Yonik Seeley [EMAIL PROTECTED] wrote:
On 4/4/07, jafarim [EMAIL PROTECTED] wrote:
Any way, is there any way to tell lucene that a field is to be
lazy-loaded,
from the very beginning of field construction?
No, that data
Hi folks,
I need to extract a subset of an index so that I can move some documents to
another isolated machine to be searched locally. I'm not sure whether the
following scenario is correct:
- extracting the documents from the index by using one of the doc(i) methods
- adding the same Document
Good to know that your devised commercial feature is already offered by
Enhydra Snapper as an open-source feature.
Check here: http://www.enhydra.org/apps/snapper/index.html
On 3/26/07, Ryan Ackley [EMAIL PROTECTED] wrote:
Yes I do have plans for adding fast save support and support for more
what do you mean by applying the result to the second one?
On 3/26/07, Mohammad Norouzi [EMAIL PROTECTED] wrote:
hi
I have two separated index but there are some fields that are common
between
them. now I want to search from one index and then apply the result to the
second one. what solution
Can anyone make a comparison between the two, namely POI API and the one
from textmining.org?
On 3/24/07, Ryan Ackley [EMAIL PROTECTED] wrote:
The site is down but you can download the word extractor library direct
here:
http://www.textmining.org/textmining.zip
Going to fix the site this
in IndexSearcher
does not contain such facilities (seemingly). Hence, the Documents I get
from the Hits.doc() would not benefit from the mentioned feature.
Am I missing an important point or this is a desired feature to go on the
todo list?
--Jafarim
Hi
My experience is not much satisfactory. It breaks very easily on many files.
On 3/23/07, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Hello,
I am planning to index Word 2003 files. I read I have to use Jakarta
Apache POI, but I also read on the POI site that their work with doc's is in
an
: does not contain such facilities (seemingly). Hence, the Documents I get
: from the Hits.doc() would not benefit from the mentioned feature.
: Am I missing an important point or this is a desired feature to go on
the
: todo list?
: --Jafarim
-Hoss
in IndexSearcher
does not contain such facilities. Hence, the Documents I get from the
Hits.doc() would not benefit from the mentioned feature.
Am I missing an important point or this is a desired feature to go on the
todo list?
--Jafarim
Hello
It's a whil that I am using lucene and as most of people seemingly do, I
used to save only some important fields of a docuemnt in the index. But
recently I thought why not store the whole document bytes as an untokenized
field in the index in order to ease the retrieval process? For example
19 matches
Mail list logo
