lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (LUCENE-7189) Make BaseGeoPointTestCase more debuggable
Date Tue, 12 Apr 2016 10:08:25 GMT


ASF subversion and git services commented on LUCENE-7189:

Commit e034b04b065ca635553672d2b35c6b36578fd673 in lucene-solr's branch refs/heads/master
from Mike McCandless
[;h=e034b04 ]

LUCENE-7189: improve geo debugging technology

> Make BaseGeoPointTestCase more debuggable
> -----------------------------------------
>                 Key: LUCENE-7189
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Robert Muir
> This class tests queries (boxes, circles, polygons) against indexed documents and fails
if the query is wrong.
> Unfortunately it can be hard to debug (depending which test method failed, if it was
NIGHTLY, etc).
> It is making issues challenging/slower to debug for me on LUCENE-7185. In general i have
found debugging geo related issues is difficult, we should invest more time to make this easier.
> I think we want to display:
> 1) original item (e.g. Rectangle, radius, polygon)
> 2) query.toString() <-- can be different in important ways!
> 3) how many total documents were wrong
> 4) info on up to N (say 5) wrong documents:
>   ID (not lucene docid) of doc.
>   Lat/Lon location(s) of doc
>   any relevant metric such as distance from origin
> 5) GeoTestUtil.toWebGLEarth output of html to visualize those N wrong documents, the
query itself, any additional stuff like bounding box that might be useful plotted too.
> I think the wrong documents we should try for one-line (rather than many) and we don't
need to print stuff like deleted=false since these queries don't do anything sneaky here around

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message