Re: [JENKINS] Lucene-Solr-BadApples-Tests-8.x - Build # 261 - Still Unstable

2019-11-01 Thread Tomás Fernández Löbbe
I pushed a fix for this On Fri, Nov 1, 2019 at 5:17 PM Apache Jenkins Server < jenk...@builds.apache.org> wrote: > Build: https://builds.apache.org/job/Lucene-Solr-BadApples-Tests-8.x/261/ > > 1 tests failed. > FAILED: > org.apache.solr.util.SolrPluginUtilsTest.testMinShouldMatchBadQueries > > Er

***UNCHECKED*** SolrCloud is sick.

2019-11-01 Thread Mark Miller
Hey All Solr Dev's, SolrCloud is sick right now. The way low level Zookeeper is handeled, the Overseer, is mix and mess of proper exception handling and super slow startup and shutdown, adding new things all the time with no concern for performance or proper ordering (which is harder to tell than

Re: [JENKINS] Lucene-Solr-8.x-Linux (64bit/jdk-12.0.1) - Build # 1434 - Failure!

2019-11-01 Thread Mikhail Khludnev
I'm on it. On Fri, Nov 1, 2019 at 3:53 PM Policeman Jenkins Server wrote: > Build: https://jenkins.thetaphi.de/job/Lucene-Solr-8.x-Linux/1434/ > Java: 64bit/jdk-12.0.1 -XX:-UseCompressedOops -XX:+UseG1GC > > All tests passed > > Build Log: > [...truncated 9780 lines...] > [javac] Compiling 2

Re: Duplicate jira emails for watched issues?

2019-11-01 Thread Alexandre Rafalovitch
Yes, I love the watched feature as well and filter all watched emails into a separate folder. But the filter stopped working and I thought it was because LUCENE's mail template was different from SOLR somehow. So, my filters were not triggering. Turned out to be that I was just getting LUCENE noti

Re: [VOTE] Release Lucene/Solr 8.3.0 RC2

2019-11-01 Thread Ishan Chattopadhyaya
Right, didn't start a new thread just for the result of this vote. I think such a thread has limited value and seems to be very sparingly followed. As of now, I'm waiting for mirrors to sync up (I'll wait few hours more) and working on curating the changelog, updating the website etc. Thanks and re

Re: [VOTE] Release Lucene/Solr 8.3.0 RC2

2019-11-01 Thread Jan Høydahl
I have not seen the vote result thread yet? Jan Høydahl > 30. okt. 2019 kl. 22:46 skrev Ishan Chattopadhyaya > : > >  > Thanks to all who voted. The vote has passed. I'll proceed to publish the > artifacts next. > >> On Thu, 31 Oct, 2019, 2:44 AM Adrien Grand, wrote: >> Ishan, should we clo

Re: forceMerge and unused metadata

2019-11-01 Thread David Smiley
To follow-up in a more official channel than Slack, I suggested that the JIRA issue for this request is: https://issues.apache.org/jira/browse/LUCENE-8551 ~ David Smiley Apache Lucene/Solr Search Developer http://www.linkedin.com/in/davidwsmiley On Tue, Oct 29, 2019 at 6:19 PM Shawn Heisey wrot

RE: Duplicate jira emails for watched issues?

2019-11-01 Thread Uwe Schindler
That’s exactly the same for me. All issues go (by filter) to the folder of the issues mailing list. Those I am directly involved or those I explicitly watch go to my personal inbox. So the stuff important to me is getting correct attention. Uwe - Uwe Schindler Achterdiek 19, D-2

Re: Duplicate jira emails for watched issues?

2019-11-01 Thread David Smiley
Personally, I like this behavior very much. When I "watch" an issue in JIRA, I want to ensure I am more aware of this issue than some random JIRA I have never even seen before. I also like auto-watch. I can manually un-watch an issue if I choose to step away from an issue; though it's very rare