Re: Newbie task + request

Hi Jason, Thanks for the information, and the invitation to the Slack channel. Appreciate it. Pramod > On Jun 30, 2020, at 5:04 AM, Jason Gerlowski wrote: > > Hi Pramod, > > I'm pretty sure Erick answered some of your questions on the > SOLR-13205 jira already, but I wanted to restate those

Re: SolrCloud upgrade process

At the Lucene level, it was deemed too much of a PITA to retain the older writing code in future versions. I think maybe this was re-discussed in the last year. I sympathize. ~ David On Tue, Jun 30, 2020 at 6:30 PM Ilan Ginzburg wrote: > If there could be a way to force the new version to

Re: SolrCloud upgrade process

If there could be a way to force the new version to continue writing in the previous format for a while, that would allow switching to writing the new format once all nodes have been upgraded (or more likely when the cluster admin decides so). Ilan Le mar. 30 juin 2020 à 21:34, David Smiley a

SolrCloud upgrade process

I was considering the process of a Solr upgrade to a SolrCloud cluster within a minor version (e.g. 8.3 -> 8.4). A concern I have is the implication of new Lucene index formats. Lucene 8.4 bumped the Codec version because of postings being written differently to be more SIMD friendly --

Re: PGP key to sign the 8.6 branch

I signed and sent the updated key to the ubuntu & sks-keyservers servers. Before signing, via other communication channels, I verified that the hexadecimal key ID was authentic. ~ David Smiley Apache Lucene/Solr Search Developer http://www.linkedin.com/in/davidwsmiley On Tue, Jun 30, 2020 at

Re: 8.6 release

Erick: AFAIK yes from now on a commit in branch_8x will not go to 8.6 branch. Le mar. 30 juin 2020 à 17:59, Erick Erickson a écrit : > Bruno: > > Just to double check, anything committed to branch_8x from here on won’t > affect the 8.6 release unless explicitly backported, correct? > > I may be

Re: 8.6 release

Bruno: Just to double check, anything committed to branch_8x from here on won’t affect the 8.6 release unless explicitly backported, correct? I may be close to upgrading Zookeeper to 3.6.1, and very much do NOT want it in the 8.6 release as it should bake longer than 2 weeks even… Thanks for

Re: 8.6 release

For the RC, I prefer to let the latest and greatest commits to bake a week rather than only 2 days. Some of them have important impact and were added very recently. So I plan a RC on July 7, if the smoke tester is fixed before that time. Bruno Le mar. 30 juin 2020 à 16:48, Uwe Schindler a écrit

RE: 8.6 release

Hi, I enabled builds for 8.6 on Policeman Jenkins: https://jenkins.thetaphi.de/job/Lucene-Solr-8.6-Linux/ https://jenkins.thetaphi.de/job/Lucene-Solr-8.6-MacOSX/ https://jenkins.thetaphi.de/job/Lucene-Solr-8.6-Windows/ Uwe

New branch and feature freeze for Lucene/Solr 8.6.0

NOTICE: Branch branch_8_6 has been cut and versions updated to 8.7 on stable branch. Please observe the normal rules: * No new features may be committed to the branch. * Documentation patches, build patches and serious bug fixes may be committed to the branch. However, you should submit all

Re: [JENKINS] Lucene-Solr-repro-Java11 - Build # 1162 - Still Failing

I had previously opened https://issues.apache.org/jira/browse/INFRA-20452 and https://issues.apache.org/jira/browse/LUCENE-9412 for this. Any more details posted there would be appreciated! On Tue, Jun 30, 2020 at 8:23 AM Jan Høydahl wrote: > @Bruno > > Note that the smoke tester is not happy,

Re: [JENKINS] Lucene-Solr-repro-Java11 - Build # 1162 - Still Failing

@Bruno Note that the smoke tester is not happy, so someone needs to fix it before the release can be made. I sent this email to dev list June 19th but no progress. Looking into it again, I see that some Jenkins smoketest runs succeeds and some fail. I think I have found a pattern that all the

Re: 8.6 release

[new branch] 0a1f68fafd6711304bbd7372567a359bcf36aab4 -> branch_8_6 Le mar. 30 juin 2020 à 14:59, Bruno Roustant a écrit : > I'm creating the branch_8_6 with the release wizard. > > Le mar. 30 juin 2020 à 12:37, Ishan Chattopadhyaya < > ichattopadhy...@gmail.com> a écrit : > >> This is

Re: 8.6 release

I'm creating the branch_8_6 with the release wizard. Le mar. 30 juin 2020 à 12:37, Ishan Chattopadhyaya < ichattopadhy...@gmail.com> a écrit : > This is done and merged. Thanks. > > On Tue, Jun 30, 2020 at 11:52 AM Ishan Chattopadhyaya < > ichattopadhy...@gmail.com> wrote: > >> Hi Bruno, >> I'd

Re: [JENKINS] Lucene-Solr-NightlyTests-master - Build # 2239 - Still Unstable

I committed a fix for these failing @Nightly tests, caused by SOLR-14561 > 30. jun. 2020 kl. 12:56 skrev Apache Jenkins Server > : > > Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-master/2239/ > > 2 tests failed. > FAILED:

Re: Newbie task + request

Hi Pramod, I'm pretty sure Erick answered some of your questions on the SOLR-13205 jira already, but I wanted to restate those answers here for other beginners that may be reading this thread or stumble on it later. The way our project is set up, only "committers" can assign tickets in JIRA. In

Re: 8.6 release

This is done and merged. Thanks. On Tue, Jun 30, 2020 at 11:52 AM Ishan Chattopadhyaya < ichattopadhy...@gmail.com> wrote: > Hi Bruno, > I'd like to get SOLR-14599 in. It is for the package manager CLI support > for cluster level (core container) level plugins. I think it is important > to have

Re: PGP key to sign the 8.6 branch

I uploaded my key (6AD29C0A) to keyserver.ubuntu.com, pgp.surfnet.nl and hkps.pool.sks-keyservers.net and it can be retrieved now: gpg --verbose --keyserver keyserver.ubuntu.com --recv-keys 6AD29C0A gpg: data source: http://162.213.33.9:11371 gpg: pub rsa4096/377C3BA26AD29C0A 2020-06-26 Bruno

Re: 8.6 release

Hi Bruno, I'd like to get SOLR-14599 in. It is for the package manager CLI support for cluster level (core container) level plugins. I think it is important to have this in 8.6 for two reasons: (a) it will unblock Marcus Eagan/Ke Zhenxu who are working on a new Solr UI package and would like to