You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Chris Male (JIRA)" <ji...@apache.org> on 2012/06/01 06:49:23 UTC
[jira] [Created] (LUCENE-4099) Remove generics from SpatialStrategy
and remove SpatialFieldInfo
Chris Male created LUCENE-4099:
----------------------------------
Summary: 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
[jira] [Commented] (LUCENE-4099) Remove generics from
SpatialStrategy and remove SpatialFieldInfo
Posted by "David Smiley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13287409#comment-13287409 ]
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: 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
[jira] [Commented] (LUCENE-4099) Remove generics from
SpatialStrategy and remove SpatialFieldInfo
Posted by "Chris Male (JIRA)" <ji...@apache.org>.
[ 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