terrible.
you have made a big mistake, since you in fact made the primary key
unsearchable.
There is no any other method, since deleteDocument, updateDocument both
need Term to be searchable.
The only way is during the traversal of all the docs and finding the
matched field and delete it.
On Fri,
I indexed my document using Field.Index.NO as the field index type, so
now I cannot search it to make updates.
Here's how the document was added:
Document doc = new Document();
doc.add(new Field("content_id", "1234", Field.Store.YES,
Field.Index.NO, Field.TermVector.NO));
The content_id is the p
And how long does it take just to read and parse the files, without
indexing them? Often that is the problem - nothing to do with lucene.
There is plenty of good advice in
http://wiki.apache.org/lucene-java/ImproveIndexingSpeed. A good match
on the subject of your message!
--
Ian.
On Thu, Nov
can you provide more information about your setup? things like how
much time does it take to index you documents, how many docs do you
index, what are your index writer settings, how many cores do you
have, where do you read from and write to (disks). oh and what version
of lucene are you using?
t
Hi all,
I have a large number of files in a directory need to be index them. All
the files are in specific format need to parse to extract information after
that i had to index.
Single thread process one file at a time then i decided to use multi
threads when the main thread that loops the directo
You can provide your own Similarity implementation, overriding
whichever of the methods you need in order to achieve your aims. Use
it via the setxxx methods mentioned in the javadocs and unless you
deliberately sort by some other field everything should fall into
place.
--
Ian.
2011/11/9 强继朋
Hi all,
In our project we like to have the ability to get search results scoped
to one 'namespace' (as we call it). This can easily be achieved by using
a filter or just an additional must-clause.
For the spellchecker (and our autocompletion, which is a modified
spellchecker), the story seems
Hi,
I am using 2.9.2 version of lucene.
For my project I need to find the term positions in the document for it to be
highlighted in the display.
For normal queries it works fine. But with wild card queries, there is no
offset info available.
This is my code:
QueryParser qp = new Que
