Re: Welcome Mayya Sharipova as Lucene/Solr committer

Congrats and welcome, Mayya! Jan > 8. jun. 2020 kl. 18:58 skrev jim ferenczi : > > Hi all, > > Please join me in welcoming Mayya Sharipova as the latest Lucene/Solr > committer. > Mayya, it's tradition for you to introduce yourself with a brief bio. > > Congratulations and Welcome! > > Jim

Re: Moving Solr to Apache TLP

by the 10th. > > We just need the PMC members for the draft resolution and I strongly feel > that this shouldn't be an opt-in as people might miss this email. They > shouldn't come back to find they missed adding themselves here and be in a > weird position. > If at all, we can

Re: Moving Solr to Apache TLP

Note: All committers, please add your name to https://cwiki.apache.org/confluence/display/LUCENE/Solr+TLP+needed+changes#SolrTLPneededchanges-resolutionDraftboardresolution

Re: [VOTE] Release Lucene/Solr 8.5.2 RC1

+1 SUCCESS! [1:03:16.225214] I did no manual tests, just ran smoketester on macOS Jan > 20. mai 2020 kl. 19:58 skrev Mike Drob : > > Devs, > > Please vote for release candidate 1 for Lucene/Solr 8.5.2 > > The artifacts can be downloaded from: >

Re: packaging Solr binaries with Ant

Try ant create-package Jan > 20. mai 2020 kl. 15:35 skrev Theyaa Matti : > > I have compiled Solr locally and I would like to know how package solr in a > tar file similar to the ones provided here > https://lucene.apache.org/solr/downloads.html >

Re: [DISCUSS] 8.5.2 Release?

> Hopefully this gets everything resolved, I'll wait a little bit for the > mirrors to pick it up and then try creating 8.5.2 again > > On Mon, May 18, 2020 at 5:18 AM Jan Høydahl <mailto:jan@cominvent.com>> wrote: >> I don't really know . I deleted the original artifacts

Re: [DISCUSS] 8.5.2 Release?

> I don't really know what step puts the entry there in the releases.json. You don’t need to worry about releases.json, it is auto generated based on what is active on the mirrors. Once you re-upload 7.7.3 it will appear there again. Jan > 18. mai 2020 kl. 10:22 skrev Jan Høydahl : >

Re: [DISCUSS] 8.5.2 Release?

up? As of right now, 7.7.3 is missing > completely from https://projects.apache.org/json/foundation/releases.json > <https://projects.apache.org/json/foundation/releases.json> (which continues > to block the releaseWizard script). > > Thanks, > Mike > > On Fri, Ma

Re: [DISCUSS] 8.5.2 Release?

my notes together and commit them at the end of the process. > >> > >> Right now I think I’m waiting on a few final steps from 7.7.3 to complete > >> and then we’ll be ready to roll with 8.5.2 > >> > >> On Wed, May 13, 2020 at 4:59 PM Jan Høydahl

Re: [DISCUSS] 8.5.2 Release?

think I’m waiting on a few final steps from 7.7.3 to complete >>> and then we’ll be ready to roll with 8.5.2 >>> >>> On Wed, May 13, 2020 at 4:59 PM Jan Høydahl wrote: >>>> >>>> Mike, I merged latest changes to releaseWizard to bra

Re: [DISCUSS] 8.5.2 Release?

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 2020 kl. 19:13 skrev Mike Drob : > > Devs, > > I know

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

I choose to be more optimistic wrt «Solr committers» ability to integrate new and changed Lucene APIs in Solr. You do not need to be a Lucene committer in order to learn how to USE the Lucene APIs, and I believe there are several «Solr committers» who already posess those skills and are pretty

Re: [jira] [Commented] (SOLR-12823) remove clusterstate.json in Lucene/Solr 8.0

s > super tricky work. > > Ilan > > On Tue, May 12, 2020 at 3:32 PM Erick Erickson > wrote: >> >> Definitely +1, but I won’t have the bandwidth to help. >> >>> On May 12, 2020, at 9:03 AM, Jan Høydahl (Jira) wrote: >>> >>

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

+1 (binding) Jan Høydahl > 12. mai 2020 kl. 09:36 skrev Dawid Weiss : > > Dear Lucene and Solr developers! > > According to an earlier [DISCUSS] thread on the dev list [2], I am > calling for a vote on the proposal to make Solr a top-level Apache > project (TLP) and sep

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

Better stick to Lucene snapshot versions. Commit the Lucene change first, then solr. If the Lucene change is not mature enough to commit to Lucene, it is probably not mature enough for Solr either. Avoid hacks or forks, spend some longer time to get it right. If things get removed from Lucene

Re: [DISCUSS] 8.5.2 Release?

+1 I’ll backport the small Admin UI fix in https://issues.apache.org/jira/browse/SOLR-14411 > 8. mai 2020 kl. 00:10 skrev Tomás Fernández Löbbe : > > +1. Thanks Mike > > On Thu, May 7, 2020 at 2:55 PM Adrien Grand > wrote: > +1 > > Le jeu. 7 mai 2020 à 19:13, Mike

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

Thanks for bringing it up Dawid. I’ve asked myself the same question several times over the last couple of years, and have kind of been waiting for someone to make the proposal :) In my head, Solr has out-grown being a sub project of Lucene, like hadoop, mahout, nutch and tika before it. The

Re: [VOTE] Release Lucene/Solr 7.7.3 RC1

Noble. The 7.7.3 release is out. Will you do the announcement emails and website news updates? Jan > 24. apr. 2020 kl. 06:51 skrev Noble Paul : > > Thanks everyone. > > I shall do the release now > > On Thu, Apr 23, 2020, 6:50 AM Anshum Gupta > wrote: > +1 >

Re: April JIRA/PR cleanup

activity on inactive PRs, and also wind down the number of open from 272 to probably half... > 28. apr. 2020 kl. 12:17 skrev Jan Høydahl : > > Hi. Time for some PR/JIRA linking cleanups. Please review the two lists below > and help link PR to JIRA, as well as closing PRs where JIRA

April JIRA/PR cleanup

Hi. Time for some PR/JIRA linking cleanups. Please review the two lists below and help link PR to JIRA, as well as closing PRs where JIRA is resolved. --- Lucene/Solr Github PR report Number of open Pull Requests: 272 PRs lacking JIRA reference in title (49) #1424: 2020-04-11 Enable

Re: Solr Admin UI Refresh 2020

. > (Having an implementation to start with is definitely a plus, and it doesn't > look like there is one for React) > > Yasa looks more complete than savantly-net/solr-admin to me, and definitely > warrants at least a look. > > - Houston > > On Wed, Apr 22, 2020 at 7:27

Re: Solr Admin UI Refresh 2020

. Jan > 22. apr. 2020 kl. 11:30 skrev Noble Paul : > > As I see it all the 12 commits to that project is made by Jeremy Branham. > > Kudos to Jan Høydahl to save Solr from potential lawsuit & > embarrassment in the future. Awesome, I guess you are a part time > private dete

Re: Solr Admin UI Refresh 2020

e: > If Marcus has ability to edit existing pages, why don't we create the empty > page for him and sort out access granting issues later. I'd hate for this > much needed SIP to bog down on a technical issue. > > -Gus > > On Mon, Apr 20, 2020 at 7:10 AM Jan Høydahl

Re: [VOTE] Release Lucene/Solr 7.7.3 RC1

SUCCESS! [1:05:02.194590] No issues +1 (did not additional manual checking than running the smoketester) Jan > 21. apr. 2020 kl. 12:27 skrev Andrzej Białecki : > > Hi, > > I’m getting the following error, looks like the checksum doesn’t match the > file: > > Test Solr... > test basics... >

Re: Solr Admin UI Refresh 2020

un, Apr 19, 2020 at 3:45 AM Jan Høydahl <mailto:jan@cominvent.com>> wrote: > Thanks. The PR is useful for people to try out the UI. But for overall > replacement plan I really think we neeed that SIP, do you still need help > with Confluence? > > Jan Høydahl

Re: Solr Admin UI Refresh 2020

Thanks. The PR is useful for people to try out the UI. But for overall replacement plan I really think we neeed that SIP, do you still need help with Confluence? Jan Høydahl > 19. apr. 2020 kl. 06:30 skrev Marcus Eagan : > >  > I hope everybody is enjoying their weekend and is in

Re: From sysv to systemd

Note that running as foreground has implications on logging that may be surprising compared to current service. You may want to start a JIRA and a PR/patch at this point, this improvement is a good one! Jan Høydahl > 16. apr. 2020 kl. 16:04 skrev Marius Ghita : > >  > &g

Re: Lucene/Solr 8.5.1 bugfix release

> planning to build the first RC this coming Wednesday. Let me know if that > works for you. > > > > On Sat, Apr 4, 2020 at 12:25 AM Jan Høydahl <mailto:jan@cominvent.com>> wrote: > Also this coould be a backport candidate: SOLR-14317 > <https://issu

Re: Solr Admin UI Refresh 2020

www.linkedin.com/in/davidwsmiley >> <http://www.linkedin.com/in/davidwsmiley> >> >> On Fri, Apr 10, 2020 at 1:35 AM Marcus Eagan > <mailto:marcusea...@gmail.com>> wrote: >> I think package management frameworks are for loading non-essential features

Re: [VOTE] Release Lucene/Solr 8.5.1 RC1

Found the bug in the bugfix :) Committed a 2-line fix to ‘index.html’, see https://github.com/apache/lucene-solr/commit/e15b02c/ and to merged to branch_8x Ignacio, let me know if you want me to merge the fix to branch_8_5 in case of a respin. Jan > 14. apr. 2020 kl. 14:36 skrev Cassandra

Re: [VOTE] Release Lucene/Solr 8.5.1 RC1

Thanks for checking Cassandra. I’m following up this investigation in https://issues.apache.org/jira/browse/SOLR-14359 to not pollute the vote thread. Jan > 14. apr. 2020 kl. 14:36 skrev Cassandra Targett : > > Jan, I also see the same text you hoped to fix with SOLR-14359. > > I think I

Re: [VOTE] Release Lucene/Solr 8.5.1 RC1

Ran the smoke tester ok. Started Solr from the downloaded package to validate the only Solr bugfix in this release: * SOLR-14359: Admin UI collection/core drop-downs had wrong placeholder text. Fixed by upgrading angular-chosen (janhoy) However, the drop-downs still show «Select an Option» as

Re: Solr Admin UI Refresh 2020

be crafted with a concrete plan. We can then have a vote on the SIP. Jan Høydahl > 9. apr. 2020 kl. 20:06 skrev Cassandra Targett : > >  > Thanks for your message, Gus. You touched on things I was thinking this > morning as I caught up to the thread, and had started to draft a m

Re: Solr Admin UI Refresh 2020

ions from my phone: > > > > > > > > > > > Jan Høydahl > Added 1 hour ago > There are many opinions around admin UI. So I think the best place to start > would be a new mail-thread in dev@ to discuss the way forward. Before we > start a major re-work, we should probably ask our

Welcome Eric Pugh as a Lucene/Solr committer

! Congratulations and welcome! It is a tradition to introduce yourself with a brief bio, Eric. Jan Høydahl - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

Re: Lucene/Solr 8.5.1 bugfix release

Also this coould be a backport candidate: SOLR-14317 <https://issues.apache.org/jira/browse/SOLR-14317> HttpClusterStateProvider throws exception when only one node down Jan > 3. apr. 2020 kl. 22:29 skrev Jan Høydahl : > > I plan to merge this to branch_8_5 > >

Re: Lucene/Solr 8.5.1 bugfix release

I plan to merge this to branch_8_5 SOLR-14359 Admin UI has "Select an option" for collections and cores drop-downs Jan > 3. apr. 2020 kl. 14:15 skrev jim ferenczi : > > +1, thanks Ignacio. > I merged the fix for LUCENE-9300 >

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

we need to give them a > separate xml file that they can use similar syntax for? > > I'm definitely against changing that for 8.6, and as much as I want this > change for 9.0 I really want to see an alternative that makes sense proposed > before we start tearing through all of

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

we effectively have no testing of the configurations that go into the > various xml files - can't speak for others, but it made me reluctant to make > changes to them. > > > Mike > > On Tue, Mar 24, 2020 at 6:36 PM Jan Høydahl <mailto:jan@cominvent.com>> wrote: > This

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

ler : > > Of course it's a single jvm. It's only a replacement for start.jar. the > mock-up is already there. > > Uwe > > Am March 24, 2020 9:45:33 PM UTC schrieb Bram Van Dam : > On 24/03/2020 16:01, Jan Høydahl wrote: > It has been proposed many times to make Solr a truly

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

allow editing files in filesystem in the dev environment, but when the > bootstrapper in production startup sees the static asset jar file in > classpath, it could use it instead. > > Should I add this to the wiki page? > > Uwe > > Am March 24, 2020 3:01:43 PM UTC sch

[DISCUSS] SIP-4 Solr should own the bootstrap process

It has been proposed many times to make Solr a truly standalone app and that we should start Jetty from within Solr and not the other way around :) Here is my formal SIP proposal for this: https://cwiki.apache.org/confluence/display/SOLR/SIP-4+Solr+should+own+the+bootstrap+process Please read

Re: 2020-03 Committer virtual meeting

Thanks for taking the lead and pulling this off David. This is very positive for the community, it supplements the lists in a very nice way. Jan Høydahl > 23. mar. 2020 kl. 13:48 skrev David Smiley : > >  > I updated the cwiki page on the meeting notes after the meeting to reflec

Re: SolrJ: ZooKeeper status path & admin requests

Noble, you are confusing the ZK API with the ZK Status API. The ZK Status API (/admin/zookeeper/status) is also currently only used by the UI, but it delivers a JSON detailing the status of all Zookeepers. Feel free to make a patch for adding it. However, we may want to mark the response as

Re: Welcome Alessandro Benedetti as a Lucene/Solr committer

Welcome Alessandro! Jan > 18. mar. 2020 kl. 14:00 skrev David Smiley : > > Hi all, > > Please join me in welcoming Alessandro Benedetti as the latest Lucene/Solr > committer! > > Alessandro has been contributing to Lucene and Solr in areas such as More > Like This, Synonym boosting, and

Re: [VOTE] Release Lucene/Solr 8.5.0 RC1

I you installed python3 through homebrew it can be that SSL root certificates are not updated. There seems to be a few workarounds here https://stackoverflow.com/questions/44649449/brew-installation-of-python-3-6-1-ssl-certificate-verify-failed-certificate Or simply download and install python3

Re: [VOTE] Release Lucene/Solr 8.5.0 RC1

+1 SUCCESS! [1:04:09.647360] Jan > 13. mar. 2020 kl. 15:26 skrev Alan Woodward : > > Please vote for release candidate 1 for Lucene/Solr 8.5.0 > > The artifacts can be downloaded from: >

Re: 8.5 release

oject%20in%20(SOLR%2C%20LUCENE)%20AND%20status%20in%20(Open%2C%20Reopened)%20AND%20priority%20%3D%20Blocker%20AND%20fixVersion%20%3D%208.5%20ORDER%20BY%20priority%20DESC >>>>> >>>>> <https://issues.apache.org/jira/issues/?jql=project%20in%20(SOLR,%20LUCENE)%20AND%20statu

Re: SOLR version 8 bug???

Please the solr-user mailing list for this. Once you get the bug confirmed you can open a jira issue. Jan Høydahl > 9. mar. 2020 kl. 16:10 skrev Staley, Phil R - DCF : > >  > We recently upgraded to our Drupal 8 sites to SOLR 8.3.1. We are now getting > reports of certain pat

Re: Upgrade from 6.2.1. to 8.4.1 HttpSolrCall

Questions like this belong to the solr-user mailing list. The dev@ list is for discussion internal development. When you issue your question to that list, you may want to re-phrase with more contextual information as to what you are actually trying to achieve (what library are you upgrading and

Re: github commit comments not(?) forwarded to list?

I think you may find the answer here :) https://github.com/apache/infrastructure-puppet/blob/a66ec4204550ef9cbc89ef65e7cec3f35f39a07a/modules/gitbox/files/cgi-bin/issues.cgi#L358-L361 I made some contributions to that code in INFRA-19263 so I

Re: Welcome Nhat Nguyen to the PMC

Welcome Nhat! Jan > 3. mar. 2020 kl. 17:34 skrev Adrien Grand : > > I am pleased to announce that Nhat Nguyen has accepted the PMC's invitation > to join. > > Welcome Nhat! > > -- > Adrien - To unsubscribe, e-mail:

Re: strange behavior of solr query parser

The *_str variant produced by the _default configset is DocValues only, as thus intended primarily for faceting and sorting. Try changing this line in your schema > >> but if you write query like, q=A:1 OR A:2 OR B:1 OR B:2, >> it will work perfect. >> >> the only difference of two queries

Re: Typo in the documentation of Spell Check

Thanks for reporting bugs. I checked the Reference Guide and the documentation seems correct: https://lucene.apache.org/solr/guide/8_4/spell-checking.html#spell-check-parameters In fact that parameter was only added to the documentation from version 7.3. Please specify exactly which

Re: Query - SOLR 1.0

We will not answer user questions on the development list. Please respect David’s request to move your questions to solr-u...@lucene.apache.org mailing list. Jan > 27. feb. 2020 kl. 10:20 skrev shilvi.par...@barclays.com.invalid > : > > Hi David, > > Thank you very much for your revert.

Re: Maintenance of Solr's official Dockerfile

he is more relaxed about re-releasing the same version, then this is > less of an issue. > > - Houston > > On Thu, Feb 13, 2020 at 9:42 AM Jan Høydahl <mailto:jan@cominvent.com>> wrote: > I propose we continue to work with the existing docker-solr repo for some >

Re: [jira] [Commented] (SOLR-599) Lightweight SolrJ client

into the solrj module to know how easy it is to carve out parts of it.. Jan Høydahl > 19. feb. 2020 kl. 20:21 skrev Gus Heck (Jira) : > >  >[ > https://issues.apache.org/jira/browse/SOLR-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17040356#comment-17040356

Re: SolrJ has 29 compile-time dependencies!

rJ impacting dependencies, we need to > be super clear about that; needs it’s own issue or dev list message > announcement. Code reviews will help. I can’t stand dependency creep in SolrJ! > > (FYI I have almost no internet connectivity this week. ) > > On Mon, Feb 17, 2020 at 7:26 P

Re: Link doesn't validate

I fixed that as part of my latest commit for some other parts of the ref guide. Jan > 19. feb. 2020 kl. 09:38 skrev Dawid Weiss : > > Erick - your latest commit to the solr guide doesn't pass gradlew > check (and fails with ant as well): > >

Re: 8.5 release

+1 That should give us time to update release docs for the new website too. Jan Høydahl > 18. feb. 2020 kl. 18:28 skrev Adrien Grand : > >  > +1 > >> On Tue, Feb 18, 2020 at 4:58 PM Alan Woodward wrote: >> Hi all, >> >> It’s been a while since

Re: issue with Lucene UpdateDocument

hough some suggestions to figure it out. Please let me know how to > enable logging for Lucene to debug the issue. > > Thanks, > Jyothsna > From: Jan Høydahl mailto:jan@cominvent.com>> > Sent: Monday, February 17, 2020 5:15 PM > To: Lucene Dev mailto:dev@l

Re: SolrJ has 29 compile-time dependencies!

va/javase/11/docs/api/java.net.http/java/net/http/package-summary.html > > <https://docs.oracle.com/en/java/javase/11/docs/api/java.net.http/java/net/http/package-summary.html> > > > On Mon, Feb 17, 2020 at 6:44 AM Jan Høydahl <mailto:jan@cominvent.com>> wrote:

SolrJ has 29 compile-time dependencies!

Hi According to https://mvnrepository.com/artifact/org.apache.solr/solr-solrj/8.4.1 SolrJ now has 29 compile-time dependencies. Those are the ones explicitly mentioned in ivy.xml and I believe that the number would be even higher if we used transitive dependencies. That means that if you want

Re: Reminder: Sync PRs with JIRA

; Thanks Jan. Is there a way to bulk close all of them? If we automate it and > run it weekly, it would be nice. > > On Sat, 15 Feb, 2020, 6:53 AM Erick Erickson, <mailto:erickerick...@gmail.com>> wrote: > Thanks, closed mine... > > > On Feb 14, 2020, at 6:28 PM, Ja

Reminder: Sync PRs with JIRA

I made a report with dev-tools/scripts/githubPRs.py which shows «orphan» PRs and PRs that have not been closed even if the linked JIRA is closed. Please help close the gap. You can typically link a PR with a JIRA just by editing the PR title and also mentioning the JIRA ID as a comment on the

Re: 7.7.3 bugfix release

Falde alarm, I needed to update my branch :) Jan Høydahl > 14. feb. 2020 kl. 19:11 skrev Jan Høydahl : > > What commit hash is the backport of SOLR-13971? I cannot find it and there > is no CHANGES entry…? > >> 14. feb. 2020 kl. 17:52 skrev Ishan Chattopadhyaya &g

Re: 7.7.3 bugfix release

the JIRA, it looks like backporting > https://github.com/apache/lucene-solr/commit/025f8763549151397284af28091cfd360307baa2 > > <https://github.com/apache/lucene-solr/commit/025f8763549151397284af28091cfd360307baa2> > should be enough. Is this correct, or am I missing something? &g

Re: 7.7.3 bugfix release

I’m afraid I don’t have the bandwidth the next couple of weeks. Jan Høydahl > 13. feb. 2020 kl. 16:27 skrev Noble Paul : > > Do you wish to backport them? > >> On Thu, Feb 13, 2020 at 7:55 PM Jan Høydahl wrote: >> >> According to NVD, there are at least two pub

Re: Maintenance of Solr's official Dockerfile

r image easily (like us). > > ~ David Smiley > Apache Lucene/Solr Search Developer > http://www.linkedin.com/in/davidwsmiley > <http://www.linkedin.com/in/davidwsmiley> > > On Sat, Jan 11, 2020 at 5:45 PM Jan Høydahl <mailto:jan@cominvent.com>> wrote: >&

Re: 7.7.3 bugfix release

According to NVD, there are at least two published CVEs that affects 7.7.2 (CVE-2019-17558 / SOLR-13971 and CVE-2019-0193 / SOLR-13669). We cannot release 7.7.3 with these still present. Jan >

Remove news section from TLP site?

Hi, Now that we are about to publish the new web site on Pelican, I propose that we remove the TLP news section. See details in https://issues.apache.org/jira/browse/LUCENE-9198 and chime in. Jan

Re: analytics.adoc validation does not pass

auto for .adoc files will guard us from a Windows user checking in an .adoc file with CRLF ending in the future, won’t it? But if you leave it as «don’t touch» such a mistake may happen, which was the root cause triggered .gitattributes in the first place? Or do you mean that it now creates

Re: Odd error in testing

Appears that rrd4j always tries to look for a font in the static initialization of RrdGraphConstants: https://github.com/rrd4j/rrd4j/blob/master/src/main/java/org/rrd4j/graph/RrdGraphConstants.java#L297

Re: Change solr/lucene Readme file format

to first time contributors! Perhaps a weekly email with a list of PRs from first timers? Jan Høydahl > 22. jan. 2020 kl. 16:11 skrev Houston Putman : > >  > Markdown is very standard at this point and I think the barrier to entry is > very small, at least much smaller than asciidoc

Re: [lucene-solr] branch master updated: Synchronizing 8.4.1 changes

d entries if we were releasing 8.4.2 after > 8.5.0. > > On Wed, Jan 22, 2020 at 9:58 AM Jan Høydahl <mailto:jan@cominvent.com>> wrote: > Just a question about this commit. > > These bug fixes released in 8.4.1 are also part of 8.5.0. > > I thought

Re: [lucene-solr] branch master updated: Synchronizing 8.4.1 changes

Just a question about this commit. These bug fixes released in 8.4.1 are also part of 8.5.0. I thought we normally duplicated changes entries between a bugfix release and the next minor version to avoid having to look at release dates and guess whether the fixes are in the next minor or not.

Re: [VOTE] Release Lucene/Solr 8.4.1 RC1

Ishan, I believe the RM job is not completed yet. Version 8.4.1 is still marked as UNRELEASED in Jira, and 8.4.0 is still in the mirrors, and https://lucene.apache.org/solr/guide/ lists 8.3 as the latest RefGuide. Have not checked whether other

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

Congrats Anshum! Jan > 15. jan. 2020 kl. 22:15 skrev Cassandra Targett : > >  > Every year, the Lucene PMC rotates the Lucene PMC chair and Apache Vice > President position. > > This year we have nominated and elected Anshum Gupta as the Chair, a decision > that the board approved in its

Re: Maintenance of Solr's official Dockerfile

>> 1. Are we allowed to maintain ASF code in a non-ASF repo? If not, how do we >> transition to >> an ASF git repo? >> * Can it be a sub folder in our main repo or does it need to be a >> separate repo? > > The way it works (from the official library’s point of view), is that we > maintain

Re: Lucene/Solr 8.4.1 bugfix release

ted keys are kept in ZK. We have >>> documented that users mustn't expose ZK when using the package >>> manager, but we feel we should do better and plug that hole. The >>> proposed change in the issue is to store keys in filesystem, which is >>> more secure than st

Re: Gradle build to land on master

+1 The sooner the better > This would ensure consistency in dependencies, for example Are you thinking to have a gradle task that fails if there is mismatch between ant and gradle dependencies versions? Jan > 8. jan. 2020 kl. 15:29 skrev Dawid Weiss : > > I think the gradle-master branch is

Re: Lucene/Solr 8.4.1 bugfix release

I’m calling off the 8.4.1 bugfix release for now. So feel free to grab the RM chair if you have any other urgent itches to scrach :) Jan > 6. jan. 2020 kl. 09:36 skrev Jan Høydahl : > > Regarding 8.4.1 release, there won’t be an RC today. > > If setting SOLR_SSL_CLIENT_HOSTNA

Re: Lucene/Solr 8.4.1 bugfix release

jan. 2020 kl. 14:57 skrev Jan Høydahl : > > Happy new year! > > I have merged these two fixes into branch_8_4 > > * SOLR-14106: Cleanup Jetty SslContextFactory usage (Ryan Rockenbaugh, Jan > Hoydahl, Kevin Risden) > * SOLR-14109: Always log to stdout from > server/sc

Maintenance of Solr's official Dockerfile

m this email thread discussion. Jan Høydahl

Re: Lucene/Solr 8.4.1 bugfix release

for 8.4.1 release on Monday, so make sure to get your important JIRAs in by then. Jan > 30. des. 2019 kl. 13:14 skrev Jan Høydahl : > > Hi > > I propose a quick 8.4.1 bugfix release and I volunteer as RM. > > I plan to build RC1 on Monday January 6th, one week from now. >

Lucene/Solr 8.4.1 bugfix release

fixes to documentation, build system etc won’t need a mention in CHANGES, unless you want to give credit to a contributor. Please leave branch_8_4 Jenkins jobs running. -- Jan Høydahl, Apache Lucene committer jan...@apache.org

Re: Propose eliminate "Versions of Major Components"

iley > <http://www.linkedin.com/in/davidwsmiley> > > On Mon, Dec 23, 2019 at 5:59 PM Jan Høydahl <mailto:jan@cominvent.com>> wrote: > In the binary distro there is no version.properties... > > Perhaps just keep Jetty version in CHANGES? > The Zookeeper versio

Re: Propose eliminate "Versions of Major Components"

In the binary distro there is no version.properties... Perhaps just keep Jetty version in CHANGES? The Zookeeper version is useful if you want to choose an external ZK to install, but the refGuide should help here. Unfortunately we do not link to the Reference Guide from README in Solr binary

Re: [VOTE] Release Lucene/Solr 8.4.0 RC2

+1 SUCCESS! [1:16:16.565000] Cool that you’re using the releaseWizard! Yea, many red days coming up, which then extends over 2 weekends in this case. I think it is safe to publish the release on friday 27th in this case though :) Jan > 20. des. 2019 kl. 11:02 skrev Adrien Grand : > > On

Re: Jackson ObjectMapper reuse

r.PackageUtils.getMapper() >> Now, that you mentioned, I'll change it to reuse it. However, this >> particular one is not performance critical as it is called from the >> SolrCLI (when "bin/solr package" support is used), and its life is as >> long as a single command.

Paying attention to deprecation warnings

Hi Our project compiles and runs with tons of deprecation warnings. Recently when working on SOLR-14106 and SOLR-14105 we found that there has been jetty deprecation warnings in the logs ever

Help needed for the Lucene website move

Hi Anyone skilled in web site building and ideally Pelican & markdown? We need some help completing the website migration in https://issues.apache.org/jira/browse/LUCENE-8987 which is currently stalled. Jan

Re: New branch and feature freeze for Lucene/Solr 8.4.0

Deprecation of DIH is ready for review https://issues.apache.org/jira/browse/SOLR-14066 One code change which is a WARN log at startup, other changes are documentation. Low risk and we’d like to deprecate sooner rather than later in 8.x. Your

Re: Commit / Code Review Policy

The SIP template should have a question that each proposal MUST answer: “Describe your consideration of what goes in solr-core and what goes in packages or contrib.” Jan Høydahl > 5. des. 2019 kl. 14:22 skrev Robert Muir : > >  > Fine, here's my SIP process. > > You can

Re: Commit / Code Review Policy

Let’s keep this thread about code review guidelines, not about feature removal, please. And be concrete with proposals for re-wording Davids proposal instead of sidetracking. As David said, we need to do both. I think the SIP process for new features and APIs may be a far better way than some

Re: Gradle build effort (respin, please read)

Great work Dawid. Just trying out solr tests now. I see that it is not very smart in parallel scheduling. But that is probably something we can improve over time? Is there some env.var or global setting to force e.g. -Ptests.seed=deadbeef for faster runs? We probably don’t need to randomize

Re: Commit / Code Review Policy

. I applaude David’s will to try improve the situation and I hope we all can contribute and be part of the solution. We’re a great team! Robert, I fully support your RCE suggestions, I.e “looks good to me” which means I don’t have the expertise to do any better :) Jan Høydahl > 2. des. 2

Re: [VOTE] Release Lucene/Solr 8.3.1 RC2

+1 SUCCESS! [1:52:34.599842] I still think https://issues.apache.org/jira/browse/SOLR-13977 <https://issues.apache.org/jira/browse/SOLR-13977> is important and should be mentioned in release email. -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com > 29. nov

Re: [jira] [Commented] (SOLR-13977) solr create -c not working unter Windows 10

The nature of the CRLF bug in solr.cmd may suggest that many more commands are broken on Windows. Perhaps all commands involving an argument “-c” or similar. Can someone on Windows do some verification? Try e.g. bin\solr.cmd start -p 8080 Jan Høydahl > 29. nov. 2019 kl. 02:42 skrev Is

Re: [VOTE] Release Lucene/Solr 8.3.1 RC1

May I recommend the ReleaseWizard to generate those upload commands? :) Jan Høydahl > 29. nov. 2019 kl. 06:25 skrev Ishan Chattopadhyaya > : > > I had uploaded the wrong artifacts. Even though I have the correct > artifacts with me locally, *I'll re-spin now* to avoid confusi

<    1   2   3   4   5   6   7   8   9   >