[
https://issues.apache.org/jira/browse/LUCENE-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095303#comment-13095303
]
Chris Male commented on LUCENE-2599:
------------------------------------
I'd like to come to an agreement here and finish this off as to make a clear
statement about spatial in Lucene 4.
It seems we have a few options in front of us now:
- Deprecate in 3x, nuke fully in trunk
- Deprecate in 3x and in trunk, moving the code to the sandbox
- Deprecate in 3x and in trunk and leave the code where it is
- Do nothing
Robert's concern that removing the contrib entirely without providing an
alternative seems very reasonable. But as I said in February, I'm very wary of
continuing to release code which has so many problems. As such, I favour
deprecating in 3x and in trunk and sandboxing the code wit big warnings that
it'll go when we have a better solution.
Any opinions? Robert? David?
> Deprecate Spatial Contrib
> -------------------------
>
> Key: LUCENE-2599
> URL: https://issues.apache.org/jira/browse/LUCENE-2599
> Project: Lucene - Java
> Issue Type: Improvement
> Components: modules/spatial
> Affects Versions: 4.0
> Reporter: Chris Male
> Attachments: LUCENE-2599.patch, LUCENE-2599.patch
>
>
> The spatial contrib is blighted by bugs. The latest series, found by Grant
> and discussed
> [here|http://search.lucidimagination.com/search/document/c32e81783642df47/spatial_rethinking_cartesian_tiers_implementation]
> shows that we need to re-think the cartesian tier implementation.
> Given the need to create a spatial module containing code taken from both
> lucene and Solr, it makes sense to deprecate the spatial contrib, and start
> from scratch in the new module.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
