[
https://issues.apache.org/jira/browse/LUCENE-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14699647#comment-14699647
]
Michael McCandless commented on LUCENE-6699:
--------------------------------------------
OK I fixed the query to use the new XYZBounds API, but I hit NPE:
{noformat}
[junit4] Suite: org.apache.lucene.bkdtree3d.TestGeo3DPointField
[junit4] 2> NOTE: reproduce with: ant test -Dtestcase=TestGeo3DPointField
-Dtests.method=testBasic -Dtests.seed=1600287909381DEB -Dtests.locale=el_CY
-Dtests.timezone=America/Mexico_City -Dtests.asserts=true
-Dtests.file.encoding=ISO-8859-1
[junit4] ERROR 0.22s J0 | TestGeo3DPointField.testBasic <<<
[junit4] > Throwable #1: java.lang.NullPointerException
[junit4] > at
__randomizedtesting.SeedInfo.seed([1600287909381DEB:BDFA356CD6E49BC5]:0)
[junit4] > at
org.apache.lucene.bkdtree3d.PointInGeo3DShapeQuery$1.scorer(PointInGeo3DShapeQuery.java:102)
[junit4] > at
org.apache.lucene.search.Weight.bulkScorer(Weight.java:135)
[junit4] > at
org.apache.lucene.search.AssertingWeight.bulkScorer(AssertingWeight.java:69)
[junit4] > at
org.apache.lucene.search.AssertingWeight.bulkScorer(AssertingWeight.java:69)
[junit4] > at
org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:618)
[junit4] > at
org.apache.lucene.search.AssertingIndexSearcher.search(AssertingIndexSearcher.java:92)
[junit4] > at
org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:425)
[junit4] > at
org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:544)
[junit4] > at
org.apache.lucene.search.IndexSearcher.searchAfter(IndexSearcher.java:402)
[junit4] > at
org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:413)
[junit4] > at
org.apache.lucene.bkdtree3d.TestGeo3DPointField.testBasic(TestGeo3DPointField.java:90)
[junit4] > at java.lang.Thread.run(Thread.java:745)
{noformat}
Is it expected that sometimes the bounds would be null? If so, I could just
swap in Integer.MIN/MAX_VALUE for that dimension... (seems like in this failure
it's only the z dimension that's null).
> Integrate lat/lon BKD and spatial3d
> -----------------------------------
>
> Key: LUCENE-6699
> URL: https://issues.apache.org/jira/browse/LUCENE-6699
> Project: Lucene - Core
> Issue Type: New Feature
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Attachments: Geo3DPacking.java, LUCENE-6699.patch, LUCENE-6699.patch,
> LUCENE-6699.patch, LUCENE-6699.patch, LUCENE-6699.patch, LUCENE-6699.patch,
> LUCENE-6699.patch, LUCENE-6699.patch, LUCENE-6699.patch, LUCENE-6699.patch,
> LUCENE-6699.patch
>
>
> I'm opening this for discussion, because I'm not yet sure how to do
> this integration, because of my ignorance about spatial in general and
> spatial3d in particular :)
> Our BKD tree impl is very fast at doing lat/lon shape intersection
> (bbox, polygon, soon distance: LUCENE-6698) against previously indexed
> points.
> I think to integrate with spatial3d, we would first need to record
> lat/lon/z into doc values. Somewhere I saw discussion about how we
> could stuff all 3 into a single long value with acceptable precision
> loss? Or, we could use BinaryDocValues? We need all 3 dims available
> to do the fast per-hit query time filtering.
> But, second: what do we index into the BKD tree? Can we "just" index
> earth surface lat/lon, and then at query time is spatial3d able to
> give me an enclosing "surface lat/lon" bbox for a 3d shape? Or
> ... must we index all 3 dimensions into the BKD tree (seems like this
> could be somewhat wasteful)?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
