25 nov 2006 kl. 17.26 skrev Robert Koberg:
What I do is add a 'path' field with the xpath to the node. Then
you first narrow your search by finding documents with paths like:
/node[1]/node[3]*
You use a wildcard query? That can turn out to be very expensive if
you have a thousand and
I tested this. I use a single static analyzer for all my documents,
and the caching analyzer was not working properly. I had to add a
method to clear the cache each time a new document was to be indexed,
and then it worked as expected. I have never looked into lucenes inner
working so I am not
Nope, not seen that one.
Looks like the reference to no such field is in the Java instance data
sense, not the Lucene document sense.
Class versioning issues somewhere?
That method takes a parameter called prohibited which is the name of
the field reported in the error. Is the word prohibited
I have already set some score at the index time. And now i want to set
some score at the query time. But i am not getting any idea of how to set
the score at query time in lucene.
Has anybody an idea how to do this?
Regards
Sajid
--
View this message in context:
Hi sajid,
As you already boost data at indexing time...
You can boost query at search time...
eg. If you are firing boolean query and phrasequery...you might need to
boost phrasequery
PhraseQuery pq = new PhraseQuery();
pq.setBoost(2.0f);
Thanks.
Bhavin pandya
- Original Message
Erick Erickson wrote:
And how are you storing your date? Field.Store.YES? NO? COMPRESSED?
I think, here is my problem...I have found this in the FileDocument.java:
doc.add(new Field(contents, new FileReader(f)));
Field.Store.YES is missing, but when I try to put this argument, i become
Hi,
I need some inputs on the database searching using lucene.
Lucene directly supports the document searching but I am unable to find
out the easy and the fastest way for database searching.
Which option would be better - SPs or Lucene search engine in terms of
implementation, performance
