lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Smiley (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4099) Remove generics from SpatialStrategy and remove SpatialFieldInfo
Date Fri, 01 Jun 2012 13:55:23 GMT


David Smiley commented on LUCENE-4099:

Although the SpatialStrategies have become fairly lightweight; I'd like to see if there is
a path forward that retains re-using SpatialStrategies across requests, sans the API awkwardness
of SpatialFieldInfo as it is is implemented today.  Perhaps a SpatialStrategy can be created
per field (although it may technically use more than one field) and then there's no need for
SpatialFieldInfo or anything like it.
> Remove generics from SpatialStrategy and remove SpatialFieldInfo
> ----------------------------------------------------------------
>                 Key: LUCENE-4099
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: modules/spatial
>            Reporter: Chris Male
>            Priority: Minor
> Same time ago I added SpatialFieldInfo as a way for SpatialStrategys to declare what
information they needed per request.  This meant that a Strategy could be used across multiple
requests.  However it doesn't really need to be that way any more, Strategies are light to
instantiate and the generics are just clumsy and annoying.
> Instead Strategies should just define what they need in their constructor. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


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

View raw message