if for no other reason than to standardise on a sane trunk everyone can work on
+1 for backport to 8
From: Erick Erickson
Sent: Saturday, November 9, 2019 10:41 AM
To: dev@lucene.apache.org
Subject: Re: Gradle build
OK, see SOLR-13914. I figure to close SOLR-13
I was also invited to become admin. However I think we should allow any
Lucene/Solr committer to join the GitHub org, and keep the separate repo for
now.
Then after transitioning knowledge from Martijn through a release or two, we
could decide on further steps such as moving the repo to asf, re
: Ok, I expected something like this. Why are some test timing related? Are
there any informations about this.
multi-threaded code.
In the extreme case, Test falures may be timing related due to buggy race
conditions between multiple threads in "real code" (ie: very problematic
for end use
I was able to get the changes Dawid and I worked out in the gradle_7_refguide
branch merged into the gradle_8 branch.
There’s one current problem with it, which may be something in my env: in the
grade_7_refguide branch the HTML files were generated in
./solr/solr-ref-guide/build, but now they
Curator is adding support for it as well to speed up some of the existing
recipes. (one of the curator devs developed the persistent recursive watch
feature as far as I can tell). I think Zookeeper and Curator are trying to
get releases out by the end of the year from what I have been reading on
th
FYI, a big new feature landed in ZooKeeper just recently, "Persistent
Recursive Watch" -- https://issues.apache.org/jira/browse/ZOOKEEPER-1416
The fix-version is 3.6.0.
~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley
Created https://issues.apache.org/jira/browse/LUCENE-9041 - will post a
patch hopefully today. I'll look at 8.x as well.
Kevin Risden
On Sat, Nov 9, 2019 at 5:41 PM Uwe Schindler wrote:
> Interesting, 8.x uses 3.18... 🤔
>
> So let's upgrade both.
>
> Uwe
>
> Am November 9, 2019 10:38:33 PM UTC
I’m trying to push this forward. I intend to keep working on the latest branch
of Mark’s Gradle build (jira/SOLR-13452_gradle_8).
This is a plea for anyone interested to at least glance at any updates to that
JIRA and chime in if you have any hints. Also, feel free to update that branch
yoursel
MoveReplicaHDFSTest.test
LegacyCloudClusterPropTest.testCreateCollectionSwitchLegacyCloud
TestModelManagerPersistence
all fail more than 10%, MoveReplicaHDFSTest 50%.
BasicAuthIntegrationTest.testBasicAuth comes in at just under 10%.
Short form:
There were 147 unannotated tests that failed in Ho
Please don't email the dev list for this, just solr-user. Thanks and good
luck.
~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley
On Mon, Nov 11, 2019 at 2:00 AM Kayak28 wrote:
> Hello, Solr Community:
>
> I am using Solr7.4.0 which uses log4j (version
> On Nov 10, 2019, at 7:23 PM, Raphael Bircher wrote:
>
> So just reproducible issues go into jira? In my experience, it makes sense in
> some case, to write an issue für a ireproducible bug. So you can collect all
> data on one place. Sometimes this helps to track the bugs down.
It’s a judg
Hello, Community:
I am using Solr7.4.0 currently, and I was testing how Solr actually behaves
when it has a corrupted index.
And I used Luke to fix the broken index from GUI.
I just came up with the following questions.
Is it possible to use the repair index tool from CLI? (in the case, Solr
was o
12 matches
Mail list logo
