clear query| facets| time Search criteria: .   Results from 1 to 10 from 105 (0.0s).
Loading phrases to help you
refine your search...
[LUCENE-8632] XYShape: Adapt LatLonShape tessellator, field type, and queries to non-geo shapes - Lucene - [issue]
...Currently the tessellator is tightly coupled with latitude and longitude (WGS84) geospatial coordinates. This issue will explore generalizing the tessellator, LatLonShape field and LatLonSha...
http://issues.apache.org/jira/browse/LUCENE-8632    Author: Nicholas Knize , 2019-06-19, 17:16
[LUCENE-8362] Add DocValue support for RangeFields - Lucene - [issue]
...I'm opening this issue to discuss adding DocValue support to {Int|Long|Float|Double}Range field types. Since existing numeric range fields already provide the methods for encoding ranges as ...
http://issues.apache.org/jira/browse/LUCENE-8362    Author: Nicholas Knize , 2019-06-10, 14:11
[SOLR-12520] Switch DateRangeField from NumberRangePrefixTree to LongRange - Solr - [issue]
...Since graduating Range field types in LUCENE-7740 we should consider switching SOLR's DateRangeField from using NumberRangePrefixTree in the spatial-extras module to LongRange in lucene-core...
http://issues.apache.org/jira/browse/SOLR-12520    Author: Nicholas Knize , 2019-06-08, 15:00
[SOLR-13039] BadApples for 7.6 Release - Solr - [issue]
...To build the 7.6 release candidate the following test cases need to be annotated as BadApple (Each of these tests have multiple known CI failures over an extended period of time):o.a.solr.Te...
http://issues.apache.org/jira/browse/SOLR-13039    Author: Nicholas Knize , 2019-06-08, 14:58
significant lucene benchmark regression: JDK11? - Lucene - [mail # dev]
...Earlier this week I noticed a significant across the board performanceregression on the nightly geo benchmarks. It appears thisregression can also be seen on other lucene benchmarks and...
   Author: Nicholas Knize , 2019-04-25, 17:57
[LUCENE-8736] LatLonShapePolygonQuery returning incorrect WITHIN results with shared boundaries - Lucene - [issue]
...Triangles that are WITHIN a target polygon query that also share a boundary with the polygon are incorrectly reported as CROSSES instead of INSIDE. This leads to incorrect WITHIN query resul...
http://issues.apache.org/jira/browse/LUCENE-8736    Author: Nicholas Knize , 2019-04-19, 15:53
[LUCENE-8686] TestTaxonomySumValueSource.testRandom Failure - Lucene - [issue]
...Reproducible test failure:NOTE: reproduce with: ant test  -Dtestcase=TestTaxonomyFacetSumValueSource -Dtests.method=testRandom -Dtests.seed=7F625DA1A252DF8E -Dtests.slow=true -Dtests.ba...
http://issues.apache.org/jira/browse/LUCENE-8686    Author: Nicholas Knize , 2019-03-14, 13:07
[LUCENE-8496] Explore selective dimension indexing in BKDReader/Writer - Lucene - [issue]
...This issue explores adding a new feature to BKDReader/Writer that enables users to select a fewer number of dimensions to be used for creating the BKD index than the total number of dimensio...
http://issues.apache.org/jira/browse/LUCENE-8496    Author: Nicholas Knize , 2019-03-14, 13:06
[LUCENE-8721] LatLonShapePolygon and LineQuery fail on shared dateline queries - Lucene - [issue]
...Indexed shapes should be returned with search geometries that share the dateline on the opposite hemisphere. For example:  public void testSharedDateline() throws Exception {  &nbs...
http://issues.apache.org/jira/browse/LUCENE-8721    Author: Nicholas Knize , 2019-03-13, 07:16
[LUCENE-8581] Change LatLonShape encoding to use 4 BYTES Per Dimension - Lucene - [issue]
...LatLonShape tessellated triangles currently use a relatively naive encoding with the first four dimensions as the bounding box of the triangle and the last three dimensions as the vertices o...
http://issues.apache.org/jira/browse/LUCENE-8581    Author: Nicholas Knize , 2019-02-11, 09:19