lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Male (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-4099) Remove generics from SpatialStrategy and remove SpatialFieldInfo
Date Fri, 01 Jun 2012 13:59:23 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13287413#comment-13287413
] 

Chris Male commented on LUCENE-4099:
------------------------------------

That can definitely happen.  I guess instead of being instantiated per request, I mean they
will be instantiated per configuration.  
                
> Remove generics from SpatialStrategy and remove SpatialFieldInfo
> ----------------------------------------------------------------
>
>                 Key: LUCENE-4099
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4099
>             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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message