Message Title

Sanne Grinovero created an issue

Issue Type:	Improvement
Assignee:	Unassigned
Created:	31/May/2017 07:13 AM
Fix Versions:	5.8
Priority:	Major
Reporter:	Sanne Grinovero

The strategy used by SpatialFieldBridge to read the coordinates is very inefficient, as it temptatively attempts a reflection call and then falls back to a second option.
The approach might be fine, but the attempt is performed for every single read of the Coordinates pair, generating a swallowed exception (with related stacktrace) each time an entity using @Spatial is indexed.

 
                                                                Stack Trace	Count
java.lang.Throwable.<init>(String)	17,731
   java.lang.Exception.<init>(String)	17,731
      java.lang.ReflectiveOperationException.<init>(String)	17,731
         java.lang.NoSuchFieldException.<init>(String)	17,731
            java.lang.Class.getField(String)	17,731
               org.hibernate.search.spatial.SpatialFieldBridge.getCoordinateFromField(String, Object)	17,731
                  org.hibernate.search.spatial.SpatialFieldBridge.getLatitude(Object)	8,866
                  org.hibernate.search.spatial.SpatialFieldBridge.getLongitude(Object)	8,865
 
                                                            

Add Comment

This message was sent by Atlassian JIRA