Suppressing Codecs

.UnsupportedOperationException: Lucene 4.0 -Houston Putman

Re: Suppressing Codecs

Fixed, thanks. On Tue, Jun 25, 2013 at 11:45 AM, Robert Muir wrote: > I think you also need to suppress "Appending". > > > On Tue, Jun 25, 2013 at 11:37 AM, Houston Putman > wrote: > >> In my testing code, how do I suppress all codecs that do not support >

Re: [VOTE] Release Lucene/Solr 8.10.0 RC1

SUCCESS! [1:04:04.335749] I also ran through some manual testing with the new s3-repository contrib using your convenience docker image, and it worked as expected. +1 On Fri, Sep 24, 2021 at 4:37 AM Namgyu Kim wrote: > +1 SUCCESS! [1:01:04.224368] > > On Thu, Sep 23, 2021 at 12:42 AM Timothy P

Re: Bugfix release Lucene/Solr 8.10.1

Hey Mayya, I think there are some issues with the lucene changelog entries in 8.10.1 across various branches (branch_8_10, branch_8x, and main). I don't see LUCENE-10119, and LUCENE-10126 is marked as an 8.11.0 entry in at least branch_8x. - Houston On Thu, Oct 7, 2021 at 9:32 PM Mayya Sharipova

Re: [VOTE] Release Lucene/Solr 8.10.1 RC1

+1 SUCCESS! [1:05:55.854939] On Thu, Oct 14, 2021 at 9:29 AM Michael Gibney wrote: > +1 SUCCESS! [1:00:31.099832] > > On Thu, Oct 14, 2021 at 7:42 AM Ignacio Vera wrote: > >> +1 >> >> SUCCESS! [1:01:50.808390] >> >> On Thu, Oct 14, 2021 at 1:40 PM Michael McCandless < >> luc...@mikemccandless.c

Re: [VOTE] Release Lucene/Solr 8.11.0 RC1

+1 SUCCESS! [1:04:19.544964] Also tested extensively with the Solr Operator. On Thu, Nov 11, 2021 at 1:06 PM Bruno Roustant wrote: > +1 > SUCCESS! [1:17:35.209577] > > Le jeu. 11 nov. 2021 à 18:30, Julie Tibshirani a > écrit : > >> +1 (nonbinding) >> SUCCESS! [1:04:58.967300] >> >> On Thu, Nov

Re: Welcome Julie Tibshirani to the Lucene PMC

Congrats Julie, welcome! On Wed, Dec 1, 2021 at 9:27 PM Nhat Nguyen wrote: > Congratulations, Julie! > > On Wed, Dec 1, 2021 at 1:17 PM Julie Tibshirani > wrote: > >> Thank you everyone. I'm really looking forward to contributing! >> >> Julie >> >> On Wed, Dec 1, 2021 at 9:39 AM Michael Wechner

Re: [VOTE] Release Lucene/Solr 8.11.1 RC1

SUCCESS! [1:10:32.826846] Also ran Jan's docker image using the Solr Operator and everything looked good to me. I also tested some of the fixes included in the release. +1 (binding) - Houston On Wed, Dec 15, 2021 at 3:42 PM Timothy Potter wrote: > Awesome, thanks Uwe! > > On Wed, Dec 15, 2021

Re: Welcome Haoyu (Patrick) Zhai as Lucene Committer

Congrats Haoyu! On Mon, Dec 20, 2021 at 12:42 PM Anshum Gupta wrote: > Congratulations and welcome, Haoyu! > > On Sun, Dec 19, 2021 at 1:12 AM Dawid Weiss wrote: > >> Hello everyone! >> >> Please welcome Haoyu Zhai as the latest Lucene committer. You may also >> know Haoyu as Patrick - this is

Mirroring the later 8.x release tags in the "new" split repositories

Hello all, As mentioned in SOLR-15874 , we are not hosting the tags for the latest 8.x releases in the split apache/solr and apache/lucene repositories. All release tags made prior to the repository split exist in the new repos, so I see no reason

Re: Mirroring the later 8.x release tags in the "new" split repositories

They don't have those commits, but they also don't have the commits for the previous release tags in the repo. You can go to any of the release tags, choose a commit to view and you will get a message saying: > This commit does not belong to any branch on this repository, > and may belong to a fo

Re: Mirroring the later 8.x release tags in the "new" split repositories

them. Since these projects > > share a common root, there is nothing to prevent this from happening. > > Then tags point at actual revisions and everything makes sense. > > > > This does not change the fact that I don't really see much value in > > doing all this.

Re: Welcome Guo Feng as Lucene committer

Congrats Feng! On Fri, Jan 28, 2022 at 12:31 AM Michael Gibney wrote: > Welcome, Feng! > > On Thu, Jan 27, 2022 at 2:23 PM Mayya Sharipova > wrote: > >> Welcome and congratulations, Feng! >> >> On Wed, Jan 26, 2022 at 11:50 AM Namgyu Kim wrote: >> >>> Congratulations and welcome, Feng! :D >>>

Re: Lucene PMC Chair Bruno Roustant

Congrats Bruno, and thanks Michael for doing such an incredible job! - Houston On Thu, Mar 24, 2022 at 10:45 AM Alessandro Benedetti wrote: > Thanks Michael for the amazing work last year! > Welcome Bruno, I am sure you'll do great! > Cheers > > On Thu, 24 Mar 2022, 09:23 Uwe Schindler, wrote:

Re: [DISCUSS] A proposal for migration to GitHub issue (LUCENE-10557)

> > It's not about features, but about accepting a new framework to me. GitHub > issue would not be a replacement Jira, and we cannot operate this project > on GitHub issue in the same way on Jira. We'd need to build our new > convention and operations on the new toolkit. > I think this is a very

Re: [DISCUSS] A proposal for migration to GitHub issue (LUCENE-10557)

github.com/helm/helm > > On Tue, May 10, 2022 at 10:16 AM Gus Heck wrote: > >> >> >> On Tue, May 10, 2022 at 10:40 AM Houston Putman >> wrote: >> >>> >>>> >>> Most modern open source projects use Github Issues for their iss

Re: [VOTE] Release Lucene 9.2.0 RC2

+1 SUCCESS! [2:17:07.370407] (java 11 & 17) - Houston On Fri, May 20, 2022 at 8:04 AM Jan Høydahl wrote: > +1 > > SUCCESS! [1:13:38.226868] > > Jan > > > 19. mai 2022 kl. 17:16 skrev Alan Woodward : > > > > Please vote for release candidate 2 for Lucene 9.2.0 > > > > The artifacts can be downl

Re: [VOTE] Migration to GitHub issue from Jira (LUCENE-10557)

+1 Approve (PMC) Thanks so much for doing all of the work for this Tomoko! - Houston On Mon, May 30, 2022 at 5:38 PM David Smiley wrote: > +1 Approve (PMC) > > ~ David Smiley > Apache Lucene/Solr Search Developer > http://www.linkedin.com/in/davidwsmiley > > > On Mon, May 30, 2022 at 11:40 AM

Re: Welcome Greg Miller to the Lucene PMC

Welcome Greg! On Tue, Jun 7, 2022 at 11:35 AM Gautam Worah wrote: > Congratulations Greg! > > On Tue, Jun 7, 2022 at 8:04 AM Patrick Zhai wrote: > >> Congrats Greg! >> >> Patrick >> >> On Tue, Jun 7, 2022, 07:53 Julie Tibshirani wrote: >> >>> Congratulations Greg!! >>> >>> On Tue, Jun 7, 2022

Re: Welcome Lu Xugang as Lucene committer

Congrats Lu! On Thu, Jun 2, 2022 at 4:09 PM Mikhail Khludnev wrote: > Welcome, Lu. > > On Wed, Jun 1, 2022 at 12:59 PM 陆徐刚 wrote: > >> Thanks Adrien for the announcement and all for the welcome! It’s a great >> honor for me be a Lucene committer. >> >> I live in ShangHai, China and work at EOI

Re: Welcome Chris Hegarty as Lucene committer

Congrats Chris! On Thu, Jun 2, 2022 at 4:07 PM Mikhail Khludnev wrote: > Welcome, Chirs! > > On Wed, Jun 1, 2022 at 10:29 AM Chris Hegarty > wrote: > >> Hi, >> >> I am both honoured and humbled to have been invited to become a >> committer. Thank you. >> >> I've been working on the development

Re: [VOTE] Release Lucene/Solr 8.11.2 RC1

+0 SUCCESS! [1:02:38.547629] I saw this in the example logs during the smoketester: > ps: Invalid process id: i��\r\001 > Waiting up to 180 seconds to see Solr running on port 8983 [/] > Started Solr server on port 8983 (pid=16758). Happy searching! > This seems related to SOLR-16191

Re: [VOTE] Release Lucene/Solr 8.11.2 RC2

+1 (binding) SUCCESS! [1:10:19.762602] - Houston On Wed, Jun 15, 2022 at 10:04 PM Anshum Gupta wrote: > Thanks for reporting that, Tim. > > Seems like this one is known to fail. I tried reproducing this w/ same > seed as well as randomizing, but wasn't able to do that over 100 runs. > > > On W

Re: Deleting old RCs

Definitely clean them up. It should be a step in the release wizard when aborting the failed RC or promoting the successful RC. (This is in the python code, not the yaml file.) I know it is in Solr, but maybe that got broken in the lucene release wizard after the split. Given the lucene-solr artif

Re: A prototype migration tool Jira to GitHub

> > Is there anybody who kindly provides a github account to make sure that > "any notifications are never triggered" when executing migration? I > confirmed this with my account, just wanted to test it with other one or > two accounts. > I've subscribed to all notifications for that sandbox-lucen

Re: [DISCUSS] Read-only Jira after the GitHub issues migration?

I think missing a few updates would be preferable to having 10k messages. Just my opinion though. On Tue, Jul 19, 2022 at 10:11 AM Tomoko Uchida wrote: > > 1. Make Jira read only >> >> At the very last step, we'll add comments saying "This was moved GitHub >> " to each Jira issue. It has to be d

Re: Welcome Vigya Sharma as Lucene committer

Welcome Vigya! On Mon, Aug 1, 2022 at 11:38 AM Alan Woodward wrote: > Congratulations and welcome, Vigya! > > - Alan > > On 28 Jul 2022, at 20:44, Vigya Sharma wrote: > > Thanks everyone for the warm welcome. It is an honor to be invited as a > Lucene committer, and I look forward to contributi

Re: Label vs. Milestone for version management?

So the Solr Operator has been using Github Issues for a few releases now, and the Milestone feature has worked really well for a blockers list. I agree that it should not be the canonical list of things that were included in that release (although it will likely be very close), but it is very good

Re: [VOTE] Release Lucene 9.4.1 RC1

SUCCESS! [0:47:29.586134] + 1 On Fri, Oct 21, 2022 at 10:33 AM Michael Sokolov wrote: > SUCCESS! [0:49:28.580122] > > +1 > > On Fri, Oct 21, 2022 at 5:57 AM Robert Muir wrote: > > > > I change my vote to +1 based on Julie's test. It fails for me with > > 9.4.0 and passes for me with 9.4.1 > >

Re: Lucene PMC Chair Greg Miller

Thanks Bruno, and good luck Greg! - Houston On Tue, Mar 7, 2023 at 3:29 PM Gus Heck wrote: > Congratulations Greg and thanks Bruno! > > On Tue, Mar 7, 2023 at 3:13 PM Tomás Fernández Löbbe < > tomasflo...@gmail.com> wrote: > >> Thanks Bruno! and Congratulations Greg! >> >> On Tue, Mar 7, 2023 a

Re: Running 10.0 build with a custom lucene 9.5

Gus, I haven't done this myself, but are you using the instructions provided in Solr's "gradle/lucene-dev/lucene-dev-repo-composite.gradle"? It looks like you need to specify the development lucene version differently than other dependencies... - Houston On Sat, May 13, 2023 at 10:14 AM Michael

Re: [VOTE] Dimension Limit for KNN Vectors

+1 on the combination of #3 and #4. Also good things to make sure of Uwe, thanks for calling those out. (Especially about the limit only being used on write, not on read). - Houston On Tue, May 16, 2023 at 9:57 AM Uwe Schindler wrote: > I agree with Dawid, > > I am +1 for those two options in

Re: JavaDoc generated with -noindex

Agreed, should be an easy change to include for 9.3. - Houston On Fri, Jul 7, 2023 at 5:42 PM Ishan Chattopadhyaya < ichattopadhy...@gmail.com> wrote: > +1 to include this in release. Thanks for noticing! > > On Sat, 8 Jul, 2023, 12:33 am Mike Drob, wrote: > >> Why is our javadoc currently gene

Re: JavaDoc generated with -noindex

Yeah my bad, didnt read which list it was. On Sun, Jul 9, 2023 at 10:19 AM Uwe Schindler wrote: > Isn't this about Lucene? So 9.8 is right version. > Am 07.07.2023 um 23:43 schrieb Houston Putman: > > Agreed, should be an easy change to include for 9.3. > > - Houston >

Final CFP Reminder: Community Over Code

Hello everyone, Today is the last day that you can submit a presentation for Community Over Code (formerly known as ApacheCon). Submissions will be accepted until 23:59:59 GMT. https://communityovercode.org/call-for-presentations/ There is a Search track that is perfect for presentations concern

Re: github milestones vs. releases mystery

Making a release in github is quite easy. You can do it from the release git tag, so it's "retroactive". (we can do it for 9.7.0 right now) For the release wizard, the Solr Operator has a section to do this: https://github.com/apache/solr-operator/blob/main/hack/release/wizard/releaseWizard.yaml#L

Bugfix release Lucene/Solr 8.11.3

NOTICE: I am now preparing for a bugfix release from branch branch_8_11 Please observe the normal rules for committing to this branch: * Before committing to the branch, reply to this thread and argue why the fix needs backporting and how long it will take. * All issues accepted for backportin

[VOTE] Release Lucene/Solr 8.11.3 RC1

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

Re: [VOTE] Release Lucene/Solr 8.11.3 RC1

gt;> >>> SUCCESS! [1:18:24.494917] >>> >>> On Wed, 7 Feb 2024 at 18:24, Jan Høydahl wrote: >>> >>>> +1 (binding) >>>> >>>> SUCCESS! [1:18:11.930433] >>>> >>>> Only ran smoke tester. macOS, Temurin 1.8.0

[RESULT] [VOTE] Release Lucene/Solr 8.11.3 RC1

It's been >72h since the vote was initiated and the result is: +1 6 (6 binding) 0 0 -1 0 This vote has PASSED

[ANNOUNCE] Apache Lucene 8.11.3 released

The Lucene PMC is pleased to announce the release of Apache Lucene 8.11.3. Apache Lucene is a high-performance, full-featured text search engine library written entirely in Java. It is a technology suitable for nearly any application that requires full-text search, especially cross-platform. This

Re: [Vote] Bump the Lucene main branch to Java 21

+1 - Houston On Mon, Feb 26, 2024 at 7:00 AM Jan Høydahl wrote: > +1 > > Jan > > 23. feb. 2024 kl. 20:01 skrev Patrick Zhai : > > +1 > > On Fri, Feb 23, 2024 at 9:34 AM Dawid Weiss wrote: > >> >> I'm fine with this requirement. >> >> +1. >> >> On Fri, Feb 23, 2024 at 12:24 PM Chris Hegarty >>

Re: [VOTE] Release Lucene 9.11.0 RC1

+1 SUCCESS! [1:49:36.192513] - Houston Putman On Wed, Jun 5, 2024 at 12:58 PM Michael McCandless < luc...@mikemccandless.com> wrote: > +1 SUCCESS! [0:24:55.332837] > > Mike McCandless > > http://blog.mikemccandless.com > > > On Wed, Jun 5, 2024 at 11:21 AM Adrien

Re: [VOTE] Release Lucene 9.11.1 RC1

+1 SUCCESS! [0:37:06.564011] - Houston On Tue, Jun 25, 2024 at 1:27 PM Anshum Gupta wrote: > +1 > > SUCCESS! [0:44:08.897482] > > On Sun, Jun 23, 2024 at 10:29 PM Ignacio Vera wrote: > >> Please vote for release candidate 1 for Lucene 9.11.1 >> >> >> The artifacts can be downloaded from: >> >

Bugfix release Lucene/Solr 8.11.4

NOTICE: I am now preparing for a bugfix release from branch branch_8_11 Please observe the normal rules for committing to this branch: * Before committing to the branch, reply to this thread and argue why the fix needs backporting and how long it will take. * All issues accepted for backportin

Adding env-var options for the Solr Prometheus Exporter

add, and we can make it sync with the naming convention used by the Solr start script. I'll probably create a JIRA and patch soon unless anyone has concerns or objections. - Houston Putman

Re: Adding env-var options for the Solr Prometheus Exporter

Yep, I'll work on that this afternoon. On Tue, Sep 17, 2019 at 12:24 PM Anshum Gupta wrote: > Sounds like a good idea, Houston. > Do you plan on creating a JIRA and PR ? > > On Tue, Sep 17, 2019 at 9:17 AM Houston Putman > wrote: > >> The startup options for the P

Re: Rethinking how we publish the Solr Ref Guide

odified date and links to the history of that page in github. That at least gives visibility to the changes, and it could show the date of the most recent update. I'm not sure how hard that would be to implement, but I would be happy to get something started if anyone else thinks it's a wor

Re: Solr jetty.port vs hostPort and host vs jetty.host

Thanks for pointing this out David. I was confused about the difference between the two when I tried to make solr work with kubernetes networking. From my understanding now, "jetty.port" is the actual port that the jetty solr server listens on. "hostPort" is the port that the solr node advertises

Re: Renaming SolrCloud

Jan, I agree strongly with your last point. And in case you haven't seen it before, there is a solr k8s operator, with a growing community, under development at https://github.com/bloomberg/solr-operator. I agree that taking control of the solr docker images could be a good idea. That way, it cou

Capturing URL params for use within Streaming Expressions

it's explicit that the user is trying to send options to the streaming expression, and extraneous URL params aren't accidentally captured when they were included for a different purpose. Anyways this would really help us for some uses cases, especially the replica routing options used in the example above. Really interested to see opinions on either of these options. - Houston Putman

Re: Capturing URL params for use within Streaming Expressions

rnstein > http://joelsolr.blogspot.com/ > > > On Wed, Oct 16, 2019 at 4:47 PM Houston Putman > wrote: > >> Streaming expressions allow for users to pass in any arbitrary URL params >> in the search streaming source. I'm looking to add the ability for certain &g

Re: Welcome Houston Putman as Lucene/Solr committer

environment, which includes making Solr itself run better in the cloud. I can’t wait to continue working with y’all and making Solr as great as it can be! - Houston Putman On Thu, Nov 14, 2019 at 2:24 PM Varun Thacker wrote: > Congratulations and welcome Houston! > > On Thu, Nov 14, 201

Re: Welcome Bruno Roustant as Lucene/Solr committer

Congrats Bruno, welcome! On Sat, Nov 23, 2019, 1:18 PM Namgyu Kim wrote: > Congratulations and welcome, Bruno! :D > > On Sun, Nov 24, 2019 at 2:16 AM Ishan Chattopadhyaya < > ichattopadhy...@gmail.com> wrote: > >> Welcome Bruno! >> >> On Sat, 23 Nov, 2019, 10:35 PM David Smiley, >> wrote: >> >>

Re: Congratulations to the new Lucene/Solr PMC Chair, Anshum Gupta!

Congrats Anshum!! On Thu, Jan 16, 2020, 8:51 AM Alan Woodward wrote: > Congratulations Anshum! > > On 15 Jan 2020, at 21:15, Cassandra Targett wrote: > > Every year, the Lucene PMC rotates the Lucene PMC chair and Apache Vice > President position. > > This year we have nominated and elected Ans

Re: Change solr/lucene Readme file format

Markdown is very standard at this point and I think the barrier to entry is very small, at least much smaller than asciidoc, which is used for the ref guide. +1 on this for me. On Wed, Jan 22, 2020 at 9:43 AM Doug Turnbull < dturnb...@opensourceconnections.com> wrote: > I think this got lost in

Re: 7.7.3 bugfix release

It looks like CVE-2019-17558 / SOLR-13971 has already been taken care of: https://issues.apache.org/jira/browse/SOLR-13971?focusedCommentId=17014356&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17014356 So now CVE-2019-0193 / SOLR-13669 should be the only blocker

Re: 7.7.3 bugfix release

n. That's my understanding as well. Please go ahead with the > backport. > > On Fri, 14 Feb, 2020, 9:02 PM Houston Putman, > wrote: > >> It looks like CVE-2019-17558 / SOLR-13971 has already been taken care of: >> https://issues.apache.org/jira/browse/SOLR-13971?

Re: Maintenance of Solr's official Dockerfile

I have a separate question about the release process. As I currently understand it, whenever docker-solr is released, every version in its configs is rebuilt and re-released. This means that v

Re: Maintenance of Solr's official Dockerfile

> The Apache Solr/Lucene binaries are still the exact same bits, we just >> change the base image — equivalent to upgrading Linux and Java on physical >> servers. >> Of course there could be bugs manifested with a certain combination of >> Linux + JRE + Solr that potentially

Updating a Response in the UpdateRequestProcessorChain

Hello everyone, As I currently understand it, there is no built in mechanism for UpdateRequestProcessors to add information to the response that is sent back to the user. It is possible to pass in the Response object to the UpdateRequestProcessor, through the corresponding UpdateRequestProcessorFa

Re: CHANGES.txt and issue categorization

+1 to move the entries. I would suggest that we document this organization somewhere though, so that future developers can adhere to the guidelines without finding this thread. I don't have a strong opinion on where this would go, maybe a legend at the top of CHANGES.txt or in the developer docs.

Re: [VOTE] Release Lucene/Solr 8.5.0 RC1

+1 Tested with Java 8. Smoke tester also did not work for me, as random unit tests would fail each time. Looked into each, and none looked like blockers. Manually ran the tests as well and got one failure that passed when running individually. On Tue, Mar 17, 2020 at 3:08 AM jim ferenczi wrote

Re: Welcome Alessandro Benedetti as a Lucene/Solr committer

Congrats Alessandro! On Wed, Mar 18, 2020 at 10:07 AM Tommaso Teofili wrote: > welcome on board Alessandro, well deserved! > I still remember when we were sitting together in the same room having fun > with Lucene/Solr a few years ago, keep up the good job ! > > Regards, > Tommaso > > On Wed, 18

Re: Welcome Eric Pugh as a Lucene/Solr committer

Congrats Eric! On Tue, Apr 7, 2020 at 9:57 AM Eric Pugh wrote: > Thank you everyone! I’ll keep it short, otherwise this will be a very > long email… ;-). > > I was first introduced to Solr and Lucene by Erik Hatcher, and today I > wonder what my life would be like if he hadn’t taken the time to

Re: [VOTE] Release Lucene/Solr 7.7.3 RC1

+1 SUCCESS! [1:23:37.392736] I also ran the multi-valued field performance test on 7.7.2 and 7.7.3 (rc1) to make sure that the backport of SOLR-14013 was successful. Definitely looks like it was. *Indexing test* 7.7.2 0m0.558s 7.7.3 0m0.926s

Re: Solr Admin UI Refresh 2020

I agree with Jan, I think we need some discussions on alternatives and the pros/cons of each before we invest in implementing a solution. I personally have the most experience with React and don't know much about other frameworks, but I'd love to understand why Angular or Vue.JS might be a better

Re: Welcome Mayya Sharipova as Lucene/Solr committer

Congrats Mayya! - Houston On Mon, Jun 8, 2020 at 1:30 PM Eric Pugh wrote: > Congratulations! Welcome! > > On Jun 8, 2020, at 1:26 PM, Steve Rowe wrote: > > Congrats and welcome, Mayya! > > -- > Steve > > On Jun 8, 2020, at 12:58 PM, jim ferenczi wrote: > > Hi all, > > Please join me in welco

Re: Welcome Ilan Ginzburg as Lucene/Solr committer

Welcome Ilan! On Mon, Jun 22, 2020 at 9:53 AM Michael Sokolov wrote: > Welcome Ilan! Nice beat on lonely boy there. > > > On Mon, Jun 22, 2020, 9:45 AM Ilan Ginzburg wrote: > >> Thank you, merci, תודה for the trust and the welcome, Noble and everybody! >> >> I’m based in France near Grenoble, a

Re: [VOTE] Release Lucene/Solr 8.6.0 RC1

+1 SUCCESS! [1:05:33.676744] Also built and tested a docker image using https://github.com/docker-solr/docker-solr: Completed all tests for dockersolr/docker-solr:8.6.0 On Thu, Jul 9, 2020 at 1:10 PM Anshum Gupta wrote: > +1 > > SUCCESS! [1:15:03.975368] > > On Wed, Jul 8, 2020 at 1:56 AM Bru

Re: 8.6.1 Release

+1 Question about the change. Since this patch added a default autoscaling policy, if users upgrade to 8.6 and then 8.6.1, does the default autoscaling policy stay once they have upgraded? If so we probably want to include instructions in the release notes on how to fix this issue once upgrading.

Re: 8.6.1 Release

m 8.6 to > > 8.6.1 get the earlier default policy? > > > > On Wed, Jul 22, 2020 at 9:09 PM Houston Putman > wrote: > > > > > > +1 > > > > > > Question about the change. Since this patch added a default > autoscaling policy, if users up

Re: Approach for a new Autoscaling framework

I think this is a valid thing to discuss on the dev list, since this isn't just about code comments. It seems to me that Ilan wants to discuss the philosophy around how to design plugins and the interfaces in Solr which the plugins will talk to. This is broad and affects much more than just the Aut

Re: 8.6.1 Release

ing of the issue? >> >> Le mer. 22 juil. 2020 à 20:08, Atri Sharma a écrit : >> >>> +1, thanks Houston. >>> >>> On Wed, Jul 22, 2020 at 10:51 PM Houston Putman >>> wrote: >>> > >>> > If we agree that this warrants a p

Re: 8.6.1 Release

> if he did this. But, it makes sense to inform them of the issue right away >>> anyway. >>> >>> On Wed, 22 Jul, 2020, 11:42 pm Ilan Ginzburg, >>> wrote: >>> >>>> Shouldn't we add a note right away to 8.6 notifying of the issue? >>

Re: 8.6.1 Release

;> >> Looking at >> https://github.com/apache/lucene-solr/commit/8e0eae2/#diff-de88ca16848af57d2474e04e26ea462cR90 >> , it seems like just upgrading to Solr 8.6.1 will be enough. >> >> >> >> On Fri, Jul 24, 2020 at 1:51 PM Houston Putman >&g

Re: Building Ref Guide on branch_8x

I can build on branch_8_6 without issue. And it looks like the offending line is the same on 8_6 and 8x. I am using: ruby 2.4.2p198 (2017-09-14 revision 59899) [x86_64-darwin16] jekyll (3.5.0) jekyll-asciidoc (3.0.0) slim (4.1.0) tilt (2.0.10) concurrent-ruby (1.1.6) Might be the jekyll-asciido

Re: 8.6.1 Release

ust > fixed it locally and made sure not to push that change. > > On Mon, Jul 27, 2020 at 12:57 PM Gus Heck wrote: > >> 8x docs not building smoothly on my laptop... (without changes) >> troubleshooting, checking deps listed in README.adoc, etc. >> >> On Mon, Jul 27, 20

Re: Building Ref Guide on branch_8x

ide gus$ git diff origin/branch_8_6 >> NS2-MacBook-Pro:solr-ref-guide gus$ git diff upstream/branch_8_6 >> NS2-MacBook-Pro:solr-ref-guide gus$ git status >> On branch branch_8_6 >> Your branch is up to date with 'origin/branch_8_6'. >> >> nothing to commit

Re: 8.6.1 Release

d fixed >> https://issues.apache.org/jira/browse/SOLR-14671 >> Can we include it in 8.6.1? >> >> Jan >> >> 27. jul. 2020 kl. 22:56 skrev Houston Putman : >> >> Added upgrade notes for the autoscaling stuff. >> >> Will begin the release proc

Re: 8.6.1 Release

o 8_6 https://github.com/apache/lucene-solr/pull/1704 if you want > to include it. > > On Mon, Jul 27, 2020 at 9:25 PM Houston Putman > wrote: > >> Both of those look good to include! >> >> Ill keep an eye out for when they get resolved. >> >&g

Re: 8.6.1 Release

revert a commit to a > file and maybe suppress a warning. I'll get this into 8.6.1 today. > > ~ David Smiley > Apache Lucene/Solr Search Developer > http://www.linkedin.com/in/davidwsmiley > > > On Wed, Jul 29, 2020 at 6:04 AM Jan Høydahl wrote: > >> Merg

Re: 8.6.1 Release

Search Developer > > http://www.linkedin.com/in/davidwsmiley > > > > > > On Wed, Jul 29, 2020 at 10:43 AM Houston Putman > wrote: > >> > >> Thanks Jan and David. > >> > >> I think that's the last issue. So after you commit it I'll

Re: 8.6.1 Release

ng a specific blocking issue in > 8.6. 8.7 would seem over arching? > > On Thu, 30 Jul 2020 at 20:33, Houston Putman > wrote: > >> I started the process last night. Is there a reason why you want this to >> make it into 8.6.1 and not 8.7? >> >> - Houston >

[VOTE] Release Lucene/Solr 8.6.1 RC1

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

Re: 8.6.1 Release

, 2020 at 11:51 AM Houston Putman wrote: > Ok, I'm finalizing the 8.6.1 release, so please do not push any commits > unless there is a large bug we have not yet identified. > > I'll be sending out the RC1 later today. > > - Houston > > On Thu, Jul 30, 2020 at 11:4

Re: [VOTE] Release Lucene/Solr 8.6.1 RC1

Due to the weekend the vote will be open until 2020-08-03 22:00 UTC. That's 96 hours, and two business days. I can leave the vote open for longer if people want an additional business day, but will end it on Monday otherwise. - Houston On Thu, Jul 30, 2020 at 5:07 PM Houston Putman

Re: 8.6.1 Release

ce/display/LUCENE/ReleaseNote861 >>> https://cwiki.apache.org/confluence/display/SOLR/ReleaseNote861 >>> >>> Any changes can be made there directly. >>> >>> - Houston >>> >>> On Thu, Jul 30, 2020 at 11:51 AM Houston Putman >>

Re: [VOTE] Release Lucene/Solr 8.6.1 RC1

one extra tag supported >>> for the tag cores in { >>> >>>> >>> >>>> "cores":"#EQUAL", >>> >>>> >>> >>>> "node":"#ANY", >>> >>>> >>> &

Re: 8.6.1 Release

ucene/Solr Search Developer > http://www.linkedin.com/in/davidwsmiley > > > On Sat, Aug 1, 2020 at 11:49 PM Houston Putman > wrote: > >> Its a manual process, but there are scripts available in the docker-solr >> repo to do it. >> >> The releases also have

Re: Migration of Lucene Jobs and Nodes

Do the precommit builds (PreCommit-LUCENE-Build and PreCommit-SOLR-Build ) need to be migrated as well? I noticed links to them when trying t

[VOTE] Release Lucene/Solr 8.6.1 RC2

Please vote for release candidate 2 for Lucene/Solr 8.6.1 The artifacts can be downloaded from: https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-8.6.1-RC2-rev6e11a1c3f0599f1c918bc69c4f51928d23160e99 You can run the smoke tester directly with this command: python3 -u dev-tools/scripts/sm

Re: [VOTE] Release Lucene/Solr 8.6.1 RC2

>> SUCCESS! [1:34:35.219332] >> >> +1 >> >> On Mon, Aug 10, 2020 at 1:02 PM Houston Putman >> wrote: >> >>> Please vote for release candidate 2 for Lucene/Solr 8.6.1 >>> >>> The artifacts can be downloaded from: >>> &g

Re: [VOTE] Release Lucene/Solr 8.6.1 RC2

ed w/ a 10 node cluster across a few local > machines and looked at the CHANGELOG. Everything LGTM on that front. > > +1 (binding) > > > On Mon, Aug 10, 2020 at 12:02 PM Houston Putman > wrote: > >> Please vote for release candidate 2 for Lucene/Solr 8.6.1 &g

[ANNOUNCE] Apache Lucene 8.6.1 released

The Lucene PMC is pleased to announce the release of Apache Lucene 8.6.1. Apache Lucene is a high-performance, full-featured text search engine library written entirely in Java. It is a technology suitable for nearly any application that requires full-text search, especially cross-platform. This

[ANNOUNCE] Apache Solr 8.6.1 released

The Lucene PMC is pleased to announce the release of Apache Solr 8.6.1. Solr is the popular, blazing fast, open source NoSQL search platform from the Apache Lucene project. Its major features include powerful full-text search, hit highlighting, faceted search, dynamic clustering, database integrat

Re: [VOTE] Release Lucene/Solr 8.6.2 RC1

+1 (non-binding) SUCCESS! [1:02:26.611225] On Thu, Aug 27, 2020 at 10:03 AM Simon Willnauer wrote: > +1 binding release looks good to me > > On Thu, Aug 27, 2020 at 3:58 PM Atri Sharma wrote: > > > > +1 (binding) > > > > SUCCESS! [1:14:17.24939] > > > > On Thu, 27 Aug 2020 at 18:41, Michael So

Re: Analytics Module; maybe should be 3rd party?

Thanks for bringing this up David. To start, I definitely agree that removal of contribs should have a discussion, then a vote before any action is taken. There have been a few bug fixes/improvements made this year, but there has not been a lot of development on it. If there is little use of the

Re: Analytics Module; maybe should be 3rd party?

Also I think that discussion around the use of a feature should take place on the user list, instead of the dev list. Users are the intended audience for that kind of question. - Houston On Mon, Aug 31, 2020 at 5:21 PM Houston Putman wrote: > Thanks for bringing this up David. > > To

Re: [VOTE] Lucene logo contest, here we go again

A1, A2, D (non-binding) On Tue, Sep 1, 2020 at 11:28 AM Steve Rowe wrote: > D (binding) > > -- > Steve > > On Aug 31, 2020, at 8:26 PM, Ryan Ernst wrote: > > Dear Lucene and Solr developers! > > In February a contest was started to design a new logo for Lucene > [jira-issue]. The initial attemp

  1   2   3   >