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

Description

I frequently makes the mistake of writing my spatial query without setting up the index. We might want to try and make that error message as descriptove as possible.

Activity

Show:

Sanne GrinoveroNovember 10, 2014 at 4:13 PM

Emmanuel BernardNovember 4, 2014 at 7:50 PM

That looks ok. I guess the report dates from before that message or the situation was different, I don't know.

Hardy FerentschikNovember 3, 2014 at 8:45 PM

If I forget the @Spatial annotation, the query involving .spatial() should fail with an explicit exception.

Hmm, there seems to already an exceptional case - HSEARCH000131 - which gets thrown from ConnectedSpatialQueryBuilder. I changed the message a bit and added some additional tests. Not sure if there is another case you had in mind? is still of course another issue.

Hardy FerentschikNovember 3, 2014 at 7:12 PM

The issue I've seen in SpatialIndexingTest is another problem really. I created to track it.

Emmanuel BernardNovember 3, 2014 at 2:31 PM

If I forget the @Spatial annotation, the query involving .spatial() should fail with an explicit exception.

Fixed

Details

Assignee

Reporter

Components

Fix versions

Priority

Created December 19, 2013 at 3:20 PM
Updated November 13, 2014 at 6:55 PM
Resolved November 10, 2014 at 4:14 PM