With the '+' prefix you are saying that both clauses must be true, so
looking for stopwords will return false since it won't find any match.
Regards,
Daniel
-javier muguruza <[EMAIL PROTECTED]> escribió: -
Para: Lucene Users List
De: javier muguruza <[EMAIL PROTECTED]>
Fecha: 15/1
I would start reading 'I love Lucene' article on The Server Side.
Regards,
Daniel Blanch
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I think you are doing it right. Fields used for sorting must be Keyword
type. See you are not adding the Field more than once for the same
Document.
-"Taylor, BE \(Beverley\)" <[EMAIL PROTECTED]> escribió: -
Para:
De: "Taylor, BE \(Beverley\)" <[EMAIL PROTECTED]>
Fecha: 23/11/2005
I'm not sure I've understand you.
If you want to point to tiles definitions you have to define tem in
s or a s element in struts-config.xml, as usual.
If you want your app to dinamicaly create tiles definitions you'll have to
write a Tiles Controller.
See http://www.lifl.fr/~dumoulin/tiles/
I have a similar problem, I have boosted documents in an index, when I run
a query it shows boosted documents first, but when I loop the Documents
through the Hits class, this is:
Document doc = hits.doc(i);
System.out.println("Query scoring: "
+ formatter.format(hits.score(i))); //never h
Providing that I have indexed documents with the following fields:
Keyword: lastmodifiedDate
Unstored: contents
And that I run a simple query only using just the contents field.
Is there anyway to change the way Lucene presents results, so documents
with a high score and lastmodifiedDa
