lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ishan Chattopadhyaya (JIRA)" <>
Subject [jira] [Updated] (SOLR-4242) A better spatial query parser
Date Tue, 24 Feb 2015 10:41:05 GMT


Ishan Chattopadhyaya updated SOLR-4242:
    Attachment: SOLR-4242.patch

Updated the patch with some more refactorings, as per David's suggestions. Updated the review
request as well.

> A better spatial query parser
> -----------------------------
>                 Key: SOLR-4242
>                 URL:
>             Project: Solr
>          Issue Type: New Feature
>          Components: spatial
>            Reporter: David Smiley
>             Fix For: 4.9, Trunk
>         Attachments: SOLR-4242.patch, SOLR-4242.patch, SOLR-4242.patch
> I've been thinking about how spatial support is exposed to Solr users. 
> Presently there's the older Solr 3 stuff, most prominently seen via \{!geofilt} and \{!bbox}
done by [~gsingers] (I think). and then there's the Solr 4 fields using a special syntax parsed
by Lucene 4 spatial that looks like mygeofield:"Intersects(Circle(1 2 d=3))" What's inside
the outer parenthesis is parsed by Spatial4j as a shape, and it has a special (non-standard)
syntax for points, rects, and circles, and then there's WKT.  I believe this scheme was devised
by [~ryantxu].
> I'd like to devise something that is both comprehensive and is aligned with standards
to the extent that it's prudent.  The old Solr 3 stuff is not comprehensive and not standardized.
 The newer stuff is comprehensive but only a little based on standards. And I think it'd be
nicer to implement it as a Solr query parser.  I'll say more in the comments.

This message was sent by Atlassian JIRA

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

View raw message