Skip to content

JtsGeoStratey's filter should implement Bits instead of testing all documents #3

@dsmiley

Description

@dsmiley

I can tell JtsGeoStrategy's filter is so slow just by looking at it. It's testing all indexed documents and returning a bitset. Talk about brute-force! Instead, it should return a DocIdSet that returns a Bits that in turn will test the given document to see if it matches. If that isn't work, then a superior approach is one that returns a DocIdSetIterator that implements advance(). In this way, the expensive logic will only occur for documents that match other aspects of the query (e.g. keyword, other filter queries). In Solr, this would be used as a post-filter with a cost >= 100.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions