thks but It doesn't work, I tried this
Hits encontrados=searcher.search(buscar,new Sort("DATE"));
and all my documents have a Field.Keyword called DATE.
If i do the search without sort parameter it returns me a lot of
results, but if i do the search with sort parameter it doesn't return
any
Excuse me I don't write the trace of error
java.lang.RuntimeException: no terms in field DATE - cannot determine
sort type
at
org.apache.lucene.search.FieldCacheImpl.getAuto(FieldCacheImpl.java:319)
at
org.apache.lucene.search.FieldSortedHitQueue.comparatorAuto(FieldSortedHitQueue
Solved, only replace
new Sort(new SortField("DATE",SortField.INT, true)));
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Thu, 2005-10-13 at 11:58 +0200, Daniel Cortes wrote:
> Solved, only replace
> new Sort(new SortField("DATE",SortField.INT, true)));
Alternatively you could use the DateField class:
http://lucene.apache.org/java/docs/api/org/apache/lucene/document/DateField.html
to translate your date's into L
Hi,
I don't understand why my third test fails. If I scape my "- delimiter"
what I expect is a character behaviour.
Could you clarify me what I'm doing wrong?
public void testStandardAnalyzer() throws Exception {
Analyzer a = new StandardAnalyzer();
assertAnalyzesTo(a, "ses1-one3", new
StandardAnalyzer does not have any escaped-character handling
capability. So the backslash and dash are treated without any
special care in "session\-one".
You will need to build your own Analyzer with a custom tokenizer to
handle this type of escaping.
Erik
On Oct 13, 2005, at 8:29
The system I'm working on requires that I also need to use a custom hit
collector. I'm not using the RemoteSearchable. Instead, I'm just binding
an object called SearcherImpl that contains an IndexSearcher and a
getResults() method that uses the custom hit collector.
Peter
> -Original Messag
Hi Yonik,
Your patch has corrected the thread thrashing problem on multi-cpu systems.
I've tested it with both 1.4.3 and 1.9. I haven't seen 100X performance
gain, but that's because I'm caching QueryFilters and Lucene is caching the
sort fields.
Thanks for the fast response!
btw, I had previous
The API for BooleanQuery only seems to allow adding clauses. The
nearest way I can see to *remove* a clause is by laboriously
constructing a new BooleanQuery (assuming you aren't absolutely tied
to the original instance) and adding all the clauses from the
original query except the one you
Oops, I'm confusing libraries. I meant I want to remove a Nutch
Clause from a Nutch Query.
--Andy
On Oct 13, 2005, at 4:45 PM, Andy Lee wrote:
The API for BooleanQuery only seems to allow adding clauses. The
nearest way I can see to *remove* a clause is by laboriously
constructing a new
10 matches
Mail list logo
