lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicholas Knize (JIRA)" <>
Subject [jira] [Updated] (LUCENE-6997) Graduate GeoUtils and postings based GeoPointField from sandbox...
Date Thu, 04 Feb 2016 06:26:39 GMT


Nicholas Knize updated LUCENE-6997:
    Attachment: LUCENE-6997.patch

Attached patch provides the following changes:
* refactors {{spatial}} module to new {{spatial-extras}} module
* refactors {{GeoPoint*}} classes from {{sandbox}} module to {{spatial}} module
* adds intellij {{.iml}} files to {{dev-tools}}
* updates ant build scripts, and maven pom files to build new module
* updates {{sandbox}} build to depend on {{spatial}} module so that sandboxed BKD point classes
and tests can remain sandboxed until they're ready to graduate

A few notes:
* I'm not an ant or maven expert, so I'll need someone to verify the changes. [~steve_rowe]?
{{precommit}} {{generate-maven-poms}} {{idea}} all work
* For collaboration I've created a new lucene-6997 feature branch that includes all of these

> Graduate GeoUtils and postings based GeoPointField from sandbox...
> ------------------------------------------------------------------
>                 Key: LUCENE-6997
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: modules/spatial
>            Reporter: Nicholas Knize
>         Attachments: LUCENE-6997.patch
> {{GeoPointField}} is a lightweight dependency-free postings based geo field currently
in sandbox. It has evolved into a very fast lightweight geo option that heavily leverages
the optimized performance of the postings structure. It was originally intended to graduate
to core but this does not seem appropriate given the variety of "built on postings" term encoding
options (e.g., see LUCENE-6930).  
> Additionally, the {{Geo*Utils}} classes are dependency free lightweight relational approximation
utilities used by both {{GeoPointField}} and the BKD based {{LatLonField}} and can also be
applied to benefit the lucene-spatial module.
> These classes have been evolving and baking for some time and are at a maturity level
qualifying for promotion from sandbox. This will allow support for experimental encoding methods
with (minimal) backwards compatibility - something sandbox does not allow.
> Since GeoPoint classes are dependency free, all GeoPointField and support and utility
classes currently in sandbox would be promoted to the spatial3d package. (possibly a separate
issue to rename spatial3d to spatialcore or spatiallite?) Such that for basic lightweight
Geo support one would only need a handful of lucene jars. By simply adding the lucene-spatial
module and its dependency jars users can obtain more advanced geospatial support (heatmap
facets, full shape relations, etc).

This message was sent by Atlassian JIRA

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

View raw message