Re: Review Request 28826: SOLR-6625: HttpClient callback in HttpSolrServer

/src/java/org/apache/solr/util/SolrCLI.java https://reviews.apache.org/r/28826/#comment106933 requestCallback is not used in this method. Is that intentional? Probably need to add the callback to line 432. - Mike Drob On Dec. 8, 2014, 10:25 p.m., Gregory Chanan wrote

Re: Review Request 28826: SOLR-6625: HttpClient callback in HttpSolrServer

On Dec. 8, 2014, 11:04 p.m., Mike Drob wrote: Which branch is this against? It doesn't apply to Ignore the branch question - I had a dirty workspace and didn't realize it. - Mike --- This is an automatically generated e-mail

Re: Querying locally before sending a distributed request

This is a cool idea, and there are two extremes to consider. One-shard, N replicas, single connection point for consumers. This case needs forwarding. Many shards, 2 replicas each, random connection points for consumers. I think this is the case that SG had in mind. In order to meet both use

Static Analysis Tooling

Devs, I'd like to bring up static analysis for Solr and Lucene again. It's been about a year since the last conversation[1] and it might be time to revisit. There is a JIRA issue too[2], but it's also in need of some love. ASF already provides a Sonar instance that we might be able to use[3],

Re: Static Analysis Tooling

this is tracked as https://issues.apache.org/jira/browse/LUCENE-3973 ~ David Smiley Freelance Apache Lucene/Solr Search Consultant/Developer http://www.linkedin.com/in/davidwsmiley On Thu, Feb 5, 2015 at 12:43 PM, Mike Drob md...@apache.org wrote: Devs, I'd like to bring up static analysis for Solr

Re: [jira] [Comment Edited] (SOLR-6673) MDC based logging of collection, shard etc.

For Eclipse you can get it but only automatically on a save. Preferences Java Editor Save Actions. If you don't like the changes that it makes, I've found that you can undo and save again, and it won't re-format. On Mon, Mar 9, 2015 at 11:38 AM, Mark Miller markrmil...@gmail.com wrote:

Ant/JUnit/Bash bug with RTL languages?

Hello, I noticed that when running tests, if the language selected is RTL then the JUnit says hello output is backwards. However, if I copy the output and try to paste it into firefox or gedit then the text is properly right-to-left. For example, when selecting hebrew, on my system it prints

Re: Ant/JUnit/Bash bug with RTL languages?

console does the Unicode bidi algo, and not about anything in the code? On Fri, Aug 21, 2015 at 10:12 AM, Mike Drob mad...@cloudera.com wrote: Hello, I noticed that when running tests, if the language selected is RTL then the JUnit says hello output is backwards. However, if I copy

Re: Ant/JUnit/Bash bug with RTL languages?

on your same console and see if its correct: usually its not. On Fri, Aug 21, 2015 at 10:13 AM, Benson Margulies bimargul...@gmail.com wrote: Isn't this all about how your console does the Unicode bidi algo, and not about anything in the code? On Fri, Aug 21, 2015 at 10:12 AM, Mike

Solr Config MergePolicy/MergeScheduler Naming Bug?

I was looking through code for unrelated reasons and this line stuck out to me: https://github.com/apache/lucene-solr/blob/trunk/solr/core/src/java/org/apache/solr/update/SolrIndexConfig.java#L180 if(mergeSchedulerInfo != null) m.put(mergeScheduler,mergeSchedulerInfo.toMap()); if(mergePolicyInfo

Re: Solr Config MergePolicy/MergeScheduler Naming Bug?

It looks like this toMap method is only used (transitively) by SolrConfigHandler.handleGet to print the config and show it to a client. Probably safe to add the other elements as well, good catch. On Tue, Jun 30, 2015 at 3:49 PM, Christine Poerschke (BLOOMBERG/ LONDON) cpoersc...@bloomberg.net

Re: Solr Config MergePolicy/MergeScheduler Naming Bug?

https://issues.apache.org/jira/browse/SOLR-7741 On Tue, Jun 30, 2015 at 3:57 PM, Mike Drob mad...@cloudera.com wrote: It looks like this toMap method is only used (transitively) by SolrConfigHandler.handleGet to print the config and show it to a client. Probably safe to add the other elements

Re: Welcome Christine Poerschke as Lucene/Solr committer

Well done! On Fri, Jul 24, 2015 at 4:46 AM, Koji Sekiguchi koji.sekigu...@rondhuit.com wrote: Congratulations, Christine! Koji On 2015/07/24 16:27, Adrien Grand wrote: I'm pleased to announce that Christine Poerschke has accepted the PMC's invitation to become a committer. Christine,

Re: Welcome Mikhail Khludnev as Lucene/Solr committer

Congratulations! On Tue, Jul 21, 2015 at 12:31 PM, Joel Bernstein joels...@gmail.com wrote: Congratulations Mikhail! Joel Bernstein http://joelsolr.blogspot.com/ On Tue, Jul 21, 2015 at 12:39 PM, Michael McCandless luc...@mikemccandless.com wrote: Welcome Mikhail! Mike McCandless

Re: Coverity scan results of Lucene

When I click through on View Defects in the report, I get a You are not authorized to access this page. response. On Tue, Jul 14, 2015 at 9:44 AM, Dawid Weiss dawid.we...@gmail.com wrote: The 444 defects is an overwhelming number. Most of those automated tools detect things that turn to be

Providing source jars for eclipse classpath

I really, really, *really* appreciate the ant eclipse task that we have in the build.xml. One feature that I would find very useful is if it could automatically link to sources for me. I guess this question breaks down into several parts - * How do I ask ivy to download sources for me? * Can we

Re: Potential Gerrit support in review/commit flow

Zhe, The canonical repository for Lucene is SVN, not Git. I'm not sure that Gerrit would be of much use to us, unless I am misunderstanding the integration points. Mike On Thu, Nov 5, 2015 at 6:40 PM, Zhe Zhang wrote: > Hi Lucene contributors, > > The Hadoop community is

Re: Welcome Tomás Fernández Löbbe to the PMC

Well done! On Fri, Nov 6, 2015 at 7:42 AM, Mark Miller wrote: > Welcome! > > - Mark > > On Fri, Nov 6, 2015 at 8:19 AM Steve Rowe wrote: > >> Welcome Tomás! >> >> Steve >> >> >> On Friday, November 6, 2015, Anshum Gupta wrote:

Re: Documenting Lucene Index Directory File Extensions

Ah! Thanks! That is exactly what I was looking for. On Sun, Aug 30, 2015 at 1:07 AM, Mikhail Khludnev mkhlud...@griddynamics.com wrote: http://lucene.apache.org/core/5_3_0/core/org/apache/lucene/codecs/lucene53/package-summary.html#file-names ? On Sun, Aug 30, 2015 at 6:10 AM, Mike Drob

Documenting Lucene Index Directory File Extensions

Is there a document somewhere describing the structure of a lucene index directory? Like, at an implementation level, what do all of the extensions mean, how do they interact, what file references what, etc. I'm trying to discover a human-readable version of this before resorting to code for this.

Re: Lucene/Solr git mirror will soon turn off

> Does anyone know of a link to this git-svn issue? Is it a known issue? If there's something simple we can do (remove old jars from our svn history, remove old branches), maybe we can sidestep the issue and infra will allow it to keep running? I believe it is partially covered under

Re: Lucene/Solr git mirror will soon turn off

3 is typically solved by adding a .gitignore or .gitkeep file in what would be an empty directory, if the directory itself is important. On Tue, Dec 15, 2015 at 12:21 PM, Dawid Weiss wrote: > > Oh, just for completeness -- moving to git is not just about the version >

Multiple Classes sharing loggers

Hi devs, While tracing some through some log statements, I noticed that not all of the classes are using their own loggers. In particular, there are several instances of using SolrCore.log outside of the SolrCore class. There's also a few places where we use an inherited logger, like in

Re: Rolling upgrades from 5.x to 6.0

A 5.x Solr could have indices that are still in a 4.x format, right? That would be one point where it's not "fully back compatible." On Tue, Feb 23, 2016 at 12:27 PM, Shai Erera wrote: > Wait, what do you mean by Lucene not supporting back-compat? Lucene 6.0 > will be able to

Re: Lucene/Solr 6.0.0 Release Branch

I'd really like to see LUCENE-6993 make it in, but unfortunately, I don't have an ETA on it at this time. On Wed, Feb 24, 2016 at 2:23 PM, Nicholas Knize wrote: > With the release of 5.5 and the previous discussion re: 6.0.0 I'd like to > keep the ball moving and volunteer as

Re: reviews.apache.org / GIT migration

To add another possibility to the mix, I'd suggest using something like Apache Yetus to manage commit process. On Tue, Jan 26, 2016 at 1:22 PM, Gregory Chanan wrote: > IMO reviewboard with git is strictly better than reviewboard with svn; > getting reviewboard from svn to

Playing with Java Object Alignment

Solr devs, I've seen some warnings on the Solr Wiki about staying under a 32G heap to take advantage of compressed pointers. Has anybody that has gone over the 32GB soft limit (but still under 64GB) played with increasing the byte alignment? For example -XX:ObjectAlignmentInBytes=16 I'm

Re: Copyrights

I would check with legal-discuss@a.o to be sure, but here is my understanding of relevant ASF policies: All work done and contributed by an individual is bound by the terms of your ICLA. You retain the copyright ownership under ASLv2, but have granted the ASF (an irrevocable?) permission and

Test Issues

I feel like I have to be missing something simple, and yet I find myself asking on the mailing list. I've narrowed down my failing test to something that I don't think it related to my code changes at all and I'm struggling to understand what I'm failing to set up correctly in this environment.

Re: Test Issues

ing 'fl=score') > > On Mon, Mar 28, 2016 at 3:07 PM Mike Drob <mad...@cloudera.com> wrote: > >> I feel like I have to be missing something simple, and yet I find myself >> asking on the mailing list. I've narrowed down my failing test to something >> that I

Solr Debug Timing Questions

Hi Solr Devs, I had a few question about the query info exposed through debug=timing parameters. 1) I noticed that the components don't always add up to the QTime. Is this delta the sum of time spent transferring between components? 2) I didn't see a breakdown of the query scatter time when

Re: Welcome Scott Blum as a Lucene/Solr committer!

Congrats, Scott! Well deserved! On Tue, Apr 19, 2016 at 9:32 AM, Shawn Heisey wrote: > On 4/19/2016 3:21 AM, Shalin Shekhar Mangar wrote: > > I'm pleased to announce that Scott Blum has accepted the Lucene PMC's > > invitation to become a committer. > > Congratulations and

Re: [VOTE] Release Lucene/Solr 6.4.0 RC?

+1 (non-binding) SUCCESS! [0:59:54.889172] Also saw "***WARNING***: javadocs want to fail!" and a lot of javadoc warnings. Filed SOLR-10004 to address this. On Tue, Jan 17, 2017 at 10:27 AM, jim ferenczi wrote: >

Re: Welcome Cao Manh Dat as a Lucene/Solr committer

Congratulations! On Monday, January 9, 2017, Uwe Schindler wrote: > Welcome Dat! > > > > Uwe > > > > - > > Uwe Schindler > > Achterdiek 19, D-28357 Bremen > > http://www.thetaphi.de > > eMail: u...@thetaphi.de > > > >

[no subject]

+1 (non-binding) Automated tests were happy for me -- SUCCESS! [1:16:35.519232] I ran a Java API compatibility check between 6.5.0 and this 6.5.1 and while there's a few changes, I don't think any of them would actually end up as user facing. Posted results at

Re: Increasing ASF Jenkins bandwidth

> There has been discussion of automatically testing patches on JIRA issues (SOLR-10912). As far as I’m concerned, we won’t be able to consider that until/unless we have more Jenkins bandwidth. I don't think we need to dedicate resources to Yetus patch testing. It runs on generic ASF nodes. On

Why Does Smoke Tester Fail with Ant 1.10?

Hi, I was recently running ant nightly-smoke and it failed because my version of ant is too new. The default installed by homebrew is 1.10.1, while the smoke test expects ant 1.8 or 1.9, looks like. Searching for ant 1.10 on the dev list gives me tons of false positives (every jenkins failure,

Re: Why Does Smoke Tester Fail with Ant 1.10?

is similar, you use the Gradle-Wrapper to make > repeatable builds with exact versions! Ant just has no “ant wrapper”  > > > > Uwe > > > > - > > Uwe Schindler > > Achterdiek 19, D-28357 Bremen > > http://www.thetaphi.de > > eMail: u...@thetaph

Re: Why Does Smoke Tester Fail with Ant 1.10?

; eMail: u...@thetaphi.de > > > > *From:* md...@cloudera.com [mailto:md...@cloudera.com] *On Behalf Of *Mike > Drob > *Sent:* Sunday, July 2, 2017 1:22 AM > *To:* Lucene Dev <dev@lucene.apache.org> > *Subject:* Why Does Smoke Tester Fail with Ant 1.10? > &g

Re: 10 Resource Leak warnings dated to Q2 2017

I think you can do this with the -Werror flag and supress annotating everything else. On Wed, Jul 5, 2017 at 10:45 AM, Erick Erickson wrote: > bq: making precommit fail for some but not all resource leaks. > Implementation wise, how might one go about that? > > No

Re: Fix versions

This would be good to see as part of the How To Contribute guide, I think, or at least linked from there. On Wed, Jul 5, 2017 at 5:10 PM, David Smiley wrote: > This makes sense to me. It's easy to forget this stuff though. Perhaps > we can propose a policy, vote on

Re: SolrCloud "master mode" planned?

Could the zk role also be guaranteed to run the Overseer (and no collections)? If we already have that separated out, it would make sense to put it with the embedded zk. I think you can already configure and place things manually this way, but it would be a huge win to package it all up nicely for

Re: JIRA Status - Finding Patch Submissions

, I can leave notes on them and somebody with more JIRA karma can do a second pass to handle the cleanup. Thanks, Mike On Fri, Apr 28, 2017 at 10:42 AM, Mike Drob <md...@apache.org> wrote: > Thanks for this hint, Alex. > > I ran the following JQL to get some idea of our

JIRA Status - Finding Patch Submissions

Devs, Does anybody have good JIRA filters or processes for finding issues with patches available and attached, or maybe with open pull requests for them? I was talking to a few folks and we remarked how patches can sometimes sit on issues for a long time, and this seems like a wasted opportunity

Re: JIRA Status - Finding Patch Submissions

ore" dropdown. > > We also have some Github Integration fields in there, but they don't > seem to be actually doing anything for Solr project. > > Regards, >Alex. > > http://www.solr-start.com/ - Resources for Solr users, new and experienced > > > On 2

Re: What should we do with the 6x code line?

+1 Release early, release often! On Tue, Aug 8, 2017 at 4:27 PM, Erick Erickson wrote: > Solr and Lucene have had fixes backported to 6x (not 6.6) since the > 7.0 label was set, most in Solr. Some of the fixes are useful "in the > field", I've back-ported some of them

Re: JIRA Status - Finding Patch Submissions

Heisey <apa...@elyograg.org> wrote: > On 4/28/2017 9:42 AM, Mike Drob wrote: > > Thanks for this hint, Alex. > > > > I ran the following JQL to get some idea of our current status: > > project in (lucene, solr) and "Attachment count" > 0 and s

Re: JIRA Status - Finding Patch Submissions

und us periodically to look. Additionally, >>> we could use that to start running precommit checks on Jenkins whenever a >>> new patch is put up. See Apache Yetus for how this might work. >>> >>> +1. We should also consider running unit tests as part of the pro

Re: Strange Solr JIRA versions (Lucene too!)

Christine, Wow, that's fantastic. You can also pass a --grep argument to git directly. Another problem that just occurred to me though, is that we might need to make updates to CHANGES files too. I'm not sure how to automate the check for that, since the format can be pretty messy. Mike On

Re: [VOTE] Release Lucene/Solr 6.6.0 RC5

I tried running the smoke test command as specified but ran into test failures: [junit4] Tests with failures [seed: 545A8F7F914CAA60]: [junit4] - org.apache.solr.cloud.CdcrBootstrapTest. testBootstrapWithSourceCluster [junit4] - org.apache.solr.cloud.CdcrBootstrapTest.

Re: [VOTE] Release Lucene/Solr 6.6.0 RC5

(kbytes, -v) unlimited Do you think that open files limit is too low? I didn't see any evidence in the log of that (could easily have missed it though). On Tue, May 30, 2017 at 4:32 PM, Steve Rowe <sar...@gmail.com> wrote: > Hi Mike, > > > On May 30, 2017, at 5:07

Re: Strange Solr JIRA versions

Reviving this old thread because I'm seeing a related issue on JIRA. When going to resolve an issue, I can set fix version to either "7.0" or "master (7.0)" I don't care which one we use, but having two is confusing and I'm sure will lead to a mistake somewhere down the line. So... what's the

Re: Release 6.6

Thanks for putting this together, Ishan! On Mon, Jun 5, 2017 at 1:05 PM, Ishan Chattopadhyaya < ichattopadhy...@gmail.com> wrote: > Hi all, > I've updated the release notes here: > https://wiki.apache.org/lucene-java/ReleaseNote66 > https://wiki.apache.org/solr/ReleaseNote66 > > Please review /

Re: VOTE: Apache Solr Reference Guide for 6.6 (RC1)

In the html source for the index page: https://home.apache.org/~ctargett/RefGuidePOC/jekyll-full/feed.xml;> Does that need to point somewhere else? On Fri, Jun 9, 2017 at 2:51 PM, Cassandra Targett wrote: > Please vote for the release of the Apache Solr Reference Guide

Re: Welcome Mike Drob as Lucene/Solr committer

wrote: > I'm pleased to announce that Mike Drob has accepted the PMC's > invitation to become a committer. > > Mike, it's tradition that you introduce yourself with a brief bio / > origin story, explaining how you arrived here. > > Your existing Apache handle has already added

Re: License headers for solr-ref-guide files?

It should be all of them, right? Can you file an issue if you find ones that are missing? Mike On Sun, May 21, 2017, 12:00 PM Jan Høydahl wrote: > Hi > > Should any of the .adoc, .css, .js or .html files under solr-ref-guide/* > get an ASL header? > > -- > Jan Høydahl,

Re: Did we request "Issue Security" to be enabled for SOLR Jira project?

I think the issue security level has to be around in order to keep some issues private. For example, https://issues.apache.org/jira/browse/SOLR-10031 before the 5.5.4 release. Not sure if there's an alternative model that will still allow for responsible disclosure of security issues. Mike On

Re: Strange Solr JIRA versions

>> wrote: >> >>> I've been using master (7.0) too. >>> >>> On Mon, Jun 5, 2017 at 11:00 AM, Joel Bernstein <joels...@gmail.com> >>> wrote: >>> > I've been using master (7.0). >>> > >>> > Joel Bernstein >>

Re: [VOTE] Release Apache Lucene/Solr 7.0.0 RC3

SUCCESS! [1:09:28.373226] On Mac OS X 10.12.6 with Oracle Java 1.8.0_131 and Ant 1.10.1 On Mon, Sep 11, 2017 at 2:39 PM, Tomás Fernández Löbbe < tomasflo...@gmail.com> wrote: > +1 > SUCCESS! [0:44:22.517203] > > Thanks for working on this Anshum! > > On Mon, Sep 11, 2017 at 10:45 AM, Tommaso

Re: Welcome Hrishikesh Gadre as Lucene/Solr committer

Welcome! On Fri, Sep 29, 2017 at 12:23 PM, Yonik Seeley wrote: > Hi All, > > Please join me in welcoming Hrishikesh Gadre as the latest Lucene/Solr > committer. > Hrishikesh, it's tradition for you to introduce yourself with a brief bio. > > Congrats and Welcome! > -Yonik > >

Re: Welcome Ishan Chattopadhyaya to the PMC

Congratulations and well deserved! On Fri, Dec 8, 2017 at 8:16 AM, Joel Bernstein wrote: > Welcome Ishan! > > Joel Bernstein > http://joelsolr.blogspot.com/ > > On Fri, Dec 8, 2017 at 9:11 AM, Yonik Seeley wrote: > >> Welcome Ishan! >> -Yonik >> >> >> On

Re: Solr test framework - Locale randomization

I think you're going to be stuck with doing something like https://github.com/apache/lucene-solr/blob/master/solr/core/src/test/org/apache/solr/cloud/KerberosTestServices.java#L55 where there is a hard-coded list of locales that we know are broken. On Fri, Oct 20, 2017 at 3:31 PM, Hrishikesh

Shenandoah GC?

Hi Devs, Has anybody tried running Lucene or Solr workloads with the Shenandoah Garbage Collector[1]? I searched through the list archives and saw somebody reported issues with it back in 2014, but I imagine that there's been a lot of change since then. We've had some initially hopeful

Re: Shenandoah GC?

ggest concern needs to be correctness. try first > getting the test suite to pass before worrying about any workloads. > The last time i tested one of the shenandoah builds, basically all > tests related to points failed. > > On Tue, Jul 31, 2018 at 10:49 AM, Mike Drob wrote: >

SOLR-13437 Forking noggit

Hey Lucene/Solr PMC, Regarding the proposed fork in SOLR-13437, has anybody checked if the original maintainer wants to keep noggit in his own namespace? I realize Yonik is part of the PMC here, so he can definitely speak for himself if he wants. Explicitly asking him in a public venue goes a

Re: SOLR-13437 Forking noggit

. On 2019/05/14 13:59:32, David Smiley wrote: > On Mon, May 13, 2019 at 11:32 PM Mike Drob wrote: > > > P.S. I am not subscribed to this list despite being an ASF Member, so > > please explicitly cc me on replies if you want me to see the responses. > > > > Instead of

Re: Propose Solr committer meeting next week

What's the medium for this? Is somebody going to make a webex/zoom/meet/whatever link? I'd like to make sure I have the right tools installed and will do my best to join from airport wifi. On Mon, Nov 18, 2019 at 2:49 AM Jan Høydahl wrote: > I view Jörn’s SIP proposal as a way for tighter gate

Re: Welcome Houston Putman as Lucene/Solr committer

Welcome, Houston! On Fri, Nov 15, 2019 at 6:00 PM Shalin Shekhar Mangar < shalinman...@gmail.com> wrote: > Congratulations and welcome Houston! > > On Thu, Nov 14, 2019 at 12:39 PM Houston Putman > wrote: > >> Thanks everyone! >> >> As requested, a brief history of me: >> >> A native Austinite,

Re: Commit / Code Review Policy

I'm coming late into this thread because a lot of the discussion happened while I was offline, so some of the focus has shifted, but I'll try to address a few topics that were brought up earlier anyway. In an effort to be brief, I'll try to summarize sentiments rather than addressing specific

Re: "Cannot start mini solr cloud cluster" errors

I suspect it’s related to my changes in SOLR-14223, can you share more logs? On Wed, Mar 4, 2020 at 6:34 AM Erick Erickson wrote: > I see 2-3 failures a day come by the dev list with this failure. I have > the full console output from one of them if you’d like to see it. Been > happening for

Re: "Cannot start mini solr cloud cluster" errors

Yep, this was definitely my change, sorry for the mess I've made of things on Windows. Regardless, not trying to make excuses for myself here. I've pushed a change that should make Windows happy, although I am not able to reproduce it myself. On Wed, Mar 4, 2020 at 10:27 AM Chris Hostetter

Re: Solr Admin UI Refresh 2020

Hi Marcus, The mailing list strips attachments for some folks, can you upload the video somewhere else and link to it for us poor unfortunate souls? Thanks for your work! Excited to see the progress as it happens. Mike On Mon, Apr 13, 2020 at 5:30 AM Marcus Eagan wrote: > In general, I asked

Re: Welcome Eric Pugh as a Lucene/Solr committer

Welcome! I definitely thought you were already a committer, so well deserved! On Mon, Apr 6, 2020 at 10:19 AM Kevin Risden wrote: > Welcome Eric! > > Kevin Risden > > On Mon, Apr 6, 2020 at 10:48 AM Alan Woodward > wrote: > > > > Welcome Eric! > > > > > On 6 Apr 2020, at 13:21, Jan Høydahl

Re: [DISCUSS] SIP-6 Solr should own the bootstrap process

nd end up in 8.6 already, then increment from there? > > Jan > > 25. mar. 2020 kl. 16:13 skrev Mike Drob : > > I'm in favor of this approach mainly because of the line mentioned in the > Test Plan: > > > If we move servlet initialization into Java code an

Re: [DISCUSS] SIP-6 Solr should own the bootstrap process

I'm in favor of this approach mainly because of the line mentioned in the Test Plan: > If we move servlet initialization into Java code and get rid of web.xml, we may be able to start Solr in the same way both in tests and in real life! I feel that this should be a top level goal, along with

Gradle Wrapper Changes

Devs, I'll be committing a set of changes for LUCENE-9266 shortly, PR can be found at https://github.com/apache/lucene-solr/pull/1390 We've tested this on Windows, Mac OS, and Ubuntu, so I'm fairly confident in what we're doing here, but because this has the potential to be an intrusive change

Re: Gradle Wrapper Changes

> Uwe Schindler > > Achterdiek 19, D-28357 Bremen > > https://www.thetaphi.de > > eMail: u...@thetaphi.de > > > > *From:* Mike Drob > *Sent:* Thursday, April 2, 2020 6:29 PM > *To:* dev@lucene.apache.org > *Subject:* Gradle Wrapper Changes > >

Re: Overseer documentation

#2 and #8 were the ones that immediately jumped out at me. On 2020/04/24 10:33:55, Ilan Ginzburg wrote: > Thanks David, Mike and Shalin. Glad you find this useful! > > Mike, do you mind pointing out here or in the doc which of the bugs > you saw in production? That way I can start filing Jiras

Re: Solr Admin UI Refresh 2020

In phase 2, will the admin ui be running in the same jetty container as the solr application? On Mon, Apr 20, 2020 at 4:35 PM Marcus Eagan wrote: > SIP here: > https://cwiki.apache.org/confluence/display/SOLR/Updated+Solr+Admin+UI > > On Mon, Apr 20, 2020 at 9:32 AM Gus Heck wrote: > >> If

Re: [DISCUSS] Lucene-Solr split (Solr promoted to TLP)

This is an interesting approach, Michael. I took it a bit further by excluding all authors with only a single commit[1], since I think GitHub PRs tend to highlight that kind of contribution more. Since 2012 I found 24 lucene-only, 31 solr-only, and 77 (about 58%) contributing to both. Since 2018,

Re: Overseer documentation

Wow Ilan! This is very comprehensive! Regarding your list of potential bugs, I can confirm that at least two of those are accurate and I've seen them in production. We found work-arounds and got distracted before creating JIRAs, and this was a great reminder of those war stories. I think this

Re: [DISCUSS] 8.5.2 Release?

to this branch including giving a notification here. On Sat, May 9, 2020 at 7:07 AM Adrien Grand wrote: > I'd rather not change signatures on a patch release. Are there ways we > could have the bug fix on 8.5 without backporting this API change? > > On Fri, May 8, 2020 at 5:18 PM Mike

Re: [DISCUSS] Lucene-Solr split (Solr promoted to TLP)

Solr maintaining a fork of Lucene sounds like exactly the situation that let to the original merge, where there are two sets of divergent development On Sun, May 10, 2020 at 1:20 AM David Smiley wrote: > I agree with Doug that the burden of proof is on keeping the codebases > together instead

Re: Getting warnings out

I agree with the one warning at a time approach. That one seems most feasible to take piecemeal On Mon, May 11, 2020 at 10:19 AM Andras Salamon wrote: > Hi, > > We have quite a few warnings, it would be difficult to fix them at once. > Checking one directory (or warning type) and handling 10-20

Re: [DISCUSS] 8.5.2 Release?

Jan Høydahl wrote: > Mike, I merged latest changes to releaseWizard to branch_8_5 as well. So > you’ll be first to test the new instructions for updating the web site. So > please be prepared for discovering quirks in that part of the releaseWizard. > > Jan > > > 7. mai 2

Re: [DISCUSS] 8.5.2 Release?

u have any idea why only 5 mirrors are updated > Noble? > > Jan > > 14. mai 2020 kl. 19:41 skrev Mike Drob : > > Noble, > > We're still missing a few: > > > https://cwiki.apache.org/confluence/display/LUCENE/ReleaseTodo#ReleaseTodo-Updatetheproje

Re: [DISCUSS] 8.5.2 Release?

rs shortly after adding > it? > > See https://dist.apache.org/repos/dist/release/lucene/solr/ - there is > only 8.5.1 there. Please re-upload 7.7.3 and it will start mirroring again. > > Jan > > 15. mai 2020 kl. 20:51 skrev Mike Drob : > > Thanks for pointing

Re: [DISCUSS] 8.5.2 Release?

isplay/LUCENE/ReleaseTodo > > Please let me know if anything is missing. > I still don't see the solr release details in https://lucene.apache.org/ > > How do i do it? > > > On Thu, May 14, 2020 at 10:47 AM Noble Paul wrote: > > > > I'll fix them today > > &g

Re: [DISCUSS] 8.5.2 Release?

On 2020/05/07 18:30:53, Alan Woodward wrote: > +1, thanks for volunteering Mike > > > On 7 May 2020, at 19:03, Anshum Gupta > <mailto:ans...@anshumgupta.net>> wrote: > > > > Thanks for doing this, Mike. > > +1 to the 8.5.2 release. > >

Re: [VOTE] Solr to become a top-level Apache project (TLP)

-1 (committer) On Tue, May 12, 2020 at 1:14 PM Chris Hostetter wrote: > > : Therefore, the proposal is to separate Solr from under Lucene TLP, and > : make it a TLP on its own. The initial structure of the new PMC, > : committer base, git repositories and other managerial aspects can be > :

Re: [VOTE] Release Lucene/Solr 8.5.0 RC1

+1 (non-binding) All testing was with Java 11.0.5 Smoke tester didn't work (expected) Manually ran lucene and solr tests, had a few solr failures but they passed when rerunning individually. Went through the tutorial, have a few minor updates to make that I'll take care of in the next few days

[DISCUSS] 8.5.2 Release?

Devs, I know that we had 8.5.1 only a few weeks ago, but with the fix for LUCENE-9350 I think we should consider another bug-fix. I know that without it I will be explicitly recommending several users to stay off of 8.5.x on their upgrade plans. There are some pretty scary looking charts on

[VOTE] Release Lucene/Solr 8.5.2 RC1

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

Re: Index documents in async way

Interesting idea! Can you explain a little more on how this would impact durability of updates? What does a failure look like, and how does that information get propagated back to the client app? Mike On Thu, Oct 8, 2020 at 9:21 AM Cao Mạnh Đạt wrote: > Hi guys, > > First of all it seems that

Re: Performance in Solr 9 / Java 11

Do you know if these mr-jars are built by default as part of the release process? I definitely had no idea about them when doing 8.5.2 and did not even think to verify anything about it. On Sat, Aug 29, 2020 at 4:05 PM Adrien Grand wrote: > It may only be indirectly related to your question,

Re: Apache Bug Bash

Note that error prone is part of our standard compilation already. On Wed, Sep 23, 2020 at 6:14 PM Alexandre Rafalovitch wrote: > On Wed, 23 Sep 2020 at 18:56, Tom DuBuisson wrote: > > > On Wed, Sep 23, 2020 at 9:11 AM Alexandre Rafalovitch < > arafa...@gmail.com> wrote: > > >> I would be

Re: Gradle build, where's the output?

It likely disappeared when I switched us to use the distribution plugin. Feel free to open either a JIRA or PR for it, depending on your comfort. On Tue, Sep 22, 2020 at 11:11 AM Erick Erickson wrote: > We’re probably talking about different things. I have access to all the > folders, I think

[ANNOUNCE] Apache Lucene 8.5.2 released

26 May 2020, Apache Lucene™ 8.5.2 available The Lucene PMC is pleased to announce the release of Apache Lucene 8.5.2. 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

[ANNOUNCE] Apache Solr 8.5.2 released

26 May 2020, Apache Solr™ 8.5.2 available The Lucene PMC is pleased to announce the release of Apache Solr 8.5.2 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

Re: [VOTE] Release Lucene/Solr 8.5.2 RC1

ow smoke test time comes from a combination of running this on a > relatively wimpy replacement MacBook and a slow network). > > > > On 23 May 2020, at 09:39, Shalin Shekhar Mangar > wrote: > > > > +1 > > > > SUCCESS! [0:47:23.934909] > > > > On Wed, May 20,

  1   2   3   4   5   6   7   8   9   >