Issues

Search 6 groundwork - Restore support for "distance" projections

Search 6 groundwork - match() queries on GeoPoint fields

Search 6 groundwork - Add spatial querying support

Current implementation of SpatialBridge prevents multi-valued locations

Comply with Hibernate ORM's access mode in @Spatial bridges

Handle private/protected field access for @Spatial fields

Provide support for more distance units

DistanceSortField should support reverse sorting

Detect invalid cardinality of fields mapped as DocValues

Options not exposed in SpatialFieldBridgeByHash

SpatialFieldBridge implementations should reuse target field name

Add various accessors and utilities to be able to exploit the spatial structures

SpatialFieldBridges implement MetadataProvidingFieldBridge but does not provide useful information about the added fields

Spatial Search with distance projection is not returning all results

Upgrade Spatial Query related implementations to avoid using Lucene's deprecated FieldCache

BenchWithGeonames should be moved into the integrationtest module and made a perf test

Using DistanceSortField does not verify the field parameter passed to the constructor

Avoid eager iteration on values read from AtomicReader in DistanceCollector until an explicit collect()

Provide better error message when the user writes a geospatial query against a non spatial field

Consider the term 'geospatial' instead of 'spatial'

Geo-distance aggregation

Make the message clearer and provide a hint when no matching @Latitude/@Longitude is found for a @Spatial index

Reword reference for Quad Tree for Spatial Hash in spatial module

Spatial API polishing

Allow @Latitude and @Longitude annotations on methods (getters) too

Improve usability and consistency of spatial API

Spatial search with sort by distance and paging orders entities incorrectly and repeats them

Incorrect example for Coordinates in Spatial document

Improve details on the spatial feature

Readability of @Latitude and @Longitude

Introduce a Sort DSL, especially for Spatial Queries

New Spatial methods on FullTextQuery are not exposed on the JPA FullTextQuery

SpatialQueryBuilder assumes usage of "km" units

Document @Latitude and @Longitude features of Spatial

Return distance to search center in spatial queries

Sorting by distance on spatial queries

Improve documentation on Spatial integrations

Add more tests to cover Range/Grid and Class/Member level combinations

Test @Embeddable nesting

How would Faceting and geolocation work?

Implement variable score on spatial queries

Move spatial code to JBoss Logging

Add support for geospatial queries