You can run into this fairly easily even if you are doing everything right
and none of your operations are intrinsically slow or problematic.
DeleteByQuery, regardless of its cost, tends to be a large contributor,
though not always. You can mitigate a bit with cautious, controlled use of
it.
I’m
I'm working on some features that involve changes to both Lucene and
Solr. Post-TLP-split, I'm wondering whether anyone has recommended
techniques to handle this kind of situation.
Ideally one would work on Lucene changes, get them merged, and then
proceed with Solr development; but realistically
On 5/25/2021 8:12 PM, Shawn Heisey wrote:
I have asked on slack #asfinfra whether Apache has anything set up for
cloaks. That does exist for freenode. A /whois for me on freenode
includes the following:
They do have cloaks set up. In the following location:
https://svn.apache.org/repos/pri
I'm investigating this one; it's related to a change I made.
~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley
On Tue, May 25, 2021 at 12:06 PM Policeman Jenkins Server <
jenk...@thetaphi.de> wrote:
> Build: https://jenkins.thetaphi.de/job/Solr-main-Linu
Hi all,
It is now committed: Solr now uses a prerelease build of Lucene (number 5),
built by ASF Jenkins and published on ASF Nighlies server (a dump for arbitrary
files, we also publish the refguide there):
https://nightlies.apache.org/solr/lucene-prereleases/
Important:
* If any
I opened:
https://issues.apache.org/jira/browse/LUCENE-9977
and for Solr:
https://issues.apache.org/jira/browse/SOLR-15436
-
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail: u...@thetaphi.de
From: Uwe Schindler
Sent: Wednesday, May 26, 2021 11:01 AM
