Dear ML,
I'm performing some developments relying on spatial capabilities of solr.
I'm using Solr 3.5, have been reading
http://wiki.apache.org/solr/SpatialSearch#Spatial_Query_Parameters and
have the basic behaviours I wanted working.
I use geofilt on a latlong field, with geodist() in the bf parameter.
When I doq=*:*&fq={!geofilt pt=x,y d=r unit=km
sfield=coordinates}&defType=edismax everything works fine.
But in some cases, documents don't have coordinates.
For example, some of them refer to a city, so they have coordinates,
while others are not so precisely geolocated and simply refer to a
broader area, a region or a state, if you will.
I tried with different queries :
- Include results from a broader area : q=*:*&fq=(state:FL OR
_query_:"{!geofilt ...}") .
=> That works fine (i.e. results showing up), but not as expected : this
only returns documents having FL as value in the state field AND some
value in the coordinates field *or* documents around my point but not
documents without a value in the coordinates field...
- Include results from a broader area, feeling lucky :
q=*:*&fq=((state:FL%20AND%20-coordinates:[*%20TO%20*])%20OR%20_query_:"{!geofilt%20pt=x,y%20d=r%20unit=km%20sfield=coordinates}")
=> which does what is asked to... Return both the results with FL in the
state field and no value in the coordinates field *plus* results within
a radius around a point, *but* the problem is that in that case, the
solr search layer dies unconditionnally with the following stack :
Problem accessing /solr/geo_xpe/select. Reason:
null
java.lang.NullPointerException
at
org.apache.lucene.spatial.DistanceUtils.parsePoint(DistanceUtils.java:351)
at org.apache.solr.schema.LatLonType.getRangeQuery(LatLonType.java:95)
at
org.apache.solr.search.SolrQueryParser.getRangeQuery(SolrQueryParser.java:165)
at
org.apache.lucene.queryParser.QueryParser.Term(QueryParser.java:1474)
at
org.apache.lucene.queryParser.QueryParser.Clause(QueryParser.java:1309)
at
org.apache.lucene.queryParser.QueryParser.Query(QueryParser.java:1266)
at
org.apache.lucene.queryParser.QueryParser.Clause(QueryParser.java:1313)
at
org.apache.lucene.queryParser.QueryParser.Query(QueryParser.java:1237)
at
org.apache.lucene.queryParser.QueryParser.Clause(QueryParser.java:1313)
at
org.apache.lucene.queryParser.QueryParser.Query(QueryParser.java:1237)
at
org.apache.lucene.queryParser.QueryParser.TopLevelQuery(QueryParser.java:1226)
at
org.apache.lucene.queryParser.QueryParser.parse(QueryParser.java:206)
at
org.apache.solr.search.LuceneQParser.parse(LuceneQParserPlugin.java:80)
at org.apache.solr.search.QParser.getQuery(QParser.java:142)
at
org.apache.solr.handler.component.QueryComponent.prepare(QueryComponent.java:94)
at
org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:173)
at
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:129)
at org.apache.solr.core.SolrCore.execute(SolrCore.java:1368)
at
org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:356)
at
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:252)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)
at
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
at
org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
at
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
at
org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
at
org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
at
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
Of course, it doesn't make sense to expect the distance computation to
work with documents lacking value in the coordinate field!
From a user perspective, having the possibility to define a default
distance to be returned for document missing a value in the coordinate
field could be helpful... If something like sortMissingFirst or
sortMissingLast is specified on the field.
* sortMissingLast="true" could be obtained with a +Inf distance returned
if no value in the field
* sortMissingFirst="true" could be obtained with a 0 distance returned
if no value in the field
I may be misunderstanding concepts, but those sorting attributes seem to
only apply for sorting and not to the documents selection process
(geofilt)..? I know that since solr3.5, it's possible to define
sortMissing(Last|First) on trie-based fields, but I don't know what
happens for fields defined that way :
...
<types>
...
<fieldType name="double" class="solr.TrieDoubleField" precisionStep="0"
omitNorms="true" positionIncrementGap="0"/>
<fieldType name="latlong" class="solr.LatLonType" indexed="true"
sortMissingLast="true" omitNorms="true" subFieldType="double" />
...
<types>
...
<fields>
...
<field name="coordinates" type="latlong" indexed="true" stored="true"
mutliValued="false"/>
...
</fields>
...
Help is welcome!
--
Tanguy
