lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Smiley (Commented) (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3795) Replace spatial contrib module with LSP's spatial-lucene module
Date Fri, 02 Mar 2012 19:32:00 GMT


David Smiley commented on LUCENE-3795:

  Regarding byte / character performance stuff, I understand.  Last night in fact, I successfully
argued with Ryan that the SpatialPrefixTree (a trie) belongs with the Lucene spatial module
because it is tightly coupled to the algorithms there.  One of the arguments was that it could/should
probably use ByteRef since it works with raw indexed data.  Now that this moved over, I don't
think there's code in Spatial4j that is or should be byte oriented.  There's some geospatial
(WKT-like) string parsing code, and code that generates such strings from shapes, and they
are String oriented and that makes sense.
  As a general statement about performance, you should know that performance is an important
goal of Spatial4j.  So if for example the API needs to be a bit uglier to make performance
compromises, this spatial library more than others is willing to bend.  I think benchmarks
need to prove this out first on a case-by-case basis though.  Other libraries, like one where
I work seems to take another extreme in which Latitude and Longitude are each separate classes!
> Replace spatial contrib module with LSP's spatial-lucene module
> ---------------------------------------------------------------
>                 Key: LUCENE-3795
>                 URL:
>             Project: Lucene - Java
>          Issue Type: New Feature
>          Components: modules/spatial
>            Reporter: David Smiley
>            Assignee: David Smiley
>             Fix For: 4.0
> I propose that Lucene's spatial contrib module be replaced with the spatial-lucene module
within Lucene Spatial Playground (LSP).  LSP has been in development for approximately 1 year
by David Smiley, Ryan McKinley, and Chris Male and we feel it is ready.  LSP is here:
 and the spatial-lucene module is intuitively in svn/trunk/spatial-lucene/.
> I'll add more comments to prevent the issue description from being too long.

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