As a follow-on to this, the problem appears to have been PBKAC (problem between keyboard and chair).
Sorting works fine as long as all indexes being referenced contain the field being sorted. When executing a remote search, the container application (that's me) needs to be sure to bubble up the exceptions appropriately. -- j On 10/5/05, Rasik Pandey <[EMAIL PROTECTED]> wrote: > > Hi Jeff, > > Sorting needs access to an IndexReader so it can do Term lookups, and > I don't think there is a remote impl of IndexReader probably because, > among other reasons, not all objects related to Terms are > Serializable. IMHO, it would be NICE to have a RemoteReader and a > ParallelMultiReader to round out the API like: > > ParallelMultiReader, RemoteReader, MultiReader, Reader > > AND > > ParallelMultiSearcher,RemoteSearcher, MultiSearcher, Searcher > > Regards, > Rus > > > > > On 10/5/05, Jeff Rodenburg <[EMAIL PROTECTED]> wrote: > > Are there known limitations or issues with sorting and RemoteSearchable? > I'm > > encountering problems attempting to sort through a MultiSearcher > > (ParallelMultiSearcher, actually). I'm using an array of > RemoteSearchable > > objects as the Searchable[] source. If I change the source indexes to be > > local IndexSearchers, sorting works just fine. > > > > I've searched the threads of this mailing list as well as the > outstanding > > issues on the Apache issue tracker, but haven't found anything related > to > > this problem. > > > > Thanks, > > j > > > > >
