[jira] [Commented] (LUCENE-7157) Geo3DPoint implementation should pay attention to the ordering of lat/lon points

[ https://issues.apache.org/jira/browse/LUCENE-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223692#comment-15223692 ] Karl Wright commented on LUCENE-7157: - bq. Just like I don't think users need to deal with radians, I

[jira] [Created] (SOLR-8937) bin/post (SimplePostTool) should stream/chunk if size not known

David Smiley created SOLR-8937: -- Summary: bin/post (SimplePostTool) should stream/chunk if size not known Key: SOLR-8937 URL: https://issues.apache.org/jira/browse/SOLR-8937 Project: Solr

[JENKINS] Lucene-Solr-Tests-6.x - Build # 117 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-Tests-6.x/117/ 1 tests failed. FAILED: org.apache.solr.update.HardAutoCommitTest.testCommitWithin Error Message: Exception during query Stack Trace: java.lang.RuntimeException: Exception during query at

[JENKINS] Lucene-Solr-6.x-Linux (64bit/jdk1.8.0_72) - Build # 336 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-6.x-Linux/336/ Java: 64bit/jdk1.8.0_72 -XX:-UseCompressedOops -XX:+UseG1GC 1 tests failed. FAILED: org.apache.solr.cloud.ChaosMonkeyNothingIsSafeTest.test Error Message: document count mismatch. control=372 sum(shards)=371 cloudClient=371

[jira] [Commented] (SOLR-8812) ExtendedDismaxQParser (edismax) ignores Boolean OR when q.op=AND

[ https://issues.apache.org/jira/browse/SOLR-8812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223581#comment-15223581 ] Greg Pendlebury commented on SOLR-8812: --- [~erickerickson], personally, I am ambivalent with regards

[jira] [Updated] (SOLR-8812) ExtendedDismaxQParser (edismax) ignores Boolean OR when q.op=AND

[ https://issues.apache.org/jira/browse/SOLR-8812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Pendlebury updated SOLR-8812: -- Attachment: SOLR-8812-barbie.patch Adding a 'hair ties -barbie' example to unit tests. Not sure

[JENKINS-EA] Lucene-Solr-6.0-Linux (64bit/jdk-9-ea+111-patched) - Build # 10 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-6.0-Linux/10/ Java: 64bit/jdk-9-ea+111-patched -XX:+UseCompressedOops -XX:+UseParallelGC -XX:-CompactStrings All tests passed Build Log: [...truncated 11867 lines...] [junit4] JVM J1: stdout was not empty, see:

[jira] [Commented] (SOLR-8208) DocTransformer executes sub-queries

[ https://issues.apache.org/jira/browse/SOLR-8208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223511#comment-15223511 ] Mikhail Khludnev commented on SOLR-8208: it seems like param tracing can be done with

RE: [VOTE] Release Lucene/Solr 6.0.0 RC2

Hi Jack > Adding this less-controversial point: > > 5. It should have been stated explicitly that Java 1.9 is not supported at > this time. I am not sure why you want to have this in the release notes. This is completely irrelevant: - Java 9 is not yet released, so nobody would use it in

[jira] [Commented] (LUCENE-7170) move BaseGeoPointTestCase to test-framework

[ https://issues.apache.org/jira/browse/LUCENE-7170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223464#comment-15223464 ] Michael McCandless commented on LUCENE-7170: +1 > move BaseGeoPointTestCase to

[jira] [Commented] (LUCENE-7159) improve spatial point/rect vs. polygon performance

[ https://issues.apache.org/jira/browse/LUCENE-7159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223438#comment-15223438 ] ASF subversion and git services commented on LUCENE-7159: - Commit

[jira] [Commented] (LUCENE-7159) improve spatial point/rect vs. polygon performance

[ https://issues.apache.org/jira/browse/LUCENE-7159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223437#comment-15223437 ] ASF subversion and git services commented on LUCENE-7159: - Commit

[JENKINS] Lucene-Solr-6.x-Linux (64bit/jdk1.8.0_72) - Build # 333 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-6.x-Linux/333/ Java: 64bit/jdk1.8.0_72 -XX:-UseCompressedOops -XX:+UseSerialGC 1 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.cloud.TestTolerantUpdateProcessorRandomCloud Error Message: There are still nodes recoverying -

[jira] [Commented] (LUCENE-7163) Refactor GeoRect and Polygon to core

[ https://issues.apache.org/jira/browse/LUCENE-7163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223428#comment-15223428 ] ASF subversion and git services commented on LUCENE-7163: - Commit

[jira] [Commented] (LUCENE-7163) Refactor GeoRect and Polygon to core

[ https://issues.apache.org/jira/browse/LUCENE-7163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223427#comment-15223427 ] ASF subversion and git services commented on LUCENE-7163: - Commit

[jira] [Updated] (LUCENE-7170) move BaseGeoPointTestCase to test-framework

[ https://issues.apache.org/jira/browse/LUCENE-7170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-7170: Attachment: LUCENE-7170.patch Here is a patch. Basically it just moves the file and removes the

[jira] [Created] (LUCENE-7170) move BaseGeoPointTestCase to test-framework

Robert Muir created LUCENE-7170: --- Summary: move BaseGeoPointTestCase to test-framework Key: LUCENE-7170 URL: https://issues.apache.org/jira/browse/LUCENE-7170 Project: Lucene - Core Issue

[jira] [Updated] (SOLR-8935) Add cycle detection PostFilter

[ https://issues.apache.org/jira/browse/SOLR-8935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Bernstein updated SOLR-8935: - Description: in SOLR- cycle detection is done in the worker node. This ticket will allow all

[jira] [Updated] (SOLR-8935) Add cycle detection PostFilter

[ https://issues.apache.org/jira/browse/SOLR-8935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Bernstein updated SOLR-8935: - Description: in SOLR- cycle detection is done in the worker node. This ticket will allow all

[jira] [Resolved] (LUCENE-7169) Add Geo3DPoint.newSolidQuery

[ https://issues.apache.org/jira/browse/LUCENE-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved LUCENE-7169. - Resolution: Won't Fix Needs to implement GeoShape and doesn't currently, so this is not worth

[jira] [Updated] (SOLR-8935) Add cycle detection PostFilter

[ https://issues.apache.org/jira/browse/SOLR-8935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Bernstein updated SOLR-8935: - Description: in SOLR- cycle detection is done in the worker node. This ticket will allow all

[jira] [Created] (SOLR-8936) Push down the DISTINCT operation into the /export handler, to support exporting distinct edges during a graph traversal

Joel Bernstein created SOLR-8936: Summary: Push down the DISTINCT operation into the /export handler, to support exporting distinct edges during a graph traversal Key: SOLR-8936 URL:

[jira] [Created] (SOLR-8935) Add cycle detection PostFilter

Joel Bernstein created SOLR-8935: Summary: Add cycle detection PostFilter Key: SOLR-8935 URL: https://issues.apache.org/jira/browse/SOLR-8935 Project: Solr Issue Type: Improvement

[jira] [Commented] (LUCENE-7168) Remove geo3d test leniency

[ https://issues.apache.org/jira/browse/LUCENE-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223385#comment-15223385 ] Nicholas Knize commented on LUCENE-7168: bq. e.g. custom planet models/distance metrics/crazy

[jira] [Created] (LUCENE-7169) Add Geo3DPoint.newSolidQuery

Karl Wright created LUCENE-7169: --- Summary: Add Geo3DPoint.newSolidQuery Key: LUCENE-7169 URL: https://issues.apache.org/jira/browse/LUCENE-7169 Project: Lucene - Core Issue Type: Improvement

[jira] [Commented] (LUCENE-7168) Remove geo3d test leniency

[ https://issues.apache.org/jira/browse/LUCENE-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223367#comment-15223367 ] Robert Muir commented on LUCENE-7168: - I think (ultimately) we should have Geo3DPoint.java and

[jira] [Commented] (SOLR-8803) OOM killer for Windows

[ https://issues.apache.org/jira/browse/SOLR-8803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223364#comment-15223364 ] Binoy Dalal commented on SOLR-8803: --- The flag is being picked up. A simple script that opens up a new

[jira] [Commented] (LUCENE-7168) Remove geo3d test leniency

[ https://issues.apache.org/jira/browse/LUCENE-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223355#comment-15223355 ] Karl Wright commented on LUCENE-7168: - bq. Right but I think we should try to simplify and reduce to

[jira] [Commented] (LUCENE-7168) Remove geo3d test leniency

[ https://issues.apache.org/jira/browse/LUCENE-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223351#comment-15223351 ] Robert Muir commented on LUCENE-7168: - {quote} While XYZSolids are used by Lucene for BKD trees, I

[jira] [Commented] (LUCENE-7168) Remove geo3d test leniency

[ https://issues.apache.org/jira/browse/LUCENE-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223348#comment-15223348 ] Karl Wright commented on LUCENE-7168: - While XYZSolids are used by Lucene for BKD trees, I cannot say

[jira] [Commented] (LUCENE-7168) Remove geo3d test leniency

[ https://issues.apache.org/jira/browse/LUCENE-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223347#comment-15223347 ] Robert Muir commented on LUCENE-7168: - And I have not tested the numbers involved either: I am just

[jira] [Commented] (LUCENE-7168) Remove geo3d test leniency

[ https://issues.apache.org/jira/browse/LUCENE-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223344#comment-15223344 ] Robert Muir commented on LUCENE-7168: - I think this is the wrong way to look at it? If some of these

[jira] [Commented] (LUCENE-7168) Remove geo3d test leniency

[ https://issues.apache.org/jira/browse/LUCENE-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223342#comment-15223342 ] Karl Wright commented on LUCENE-7168: - Handling geometric degeneracy conditions properly, I agree,

[jira] [Commented] (LUCENE-7168) Remove geo3d test leniency

[ https://issues.apache.org/jira/browse/LUCENE-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223338#comment-15223338 ] Robert Muir commented on LUCENE-7168: - Its an important implementation detail. If we can make

[jira] [Commented] (LUCENE-7168) Remove geo3d test leniency

[ https://issues.apache.org/jira/browse/LUCENE-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223335#comment-15223335 ] Karl Wright commented on LUCENE-7168: - That's an implementation detail. All of the stuff in

[jira] [Commented] (LUCENE-7168) Remove geo3d test leniency

[ https://issues.apache.org/jira/browse/LUCENE-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223334#comment-15223334 ] Robert Muir commented on LUCENE-7168: - But we do not have the numeric resolution of a double. It is

[jira] [Commented] (LUCENE-7168) Remove geo3d test leniency

[ https://issues.apache.org/jira/browse/LUCENE-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1522#comment-1522 ] Karl Wright commented on LUCENE-7168: - "Immeasurably" means within the resolution of the mathematics

[jira] [Commented] (LUCENE-7168) Remove geo3d test leniency

[ https://issues.apache.org/jira/browse/LUCENE-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223332#comment-15223332 ] Robert Muir commented on LUCENE-7168: - I don't see how it can be immeasurably small. We use a 32-bit

[jira] [Commented] (LUCENE-7168) Remove geo3d test leniency

[ https://issues.apache.org/jira/browse/LUCENE-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223327#comment-15223327 ] Karl Wright commented on LUCENE-7168: - Hi Robert, The reason for the 8 implementations is because

[JENKINS] Lucene-Solr-Tests-6.0 - Build # 6 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-Tests-6.0/6/ 3 tests failed. FAILED: org.apache.solr.cloud.CollectionsAPIDistributedZkTest.test Error Message: replicaCount expected:<0> but was:<1> Stack Trace: java.lang.AssertionError: replicaCount expected:<0> but was:<1> at

[jira] [Commented] (LUCENE-7168) Remove geo3d test leniency

[ https://issues.apache.org/jira/browse/LUCENE-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223323#comment-15223323 ] Robert Muir commented on LUCENE-7168: - It seems also that the current test design (testing

[jira] [Created] (LUCENE-7168) Remove geo3d test leniency

Michael McCandless created LUCENE-7168: -- Summary: Remove geo3d test leniency Key: LUCENE-7168 URL: https://issues.apache.org/jira/browse/LUCENE-7168 Project: Lucene - Core Issue Type:

[jira] [Commented] (LUCENE-7167) Re-engineer or remove all of geo3D

[ https://issues.apache.org/jira/browse/LUCENE-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223321#comment-15223321 ] Michael McCandless commented on LUCENE-7167: I opened LUCENE-7168 for the test quantization.

[jira] [Commented] (LUCENE-7167) Re-engineer or remove all of geo3D

[ https://issues.apache.org/jira/browse/LUCENE-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223319#comment-15223319 ] Michael McCandless commented on LUCENE-7167: I'll open a separate issue to remove geo3d test

Re: lucene-solr:lucene-7157: LUCENE_7157: current patch

I will remove this branch. Let's debate on the issue instead: https://issues.apache.org/jira/browse/LUCENE-7157 Mike McCandless http://blog.mikemccandless.com On Sun, Apr 3, 2016 at 9:08 AM, Robert Muir wrote: > I'm not going to argue with you about why

[jira] [Commented] (LUCENE-7167) Re-engineer or remove all of geo3D

[ https://issues.apache.org/jira/browse/LUCENE-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223315#comment-15223315 ] Robert Muir commented on LUCENE-7167: - +1 for this patch. It reduces the surface area of geo3d api by

[jira] [Commented] (LUCENE-7167) Re-engineer or remove all of geo3D

[ https://issues.apache.org/jira/browse/LUCENE-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223311#comment-15223311 ] Robert Muir commented on LUCENE-7167: - {quote} Yes, that's what I thought we were doing, but the BKD

[jira] [Updated] (LUCENE-7167) Re-engineer or remove all of geo3D

[ https://issues.apache.org/jira/browse/LUCENE-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated LUCENE-7167: Attachment: LUCENE-7167.diff Make package private the classes we don't expect people to extend or

[jira] [Commented] (SOLR-8803) OOM killer for Windows

[ https://issues.apache.org/jira/browse/SOLR-8803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223296#comment-15223296 ] Binoy Dalal commented on SOLR-8803: --- Tried on Solr 5.3.1, 5.4.1, 4.10.4 Still facing the same issue, with

[jira] [Commented] (LUCENE-7167) Re-engineer or remove all of geo3D

[ https://issues.apache.org/jira/browse/LUCENE-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223292#comment-15223292 ] Karl Wright commented on LUCENE-7167: - bq. We decide to use a lossy encoding, that is fine, but we

[jira] [Commented] (LUCENE-7167) Re-engineer or remove all of geo3D

[ https://issues.apache.org/jira/browse/LUCENE-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223289#comment-15223289 ] Michael McCandless commented on LUCENE-7167: bq. Michael McCandless: You wrote the test – can

[jira] [Commented] (LUCENE-7167) Re-engineer or remove all of geo3D

[ https://issues.apache.org/jira/browse/LUCENE-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223287#comment-15223287 ] Robert Muir commented on LUCENE-7167: - That is fine, I just want us to make progress on simplifying

[jira] [Comment Edited] (LUCENE-7167) Re-engineer or remove all of geo3D

[ https://issues.apache.org/jira/browse/LUCENE-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223283#comment-15223283 ] Karl Wright edited comment on LUCENE-7167 at 4/3/16 1:27 PM: - This clause was

[jira] [Commented] (LUCENE-7167) Re-engineer or remove all of geo3D

[ https://issues.apache.org/jira/browse/LUCENE-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223284#comment-15223284 ] Karl Wright commented on LUCENE-7167: - I would be happy to do that but there are several commits

[jira] [Commented] (LUCENE-7167) Re-engineer or remove all of geo3D

[ https://issues.apache.org/jira/browse/LUCENE-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223283#comment-15223283 ] Karl Wright commented on LUCENE-7167: - This clause was added to the test alone, because the

[jira] [Commented] (LUCENE-7167) Re-engineer or remove all of geo3D

[ https://issues.apache.org/jira/browse/LUCENE-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223279#comment-15223279 ] Robert Muir commented on LUCENE-7167: - {quote} Some classes that are public that don't need to be:

[jira] [Commented] (LUCENE-7167) Re-engineer or remove all of geo3D

[ https://issues.apache.org/jira/browse/LUCENE-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223278#comment-15223278 ] Robert Muir commented on LUCENE-7167: - My issue with the edge case testing is right here:

[jira] [Commented] (LUCENE-7167) Re-engineer or remove all of geo3D

[ https://issues.apache.org/jira/browse/LUCENE-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223277#comment-15223277 ] Karl Wright commented on LUCENE-7167: - bq. The test explicitly discards any edge cases. (1) Can you

Re: lucene-solr:lucene-7157: LUCENE_7157: current patch

I'm not going to argue with you about why GeoConcavePolygon.java should not be public. Instead, you can convince me why it should be. public should not be the default. On Sun, Apr 3, 2016 at 8:56 AM, Karl Wright wrote: >>> > No, I responded to the commit, because I

[jira] [Commented] (SOLR-8803) OOM killer for Windows

[ https://issues.apache.org/jira/browse/SOLR-8803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223276#comment-15223276 ] Binoy Dalal commented on SOLR-8803: --- I noticed that very silly mistake and corrected it. But still

[jira] [Commented] (LUCENE-7167) Re-engineer or remove all of geo3D

[ https://issues.apache.org/jira/browse/LUCENE-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223275#comment-15223275 ] Karl Wright commented on LUCENE-7167: - Some classes that are public that don't need to be: (1) Any

[jira] [Commented] (LUCENE-7167) Re-engineer or remove all of geo3D

[ https://issues.apache.org/jira/browse/LUCENE-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223271#comment-15223271 ] Robert Muir commented on LUCENE-7167: - Sorry karl, it has not been beasted to death. Please don't

[jira] [Commented] (LUCENE-7167) Re-engineer or remove all of geo3D

[ https://issues.apache.org/jira/browse/LUCENE-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223270#comment-15223270 ] Karl Wright commented on LUCENE-7167: - Would you make allowances for opening the API's enough to

[jira] [Commented] (LUCENE-7167) Re-engineer or remove all of geo3D

[ https://issues.apache.org/jira/browse/LUCENE-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223268#comment-15223268 ] Karl Wright commented on LUCENE-7167: - bq. So if its gonna do that, why does it do this ridiculous

[jira] [Commented] (LUCENE-7167) Re-engineer or remove all of geo3D

[ https://issues.apache.org/jira/browse/LUCENE-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223266#comment-15223266 ] Robert Muir commented on LUCENE-7167: - {quote} Robert Muir In this ticket, please make your wishes

[jira] [Commented] (LUCENE-7167) Re-engineer or remove all of geo3D

[ https://issues.apache.org/jira/browse/LUCENE-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223261#comment-15223261 ] Robert Muir commented on LUCENE-7167: - I'll list some one problem: Ryan already mentioned, why do

[jira] [Comment Edited] (LUCENE-7167) Re-engineer or remove all of geo3D

[ https://issues.apache.org/jira/browse/LUCENE-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223261#comment-15223261 ] Robert Muir edited comment on LUCENE-7167 at 4/3/16 12:56 PM: -- I'll list one

[JENKINS] Lucene-Solr-Tests-6.x - Build # 116 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-Tests-6.x/116/ 2 tests failed. FAILED: org.apache.solr.client.solrj.ConnectionReuseTest.test Error Message: We expected all communication via streaming client to use one connection! expected=65 got=62 Stack Trace: java.lang.AssertionError: We

[jira] [Commented] (LUCENE-7167) Re-engineer or remove all of geo3D

[ https://issues.apache.org/jira/browse/LUCENE-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223256#comment-15223256 ] Robert Muir commented on LUCENE-7167: - Why would we remove it when we can fix it? > Re-engineer or

Re: lucene-solr:lucene-7157: LUCENE_7157: current patch

No, I responded to the commit, because I already said on the ticket "i don't think a user should have to know about concaveness", and then I see GeoConcavePolygon.java added in this commit On Sun, Apr 3, 2016 at 8:40 AM, Karl Wright wrote: > Hi Robert, > > In case

[jira] [Commented] (LUCENE-7167) Re-engineer or remove all of geo3D

[ https://issues.apache.org/jira/browse/LUCENE-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223250#comment-15223250 ] Karl Wright commented on LUCENE-7167: - [~rcmuir] In this ticket, please make your wishes clear as to

[jira] [Created] (LUCENE-7167) Re-engineer or remove all of geo3D

Karl Wright created LUCENE-7167: --- Summary: Re-engineer or remove all of geo3D Key: LUCENE-7167 URL: https://issues.apache.org/jira/browse/LUCENE-7167 Project: Lucene - Core Issue Type: Task

Re: lucene-solr:lucene-7157: LUCENE_7157: current patch

My concern has everything to do with the ticket. Please back the change out. We are an API and so adding a public class is a very serious thing. On Sun, Apr 3, 2016 at 8:14 AM, Karl Wright wrote: > Robert, > > Your concern is noted but that has nothing really to do with this

[jira] [Commented] (SOLR-8812) ExtendedDismaxQParser (edismax) ignores Boolean OR when q.op=AND

[ https://issues.apache.org/jira/browse/SOLR-8812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223238#comment-15223238 ] Ishan Chattopadhyaya commented on SOLR-8812: How about initiating a 5.5.1 and 6.0.1 release

Re: lucene-solr:lucene-7157: LUCENE_7157: current patch

Why does this change need to add so many public classes? I already mentioned on the issue: the user need not concern themselves with these impl details. It is frustrating that this package has 60 public classes (and if everything is public, why the hell does it need factories?). Can we please

[jira] [Updated] (SOLR-8934) Spellchecker collaction should return in popular order

[ https://issues.apache.org/jira/browse/SOLR-8934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Solomon updated SOLR-8934: -- Priority: Minor (was: Trivial) > Spellchecker collaction should return in popular order >

[jira] [Created] (SOLR-8934) Spellchecker collaction should return in popular order

Michael Solomon created SOLR-8934: - Summary: Spellchecker collaction should return in popular order Key: SOLR-8934 URL: https://issues.apache.org/jira/browse/SOLR-8934 Project: Solr Issue

[jira] [Updated] (LUCENE-7157) Geo3DPoint implementation should pay attention to the ordering of lat/lon points

[ https://issues.apache.org/jira/browse/LUCENE-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated LUCENE-7157: Attachment: LUCENE-7157.diff Everything is now working. [~mikemccand]: This is ready for review.

[JENKINS] Lucene-Solr-Tests-master - Build # 1054 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-Tests-master/1054/ 1 tests failed. FAILED: org.apache.solr.cloud.overseer.ZkStateReaderTest.testStateFormatUpdateWithExplicitRefreshLazy Error Message: Could not find collection : c1 Stack Trace: org.apache.solr.common.SolrException: Could not

[jira] [Commented] (LUCENE-7132) BooleanQuery scores can be diff for same docs+sim when using coord (disagree with Explanation which doesn't change)

[ https://issues.apache.org/jira/browse/LUCENE-7132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223206#comment-15223206 ] Uwe Schindler commented on LUCENE-7132: --- I added

[jira] [Updated] (LUCENE-7157) Geo3DPoint implementation should pay attention to the ordering of lat/lon points

[ https://issues.apache.org/jira/browse/LUCENE-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated LUCENE-7157: Attachment: LUCENE-7157.diff No more hash-order dependencies, and fix some of the logical errors

[jira] [Commented] (SOLR-8803) OOM killer for Windows

[ https://issues.apache.org/jira/browse/SOLR-8803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223196#comment-15223196 ] jmlucjav commented on SOLR-8803: set an absolute path to oom_win.bat maybe? > OOM killer for Windows >

[JENKINS] Lucene-Solr-master-Solaris (64bit/jdk1.8.0) - Build # 498 - Still Failing!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-master-Solaris/498/ Java: 64bit/jdk1.8.0 -XX:-UseCompressedOops -XX:+UseParallelGC 1 tests failed. FAILED: org.apache.solr.cloud.overseer.ZkStateReaderTest.testStateFormatUpdateWithExplicitRefreshLazy Error Message: Could not find collection :

[JENKINS] Lucene-Solr-NightlyTests-6.x - Build # 28 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-6.x/28/ 9 tests failed. FAILED: org.apache.solr.cloud.CloudExitableDirectoryReaderTest.test Error Message: No live SolrServers available to handle this request:[https://127.0.0.1:38388/xi/j/collection1] Stack Trace:

[jira] [Comment Edited] (LUCENE-7132) BooleanQuery scores can be diff for same docs+sim when using coord (disagree with Explanation which doesn't change)

[ https://issues.apache.org/jira/browse/LUCENE-7132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223008#comment-15223008 ] Uwe Schindler edited comment on LUCENE-7132 at 4/3/16 8:36 AM: --- Here is