Spatial sort on optional field may fail in corner cases

Description

Given an index with a spatial field (say, "location"), it seems that indexing a document with missing location in a separate transaction will prevent the sort from working properly.
If we index it in a transaction where other documents are indexed, everything works well, though.

We get that kind of stack trace:

Test case here: https://github.com/hibernate/hibernate-search/pull/1136

Activity

Show:
Fixed

Details

Assignee

Reporter

Components

Sprint

Fix versions

Affects versions

Priority

Created August 12, 2016 at 11:18 AM
Updated September 5, 2016 at 6:42 PM
Resolved August 19, 2016 at 8:38 AM