Uploaded image for project: 'Lucene - Core'
  1. Lucene - Core
  2. LUCENE-6520

Geo3D GeoPath: co-linear end-points result in NPE

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 5.2
    • 5.3
    • modules/spatial
    • None
    • New

    Description

      FAILED: org.apache.lucene.spatial.spatial4j.Geo3dRptTest.testOperations

      {#2 seed=[4AB0FA45EF43F0C3:2240DF3E6EDF83C]}
      Stack Trace:
      java.lang.NullPointerException
              at __randomizedtesting.SeedInfo.seed([4AB0FA45EF43F0C3:2240DF3E6EDF83C]:0)
              at org.apache.lucene.spatial.spatial4j.geo3d.GeoPath$SegmentEndpoint.<init>(GeoPath.java:480)
              at org.apache.lucene.spatial.spatial4j.geo3d.GeoPath.done(GeoPath.java:121)
              at org.apache.lucene.spatial.spatial4j.Geo3dRptTest.randomQueryShape(Geo3dRptTest.java:195)
              at org.apache.lucene.spatial.prefix.RandomSpatialOpStrategyTestCase.testOperationRandomShapes(RandomSpatialOpStrategyTestCase.java:53)
              at org.apache.lucene.spatial.spatial4j.Geo3dRptTest.testOperations(Geo3dRptTest.java:100)
      

      Karl Wright says:

      This is happening because the endpoints that define two path segments are co-linear. There's a check for that too, but clearly it's not firing properly in this case for some reason.

      Attachments

        1. LUCENE-6520.patch
          9 kB
          David Smiley

        Issue Links

          Activity

            People

              dsmiley David Smiley
              dsmiley David Smiley
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Slack

                  Issue deployment