Re: [VOTE] Release Lucene/Solr 8.10.0 RC1

+1 SUCCESS! [1:06:53.158391] On Wed, Sep 22, 2021 at 5:42 PM Cassandra Targett wrote: > OK, they’re fixed in SVN but will take a few minutes to get propagate out > to the site. I’ll check in a little bit after dinner. > On Sep 22, 2021, 4:34 PM -0500, Cassandra Targett , > wrote: > > Because

Re: [VOTE] Release Lucene/Solr 8.10.0 RC1

OK, they’re fixed in SVN but will take a few minutes to get propagate out to the site. I’ll check in a little bit after dinner. On Sep 22, 2021, 4:34 PM -0500, Cassandra Targett , wrote: > Because when I tried to fix my initial mistake I only updated the HTML pages > and thought I could skip

Re: [VOTE] Release Lucene/Solr 8.10.0 RC1

Because when I tried to fix my initial mistake I only updated the HTML pages and thought I could skip updating the image dir but forgot there are new ones :-| I’ll fix it now. On Sep 22, 2021, 3:45 PM -0500, Timothy Potter , wrote: > Thank you Cassandra! Any idea why the schema designer images

Re: [VOTE] Release Lucene/Solr 8.10.0 RC1

Thank you Cassandra! Any idea why the schema designer images are showing as broken links? https://solr.apache.org/guide/8_10/schema-designer.html ... the images are in images/schema-designer On Wed, Sep 22, 2021 at 2:31 PM Cassandra Targett wrote: > > I uploaded the 8.10 Ref Guide to

Re: [VOTE] Release Lucene/Solr 8.10.0 RC1

I uploaded the 8.10 Ref Guide to https://solr.apache.org/guide/8_10/ in DRAFT while we’re voting on the release. I accidentally first uploaded a version of the Ref Guide built on `main` branch back in March (a leftover from before the project split that didn’t get caught with `ant clean`). I’m

Re: [VOTE] Release Lucene/Solr 8.10.0 RC1

+1 SUCCESS! [1:09:04.477915] Just ran smoke tester. Jan > 22. sep. 2021 kl. 17:41 skrev Timothy Potter : > > Please vote for release candidate 1 for Lucene/Solr 8.10.0 > > The artifacts can be downloaded from: >

Re: Soften Jira's note when opening new issues?

Hmm. How is this? It is a single longer sentence, but essentially a string of simple ones. If you want help or have a feature idea, please ask on the mailing list or IRC channel before submitting a Jira issue. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my

Re: Soften Jira's note when opening new issues?

Greg, I understand and agree with the intent, but I also would like to keep this as short as possible since the screen to create a new issue in JIRA is already quite intimidating with all its text boxes, and the current version is already taking two lines even though it's short. Maybe this is the

Re: Soften Jira's note when opening new issues?

Two excellent points. So it could be: Are you looking for support for Lucene? Have you seen unexpected behavior? Have an idea for a new feature or improvement? Please ask for help on the Lucene user mailing list or the IRC channel. If it is a new problem or idea, then you can submit a Jira

[VOTE] Release Lucene/Solr 8.10.0 RC1

Please vote for release candidate 1 for Lucene/Solr 8.10.0 The artifacts can be downloaded from: https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-8.10.0-RC1-rev377e7349979f8e418eacf03f1379b3dfacf7cccb You can run the smoke tester directly with this command: python3 -u

Re: Soften Jira's note when opening new issues?

Love this idea! I wonder if there's a way to make the messaging clear that ideas for new features/improvements are also always welcome? When I read the current language, I interpret it as bug reporting. Maybe adding a leading sentence would help? ``` Bug reports, improvements and new feature

Re: Accessibility of MergeThread.rateLimiter

Hi Adrien, > On 22 Sep 2021, at 12:56, Adrien Grand wrote: > > You interpreted my suggestion correctly. Great. Thanks for the confirmation. I filed the following issue to track this: https://issues.apache.org/jira/browse/LUCENE-10118 >

Re: Soften Jira's note when opening new issues?

Hi Walter, Though it doesn't invalidate your comment, I was considering changing the message only for the Lucene JIRA, at least for now. On Tue, Sep 21, 2021 at 5:08 PM Walter Underwood wrote: > Here is one with shorter, less complex sentences and clear calls to action. > > Are you looking for

Re: Accessibility of MergeThread.rateLimiter

You interpreted my suggestion correctly. Elasticsearch can indeed leverage information that is sent to the InfoStream: look up the class called LoggerInfoStream, which forwards all the InfoStream logging to Log4J. On Wed, Sep 22, 2021 at 1:40 PM Chris Hegarty wrote: > Hi Adrien, > > Great

Re: Accessibility of MergeThread.rateLimiter

Hi Adrien, Great suggestion. If I understand correctly, then what you are suggesting is something along the lines of ( subject to exact message details, which we can trash out in a PR ): diff --git a/lucene/core/src/java/org/apache/lucene/index/ConcurrentMergeScheduler.java

Re: Accessibility of MergeThread.rateLimiter

Hi Chris, I looked into this and Elasticsearch seems to only need access to the rate limiter for logging purposes, without adding any information that Lucene doesn't have. Maybe another option would consist of moving the logging to Lucene? Having information in the IndexWriter's InfoStream about

Accessibility of MergeThread.rateLimiter

In an effort to prepare Elasticsearch for modularization, we are investigating and eliminating split packages. The situation has improved through recent refactoring in Lucene 9.0, but a number of split packages still remain. This message identifies one such, so that it can be discussed in