lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <>
Subject [jira] Commented: (LUCENE-548) Sort bug using ParallelMultiSearcher
Date Thu, 20 Apr 2006 14:46:06 GMT
    [ ] 

Yonik Seeley commented on LUCENE-548:

It looks like problems could also happen with a MultiSearcher too.
In general, don't use sort type AUTO... always explicitly specify how to sort.  Different
searchers may come back with different sort types, and then there isn't a good way to merge
the results.

This could probably be fixed in the straight MultiSearcher case by getting the sort type from
the first searcher that returns results, and using that for all the other searchers.  Not
sure if it's worth the fix though...

> Sort bug using ParallelMultiSearcher
> ------------------------------------
>          Key: LUCENE-548
>          URL:
>      Project: Lucene - Java
>         Type: Bug

>   Components: Search
>     Versions: 1.9
>  Environment: Linux FC2 Java 1.4.9
>     Reporter: dan
>     Priority: Minor

> >>>>> Output:
> java.lang.ClassCastException: java.lang.String
>         at
>         at org.apache.lucene.util.PriorityQueue.insert(
>         at
> >>>>> Input:
> - This only occurs when searching more than one index using ParallelMultiSearcher
> - I use the signature new Sort( "date", true)
> - The values in dates are strings in the form 20060419
> - The call to getType in FieldDocSortedHitQueue misinterprets the value as an INT, then
the exception is thrown
> >>>>> Available workaround
> - I use the the signature new Sort(new SortField( "date", SortField.STRING, true)) and
the problem goes away.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message