This is occuring with search_api_location where we have some entities that have a location and some don't. When the entities are being indexed in solr, the ones that don't have a geofield throw an error because the value for the geolocation is ",". I've tracked this down to geofield not doing a good enough check of the data array coming in before sending a response. It checks to see if there is an array but not that the values in the array are set so then solr tries to set the latlon fields to "," which causes an error.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

randallknutson’s picture

Status: Active » Needs review
FileSize
578 bytes

Attaching patch

phayes’s picture

Status: Needs review » Fixed

This is fixed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

randallknutson’s picture

Version: 7.x-2.x-dev » 7.x-1.x-dev
Status: Closed (fixed) » Needs review

This is still not fixed in the 1.x branch which is the current branch. I had to apply it with the latest 1.2 to get search_api working again.

Brandonian’s picture

Status: Needs review » Fixed

Good catch, @randallknutson. Patch applied to 7.x-1.x

http://drupalcode.org/project/geofield.git/commit/c9e90ad

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.