Re: Welcome Munendra SN to the PMC

Thank you all Regards, Munendra S N On Wed, Aug 5, 2020 at 8:45 PM Michael McCandless wrote: > Welcome Munendra! > > Mike McCandless > > http://blog.mikemccandless.com > > > On Tue, Aug 4, 2020 at 5:09 PM David Smiley wrote: > >> Welcome Munendra! >> >> ~ David Smiley >> Apache Lucene/Solr S

Re: Welcome Namgyu Kim to the PMC

Congratulations Namgyu! Regards, Munendra S N On Wed, Aug 5, 2020 at 8:47 PM Michael McCandless wrote: > Welcome Namgyu! > > Mike McCandless > > http://blog.mikemccandless.com > > > On Tue, Aug 4, 2020 at 5:08 PM David Smiley wrote: > >> Welcome Namgyu! >> >> ~ David Smiley >> Apache Lucene/

Re: Welcome Gus Heck to the PMC

Congratulations Gus! Regards, Munendra S N On Wed, Aug 5, 2020 at 8:46 PM Michael McCandless wrote: > Welcome Gus! > > Mike McCandless > > http://blog.mikemccandless.com > > > On Tue, Aug 4, 2020 at 5:09 PM David Smiley wrote: > >> Welcome Gus! >> >> ~ David Smiley >> Apache Lucene/Solr Sear

Re: Standardize Leading Test or Trailing Test

+1 On Wed, Aug 5, 2020 at 10:37 PM David Smiley wrote: > +1 to standardize on something. > This has been brought up before: LUCENE-8626 > -- credit to > Christine who started the work. I recommend resuming the discussion there. > > ~ David > >

Re: Standardize Leading Test or Trailing Test

+1 to standardize on something. This has been brought up before: LUCENE-8626 -- credit to Christine who started the work. I recommend resuming the discussion there. ~ David On Thu, Aug 6, 2020 at 12:08 AM Anshum Gupta wrote: > +1 > > Thanks

Re: First Issue Label

There used to be a 'newdev' label in the past that fell through the cracks. https://cwiki.apache.org/confluence/display/LUCENE/HowToContribute mentions the label, but of course, not a ton of JIRAs exist with that label for new devs to pick up and run with. We could start using the label. I persona

Re: Standardize Leading Test or Trailing Test

+1 Thanks for bringing this up, Marcus. Standardizing this is really great. On Wed, Aug 5, 2020 at 8:01 PM Marcus Eagan wrote: > Hi community, what do you think a small effort to standardize on leading > with the word "Test" or trailing with the word "Test" in the repo. Most > projects do one o

Re: Standardize Leading Test or Trailing Test

This is almost a comical level of inconsistency in our code! On Wed, Aug 5, 2020 at 10:35 PM Robert Muir wrote: > > > On Wed, Aug 5, 2020 at 11:25 PM Mike Drob wrote: > >> +1 >> >> This is something I’ve been annoyed with before but then never did >> anything about. >> >> My suggestion would be

Re: Standardize Leading Test or Trailing Test

On Wed, Aug 5, 2020 at 11:25 PM Mike Drob wrote: > +1 > > This is something I’ve been annoyed with before but then never did > anything about. > > My suggestion would be to end class names with Test and start method names > with test. I think LuceneTestCase already checks for the latter. > > Pers

Re: Standardize Leading Test or Trailing Test

+1 Maybe we can add naming rules for test classes on check-source-patterns.groovy? https://github.com/apache/lucene-solr/blob/f03e6aac59cbdb0422aa05047fbc1c4bc5324cd9/lucene/tools/src/groovy/check-source-patterns.groovy Tomoko 2020年8月6日(木) 12:17 Robert Muir : > +1 > > There is no good reason t

Re: Standardize Leading Test or Trailing Test

+1 This is something I’ve been annoyed with before but then never did anything about. My suggestion would be to end class names with Test and start method names with test. I think LuceneTestCase already checks for the latter. Mike On Wed, Aug 5, 2020 at 10:17 PM Robert Muir wrote: > +1 > > Th

Re: Standardize Leading Test or Trailing Test

+1 There is no good reason to name the source files inconsistently. It should be as easy as possible to do things with the tests with regular expressions, simple tools like grep and so on. Ideally we can fail the build if one tries to get added in the wrong way (some kind of precommit check: simp

Re: First Issue Label

I think we already had some. But nobody really jumped on it. Still, if somebody wants to monitor it, it can be restarted. Regards, Alex On Wed., Aug. 5, 2020, 11:04 p.m. Marcus Eagan, wrote: > Community, > > In the vane of more developer friendly, I think we should create a first > issue la

First Issue Label

Community, In the vane of more developer friendly, I think we should create a first issue label. In my experience, that label has been a great way to get newcomers involved in projects new to them. I've seen it in a number of Apache projects that I have contributed to, proprietary projects, and i

Standardize Leading Test or Trailing Test

Hi community, what do you think a small effort to standardize on leading with the word "Test" or trailing with the word "Test" in the repo. Most projects do one or the other and it has an impact on developer productivity. I'll explain my use case: I'm working on a class and I want to modify the te

When zero offsets are not bad - a.k.a. multi-token synonyms yet again

Hello devs, I wanted to create an issue but the helpful message in red letters reminded me to ask first. While porting from lucene 6.x to 7x I'm struggling with a change that was introduced in LUCENE-7626 (https://issues.apache.org/jira/browse/LUCENE-7626) It is believed that zero offset tokens

Re: SolrClient and making requests asynchronously

On Sun, Aug 2, 2020 at 10:47 AM Atri Sharma wrote: > I am +1 to this approach. Some thoughts inline. > > How would query timeout be respected in this approach? > The backend would need to "complete exceptionally" with a timeout exception we think is appropriate. It'd call completableFuture.com

RE: [JENKINS] Lucene » Solr-reference-guide-8.6 - Build # 6 - Still Failing!

I disabled the reference guide jobs for now until Infra has fixed the access rights on the secondary documentation jenkins node. Uwe - Uwe Schindler Achterdiek 19, D-28357 Bremen https://www.thetaphi.de eMail: u...@thetaphi.de > -Original Message- > From: Apache Jenkins Server > Se

Re: [VOTE] Release Lucene/Solr 8.6.1 RC1

Bravo to Gus for doing a more thorough examination of the release to see there is a serious problem! ~ David Smiley Apache Lucene/Solr Search Developer http://www.linkedin.com/in/davidwsmiley On Mon, Aug 3, 2020 at 12:36 AM Gus Heck wrote: > Digging a little further, I notice that the deploymen

Re: Deprecate Schemaless Mode?

As David said, I did a lot of breaking apart of default configuration and it is a bit of a mess in there. (if anybody wants to review the breakdown for Solr 6: https://www.slideshare.net/arafalov/rebuilding-solr-6-examples-layer-by-layer-lucenesolrrevolution-2016, slide 19 is the kicker) I certain

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

Re: Welcome Namgyu Kim to the PMC

Welcome Namgyu! Mike McCandless http://blog.mikemccandless.com On Tue, Aug 4, 2020 at 5:08 PM David Smiley wrote: > Welcome Namgyu! > > ~ David Smiley > Apache Lucene/Solr Search Developer > http://www.linkedin.com/in/davidwsmiley > > > On Sun, Aug 2, 2020 at 7:20 PM Ishan Chattopadhyaya < >

Re: Welcome Gus Heck to the PMC

Welcome Gus! Mike McCandless http://blog.mikemccandless.com On Tue, Aug 4, 2020 at 5:09 PM David Smiley wrote: > Welcome Gus! > > ~ David Smiley > Apache Lucene/Solr Search Developer > http://www.linkedin.com/in/davidwsmiley > > > On Sun, Aug 2, 2020 at 7:21 PM Ishan Chattopadhyaya < > ichatt

Re: Welcome Munendra SN to the PMC

Welcome Munendra! Mike McCandless http://blog.mikemccandless.com On Tue, Aug 4, 2020 at 5:09 PM David Smiley wrote: > Welcome Munendra! > > ~ David Smiley > Apache Lucene/Solr Search Developer > http://www.linkedin.com/in/davidwsmiley > > > On Sun, Aug 2, 2020 at 7:20 PM Ishan Chattopadhyaya

RE: Your project websites

Hi Andrew, Lucene/Solr no longer uses the old Apache CMS and switched to Pelican half a year ago. But before deleting any stuff keep in mind, that some static parts (not CMS-related) like Javadocs are still saved in a huge SVN repository (the former CMS production repo). Those approx 20 Giga

Your project websites

Hi: I am part of the Infrastructure team, and am writing to ask whether your project is still using the Apache CMS for your project websites. As you know, the CMS is reaching end-of-life, and we need projects to move their websites onto a different option within the next few weeks. There are seve

RE: Migration of Lucene Jobs and Nodes

Hi, Gavin and I moved all the Lucene builds to the new Cloudbees ASF Jenkins. The root URL is: https://ci-builds.apache.org/job/Lucene/ All PMC members should be able to access it. There are still some minor issues, like we need to cleanup o

RE: [JENKINS] Lucene » Solr-reference-guide-8.6 - Build # 3 - Still Failing!

Hi, we automatically migrated all builds to the new ASF build server. It looks like the documentation builds have some problems in the shell script (permission denied). I have no idea how those builds work, so maybe Steve Rowe / Cassandra Target can fix it. Ping me on Slack! Uwe - Uwe Sch

RE: Migration of Lucene Jobs and Nodes

Hi Gavin, many thanks was very helpful. In the meantime I was also able to get JOB configs through the REST API (just append config.xml to the JOB URL on the old Jenkins), but thanks to your work, it makes it easier for me to review what we have. >From what I found out the jobs should mo

Re: Migration of Lucene Jobs and Nodes

Hi Uwe, On Tue, Aug 4, 2020 at 6:12 PM Uwe Schindler wrote: > Sorry still busy… > > > > Can you create the folder for Lucene and maybe export the jobs’ XML. They > are about 20 jobs all with Regex /^(Lucene|Solr)-.*/ > I found 57 config.xml files related to Lucene and Solr > > > You can attac