Re: [VOTE] Release Solr 9.6.1 RC1

[Arrieta, Alejandro]

+1 not binding

SUCCESS! [0:38:34.087315]

Dockers
[+] Building 45.1s (10/10) FINISHED
[+] Building 28.5s (10/10) FINISHED

Kind regards,
Alejandro Arrieta

On Mon, May 27, 2024, 2:58 PM Jan Høydahl  wrote:

> +1
>
> SUCCESS! [0:45:03.659058]
>
> -Jan
>
> > 23. mai 2024 kl. 21:39 skrev Houston Putman :
> >
> > Please vote for release candidate 1 for Solr 9.6.1
> >
> > The artifacts can be downloaded from:
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.6.1-RC1-rev-d7f7166567f52f1b31e3315b0188e11f2c4c9b60
> >
> > You can run the smoke tester directly with this command:
> >
> > python3 -u dev-tools/scripts/smokeTestRelease.py \
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.6.1-RC1-rev-d7f7166567f52f1b31e3315b0188e11f2c4c9b60
> >
> > You can build a release-candidate of the official docker images (full &
> > slim) using the following command:
> >
> > SOLR_DOWNLOAD_SERVER=
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.6.1-RC1-rev-d7f7166567f52f1b31e3315b0188e11f2c4c9b60/solr
> > && \
> >  docker build
> $SOLR_DOWNLOAD_SERVER/9.6.1/docker/Dockerfile.official-full \
> >--build-arg SOLR_DOWNLOAD_SERVER=$SOLR_DOWNLOAD_SERVER \
> >-t solr-rc:9.6.1-1 && \
> >  docker build
> $SOLR_DOWNLOAD_SERVER/9.6.1/docker/Dockerfile.official-slim \
> >--build-arg SOLR_DOWNLOAD_SERVER=$SOLR_DOWNLOAD_SERVER \
> >-t solr-rc:9.6.1-1-slim
> >
> > The vote will be open for at least 72 hours i.e. until 2024-05-29 20:00
> UTC.
> > (Extended due to weekend and US holiday)
> >
> > [ ] +1  approve
> > [ ] +0  no opinion
> > [ ] -1  disapprove (and reason why)
> >
> > Here is my +1
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org
> For additional commands, e-mail: dev-h...@solr.apache.org
>
>

Re: [VOTE] Release Solr 9.6.0 RC1

[Arrieta, Alejandro]

+1 not binding

SUCCESS! [0:36:54.492872]

docker builds successfully, too
[+] Building 56.6s (10/10) FINISHED
 => => naming to docker.io/library/solr-rc:9.6.0-1
[+] Building 25.8s (10/10) FINISHED
=> => naming to docker.io/library/solr-rc:9.6.0-1-slim

Kind Regards,
Alejandro Arrieta

On Tue, Apr 23, 2024 at 4:28 PM Gus Heck  wrote:

> As a side note the clamav process appears to have been a red herring. For
> me the command succeeds ~40-50% of the time (after adding --no-cache) no
> idea why.
>
> On Tue, Apr 23, 2024 at 9:23 AM Gus Heck  wrote:
>
> > This could be an issue with anti-virus software or gpg-agent... I got the
> > same result with the docker build until I killed clamav
> >
> > gus@ns-l1:~$ ps aux | grep clamav
> > clamav  1806  0.0  0.0  59124 14080 ?Ss   09:01   0:00
> > /usr/bin/freshclam -d --foreground=true
> > gus11896  0.0  0.0   9212  2304 pts/0S+   09:09   0:00 grep
> > --color=auto clamav
> > gus@ns-l1:~$ sudo kill -9 1806
> > [sudo] password for gus:
> > gus@ns-l1:~$ ps aux | grep clamav
> > gus11940  0.0  0.0   9080  2304 pts/0S+   09:09   0:00 grep
> > --color=auto clamav
> > gus@ns-l1:~$ SOLR_DOWNLOAD_SERVER=
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.6.0-RC1-rev-f8e5a93c11267e13b7b43005a428bfb910ac6e57/solr
> > &&   docker build
> > $SOLR_DOWNLOAD_SERVER/9.6.0/docker/Dockerfile.official-full
>  --build-arg
> > SOLR_DOWNLOAD_SERVER=$SOLR_DOWNLOAD_SERVER -t solr-rc:9.6.0-1 &&
> > docker build $SOLR_DOWNLOAD_SERVER/9.6.0/docker/Dockerfile.official-slim
> >   --build-arg SOLR_DOWNLOAD_SERVER=$SOLR_DOWNLOAD_SERVER -t
> > solr-rc:9.6.0-1-slim
> > [+] Building 29.1s (10/10) FINISHED
> >
> > docker:default
> >  => CACHED [internal] load remote build context
> >
> >   0.2s
> >  => [internal] load metadata for
> > docker.io/library/eclipse-temurin:17-jre-jammy
> >
> >   0.3s
> >  => CACHED [1/7] FROM
> >
> docker.io/library/eclipse-temurin:17-jre-jammy@sha256:1b646daef966395c93995e73347d4c7c726c9ddba8695e984cd8dcf5d8b5b253
> >0.0s
> >  => [2/7] RUN set -ex;   apt-get update;   apt-get -y
> > --no-install-recommends install wget gpg gnupg dirmngr;   rm -rf
> > /var/lib/apt/lists/*;   export SOLR_BINARY="solr-9.6.0.tgz";   MAX_RED
> >  20.7s
> >  => [3/7] RUN set -ex;   groupadd -r --gid "8983" "solr";   useradd -r
> > --uid "8983" --gid "8983" "solr"
> >   0.4s
> >  => [4/7] RUN set -ex;   (cd /opt; ln -s solr-*/ solr);   rm -Rf
> > /opt/solr/docs /opt/solr/docker/Dockerfile;
> >0.4s
> >  => [5/7] RUN set -ex;   mkdir -p /opt/solr/server/solr/lib
> > /docker-entrypoint-initdb.d;   cp /opt/solr/bin/solr.in.sh /etc/default/
> > solr.in.sh;   mv /opt/solr/bin/solr.in.sh /opt/solr/bin/so  0.5s
> >  => [6/7] RUN set -ex; apt-get update; apt-get -y
> > --no-install-recommends install acl lsof procps wget netcat gosu tini
> > jattach; rm -rf /var/lib/apt/lists/*;   5.3s
> >  => [7/7] WORKDIR /opt/solr
> >
> >   0.1s
> >  => exporting to image
> >
> >  0.9s
> >  => => exporting layers
> >
> >   0.9s
> >  => => writing image
> > sha256:e426f6991bd325a5b01a31e90f3304ce45a787004c34fc6a90a2aa86c5193afc
> >
> >0.0s
> >  => => naming to docker.io/library/solr-rc:9.6.0-1
> >
> >0.0s
> > [+] Building 19.3s (10/10) FINISHED
> >
> > docker:default
> >  => [internal] load remote build context
> >
> >  0.2s
> >  => [internal] load metadata for
> > docker.io/library/eclipse-temurin:17-jre-jammy
> >
> >   0.2s
> >  => CACHED [1/7] FROM
> >
> docker.io/library/eclipse-temurin:17-jre-jammy@sha256:1b646daef966395c93995e73347d4c7c726c9ddba8695e984cd8dcf5d8b5b253
> >0.0s
> >  => [2/7] RUN set -ex;   apt-get update;   apt-get -y
> > --no-install-recommends install wget gpg gnupg dirmngr;   rm -rf
> > /var/lib/apt/lists/*;   export SOLR_BINARY="solr-9.6.0-slim.tgz";   MA
> >  11.3s
> >  => [3/7] RUN set -ex;   groupadd -r --gid "8983" "solr";   useradd -r
> > --uid "8983" --gid "8983" "solr"
> >   0.5s
> >  => [4/7] RUN set -ex;   (cd /opt; ln -s solr-*/ solr);   rm -Rf
> > /opt/solr/docs /opt/solr/docker/Dockerfile;
> >0.5s
> >  => [5/7] RUN set -ex;   mkdir -p /opt/solr/server/solr/lib
> > /docker-entrypoint-initdb.d;   cp /opt/solr/bin/solr.in.sh /etc/default/
> > solr.in.sh;   mv /opt/solr/bin/solr.in.sh /opt/solr/bin/so  0.5s
> >  => [6/7] RUN set -ex; apt-get update; apt-get -y
> > 

Re: MixedCase or dashed-case for long options in Solr CLI?

[Arrieta, Alejandro]

I prefer

—zk-host

Kind Regards,
Alejandro Arrieta

On Mon, Mar 4, 2024 at 8:45 AM Eric Pugh 
wrote:

> “zkHost” —> “—zk-host” or “—zkhost” ?
>
>
> > On Mar 4, 2024, at 6:34 AM, Eric Pugh 
> wrote:
> >
> > Kebab!  I love it.
> >
> >
> >> On Mar 3, 2024, at 1:14 PM, Arrieta, Alejandro <
> aarri...@perrinsoftware.com> wrote:
> >>
> >> Hello,
> >>
> >> dashed-case is called kebab case almost everywhere. One example:
> >> https://www.theserverside.com/definition/Kebab-case
> >> I was looking at the meaning of dashed-case, and it always pointed to
> >> kebab-case.
> >>
> >> Having kebab, Kamel, and other cases helps troubleshoot over a
> conference
> >> to see command errors faster or to tell where to insert other words.
> >> For scripts it does not matter imho.
> >>
> >> Yes, please go with Kebab case everything. Now you know the most common
> >> name it will never go away.
> >>
> >> Kind Regards,
> >> Alejandro Arrieta
> >>
> >> On Sun, Mar 3, 2024 at 2:10 PM Eric Pugh <
> ep...@opensourceconnections.com <mailto:ep...@opensourceconnections.com>>
> >> wrote:
> >>
> >>> Thanks all for weighing in.   So I’m going to go for —dashed-case for
> long
> >>> options.   So expect some —solr-url and —zk-host parameters coming!
> >>>
> >>>
> >>>
> >>>> On Feb 26, 2024, at 10:28 AM, Walter Underwood  >
> >>> wrote:
> >>>>
> >>>> Long options are dashed-case, following the GNU convention. POSIX only
> >>> specifies single character options. The “—“ prefix for long options is
> a
> >>> GNU invention, as far as I know. Older Unix commands with long option
> >>> names, e.g. find, only use a single dash.
> >>>>
> >>>>
> https://www.gnu.org/software/libc/manual/html_node/Argument-Syntax.html
> >>>>
> https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap12.html
> >>>>
> >>>> wunder
> >>>> Walter Underwood
> >>>> wun...@wunderwood.org <mailto:wun...@wunderwood.org>  wun...@wunderwood.org>
> >>>> http://observer.wunderwood.org/  (my blog)
> >>>>
> >>>>> On Feb 26, 2024, at 5:29 AM, Eric Pugh <
> ep...@opensourceconnections.com <mailto:ep...@opensourceconnections.com>
> >>> <mailto:ep...@opensourceconnections.com>> wrote:
> >>>>>
> >>>>> I hear a vote for dashed-case, how about some more votes?
> >>> —solr-update-url versus —solrUpdateUrl ?
> >>>>>
> >>>>>
> >>>>>
> >>>>>> On Feb 26, 2024, at 7:29 AM, Jason Gerlowski  <mailto:gerlowsk...@gmail.com>>
> >>> wrote:
> >>>>>>
> >>>>>> My guess is that "dashed-case" is slightly more common -- at least,
> >>>>>> that's my sense from haphazardly checking a few tools I use often
> >>>>>> ("curl", "kubectl", "git", "docker").
> >>>>>>
> >>>>>> But I don't have an opinion as long as we're internally consistent
> >>>>>> about using one convention or the other.
> >>>>>>
> >>>>>> Best,
> >>>>>>
> >>>>>> Jason
> >>>>>>
> >>>>>> On Sat, Feb 24, 2024 at 11:35 AM Eric Pugh
> >>>>>>  ep...@opensourceconnections.com>  >>> ep...@opensourceconnections.com  ep...@opensourceconnections.com>> <mailto:ep...@opensourceconnections.com
> >>
> >>> wrote:
> >>>>>>>
> >>>>>>> Hi all,
> >>>>>>>
> >>>>>>> I wanted to get the communities input on formatting of long options
> >>> for the Solr CLI.   I noticed on
> >>> https://commons.apache.org/proper/commons-cli/ that their examples all
> >>> are —dashed-case.
> >>>>>>>
> >>>>>>> However, we have —solrUrl or —zkHost as our pattern.   Though in
> >>> working on the PostTool, I used —solr-update-url as the parameter
> because I
> >>> had been reading the commons-cli docs...
> >>>>>>>
> >>>>>>> I’d like to get this sorted so that I can get
> >>> htt

Re: MixedCase or dashed-case for long options in Solr CLI?

[Arrieta, Alejandro]

 Hello,

dashed-case is called kebab case almost everywhere. One example:
https://www.theserverside.com/definition/Kebab-case
I was looking at the meaning of dashed-case, and it always pointed to
kebab-case.

Having kebab, Kamel, and other cases helps troubleshoot over a conference
to see command errors faster or to tell where to insert other words.
For scripts it does not matter imho.

Yes, please go with Kebab case everything. Now you know the most common
name it will never go away.

Kind Regards,
Alejandro Arrieta

On Sun, Mar 3, 2024 at 2:10 PM Eric Pugh 
wrote:

> Thanks all for weighing in.   So I’m going to go for —dashed-case for long
> options.   So expect some —solr-url and —zk-host parameters coming!
>
>
>
> > On Feb 26, 2024, at 10:28 AM, Walter Underwood 
> wrote:
> >
> > Long options are dashed-case, following the GNU convention. POSIX only
> specifies single character options. The “—“ prefix for long options is a
> GNU invention, as far as I know. Older Unix commands with long option
> names, e.g. find, only use a single dash.
> >
> > https://www.gnu.org/software/libc/manual/html_node/Argument-Syntax.html
> > https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap12.html
> >
> > wunder
> > Walter Underwood
> > wun...@wunderwood.org 
> > http://observer.wunderwood.org/  (my blog)
> >
> >> On Feb 26, 2024, at 5:29 AM, Eric Pugh  > wrote:
> >>
> >> I hear a vote for dashed-case, how about some more votes?
>  —solr-update-url versus —solrUpdateUrl ?
> >>
> >>
> >>
> >>> On Feb 26, 2024, at 7:29 AM, Jason Gerlowski 
> wrote:
> >>>
> >>> My guess is that "dashed-case" is slightly more common -- at least,
> >>> that's my sense from haphazardly checking a few tools I use often
> >>> ("curl", "kubectl", "git", "docker").
> >>>
> >>> But I don't have an opinion as long as we're internally consistent
> >>> about using one convention or the other.
> >>>
> >>> Best,
> >>>
> >>> Jason
> >>>
> >>> On Sat, Feb 24, 2024 at 11:35 AM Eric Pugh
> >>>  ep...@opensourceconnections.com> >
> wrote:
> 
>  Hi all,
> 
>  I wanted to get the communities input on formatting of long options
> for the Solr CLI.   I noticed on
> https://commons.apache.org/proper/commons-cli/ that their examples all
> are —dashed-case.
> 
>  However, we have —solrUrl or —zkHost as our pattern.   Though in
> working on the PostTool, I used —solr-update-url as the parameter because I
> had been reading the commons-cli docs...
> 
>  I’d like to get this sorted so that I can get
> https://issues.apache.org/jira/browse/SOLR-16824 over the finish line.
>  So please do speak up with preferences!   (And please let’s not support
> both!)
> 
> 
>  The changes to the formatting will be a 10x thing.
> 
>  Eric
> 
>  ___
>  Eric Pugh | Founder & CEO | OpenSource Connections, LLC |
> 434.466.1467 | http://www.opensourceconnections.com <
> http://www.opensourceconnections.com/> <
> http://www.opensourceconnections.com/><
> http://www.opensourceconnections.com/> | My Free/Busy <
> http://tinyurl.com/eric-cal>
>  Co-Author: Apache Solr Enterprise Search Server, 3rd Ed <
> https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw
> >
>  This e-mail and all contents, including attachments, is considered to
> be Company Confidential unless explicitly stated otherwise, regardless of
> whether attachments are marked as such.
> 
> >>>
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org  dev-unsubscr...@solr.apache.org> 
> >>> For additional commands, e-mail: dev-h...@solr.apache.org  dev-h...@solr.apache.org> 
> >> ___
> >> Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467
> | http://www.opensourceconnections.com <
> http://www.opensourceconnections.com/> <
> http://www.opensourceconnections.com/> | My Free/Busy <
> http://tinyurl.com/eric-cal>
> >> Co-Author: Apache Solr Enterprise Search Server, 3rd Ed <
> https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw>
>
> >> This e-mail and all contents, including attachments, is considered to
> be Company Confidential unless explicitly stated otherwise, regardless of
> whether attachments are marked as such.
>
> ___
> Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467 |
> http://www.opensourceconnections.com <
> http://www.opensourceconnections.com/> | My Free/Busy <
> http://tinyurl.com/eric-cal>
> Co-Author: Apache Solr Enterprise Search Server, 3rd Ed <
> 

Re: Moving to bin/solr start defaulting to SolrCloud mode?

[Arrieta, Alejandro]

 Hello Eric,

1) The idea here is that when a user run’s “bin/solr start” it fires up an
embedded zookeeper.   Same behavior as “bin/solr -c” in Solr 9.5.If you
have a Zookeeper Ensemble then “bin/solr start -z YOUR_ZK_SETUP” would
connect to the external ensemble instead.
If Solrcloud is the new default, this sounds good to me from a user
perspective.

2) bin/solr start —standalone
I have always known the modes as standalone and solrcloud. But current
documentation uses "user-managed" instead of "standalone":
https://solr.apache.org/guide/solr/latest/deployment-guide/cluster-types.html#solrcloud-mode
Mail thread shared by Jan uses "standalone" too.
IMHO, standalone describes it better, but if all users know it as
"user-managed" and documentation uses that name.

2) Ref Guide changes to put Solrcloud first and standalone/user-managed
second.
Not all docs have solrcloud at the end. Some point to a different page for
solrcloud at the start, like Backups:
https://solr.apache.org/guide/solr/latest/deployment-guide/backup-restore.html
The new/current default should appear first in the documentation, including
the starting guide. I know from my experience users will not read the
complete page and use/test the first part.

Kind Regards,
Alejandro Arrieta

On Mon, Feb 26, 2024 at 9:23 AM Jason Gerlowski 
wrote:

> Thanks for the link to that 2021 discussion Jan - had forgotten about that.
>
> I agree that SIP-14 (or some portion of it) goes a long way towards
> making SolrCloud (w/ embedded ZK) a more serviceable default.
>
> On Fri, Feb 23, 2024 at 7:14 PM Jan Høydahl  wrote:
> >
> > Cross referencing earlier discussion "[DISCUSS] Make Cloud mode the
> default option in bin/solr" from May 2021:
> >  https://lists.apache.org/thread/79xp2xfvqwhr9zccmsvjvj0hckgg5m6w
> >
> > Some valid arguments for an against in that thread.
> >
> > Ideally I'd prefer SIP-14 to be done before embedded zk is promoted as
> the best way to run Solr.
> >
> > Jan
> >
> > > 23. feb. 2024 kl. 19:06 skrev Eric Pugh <
> ep...@opensourceconnections.com>:
> > >
> > > During today’s community discussion the topic of moving to defaulting
> to SolrCloud mode came up.
> > >
> > > The idea here is that when a user run’s “bin/solr start” it fires up
> an embedded zookeeper.   Same behavior as “bin/solr -c” in Solr 9.5.If
> you have a Zookeeper Ensemble then “bin/solr start -z YOUR_ZK_SETUP” would
> connect to the external ensemble instead.
> > >
> > > If you want to continue to use the class user managed mode, then
> bin/solr start —user-managed maybe?   Or bin/solr start —standalone ???
> > >
> > > Other changes would be to go through the Ref Guide and where we have
> both SolrCloud and non SolrCloud content that we make sure SolrCloud
> content is at the top instead of at the bottom.
> > >
> > > To me, this feels like a change that would go on main.
> > >
> > > Thoughts?
> > >
> > > Eric
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > ___
> > > Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467
> | http://www.opensourceconnections.com <
> http://www.opensourceconnections.com/> | My Free/Busy <
> http://tinyurl.com/eric-cal>
> > > Co-Author: Apache Solr Enterprise Search Server, 3rd Ed <
> https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw
> >
> > > This e-mail and all contents, including attachments, is considered to
> be Company Confidential unless explicitly stated otherwise, regardless of
> whether attachments are marked as such.
> > >
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org
> For additional commands, e-mail: dev-h...@solr.apache.org
>
>

Re: [dev help wanted] upgrade Solr to use Lucene 9.10

[Arrieta, Alejandro]

Hello Christine,

I will give it a go.
It is an excellent opportunity to learn and blog/video.
I just requested the Jira account to be able to answer the Jira.

Kind Regards,
Alejandro Arrieta

On Wed, Feb 21, 2024 at 6:03 AM Christine Poerschke (BLOOMBERG/ LONDON) <
cpoersc...@bloomberg.net> wrote:

> Hi Everyone,
>
> Apache Lucene 9.10 was recently released - would you be interested in
> contributing to update Solr to use it?
>
> Please see https://issues.apache.org/jira/browse/SOLR-17157 for details.
>
> Thanks,
> Christine

Re: [VOTE] Release Solr 9.5.0 RC3

[Arrieta, Alejandro]

Hello Team,

Awesome news.
I wrote a blog post about the procedure of testing the RC.
https://www.searchistheway.com/posts/How_to_help_Apache_Solr_project_testing_Solr_9.5.RC3/
It may be included in the next RC mail if useful.

Kind Regards,
Alejandro Arrieta

On Mon, Feb 12, 2024 at 11:38 AM Jason Gerlowski 
wrote:

> It's been >72h since the vote was initiated and the result is:
>
> +1  6  (5 binding)
>  0  0
> -1  0
>
> This vote has PASSED.
>
> Thanks all - I'll start finalizing the release today!
>
> On Sun, Feb 11, 2024 at 1:57 PM David Smiley  wrote:
>
> > +1 SUCCESS! [0:51:20.054401]
> >
> > BTW the first run failed due to a test.  I ran the repro line and it
> > did reproduce ... but just once and not again.  Didn't on main.
> > Didn't see in build failures (tracked via fucit.org) but saw once in
> > Gradle Enterprise albeit in that build 50 tests failed:
> >
> >
> https://ge.apache.org/s/noe3h4xdd6a5m/tests/overview?help=own-time=FAILED
> > I "beasted" shortly and didn't repro.
> >
> > gradlew :solr:core:test --tests
> >
> >
> "org.apache.solr.cloud.LeaderVoteWaitTimeoutTest.testMostInSyncReplicasCanWinElection"
> > -Ptests.jvms=8 "-Ptests.jvmargs=-XX:TieredStopAtLevel=1
> > -XX:+UseParallelGC -XX:ActiveProcessorCount=1
> > -XX:ReservedCodeCacheSize=120m" -Ptests.seed=3BEF0DB1F4994AE0
> > -Ptests.badapples=false -Ptests.file.encoding=UTF-8
> >
> > On Fri, Feb 9, 2024 at 6:48 AM Jan Høydahl 
> wrote:
> > >
> > > +1 (binding)
> > >
> > > SUCCESS! [0:42:27.908762]
> > >
> > > ALso built and started docker image.
> > >
> > > Jan
> > >
> > > > 7. feb. 2024 kl. 21:57 skrev Jason Gerlowski  >:
> > > >
> > > > Please vote for release candidate 3 for Solr 9.5.0
> > > >
> > > > The artifacts can be downloaded from:
> > > >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.5.0-RC3-rev-cdd27dd15c3a6574032e9b1b92b148ab4e383599
> > > >
> > > > You can run the smoke tester directly with this command:
> > > >
> > > > python3 -u dev-tools/scripts/smokeTestRelease.py \
> > > >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.5.0-RC3-rev-cdd27dd15c3a6574032e9b1b92b148ab4e383599
> > > >
> > > > You can build a release-candidate of the official docker images
> (full &
> > > > slim) using the following command:
> > > >
> > > > SOLR_DOWNLOAD_SERVER=
> > > >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.5.0-RC3-rev-cdd27dd15c3a6574032e9b1b92b148ab4e383599/solr
> > > > && \
> > > >  docker build
> > $SOLR_DOWNLOAD_SERVER/9.5.0/docker/Dockerfile.official-full \
> > > >--build-arg SOLR_DOWNLOAD_SERVER=$SOLR_DOWNLOAD_SERVER \
> > > >-t solr-rc:9.5.0-3 && \
> > > >  docker build
> > $SOLR_DOWNLOAD_SERVER/9.5.0/docker/Dockerfile.official-slim \
> > > >--build-arg SOLR_DOWNLOAD_SERVER=$SOLR_DOWNLOAD_SERVER \
> > > >-t solr-rc:9.5.0-3-slim
> > > >
> > > > The vote will be open for at least 72 hours i.e. until 2024-02-10
> > 21:00 UTC.
> > > >
> > > > [ ] +1  approve
> > > > [ ] +0  no opinion
> > > > [ ] -1  disapprove (and reason why)
> > > >
> > > > Here is my +1
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org
> > > For additional commands, e-mail: dev-h...@solr.apache.org
> > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org
> > For additional commands, e-mail: dev-h...@solr.apache.org
> >
> >
>

Re: [VOTE] Release Solr 9.5.0 RC3

[Arrieta, Alejandro]

+1 not binding

SUCCESS! [0:38:06.897217]

and solr operator:
$ SOLR_IMAGE=solr-rc:9.5.0-3 make e2e-tests

Ran 23 of 23 Specs in 503.584 seconds
SUCCESS! -- 23 Passed | 0 Failed | 0 Pending | 0 Skipped


Ginkgo ran 1 suite in 8m46.160736769s
Test Suite Passed

Kind regards,
Alejandro Arrieta

On Thu, Feb 8, 2024 at 2:09 PM Houston Putman  wrote:

> +1 (binding)
>
> SUCCESS! [0:32:49.440577]
>
> I also built both docker images, and ran the Solr Operator integration
> tests with the full image:
>
> $ SOLR_IMAGE=solr-rc:9.5.0-3 make e2e-tests
> ...
>
> •••
>
>
> Ran 23 of 23 Specs in 642.235 seconds
> SUCCESS! -- 23 Passed | 0 Failed | 0 Pending | 0 Skipped
>
>
> - Houston
>
> On Wed, Feb 7, 2024 at 6:30 PM Kevin Risden  wrote:
>
> > +1 binding
> >
> > SUCCESS! [0:34:18.332100]
> >
> > Kevin Risden
> >
> >
> > On Wed, Feb 7, 2024 at 3:58 PM Jason Gerlowski 
> > wrote:
> >
> > > Please vote for release candidate 3 for Solr 9.5.0
> > >
> > > The artifacts can be downloaded from:
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.5.0-RC3-rev-cdd27dd15c3a6574032e9b1b92b148ab4e383599
> > >
> > > You can run the smoke tester directly with this command:
> > >
> > > python3 -u dev-tools/scripts/smokeTestRelease.py \
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.5.0-RC3-rev-cdd27dd15c3a6574032e9b1b92b148ab4e383599
> > >
> > > You can build a release-candidate of the official docker images (full &
> > > slim) using the following command:
> > >
> > > SOLR_DOWNLOAD_SERVER=
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.5.0-RC3-rev-cdd27dd15c3a6574032e9b1b92b148ab4e383599/solr
> > > &&
> > > <
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.5.0-RC3-rev-cdd27dd15c3a6574032e9b1b92b148ab4e383599/solr&;
> > >
> > > \
> > >   docker build
> > $SOLR_DOWNLOAD_SERVER/9.5.0/docker/Dockerfile.official-full
> > > \
> > > --build-arg SOLR_DOWNLOAD_SERVER=$SOLR_DOWNLOAD_SERVER \
> > > -t solr-rc:9.5.0-3 && \
> > >   docker build
> > $SOLR_DOWNLOAD_SERVER/9.5.0/docker/Dockerfile.official-slim
> > > \
> > > --build-arg SOLR_DOWNLOAD_SERVER=$SOLR_DOWNLOAD_SERVER \
> > > -t solr-rc:9.5.0-3-slim
> > >
> > > The vote will be open for at least 72 hours i.e. until 2024-02-10 21:00
> > > UTC.
> > >
> > > [ ] +1  approve
> > > [ ] +0  no opinion
> > > [ ] -1  disapprove (and reason why)
> > >
> > > Here is my +1
> > >
> >
>

Re: [VOTE] Release Solr 9.5.0 RC2

[Arrieta, Alejandro]

Hello Team,

SUCCESS! [0:44:46.772429]

docker full and slim created fine.

+1 non binding

Kind Regards,
Alejandro Arrieta


On Tue, Feb 6, 2024 at 1:37 PM Houston Putman  wrote:

> +1 (binding)
>
> SUCCESS! [0:32:51.658820]
>
> I also built both Docker images and ran the Solr Operator integration tests
> with the full image:
>
> •••
>
> Ran 23 of 23 Specs in 450.649 seconds
> SUCCESS! -- 23 Passed | 0 Failed | 0 Pending | 0 Skipped
>
> - Houston
>
> On Tue, Feb 6, 2024 at 11:43 AM Jason Gerlowski 
> wrote:
>
> > Please vote for release candidate 2 for Solr 9.5.0
> >
> > The artifacts can be downloaded from:
> >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.5.0-RC2-rev-b03df01e89e64bc897a6be93de00af9ded2ee99b
> >
> > You can run the smoke tester directly with this command:
> >
> > python3 -u dev-tools/scripts/smokeTestRelease.py \
> >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.5.0-RC2-rev-b03df01e89e64bc897a6be93de00af9ded2ee99b
> >
> > You can build a release-candidate of the official docker images (full &
> > slim) using the following command:
> >
> > SOLR_DOWNLOAD_SERVER=
> >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.5.0-RC2-rev-b03df01e89e64bc897a6be93de00af9ded2ee99b/solr
> > &&
> > <
> https://dist.apache.org/repos/dist/dev/solr/solr-9.5.0-RC2-rev-b03df01e89e64bc897a6be93de00af9ded2ee99b/solr&;
> >
> > \
> >   docker build
> $SOLR_DOWNLOAD_SERVER/9.5.0/docker/Dockerfile.official-full
> > \
> > --build-arg SOLR_DOWNLOAD_SERVER=$SOLR_DOWNLOAD_SERVER \
> > -t solr-rc:9.5.0-2 && \
> >   docker build
> $SOLR_DOWNLOAD_SERVER/9.5.0/docker/Dockerfile.official-slim
> > \
> > --build-arg SOLR_DOWNLOAD_SERVER=$SOLR_DOWNLOAD_SERVER \
> > -t solr-rc:9.5.0-2-slim
> >
> > The vote will be open for at least 72 hours i.e. until 2024-02-09 18:00
> > UTC.
> >
> > [ ] +1  approve
> > [ ] +0  no opinion
> > [ ] -1  disapprove (and reason why)
> >
> > Here is my +1 (binding)
> >
>

Re: [VOTE] Release Solr 9.4.1 RC1

[Arrieta, Alejandro]

+1 (not binding)

SUCCESS! [0:43:05.715183]

built solr and solr-slim successfully.

note: back online after a crazy end of year 2023.

On Tue, Jan 16, 2024 at 7:03 PM Houston Putman  wrote:

> +1 (binding)
>
> SUCCESS! [0:51:47.471576]
>
> I also successfully built both Docker images and ran the Solr Operator
> integration tests with the full image:
>
> Will run 23 of 23 specs
> Running in parallel across 3 processes
> •••
>
> Ran 23 of 23 Specs in 433.438 seconds
> SUCCESS! -- 23 Passed | 0 Failed | 0 Pending | 0 Skipped
>
> - Houston
>
> On Tue, Jan 16, 2024 at 8:28 AM Kevin Risden  wrote:
>
> > +1 (binding)
> >
> > SUCCESS! [0:33:05.648738]
> >
> > Kevin Risden
> >
> >
> > On Sat, Jan 13, 2024 at 3:34 PM Jan Høydahl 
> wrote:
> >
> > > +1 (binding)
> > >
> > > SUCCESS! [0:42:51.792486]
> > >
> > > Also built docker container and spun up the server locally.
> > >
> > >
> > > PS: Need to remove extra newline between the two lines of command when
> > > copy/pasting:
> > >
> > > python3 -u dev-tools/scripts/smokeTestRelease.py \
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.4.1-RC1-rev-57762a5b52a9d40a6f15441c4adeb76f0b045476
> > >
> > > Jan
> > >
> > > > 13. jan. 2024 kl. 17:14 skrev David Smiley :
> > > >
> > > > Please vote for release candidate 1 for Solr 9.4.1
> > > >
> > > > The artifacts can be downloaded from:
> > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.4.1-RC1-rev-57762a5b52a9d40a6f15441c4adeb76f0b045476
> > > >
> > > >
> > > > You can run the smoke tester directly with this command:
> > > >
> > > >
> > > > python3 -u dev-tools/scripts/smokeTestRelease.py \
> > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.4.1-RC1-rev-57762a5b52a9d40a6f15441c4adeb76f0b045476
> > > >
> > > >
> > > > You can build a release-candidate of the official docker images
> (full &
> > > > slim) using the following command:
> > > >
> > > >
> > > > SOLR_DOWNLOAD_SERVER=
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.4.1-RC1-rev-57762a5b52a9d40a6f15441c4adeb76f0b045476/solr
> > > > && \
> > > >
> > > >  docker build
> > > $SOLR_DOWNLOAD_SERVER/9.4.1/docker/Dockerfile.official-full \
> > > >
> > > >--build-arg SOLR_DOWNLOAD_SERVER=$SOLR_DOWNLOAD_SERVER \
> > > >
> > > >-t solr-rc:9.4.1-1 && \
> > > >
> > > >  docker build
> > > $SOLR_DOWNLOAD_SERVER/9.4.1/docker/Dockerfile.official-slim \
> > > >
> > > >--build-arg SOLR_DOWNLOAD_SERVER=$SOLR_DOWNLOAD_SERVER \
> > > >
> > > >-t solr-rc:9.4.1-1-slim
> > > >
> > > >
> > > > The vote will be open for at least 72 hours i.e. until 2024-01-16
> 17:00
> > > UTC.
> > > >
> > > >
> > > > [ ] +1  approve
> > > >
> > > > [ ] +0  no opinion
> > > >
> > > > [ ] -1  disapprove (and reason why)
> > > >
> > > >
> > > > Here is my +1
> > > >
> > > > ~ David Smiley
> > > > Apache Lucene/Solr Search Developer
> > > > http://www.linkedin.com/in/davidwsmiley
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org
> > > For additional commands, e-mail: dev-h...@solr.apache.org
> > >
> > >
> >
>

Help Solr Newsletter October 2023 with links, blogs, articles

[Arrieta, Alejandro]

Hello Solr Community,

We are working on the October Newsletter, and Solr/Lucene/search-related
content is welcome.

Please check the draft here:
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=272927879

If the content you want to suggest is not there, please add it to the wiki
or reply to this email thread with the following:

title
Two lines description
link

What we are looking for is:

-meetups or conferences that will take place in the following months,
starting in November 2023.
-blogs, photos, videos, and recordings of the Search/Solr/Lucene-related
meetups conference in October 2023 or before. If the talk is good, could
you send the link?
-any article, blog, post, or link you think is exciting and relevant to
Solr/Search/Lucene/community, even if it is older.

We plan to finish the Solr Newsletter October 2023 edition on the first
days of November. You still have five days.

Kind Regards,
Alejandro Arrieta

Re: [DISCUSS] Community Virtual Meetup, October 2023

[Arrieta, Alejandro]

Hello Team,

Updated the Solr Wiki.
Joined/created a meetup account.
Posted on Linkedin:
https://www.linkedin.com/posts/alejandro-arrieta_solr-apachesolr-opensource-activity-7121032862354530304-tSiV
Posted on Twitter/X: https://x.com/searchistheway/status/1715270164428530142
Advertising the meetup with 6-7 days in advance.

Question: should I put the conference link to the wiki before the day of
the conference?

Kind Regards,
Alejandro Arrieta

On Thu, Oct 19, 2023 at 10:57 AM Jason Gerlowski 
wrote:

> > Please the meetup group owner can create the meetup and zoom/meet link,
> so we can start sharing about the meetup on social media?
>
> Created, see below!  (Don't forget to put these on the Confluence
> "Meeting Notes" page when you get a chance)
>
> Meet link: https://meet.google.com/vov-zirs-mno
>
> Meetup.com event:
>
> https://www.meetup.com/apache-solr-virtual-community-meetups/events/296835049
> (If you organize again in the future and you create a Meetup.com
> account, we can give you the required permissions to create this
> yourself next time.)
>
> Thanks again Alejandro!
>
> Jason
>
> On Thu, Oct 19, 2023 at 9:25 AM Alessandro Benedetti
>  wrote:
> >
> > I'll be travelling to the Middle East (it should be 19:00 where I'll be),
> > I'll try to attend!
> >
> > The idea of a competition is a cool one, I'm not a fan of rushing stuff
> and
> > I'm not sure how much time we should allocate to such an activity, I
> > suspect half an hour will not produce anything useful.
> > But I'm definitely happy to see this as a separate new activity!
> >
> > --
> > *Alessandro Benedetti*
> > Director @ Sease Ltd.
> > *Apache Lucene/Solr Committer*
> > *Apache Solr PMC Member*
> >
> > e-mail: a.benede...@sease.io
> >
> >
> > *Sease* - Information Retrieval Applied
> > Consulting | Training | Open Source
> >
> > Website: Sease.io <http://sease.io/>
> > LinkedIn <https://linkedin.com/company/sease-ltd> | Twitter
> > <https://twitter.com/seaseltd> | Youtube
> > <https://www.youtube.com/channel/UCDx86ZKLYNpI3gzMercM7BQ> | Github
> > <https://github.com/seaseltd>
> >
> >
> > On Thu, 19 Oct 2023 at 14:22, Arrieta, Alejandro <
> > aarri...@perrinsoftware.com> wrote:
> >
> > > Hello Team,
> > >
> > > Option A:
> > > Thursday, Oct  26th, 9 AM Pacific/12PM US East
> > > had the most/all votes so we have date and time.
> > >
> > > Please the meetup group owner can create the meetup and zoom/meet
> link, so
> > > we can start sharing about the meetup on social media?
> > >
> > > Solr Wiki meetup link:
> > >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=272927807
> > >
> > > Note: I created the newsletter as meeting notes and they appear on the
> list
> > > of meetups, I will fix this later today. First time using Solr Wiki.
> > >
> > > Kind Regards,
> > > Alejandro Arrieta
> > >
> > >
> > > On Tue, Oct 17, 2023 at 8:21 AM Jason Gerlowski  >
> > > wrote:
> > >
> > > > Thanks for volunteering Alejandro.  Option 1 works for me.
> > > >
> > > > Ping me here or on Slack if you run into any permission issues (in
> > > > Confluence, Meetup.com, etc.) getting things setup for the meetup;
> > > > happy to help!
> > > >
> > > > > eating your own dogfood kind of competitions
> > > >
> > > > I really like the idea!  Though I agree with David that it seems like
> > > > something that maybe merits its own event.  Unless the actual
> > > > challenge part is asynchronous/offline?  That'd maybe be a bit less
> > > > social/interactive, but it would help us fit the idea into the
> current
> > > > monthly meetup, if that's the goal.  Anyway, definitely a fun idea
> > > > worth pursuing!  Maybe spin off a separate thread to discuss, Ishan?
> > > >
> > > > Best,
> > > >
> > > > Jason
> > > >
> > > > On Tue, Oct 17, 2023 at 12:43 AM David Smiley <
> david.w.smi...@gmail.com>
> > > > wrote:
> > > > >
> > > > > I prefer the 26th (Thursday) as well.
> > > > > ~ David
> > > > >
> > > > >
> > > > > On Mon, Oct 16, 2023 at 11:06 AM Arrieta, Alejandro <
> > > > > aarri...@perrinsoftware.com> wrote:
> > > >

Re: [Operator] [VOTE] Release the Solr Operator v0.8.0 RC1

[Arrieta, Alejandro]

Hello Team,

+1 non-binding

...
Local end-to-end cluster test successfully run!




Successfully smoke tested the Solr Operator v0.8.0!

Kind Regards,
Alejandro Arrieta

On Thu, Oct 19, 2023 at 11:53 PM Mark Miller  wrote:

> +1
>
> Successfully smoke tested the Solr Operator v0.8.0!
>
> On Mon, Oct 16, 2023 at 2:37 PM Jason Gerlowski 
> wrote:
>
> > Please vote for release candidate 1 for the Solr Operator v0.8.0
> >
> > The artifacts can be downloaded from:
> >
> >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-operator/solr-operator-v0.8.0-RC1-revf2c27102a7e9056c6fe7d8cea6c97bac5a47fcc0
> >
> > You can run the full smoke tester, with instructions below.
> > However, it is also encouraged to go and use the artifacts yourself in
> > a test Kubernetes cluster.
> > The smoke tester does not require you to download or install the RC
> > artifacts before running.
> > If you plan on just running the smoke tests, then ignore all other
> > instructions.
> >
> > The artifacts are laid out in the following way:
> >   * solr-operator-v0.8.0.tgz - Contains the source release
> >   * crds/ - Contains the CRD files
> >   * helm-charts/ - Contains the Helm release packages
> >
> > The RC Docker image can be found at:
> >   apache/solr-operator:v0.8.0-rc1
> >
> > The RC Helm repo can be added with:
> >   helm repo add apache-solr-rc
> >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-operator/solr-operator-v0.8.0-RC1-revf2c27102a7e9056c6fe7d8cea6c97bac5a47fcc0/helm-charts
> >
> > You can install the RC Solr Operator and Solr CRDs and an example Solr
> > Cloud with:
> >   curl -sL0 "https://dist.apache.org/repos/dist/release/solr/KEYS; |
> > gpg --import --quiet
> >   # This will export your public keys into a format that helm can
> > understand.
> >   # Skip verification by removing "--verify" in the helm command below.
> >   if ! (gpg --no-default-keyring --keyring=~/.gnupg/pubring.gpg
> > --list-keys "60392455"); then gpg --export >~/.gnupg/pubring.gpg; fi
> >   kubectl create -f
> >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-operator/solr-operator-v0.8.0-RC1-revf2c27102a7e9056c6fe7d8cea6c97bac5a47fcc0/crds/all-with-dependencies.yaml
> > || \
> > kubectl replace -f
> >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-operator/solr-operator-v0.8.0-RC1-revf2c27102a7e9056c6fe7d8cea6c97bac5a47fcc0/crds/all-with-dependencies.yaml
> >   helm install --verify solr-operator apache-solr-rc/solr-operator
> > --set image.tag=v0.8.0-rc1
> >   helm install --verify example apache-solr-rc/solr
> >
> > You can run the full smoke tester directly with this command: (First
> > checkout the release-0.8 branch of the solr-operator)
> >
> > # First clear your go-mod cache to make sure old cache entries don't
> > cause smoke test failures
> > make mod-clean
> > ./hack/release/smoke_test/smoke_test.sh -v "v0.8.0" -s "f2c2710" -i
> > "apache/solr-operator:v0.8.0-rc1" -g "60392455" \
> > -l '
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-operator/solr-operator-v0.8.0-RC1-revf2c27102a7e9056c6fe7d8cea6c97bac5a47fcc0
> > '
> >
> > If you want to run the smoke test with a specific version of
> > kubernetes, use the -k option with a full version tag. (e.g. -k
> > v1.19.3)
> > If you want to run the smoke test with a custom version of solr, use
> > the -t option with an official Solr image version. (e.g. -t 8.10.0)
> >   However, for this smoke test, you must use a solr version that
> > supports incremental backups. (i.e. 8.9+)
> >
> > Make sure you have the following installed before running the smoke test:
> >   - Docker (Give it enough memory and CPU to run ~12 containers, 3 of
> > which are Solr nodes)
> > More information on required resources can be found here:
> >
> https://kind.sigs.k8s.io/docs/user/quick-start/#settings-for-docker-desktop
> >   - Go 1.20
> >   - Kubectl
> >   - GnuPG
> >   - Helm v3.4.0+
> >   - Kustomize (v4.0.0+) This will be installed for you, but NOT
> > upgraded if a lower version is already installed.
> >   - yq
> >   - jq
> >   - coreutils (if using Mac OS)
> >
> > The vote will be open for at least 72 hours i.e. until 2023-10-19 20:00
> > UTC.
> >
> > [ ] +1  approve
> > [ ] +0  no opinion
> > [ ] -1  disapprove (and reason why)
> >
> > Here is my +1
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org
> > For additional commands, e-mail: dev-h...@solr.apache.org
> >
> >
>
> --
> - MRM
>

Re: [DISCUSS] Community Virtual Meetup, October 2023

[Arrieta, Alejandro]

Hello Team,

Option A:
Thursday, Oct  26th, 9 AM Pacific/12PM US East
had the most/all votes so we have date and time.

Please the meetup group owner can create the meetup and zoom/meet link, so
we can start sharing about the meetup on social media?

Solr Wiki meetup link:
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=272927807

Note: I created the newsletter as meeting notes and they appear on the list
of meetups, I will fix this later today. First time using Solr Wiki.

Kind Regards,
Alejandro Arrieta


On Tue, Oct 17, 2023 at 8:21 AM Jason Gerlowski 
wrote:

> Thanks for volunteering Alejandro.  Option 1 works for me.
>
> Ping me here or on Slack if you run into any permission issues (in
> Confluence, Meetup.com, etc.) getting things setup for the meetup;
> happy to help!
>
> > eating your own dogfood kind of competitions
>
> I really like the idea!  Though I agree with David that it seems like
> something that maybe merits its own event.  Unless the actual
> challenge part is asynchronous/offline?  That'd maybe be a bit less
> social/interactive, but it would help us fit the idea into the current
> monthly meetup, if that's the goal.  Anyway, definitely a fun idea
> worth pursuing!  Maybe spin off a separate thread to discuss, Ishan?
>
> Best,
>
> Jason
>
> On Tue, Oct 17, 2023 at 12:43 AM David Smiley 
> wrote:
> >
> > I prefer the 26th (Thursday) as well.
> > ~ David
> >
> >
> > On Mon, Oct 16, 2023 at 11:06 AM Arrieta, Alejandro <
> > aarri...@perrinsoftware.com> wrote:
> >
> > > Hello Team,
> > >
> > > 1) pick me
> > >
> > > 2) proposed dates/time
> > > Thursday, Oct  26th, 9 AM Pacific/12PM US East
> > > or
> > > Friday, Oct  27th, 9 AM Pacific/12PM US East
> > > To have at least one week to promote the event.
> > > The vote should end Wednesday, Oct 18th, 11:59 PM Pacific, to publish
> the
> > > meetup link on Thursday, Oct 19th.
> > >
> > > Kind Regards,
> > > Alejandro Arrieta
> > >
> > > On Mon, Oct 16, 2023 at 9:40 AM Jason Gerlowski  >
> > > wrote:
> > >
> > > > Hey all,
> > > >
> > > > It's time once again to start thinking ahead to our Virtual Meetup
> for
> > > > October.  As always, there's two main questions to answer in terms of
> > > > planning:
> > > >
> > > > 1. Any volunteers to organize?  Organizer duties are pretty light and
> > > > are summarized here:
> > > > https://cwiki.apache.org/confluence/display/SOLR/Meeting+notes.
> > > > Volunteers get some discretion in terms of picking a meeting time/day
> > > > that works for them.  If there are no volunteers by mid-week or so,
> I'm
> > > > more than happy to set things up for this month.
> > > >
> > > > 2. When should we meet?  It's already a good bit into the month, so
> > > > we'll have to plan for the latter half.  If you have any
> > > > opinions, please discuss.
> > > >
> > > > Best,
> > > >
> > > > Jason
> > > >
> > > > -
> > > > To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org
> > > > For additional commands, e-mail: dev-h...@solr.apache.org
> > > >
> > > >
> > >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org
> For additional commands, e-mail: dev-h...@solr.apache.org
>
>

Re: Apache Solr Newsletter proposal September 2023

[Arrieta, Alejandro]

Hello Team,

> I'm not very comfortable over-publicizing what I view as a first draft of
>the first edition.
Sure, no problem. Nothing shared.

>What is 10-20-30 about?
The number of news/links available for that newsletter. We need to decide
on the minimum news (non-relevant, like a new release) to publish the
newsletter. If there is not enough news, we roll over them to next month.

>At first you seemed super fixed on monthly, here you seem more
>flexible.
If we do not set an internal monthly release goal, it will continue to next
month. But if there is not enough/relevant news for one month, nothing to
do, move to next month. That is why I did not mention "monthly newsletter"
in my draft/proposal, but instead, to start working on the October edition.

> BTW I just created
>https://cwiki.apache.org/confluence/display/SOLR/Newsletters as a parent
>for the newsletters.
Awesome. :-)

We need to establish how a draft/proposal becomes official. Maybe there is
already a default protocol, like for the release candidates.
Send the draft/link to wiki to dev the first day of each month and wait YY
hours for votes. If we do not have enough news for that month, inform the
dev and move all news to next month.

Note: I am just a member of the Solr community trying to help. I may not be
familiar with all the protocols or politics involved. :-)

Kind Regards,
Alejandro Arrieta

On Tue, Oct 17, 2023 at 7:49 PM David Smiley 
wrote:

> On Tue, Oct 17, 2023 at 1:01 PM Arrieta, Alejandro <
> aarri...@perrinsoftware.com> wrote:
>
> >
> > Editing:  I agree with David's comments.
> > I would add only one thing. The September edition is finished/over unless
> > something is wrong with it and needs to be fixed. Draft or not draft that
> > is the September edition.  It is better to use our limited time preparing
> > the October/November
>
> newsletter and make it better than the previous edition.
> >
>
> This is more about periodicity (covered below) than it is about editing.
>
>
> > I will share the September newsletter as Draft/Proposal on my social
> media
> > later today to make Solr noise :-)
> >
> > Publishing:
> > Anywhere it can be indexed by the googles and bings, and PC/Tablet/Mobile
> > can access it. Solr Wiki is fine.
> > We need to make noise about it everywhere: LinkedIn, Twitter/X, Mastodon,
> > mailing lists, ASF social media.
> > Here is one example of a newsletter from another project:
> > https://opensearch.org/blog/opensearch-newsletter-vol1-issue1/
>
>
> There's something to be said for not dating a newsletter, as I see there in
> the URL of that one.  Flexibility.
>
>
> > Brian told me they can share on ASF social media accounts what we need to
> > share, the newsletter, or a link to the newsletter. ASF publishes at
> least
> > once per one or two weeks project news on Linkedin. We need to send him
> > what and when to share it.
> >
>
> I'm not very comfortable over-publicizing what I view as a first draft of
> the first edition.
>
> I propose that *EITHER* (A): more text be put into the September
> newsletter, not to change the past, only to elaborate what happened in the
> past :-).  Then share it widely.  In its current form, I think it's too
> draft-like to be our first inaugural newsletter.  It will get attention;
> it's our first one.  I want to impress people and not have Solr appear
> second rate simply because you ran out of time Alejandro.  OR (B) let's
> make October's newsletter be the awesome one and that which will be shared
> widely.  Not September's newsletter.  That is what I would most prefer; we
> can announce both a new Solr version and also take the opportunity to
> highlight topics discussed at Community-over-Code.  WDYT?
>
>
> > Periodicity:
> > -If we have enough news/links to share on the release date (first three
> > days of the month), the threshold can be 10-20-30 news. If we do not have
> > that many, we do not release and join what we have next month.
> > IMHO, for the first months/releases, we can share old but still relevant
> > links or highlight Solr documentation.
> >
>
> What is 10-20-30 about?
>
>
> > -If something relevant happens, like a new release or some CVE that we
> need
> > to comment on, we do a release even if we are short of news/links. When
> the
> > next major release process starts, users know Solr 10 is coming.
> >
> >
> Sure.  At first you seemed super fixed on monthly, here you seem more
> flexible.  Hey whatever.
>
> BTW I just created
> https://cwiki.apache.org/confluence/display/SOLR/Newsletters as a parent
> for the newsletters.
>

Re: Apache Solr Newsletter proposal September 2023

[Arrieta, Alejandro]

one in the community?) send messages to readers
> >> like:
> >> ** ex: "who is actually using feature XYZ anyway?  No response means
> >> deprecation!"<--- yeah there we go, a threat to compel users to
> >> subscribe LOL
> >> ** ex: Interest in a meetup for Solr in city X.
> >>
> >> Even if it's "just links" (like Alejandro's first draft), it's better
> than
> >> no newsletter at all.  Over time, we can hope for more.
> >>
> >> 
> >>
> >> Jason's questions were spot on.
> >>
> >> Editing:  I think everyone with edit access to the Solr "space" in
> >> Confuence (mostly just commiters but + some others) should feel welcome
> to
> >> add/edit without permission at any time and without coordination.
> >> Confluence has tools to "watch" and see edit history.  Perhaps the
> >> non-published page can be named this clearly like "NEXT-DRAFT" which
> will
> >> later be renamed to a year-month like dated version once it's published,
> >> and they can all live in one listing (i.e. under one parent page for the
> >> newsletters).  Then treat it as read-only.  A "TEMPLATE" one might
> exist to
> >> create the next "NEXT-DRAFT".  Alejandro can lead this effort and add
> much
> >> of the content as he has time for.  He already has the first draft.
> >>
> >> Publishing: Not sure either on how it should be published exactly.
> >> Alejandro; what are you thinking?  Personally I think Confluence
> (in-place)
> >> is fine.  Maybe start this way because it's simple & adequate?  We might
> >> consider somewhere on the Solr website as an alternative.  There are
> many
> >> places where you could share a link. For some mediums like email,
> publish
> >> the newsletter content so nobody has to click the link (albeit still
> >> provide it).  Ensure the formatting is reasonable.  Alejandro, where was
> >> Brian Profit proposing that the ASF would share such a thing?  If the
> >> newsletter is mostly a list of links (as it is in its current form,
> albeit
> >> a draft), I think it should not be shared beyond Solr audiences (i.e.
> not
> >> beyond users@s.a.o email & slack).
> >>
> >> Periodicity:  I worry a little Alejandro if you or others feel this
> needs
> >> to be monthly, that it'll maybe be too burdensome, or that some months
> are
> >> simply not that interesting.  I recommend feeling free to be loose on
> the
> >> periodicity.  Maybe shoot for bi-monthly-ish?  I think publishing soon
> >> after a new release (we just did 9.4!) could be really useful for users
> >> that might just want to pay attention to the newsletter for news on
> >> releases.
> >>
> >> Thanks again.  Looking forward to further discussion!
> >>
> >> ~ David
> >>
> >>
> >> On Mon, Oct 16, 2023 at 10:17 AM Jason Gerlowski  >
> >> wrote:
> >>
> >>> Hi Alejandro,
> >>>
> >>> Thanks for taking the initiative on this!  You should now have
> >>> permission to create and edit pages in Confluence - let me know if
> >>> you're not seeing that on your end.  Happy to help with some
> >>> copy-editing once it's up there!
> >>>
> >>> Since this is the first of these newsletter proposals, maybe we should
> >>> also use this thread to discuss a few "process" questions around the
> >>> newsletter?  (Or maybe I missed these getting discussed elsewhere?)
> >>>
> >>> The biggest question I was curious about: what does "publication" look
> >>> like for these newsletters?  Will it be published in "Confluence", or
> >>> are we using Confluence for editing before eventually publishing in
> >>> some other medium like annou...@solr.apache.org, the Solr website,
> >>> etc.
> >>>
> >>> Best,
> >>>
> >>> Jason
> >>>
> >>> On Thu, Oct 12, 2023 at 7:09 PM Arrieta, Alejandro
> >>>  wrote:
> >>>>
> >>>> Hello Team,
> >>>>
> >>>> Newsletter on ASF social media:
> >>>> I just returned home from Community over Code, where I talked with the
> >>>> Asfinfra team, and they redirected me to talk with Brian Proffit.
> >>>> I talked with him about the new Solr newsletter, and he told me to
> send
> >>> him
> &

Re: [DISCUSS] Community Virtual Meetup, October 2023

[Arrieta, Alejandro]

Hello Team,

1) pick me

2) proposed dates/time
Thursday, Oct  26th, 9 AM Pacific/12PM US East
or
Friday, Oct  27th, 9 AM Pacific/12PM US East
To have at least one week to promote the event.
The vote should end Wednesday, Oct 18th, 11:59 PM Pacific, to publish the
meetup link on Thursday, Oct 19th.

Kind Regards,
Alejandro Arrieta

On Mon, Oct 16, 2023 at 9:40 AM Jason Gerlowski 
wrote:

> Hey all,
>
> It's time once again to start thinking ahead to our Virtual Meetup for
> October.  As always, there's two main questions to answer in terms of
> planning:
>
> 1. Any volunteers to organize?  Organizer duties are pretty light and
> are summarized here:
> https://cwiki.apache.org/confluence/display/SOLR/Meeting+notes.
> Volunteers get some discretion in terms of picking a meeting time/day
> that works for them.  If there are no volunteers by mid-week or so, I'm
> more than happy to set things up for this month.
>
> 2. When should we meet?  It's already a good bit into the month, so
> we'll have to plan for the latter half.  If you have any
> opinions, please discuss.
>
> Best,
>
> Jason
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org
> For additional commands, e-mail: dev-h...@solr.apache.org
>
>

Re: Some help needed to complete the release

[Arrieta, Alejandro]

Hello Alex,

Thanks for the release! :-)

I do not see 9.4-beta anywhere on
https://solr.apache.org/guide/solr/9_4/index.html (redirects to
https://solr.apache.org/guide/solr/latest/index.html)
If going from https://solr.apache.org/ -> resources -> reference guide
points to
https://solr.apache.org/guide
redirects to
https://solr.apache.org/guide/solr/latest/index.html
beta not on the menus to select the version, they show 9.4 and inside the
doc for example:

There are three separate packages:

   -

   solr-9.4.0.tgz the full binary package, for all operating systems. This
   package includes all first-party Solr modules and accessories (e.g. the
   prometheus-exporter).
   -

   solr-9.4.0-slim.tgz the slim binary package, for all operating systems.
   This package only includes what is necessary to run Solr. Modules and
   accessories (e.g. the prometheus-exporter) are not included.
   -

   solr-9.4.0-src.tgz the package Solr source code. This is useful if you
   want to develop on Solr without using the official Git repository.

Maybe there is a cache issue in your browser or latency on the refresh of
the pages (cdn)?

I hope this helps.

Kind Regards.
Alejandro Arrieta

On Sun, Oct 15, 2023 at 5:27 PM Alex Deparvu  wrote:

> Hi,
>
> I am completing the 9.4 release and I need some help with these steps
>
> The RefGuide version shows as `9.4-beta`: I have published everything
> following the wizard but the guide version shows up as 9.4-beta I probably
> forgot to check some box somewhere.
> https://solr.apache.org/guide/solr/9_4/index.html
>
> Step `8 - Announce the release`.
>
> > 4 - Add the new version to Wikipedia
>
> I don't have an account on wikidata.org - can anyone update this page, or
> should I create an account just for this release?
>
> > 5 - Add the new version to the Apache Release Reporter
>
> This is only available to PMC members:
> "Could not save. Make sure you have filled out all fields and have access
> to this committee data! For further inquiries, please contact
> d...@community.apache.org
> Error: User stillalex not a member of PMC solr nor an ASF member"
>
> I am thinking a PMC member could help do this, as it's a 5 second task.
>
>
> thanks,
> alex
>

Re: Apache Solr Newsletter proposal September 2023

[Arrieta, Alejandro]

Hello Team,

Newsletter on ASF social media:
I just returned home from Community over Code, where I talked with the
Asfinfra team, and they redirected me to talk with Brian Proffit.
I talked with him about the new Solr newsletter, and he told me to send him
what we want to publish, the date to publish, and the email with a copy to
the Solr PMC chair.
David Smiley, please confirm you are okay so I can email Brian to publish
the September 2023 newsletter.

Apache Solr wiki newsletter:
As discussed during the conference, please give me edit authorization to
Solr Wiki to start uploading the newsletter there. My account should be
aarrieta and email aarri...@perrinsoftware.com

Linkedin Apache Solr account/group:
The Asinfra team told me they do not create social media accounts. These
are created and managed by each project. We can request templates and
publishing guides from pr...@apache.org and mmp group.

Kind Regards,
Alejandro Arrieta


On Tue, Oct 10, 2023 at 9:43 AM Bruno Roustant 
wrote:

> +1 !
>
> Le lun. 9 oct. 2023 à 16:54, Eric Pugh  a
> écrit :
>
> > I’d love to see it on mastodon/twitterX/linkedin too….   I bet ASF PR
> > would love to see this as well ;-)
> >
> > > On Oct 8, 2023, at 5:36 PM, Alessandro Benedetti  >
> > wrote:
> > >
> > > +1 I think it's a wonderful idea!
> > >
> > > On Sun, 8 Oct 2023, 17:26 Arrieta, Alejandro, <
> > aarri...@perrinsoftware.com>
> > > wrote:
> > >
> > >> 0. Intro
> > >> Welcome to the Apache Solr Newsletter proposal September 2023. As this
> > is
> > >> the first newsletter proposal of 2023 we include Solr Community news
> > >> starting from January 2023:
> > >>
> > >> Welcome Alex Deparvu as Solr committer:
> > >> https://lists.apache.org/thread/fx4o3y55ypqy1n06kdbq5k8h4pjxlowj
> > >>
> > >> Welcome Marcus Eagan as Solr committer:
> > >> https://lists.apache.org/thread/2p2fjm18g39x2mknxqnbr3gfcx0q6rrx
> > >>
> > >> Welcome David Smiley as Solr's new PMC chair:
> > >> https://lists.apache.org/thread/yrp2yll52r0fm2pbhw17b62oln63fp33
> > >>
> > >> Welcome Andy Webb as Solr committer:
> > >> https://lists.apache.org/thread/k449v7jl4bwg6f7x707tvw5ch2dk8h3f
> > >>
> > >> Welcome Justin Sweeney as Solr committer:
> > >> https://lists.apache.org/thread/g588106pohdwok7gpwwcsxpgvwxwwh41
> > >>
> > >> Welcome Colvin Cowie as Solr committer:
> > >> https://lists.apache.org/thread/ngzjs0b3mb201d2shfvzdysdd5g6xqz1
> > >>
> > >> 1. Current versions
> > >> Solr 9.3.0:
> > >> https://solr.apache.org/downloads.html#solr-930
> > >>
> > >> Solr 8.11.2:
> > >> https://solr.apache.org/downloads.html#solr-8112
> > >>
> > >> Solr Operator v0.7.1:
> > >> https://solr.apache.org/operator/artifacts.html#solr-v071
> > >>
> > >> 2. Incoming versions
> > >> Solr 9.4.0
> > >> mailing list thread:
> > >> https://lists.apache.org/thread/j44golmqp4sjf2rk74pqktkrsc1do58r
> > >>
> > >> Solr 8.11.3
> > >> mailing list thread:
> > >> https://lists.apache.org/thread/j44golmqp4sjf2rk74pqktkrsc1do58r
> > >>
> > >> 3. Solr Improvement Proposals News
> > >> SIP-13: Cross Data Center Replication
> > >> mailing list thread:
> > >> https://lists.apache.org/thread/9y2qd7rs45049xbrt0gty40m4b5cv22y
> > >> wiki link:
> > >>
> > >>
> >
> https://cwiki.apache.org/confluence/display/SOLR/SIP-13%3A+Cross+Data+Center+Replication
> > >>
> > >> SIP-14 Embedded Zookeeper
> > >> mailing list thread:
> > >> https://lists.apache.org/thread/mch6y4wsbqykcmfy4r76movmx1wz0375
> > >> wiki link:
> > >>
> >
> https://cwiki.apache.org/confluence/display/SOLR/SIP-14+Embedded+Zookeeper
> > >>
> > >> SIP-15 Node roles
> > >> mailing list thread:
> > >> https://lists.apache.org/thread/kwq609jxckpdqk54fvghxs66jtk92kof
> > >> wiki link:
> > >> https://cwiki.apache.org/confluence/display/SOLR/SIP-15+Node+roles
> > >>
> > >> SIP-19 Adopt JSR-330 dependency injection
> > >> mailing list thread:
> > >> https://lists.apache.org/thread/9y2qd7rs45049xbrt0gty40m4b5cv22y
> > >> wiki link:
> > >>
> > >>
> >
> https://cwiki.apache.org/confluence/display/SOLR/SIP-19+Adopt+JSR-330+dependency+i

Apache Solr Newsletter proposal September 2023

[Arrieta, Alejandro]

0. Intro
Welcome to the Apache Solr Newsletter proposal September 2023. As this is
the first newsletter proposal of 2023 we include Solr Community news
starting from January 2023:

Welcome Alex Deparvu as Solr committer:
https://lists.apache.org/thread/fx4o3y55ypqy1n06kdbq5k8h4pjxlowj

Welcome Marcus Eagan as Solr committer:
https://lists.apache.org/thread/2p2fjm18g39x2mknxqnbr3gfcx0q6rrx

Welcome David Smiley as Solr's new PMC chair:
https://lists.apache.org/thread/yrp2yll52r0fm2pbhw17b62oln63fp33

Welcome Andy Webb as Solr committer:
https://lists.apache.org/thread/k449v7jl4bwg6f7x707tvw5ch2dk8h3f

Welcome Justin Sweeney as Solr committer:
https://lists.apache.org/thread/g588106pohdwok7gpwwcsxpgvwxwwh41

Welcome Colvin Cowie as Solr committer:
https://lists.apache.org/thread/ngzjs0b3mb201d2shfvzdysdd5g6xqz1

1. Current versions
Solr 9.3.0:
https://solr.apache.org/downloads.html#solr-930

Solr 8.11.2:
https://solr.apache.org/downloads.html#solr-8112

Solr Operator v0.7.1:
https://solr.apache.org/operator/artifacts.html#solr-v071

2. Incoming versions
Solr 9.4.0
mailing list thread:
https://lists.apache.org/thread/j44golmqp4sjf2rk74pqktkrsc1do58r

Solr 8.11.3
mailing list thread:
https://lists.apache.org/thread/j44golmqp4sjf2rk74pqktkrsc1do58r

3. Solr Improvement Proposals News
SIP-13: Cross Data Center Replication
mailing list thread:
https://lists.apache.org/thread/9y2qd7rs45049xbrt0gty40m4b5cv22y
wiki link:
https://cwiki.apache.org/confluence/display/SOLR/SIP-13%3A+Cross+Data+Center+Replication

SIP-14 Embedded Zookeeper
mailing list thread:
https://lists.apache.org/thread/mch6y4wsbqykcmfy4r76movmx1wz0375
wiki link:
https://cwiki.apache.org/confluence/display/SOLR/SIP-14+Embedded+Zookeeper

SIP-15 Node roles
mailing list thread:
https://lists.apache.org/thread/kwq609jxckpdqk54fvghxs66jtk92kof
wiki link:
https://cwiki.apache.org/confluence/display/SOLR/SIP-15+Node+roles

SIP-19 Adopt JSR-330 dependency injection
mailing list thread:
https://lists.apache.org/thread/9y2qd7rs45049xbrt0gty40m4b5cv22y
wiki link:
https://cwiki.apache.org/confluence/display/SOLR/SIP-19+Adopt+JSR-330+dependency+injection

4. Links to blogs, videos, others related to Solr:
Apache Solr Community Virtual Meetup, September 2023:
https://www.meetup.com/apache-solr-virtual-community-meetups/events/296344421/

DataImportHandler 9.3.0 released:
https://lists.apache.org/thread/8z65tf4jr2ppdm4xo5r1bygjzt8z8r3f

5. Upcoming Events & meetings
ASF Community over Code in Halifax, October 7-10 2023:
https://communityovercode.org/

Apache Solr Community Virtual Meetup, October 2023:
https://www.meetup.com/apache-solr-virtual-community-meetups/events/

6. Connect with the Apache Solr Community
Subscribe to Apache Solr Virtual Meetup for monthly meeting:
https://www.meetup.com/apache-solr-virtual-community-meetups/

Follow us on Twitter/X:
https://twitter.com/apachesolr

Visit our mailing list, jira, irc and slack:
https://solr.apache.org/community.html

How to contribute:
https://solr.apache.org/community.html#how-to-contribute

Apache Solr website:
https://solr.apache.org/

Apache Solr Operator website:
https://solr.apache.org/operator/

Note: This is a proposal and I will start working on the October 2023
newsletter proposal and create a Jira to accept contributions. Maybe we can
publish this on the Apache Solr web if accepted in the future.

Kind Regards,
Alejandro Arrieta

Re: Sitemap to get latest reference manual to rank in Google/Bing?

[Arrieta, Alejandro]

Hello,

Please don't remove the indexing of older Solr guides. It helps to search
for "Solr X.Y what_to_search" and get the link to the corresponding guide.
Thumbs up to give higher priority to the latest guide.

Kind Regards,
Alejandro Arrieta

On Thu, Sep 21, 2023 at 3:42 PM Walter Underwood 
wrote:

> Actually, the robots.txt file should also disallow the 9.x guides. That
> won’t touch guide/latest.
>
> User-agent: *
> Disallow: /guide/9*
> Disallow: /guide/8*
> Disallow: /guide/7*
> Disallow: /guide/6*
>
> wunder
>
> > On Sep 21, 2023, at 2:38 PM, Walter Underwood 
> wrote:
> >
> > I’m actually OK with them being indexed. It could be helpful to search
> for “Solr 8.11 aliases” or something like that.
> >
> > The priority attribute in sitemap.xml should boost the default, latest
> manual and that shouldn’t require any web server config. I’m glad to craft
> a static sitemap.xml file. One generated from the guide would be better,
> but that can be a later improvement.
> >
> > To get the old versions completely out of the index, add a robots.txt
> file to the solr-site repo under contents/ with these lines:
> >
> > User-agent: *
> > Disallow: /guide/8*
> > Disallow: /guide/7*
> > Disallow: /guide/6*
> >
> > Note that the wildcards on the paths aren't needed, but they helps
> humans understand that the disallows are a prefix match.
> >
> > wunder
> > Walter Underwood
> > wun...@wunderwood.org
> > http://observer.wunderwood.org/  (my blog)
> >
> >> On Sep 21, 2023, at 12:08 PM, Houston Putman 
> wrote:
> >>
> >> I've been trying to get this working for the last year. Basically our
> issue
> >> is that the htaccess files do not add the right X-Robots-Tag header for
> old
> >> ref guide pages.
> >>
> >>
> https://github.com/apache/solr-site/blob/main/themes/solr/templates/htaccess.ref-guide-old#L1
> >>
> >> This works locally, but in the actual Solr site, the headers are not
> >> returned. I have no idea why. Would love some help though, as I also
> hate
> >> seeing the old ref guide in the google results.
> >>
> >> - Houston
> >>
> >> On Thu, Sep 21, 2023 at 11:30 AM Walter Underwood <
> wun...@wunderwood.org>
> >> wrote:
> >>
> >>> When I get web search results that include the Solr Reference Guide, I
> >>> often get older versions (6.6, 7.4) in the results. I would prefer to
> >>> always get the latest reference (
> >>> https://solr.apache.org/guide/solr/latest/index.html).
> >>>
> >>> I think we can list the URLs for that in a sitemap.xml file with a
> higher
> >>> priority to suggest to the crawlers that these are the preferred pages.
> >>>
> >>> I don’t see a sitemap.xml or sitemap.xml.gz at
> https://solr.apached.org <
> >>> https://solr.apached.org/>.
> >>>
> >>> Should we prefer the latest manual? How do we build/deploy a sitemap?
> See:
> >>> https://www.sitemaps.org/
> >>>
> >>> wunder
> >>> Walter Underwood
> >>> wun...@wunderwood.org
> >>> http://observer.wunderwood.org/  (my blog)
> >>>
> >>>
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org
> For additional commands, e-mail: dev-h...@solr.apache.org
>
>

Re: I'm going to ASF Community-over-Code in Halifax

[Arrieta, Alejandro]

Hello,

Will there be a Solr Birds of a Feather session this year?

Kind Regards
Alejandro Arrieta

On Thu, Sep 7, 2023 at 3:00 PM David Smiley 
wrote:

> Just an FYI that I'll be at the ASF Community-over-Code conference in
> Halifax this October.  I hope to see some of you there!
>
> ~ David
>

Re: [VOTE] Release Solr 9.3.0 RC2

[Arrieta, Alejandro]

+1 (non-binding) on ubuntu 22.04 temurin openjdk 11 virtualbox

SUCCESS! [0:31:20.943266]

Kind Regards,
Alejandro Arrieta

On Thu, Jul 20, 2023 at 5:04 AM Uwe Schindler  wrote:

> Hi,
>
> It looks like your python3 version is outdated or the trust anchors in
> your operating system that python refers to are outdated. The
> certificate chain cannot be resolved and the Sctigo root certificate is
> out of reach for ptyhon. I see no problems with the "*.apache.org"
> certificate, it is still valid vor 10 more days.
>
> Uwe
>
> Maybe it is a good idea to
>
> Am 19.07.2023 um 23:31 schrieb David Smiley:
> > I tried to run this on my machine and ran into some issues.  First seemed
> > to be an out-of-date gpg due to a param it didn't know about so I updated
> > gpg and was able to make further progress.  Now I get some sort of SSL
> > certificate issue.  I'm sharing here in case others have seen:
> >
> > python3 -u dev-tools/scripts/smokeTestRelease.py \
> >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.3.0-RC2-rev-de33f50ce79ec1d156faf204553012037e2bc1cb
> >
> >
> > Revision: de33f50ce79ec1d156faf204553012037e2bc1cb
> >
> > Java 11
> > JAVA_HOME=/Library/Java/JavaVirtualMachines/zulu-11.jdk/Contents/Home
> >
> > NOTE: output encoding is UTF-8
> >
> > NOTE: Not running @Nightly or @BadApple tests. Please verify that recent
> > Jenkins runs have passed.
> >
> >
> > Load release URL "
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.3.0-RC2-rev-de33f50ce79ec1d156faf204553012037e2bc1cb
> > "...
> >
> > Traceback (most recent call last):
> >
> >File "dev-tools/scripts/smokeTestRelease.py", line 1174, in 
> >
> >  main()
> >
> >File "dev-tools/scripts/smokeTestRelease.py", line 1101, in main
> >
> >  downloadOnly=c.download_only)
> >
> >File "dev-tools/scripts/smokeTestRelease.py", line 1132, in smokeTest
> >
> >  for text, subURL in getDirEntries(baseURL):
> >
> >File "dev-tools/scripts/smokeTestRelease.py", line 526, in
> getDirEntries
> >
> >  links = getHREFs(urlString)
> >
> >File "dev-tools/scripts/smokeTestRelease.py", line 79, in getHREFs
> >
> >  h.request('HEAD', url.path)
> >
> >File
> >
> "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.7/lib/python3.7/http/client.py",
> > line 1229, in request
> >
> >  self._send_request(method, url, body, headers, encode_chunked)
> >
> >File
> >
> "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.7/lib/python3.7/http/client.py",
> > line 1275, in _send_request
> >
> >  self.endheaders(body, encode_chunked=encode_chunked)
> >
> >File
> >
> "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.7/lib/python3.7/http/client.py",
> > line 1224, in endheaders
> >
> >  self._send_output(message_body, encode_chunked=encode_chunked)
> >
> >File
> >
> "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.7/lib/python3.7/http/client.py",
> > line 1016, in _send_output
> >
> >  self.send(msg)
> >
> >File
> >
> "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.7/lib/python3.7/http/client.py",
> > line 956, in send
> >
> >  self.connect()
> >
> >File
> >
> "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.7/lib/python3.7/http/client.py",
> > line 1392, in connect
> >
> >  server_hostname=server_hostname)
> >
> >File
> >
> "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.7/lib/python3.7/ssl.py",
> > line 412, in wrap_socket
> >
> >  session=session
> >
> >File
> >
> "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.7/lib/python3.7/ssl.py",
> > line 853, in _create
> >
> >  self.do_handshake()
> >
> >File
> >
> "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.7/lib/python3.7/ssl.py",
> > line 1117, in do_handshake
> >
> >  self._sslobj.do_handshake()
> >
> > ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED]
> certificate
> > verify failed: unable to get local issuer certificate (_ssl.c:1056)
> >
> > On Wed, Jul 19, 2023 at 4:26 PM Alex Deparvu 
> wrote:
> >
> >> +1 (non-binding)
> >>
> >> SUCCESS! [0:37:06.301788]
> >>
> >>
> >> On Mon, Jul 17, 2023 at 2:53 PM Houston Putman 
> wrote:
> >>
> >>> Please vote for release candidate 2 for Solr 9.3.0
> >>>
> >>> The artifacts can be downloaded from:
> >>>
> >>>
> >>
> https://dist.apache.org/repos/dist/dev/solr/solr-9.3.0-RC2-rev-de33f50ce79ec1d156faf204553012037e2bc1cb
> >>> You can run the smoke tester directly with this command:
> >>>
> >>> python3 -u dev-tools/scripts/smokeTestRelease.py \
> >>>
> >>>
> >>
> https://dist.apache.org/repos/dist/dev/solr/solr-9.3.0-RC2-rev-de33f50ce79ec1d156faf204553012037e2bc1cb
> >>> You can build a release-candidate of the official docker images (full &
> 

Re: [DISCUSS] Community Virtual Meetup, June 2023

[Arrieta, Alejandro]

Hello,

created an account, but I think I can not edit.

June 16th is good for me in either proposed schedule.

proposed topics:
1) Social Media
create a list of Social Media official Apache Solr accounts that exists
today:
could not find Linkedin, youtube, tiktok, instagram
could find: twitter
I think we need at least to create a Linkedin Apache Solr account to make
some noise, like other search engines do.
define what can be posted on those channels so we can create some stuff to
share.
define nominate (maybe someone has already this role) social media manager
who approves the content to be shared.

2) How do you performance test Solr in generic or specific use cases, share
the tools and other insights.

Kind Regards,
Alejandro Arrieta

On Wed, Jun 7, 2023 at 12:58 PM Eric Pugh  wrote:

> I wanted to follow up with folks about the June meetup, especially as it's
> been pretty quiet!
>
> I'd live to propose next week, June 16th, at either 11 AM EST or 3 PM
> EST.   Please let me know if you have a preference, and if no one speaks up
> in the next day or so, I'll pick one ;-).
>
> So far it's Jason and I ;-)
>
> https://cwiki.apache.org/confluence/display/SOLR/2023-06-16+Meeting+notes
>
> Eric
>
>
> On 2023/05/30 13:04:15 Jason Gerlowski wrote:
> > Hey,
> >
> > Thanks for volunteering Eric!  That time and date work great for me,
> > though maybe others have opinions before we lock that in.  (I know
> > this thread was created really far in advance, so maybe this reply
> > will bring it to people's attention again.)
> >
> > It looks like the Confluence page for this June already exists as
> > well, so folks can start adding their topics there as well?
> >
> > Best,
> >
> > Jason
> >
> > On Fri, Mar 31, 2023 at 2:38 PM Eric Pugh
> >  wrote:
> > >
> > > Hi all..   I won’t be at the April meetup, as I’ll be shepherding 20
> high school students on a trip to Spain ;-).
> > >
> > > However, I’d love to go ahead and sign up for hosting in June.I’m
> proposing June 8th at 11:00 EST.
> > >
> > > I’ll go ahead and create the wiki page, and then do the other steps in
> https://cwiki.apache.org/confluence/display/SOLR/Meeting+notes closer to
> that date ;-)
> > >
> > > Eric
> > >
> > > ___
> > > Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467
> | http://www.opensourceconnections.com <
> http://www.opensourceconnections.com/> | My Free/Busy <
> http://tinyurl.com/eric-cal>
> > > Co-Author: Apache Solr Enterprise Search Server, 3rd Ed <
> https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw
> >
> > > This e-mail and all contents, including attachments, is considered to
> be Company Confidential unless explicitly stated otherwise, regardless of
> whether attachments are marked as such.
> > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org
> > For additional commands, e-mail: dev-h...@solr.apache.org
> >
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org
> For additional commands, e-mail: dev-h...@solr.apache.org
>
>

Re: Anyone using more obscure features of SimplePostTool?

[Arrieta, Alejandro]

 Hello Team,

In previous Solr versions, afaik examples post tool did not support
Kerberos (have not checked Solr 9.x), so each time a customer asked about
the Apache Solr tutorial I recommended them to use curl command as it works
with/without kerberos (curl --negotiate ). There are some curls that do
not support Kerberos (anaconda curl), but the linux distro default supports
it.
Yes, I work with kerberized Solr :-)

Kind Regards,
Alejandro Arrieta

On Tue, May 23, 2023 at 6:05 AM Eric Pugh 
wrote:

> Lots of feedback!
>
> So, would renaming SOLR-6994 from "Implement Windows version of bin/post"
> to “Implement Windows version of bin/post via implementing bin/solr post”
> address your concern David?
>
> It’s both for Solr technical simplicity, but also to let Window’s users
> actually have better support.In the not too distant future I want to
> get BASIC and JWT auth across all our CLI tools and not having this one
> orphaned “bin/post” and random checked in “post.jar” hanging out would help
> that.
>
> I don’t think we can remove the capability to post documents completely,
> that it has to be deprecated.   And honestly, if the darn thing worked a
> bit better (like in the aforementioned more secure scenarios) then it would
> provide plenty of value.
>
>
>
>
> > On May 23, 2023, at 2:16 AM, Marcus Eagan  wrote:
> >
> > Smiley, that's actually a pretty good use case.
> >
> > On Tue, May 23, 2023 at 2:15 AM David Smiley  wrote:
> >
> >> Glad to see we can limit this discussion to "bin/post" and not
> >> other non-prod/maybe-prod things listed.
> >>
> >> I think bin/post should either exist where it is or not exist; moving
> it to
> >> the sandbox misses the point.
> >> "curl" may very well be plenty adequate.  FWIW your arguments work for
> me
> >> to ditch bin/post, but it could be useful to hear from
> educators/trainers
> >> as well. It's been a while since I could count myself as such.
> >>
> >> BTW I know of at least one advantage over curl.  I was once posting
> massive
> >> many-gigabyte files to Solr in CSV (for a POC scenario).  Curl wanted to
> >> memory-map the whole thing and failed to get the RAM to do it.
> "bin/post"
> >> streamed the whole thing quite fast.  I know I made improvements to
> help it
> >> in this specific regard.  That said, if bin/post is mostly redundant, I
> >> wouldn't want us to maintain bin/post forever *just* because of this.
> >>
> >> ~ David Smiley
> >> Apache Lucene/Solr Search Developer
> >> http://www.linkedin.com/in/davidwsmiley
> >>
> >>
> >> On Tue, May 23, 2023 at 2:05 AM Ishan Chattopadhyaya <
> >> ichattopadhy...@gmail.com> wrote:
> >>
> >>> We have advertised the post tool in the past in our examples/tutorials.
> >>> Difficult to erase all traces of it from the web.
> >>> It is better to remove the tool from the Solr distro, and, maybe,
> >> relocate
> >>> it to the sandbox/extras repo, from where a user can consciously choose
> >> to
> >>> download and use it if needed.
> >>>
> >>> If we have proper documentation, I don't see how anyone building POCs
> >> will
> >>> miss out on the post tool. Is there a use case that users can't achieve
> >>> easily through a documented method that the post tool caters to?
> >>>
> >>> On Tue, 23 May 2023 at 11:25, David Smiley  wrote:
> >>>
>  Ishan, your beliefs surprise me.  Maybe I'm misunderstanding your
> point
> >>> of
>  view... is the key word of your response "advertise" and we can then
> >>> debate
>  what that means?  In other words, are you saying bin/post (and other
> >>> things
>  you don't think should be used in production) should not exist at all
> >> or
> >>> we
>  should be very careful about how we "advertise" its existence?  I
> think
>  features that help people build POCs / explore / learn are good
> things,
>  even if not used typically in production.  At times we over-advertised
>  features without enough disclaimers on the suitability of the feature
> >> in
>  question.
> 
>  ~ David Smiley
>  Apache Lucene/Solr Search Developer
>  http://www.linkedin.com/in/davidwsmiley
> 
> 
>  On Mon, May 22, 2023 at 10:09 PM Ishan Chattopadhyaya <
>  ichattopadhy...@gmail.com> wrote:
> 
> >> Ishan, you did not give an argument for why you believe bin/post
> >>> should
> > go away. Do you feel it is better to document all the cURL commands
> >> to
> >>> be
> > more "standard"?
> >
> > Precisely! We should never advertise anything that shouldn't be used
> >> at
> > scale or in production. That includes the post tool, example modes of
> > startup, schemaless/data-driven etc.
> >
> > Curl is popular enough on Windows as well, through ports or WSL.
> >> There
>  are
> > tools like Insomnia or Postman too. We should encourage their use,
> >>> rather
> > than promote our home grown tool by shipping oob and/or referring to
> >> it
>  in
> > tutorials.
> >
> > On Tue, 23 May, 

Re: [Proposal] Security Working Group

[Arrieta, Alejandro]

Hi Gus,

thx 4 clarification.
Well I need to work on those 2 requirements then :-)

Thanks
Alejandro Arrieta


On Tue, May 2, 2023 at 3:40 PM Gus Heck  wrote:

> Unfortunately, since part of the duties will be responding to the queries
> sent to secur...@solr.apache.org, one must be both a committer and a PMC
> member. However, I expect that this group will make suggestions about
> anything unrelated to un-announced security issues to the wider list for a
> typical discussion/proposal/vote cycle.
>
> On Tue, May 2, 2023 at 3:28 PM Arrieta, Alejandro <
> aarri...@perrinsoftware.com> wrote:
>
> >  Hello Team,
> >
> > Do you need to be a committer to join the group?
> >
> > Kind Regards,
> > Alejandro Arrieta
> >
> > On Tue, May 2, 2023 at 3:23 PM Gus Heck  wrote:
> >
> > > Cool that means so far we have:
> > >
> > >1. Me (Gus Heck)
> > >2. Jason Gerlowski
> > >3. Mike Drob
> > >4. (maybe?) David Smiley
> > >
> > >
> > > On Tue, May 2, 2023 at 3:02 PM Mike Drob  wrote:
> > >
> > > > Howdy folks. I'd be happy to step into this working group.
> > > >
> > > > On Mon, May 1, 2023 at 12:34 PM Gus Heck  wrote:
> > > >
> > > > > Awesome, glad to have you Jason, I in the end feel the same way
> about
> > > my
> > > > > spot. Mostly I qualify as "concerned citizen", possibly with "who
> > > thought
> > > > > about it some and has ideas" added. If we get more than 5
> volunteers
> > we
> > > > can
> > > > > start comparing credentials.
> > > > >
> > > > > On Mon, May 1, 2023 at 1:17 PM Jason Gerlowski <
> > gerlowsk...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Hi Gus,
> > > > > >
> > > > > > I think this is a great idea.
> > > > > >
> > > > > > I don't have much security background that'd make me a
> particularly
> > > > > > good fit, but absent someone with that background stepping up,
> I'm
> > > > > > willing to volunteer for one of the spots.  (I'd be more than
> happy
> > > to
> > > > > > bow out if better qualified folks come along.)
> > > > > >
> > > > > > Best,
> > > > > >
> > > > > > Jason
> > > > > >
> > > > > > On Sun, Apr 30, 2023 at 7:14 PM David Smiley  >
> > > > wrote:
> > > > > > >
> > > > > > > Pretty sleepy thread so far; apparently nobody else is
> interested
> > > in
> > > > > > > talking about Solr security -- LOL ;-)
> > > > > > >
> > > > > > > ~ David Smiley
> > > > > > > Apache Lucene/Solr Search Developer
> > > > > > > http://www.linkedin.com/in/davidwsmiley
> > > > > > >
> > > > > > >
> > > > > > > On Wed, Apr 26, 2023 at 8:25 AM Gus Heck 
> > > wrote:
> > > > > > >
> > > > > > > > Thanks David. It would be great to have you if you can find
> > time
> > > > for
> > > > > > it. As
> > > > > > > > far as time commitment goes, I think it should become minimal
> > > > after a
> > > > > > while
> > > > > > > > unless we have a flood of security reports to respond to.
> For a
> > > > > little
> > > > > > > > while after initial organization, I think the members will
> want
> > > to
> > > > > put
> > > > > > a
> > > > > > > > bit of effort into hitting some of the goals I mentioned.
> > > > > > > >
> > > > > > > > On Tue, Apr 25, 2023 at 12:28 AM David Smiley <
> > > dsmi...@apache.org>
> > > > > > wrote:
> > > > > > > >
> > > > > > > > > This is a thoughtful organization attempt and needed, I
> > think.
> > > > > > Thanks
> > > > > > > > Gus!
> > > > > > > > >
> > > > > > > > > I want to see if I could get a security specialist/engineer
> > > > where I
> > > > > > work
> > > > > > > > to
> > > > >

Re: [Proposal] Security Working Group

[Arrieta, Alejandro]

 Hello Team,

Do you need to be a committer to join the group?

Kind Regards,
Alejandro Arrieta

On Tue, May 2, 2023 at 3:23 PM Gus Heck  wrote:

> Cool that means so far we have:
>
>1. Me (Gus Heck)
>2. Jason Gerlowski
>3. Mike Drob
>4. (maybe?) David Smiley
>
>
> On Tue, May 2, 2023 at 3:02 PM Mike Drob  wrote:
>
> > Howdy folks. I'd be happy to step into this working group.
> >
> > On Mon, May 1, 2023 at 12:34 PM Gus Heck  wrote:
> >
> > > Awesome, glad to have you Jason, I in the end feel the same way about
> my
> > > spot. Mostly I qualify as "concerned citizen", possibly with "who
> thought
> > > about it some and has ideas" added. If we get more than 5 volunteers we
> > can
> > > start comparing credentials.
> > >
> > > On Mon, May 1, 2023 at 1:17 PM Jason Gerlowski 
> > > wrote:
> > >
> > > > Hi Gus,
> > > >
> > > > I think this is a great idea.
> > > >
> > > > I don't have much security background that'd make me a particularly
> > > > good fit, but absent someone with that background stepping up, I'm
> > > > willing to volunteer for one of the spots.  (I'd be more than happy
> to
> > > > bow out if better qualified folks come along.)
> > > >
> > > > Best,
> > > >
> > > > Jason
> > > >
> > > > On Sun, Apr 30, 2023 at 7:14 PM David Smiley 
> > wrote:
> > > > >
> > > > > Pretty sleepy thread so far; apparently nobody else is interested
> in
> > > > > talking about Solr security -- LOL ;-)
> > > > >
> > > > > ~ David Smiley
> > > > > Apache Lucene/Solr Search Developer
> > > > > http://www.linkedin.com/in/davidwsmiley
> > > > >
> > > > >
> > > > > On Wed, Apr 26, 2023 at 8:25 AM Gus Heck 
> wrote:
> > > > >
> > > > > > Thanks David. It would be great to have you if you can find time
> > for
> > > > it. As
> > > > > > far as time commitment goes, I think it should become minimal
> > after a
> > > > while
> > > > > > unless we have a flood of security reports to respond to. For a
> > > little
> > > > > > while after initial organization, I think the members will want
> to
> > > put
> > > > a
> > > > > > bit of effort into hitting some of the goals I mentioned.
> > > > > >
> > > > > > On Tue, Apr 25, 2023 at 12:28 AM David Smiley <
> dsmi...@apache.org>
> > > > wrote:
> > > > > >
> > > > > > > This is a thoughtful organization attempt and needed, I think.
> > > > Thanks
> > > > > > Gus!
> > > > > > >
> > > > > > > I want to see if I could get a security specialist/engineer
> > where I
> > > > work
> > > > > > to
> > > > > > > help us with this.  I'm tempted to say I'm joining this thing
> but
> > > I'm
> > > > > > weary
> > > > > > > of dedicating time per week.
> > > > > > >
> > > > > > > ~ David Smiley
> > > > > > > Apache Lucene/Solr Search Developer
> > > > > > > http://www.linkedin.com/in/davidwsmiley
> > > > > > >
> > > > > > >
> > > > > > > On Mon, Apr 24, 2023 at 1:33 PM Gus Heck 
> > > wrote:
> > > > > > >
> > > > > > > > *Rationale*
> > > > > > > >
> > > > > > > > Over the course of the last decade the way software security
> is
> > > > viewed
> > > > > > > has
> > > > > > > > changed. Solr has changed significantly over this time too
> and
> > we
> > > > have
> > > > > > > > gained some important security features and fixed a variety
> of
> > > > > > > > vulnerabilities. However, I think as a project we have not
> > really
> > > > > > > developed
> > > > > > > > a clear vision of what our security goals and use cases are.
> I
> > > have
> > > > > > > > witnessed a fair bit of variability in the responses to
> > security
> > > > > > related
> > > > > > > > queries, and I think much of the variability comes from
> > > conflation
> > > > > > among
> > > > > > > > "good practical advice", "somewhat dated advice" and "varying
> > > > notions
> > > > > > of
> > > > > > > > supported use cases". We also regularly receive reports to
> the
> > > > > > > > secur...@solr.apache.org address that involve investigations
> > > into
> > > > > > > systems
> > > > > > > > that are not properly secured to begin with or configured to
> > > > explicitly
> > > > > > > > allow the dangerous behavior and it's a shame to see security
> > > > > > researchers
> > > > > > > > waste their time on that. Finally, the PMC and set of people
> > > > subscribed
> > > > > > > to
> > > > > > > > secur...@solr.apache.org is a large enough group that
> incoming
> > > > mails
> > > > > > > often
> > > > > > > > seem to languish in a classic example of nobody having actual
> > > > specific
> > > > > > > > responsibility for responding.
> > > > > > > >
> > > > > > > > *Proposal*
> > > > > > > > The Solr PMC should appoint from among its members either 3
> to
> > 5
> > > > > > > > individuals to serve as a "security working group" Membership
> > in
> > > > the
> > > > > > > > "Security Working Group" requires subscribing to
> > > > > > > secur...@solr.apache.org,
> > > > > > > > and a 30 minute conference call once or twice a month. This
> > > working
> > > > > > group
> > > > > > > > would have the following goals.
> 

Re: [VOTE] Release Solr 9.2.1 RC1

[Arrieta, Alejandro]

+1
SUCCESS! [0:29:31.135392]

And run Solr operator tests successfully following instructions:
Local end-to-end cluster test successfully run!

ubuntu 23.04 amd64 temurin-openjdk11 on virtualbox 7.

Kind Regards,
Alejandro Arrieta

On Thu, Apr 27, 2023 at 4:23 PM Joel Bernstein  wrote:

> +1 (binding)
>
> SUCCESS! [0:43:48.160659]
>
>
> I tested out the assets as well and looked fine.
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
>
> On Thu, Apr 27, 2023 at 1:23 PM Jan Høydahl  wrote:
>
> > +1 (binding)
> >
> > SUCCESS! [0:38:44.920838]
> >
> > Jan
> >
> > > 27. apr. 2023 kl. 16:12 skrev Justin Sweeney <
> justin.sweene...@gmail.com
> > >:
> > >
> > > Hi all, we are back on for the vote:
> > >
> > > Please vote for release candidate 1 for Solr 9.2.1
> > >
> > > The artifacts can be downloaded from:
> > >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.2.1-RC1-rev-a4c64ab6a2a270ca69c28c706dabb2927ed8a7c2
> > >
> > > You can run the smoke tester directly with this command:
> > >
> > > python3 -u dev-tools/scripts/smokeTestRelease.py \
> > >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.2.1-RC1-rev-a4c64ab6a2a270ca69c28c706dabb2927ed8a7c2
> > >
> > > You can build a release-candidate of the official docker image using
> the
> > > following command:
> > >
> > > DIST_BASE=https://dist.apache.org/repos/dist/dev/solr && \
> > >  RC_FOLDER=solr-9.2.1-RC1-rev-a4c64ab6a2a270ca69c28c706dabb2927ed8a7c2
> > && \
> > >  docker build $DIST_BASE/$RC_FOLDER/solr/docker/Dockerfile.official \
> > >  --build-arg
> SOLR_DOWNLOAD_URL=$DIST_BASE/$RC_FOLDER/solr/solr-9.2.1.tgz
> > \
> > >  -t solr-rc:9.2.1-1
> > >
> > > The vote will be open for at least 72 hours i.e. until 2023-04-30 15:00
> > UTC.
> > >
> > > [ ] +1  approve
> > > [ ] +0  no opinion
> > > [ ] -1  disapprove (and reason why)
> > >
> > > On Mon, Apr 24, 2023 at 12:38 PM Justin Sweeney <
> > justin.sweene...@gmail.com>
> > > wrote:
> > >
> > >> Yup, let's wait in that case. I didn't realize it would fail since I
> had
> > >> temporarily added my key locally to be able to execute the additional
> > >> steps. This results in the smoketester passing for me. I'll resend a
> > vote
> > >> once I'm able to push my key.
> > >>
> > >> On Mon, Apr 24, 2023 at 12:32 PM Houston Putman 
> > >> wrote:
> > >>
> > >>> Hey Justin,
> > >>>
> > >>> Should we wait to run this until after your GPG key is in
> > >>> https://downloads.apache.org/solr/KEYS?
> > >>>
> > >>> The smoketester fails for me because it can't find your key.
> > >>>
> > >>> - Houston
> > >>>
> > >>> On Mon, Apr 24, 2023 at 12:20 PM Justin Sweeney <
> > >>> justin.sweene...@gmail.com>
> > >>> wrote:
> > >>>
> >  Please vote for release candidate 1 for Solr 9.2.1
> > 
> >  The artifacts can be downloaded from:
> > 
> > 
> > >>>
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.2.1-RC1-rev-a4c64ab6a2a270ca69c28c706dabb2927ed8a7c2
> > 
> >  You can run the smoke tester directly with this command:
> > 
> >  python3 -u dev-tools/scripts/smokeTestRelease.py \
> > 
> > 
> > >>>
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.2.1-RC1-rev-a4c64ab6a2a270ca69c28c706dabb2927ed8a7c2
> > 
> >  You can build a release-candidate of the official docker image using
> > the
> >  following command:
> > 
> >  DIST_BASE=https://dist.apache.org/repos/dist/dev/solr && \
> > 
> RC_FOLDER=solr-9.2.1-RC1-rev-a4c64ab6a2a270ca69c28c706dabb2927ed8a7c2
> > >>> &&
> >  \
> >   docker build $DIST_BASE/$RC_FOLDER/solr/docker/Dockerfile.official
> \
> >   --build-arg
> > >>> SOLR_DOWNLOAD_URL=$DIST_BASE/$RC_FOLDER/solr/solr-9.2.1.tgz \
> >   -t solr-rc:9.2.1-1
> > 
> >  The vote will be open for at least 72 hours i.e. until 2023-04-27
> > 17:00
> >  UTC.
> > 
> >  [ ] +1  approve
> >  [ ] +0  no opinion
> >  [ ] -1  disapprove (and reason why)
> > 
> > >>>
> > >>
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org
> > For additional commands, e-mail: dev-h...@solr.apache.org
> >
> >
>

Re: [Operator] [VOTE] Release the Solr Operator v0.7.0 RC1

[Arrieta, Alejandro]

Hello Team

+1
#Successfully smoke tested the Solr Operator v0.7.0!

On a clean ubuntu 22.04 amd64 to run the smoke test I had to install
apt: make, gcc, jq
downloaded from project page: go 1.19.8, helm, kubectl, docker, kind
I did not install yq, was downloaded/compiled and was here:
/tmp/solr-operator-smoke-test-source-PT17ON4G/solr-operator-v0.7.0/bin/yq

Kind Regards.
Alejandro Arrieta
On Fri, Apr 21, 2023 at 2:49 PM Jan Høydahl  wrote:

> It is enough with (C) 2006, then we never need to change it again.
>
> Jan Høydahl
>
> > 21. apr. 2023 kl. 18:57 skrev Houston Putman :
> >
> > Thanks for checking that Jan.
> >
> > I don't think it's a blocker, but I'll fix it for the next set of
> releases.
> >
> > - Houston
> >
> >> On Fri, Apr 21, 2023 at 5:34 AM Jan Høydahl 
> wrote:
> >>
> >> +1
> >>
> >>> Successfully smoke tested the Solr Operator v0.7.0!
> >>
> >> Only ran smoke tester. Would have upgraded a test cluster but won't be
> >> able to before next week.
> >>
> >> Minor: NOTICE file in both helm chart tgzs still says "Copyright
> 2006-2021
> >> The Apache Software Foundation"
> >>
> >> Jan
> >>
>  19. apr. 2023 kl. 22:02 skrev Houston Putman :
> >>>
> >>> Please vote for release candidate 1 for the Solr Operator v0.7.0
> >>>
> >>> The artifacts can be downloaded from:
> >>>
> >>
> https://dist.apache.org/repos/dist/dev/solr/solr-operator/solr-operator-v0.7.0-RC1-rev0e16c6bd5cc12202c562188c2e55ef111d65a847
> >>>
> >>> You can run the full smoke tester, with instructions below.
> >>> However, it is also encouraged to go and use the artifacts yourself in
> a
> >>> test Kubernetes cluster.
> >>> The smoke tester does not require you to download or install the RC
> >>> artifacts before running.
> >>> If you plan on just running the smoke tests, then ignore all other
> >>> instructions.
> >>>
> >>> The artifacts are layed out in the following way:
> >>> * solr-operator-v0.7.0.tgz - Contains the source release
> >>> * crds/ - Contains the CRD files
> >>> * helm-charts/ - Contains the Helm release packages
> >>>
> >>> The RC Docker image can be found at:
> >>> apache/solr-operator:v0.7.0-rc1
> >>>
> >>> The RC Helm repo can be added with:
> >>> helm repo add apache-solr-rc
> >>>
> >>
> https://dist.apache.org/repos/dist/dev/solr/solr-operator/solr-operator-v0.7.0-RC1-rev0e16c6bd5cc12202c562188c2e55ef111d65a847/helm-charts
> >>>
> >>> You can install the RC Solr Operator and Solr CRDs and an example Solr
> >>> Cloud with:
> >>> curl -sL0 "https://dist.apache.org/repos/dist/release/solr/KEYS; | gpg
> >>> --import --quiet
> >>> # This will export your public keys into a format that helm can
> >>> understand.
> >>> # Skip verification by removing "--verify" in the helm command below.
> >>> if ! (gpg --no-default-keyring --keyring=~/.gnupg/pubring.gpg
> >> --list-keys
> >>> "98F3F6EC"); then gpg --export >~/.gnupg/pubring.gpg; fi
> >>> kubectl create -f
> >>>
> >>
> https://dist.apache.org/repos/dist/dev/solr/solr-operator/solr-operator-v0.7.0-RC1-rev0e16c6bd5cc12202c562188c2e55ef111d65a847/crds/all-with-dependencies.yaml
> >>> || \
> >>>   kubectl replace -f
> >>>
> >>
> https://dist.apache.org/repos/dist/dev/solr/solr-operator/solr-operator-v0.7.0-RC1-rev0e16c6bd5cc12202c562188c2e55ef111d65a847/crds/all-with-dependencies.yaml
> >>> helm install --verify solr-operator apache-solr-rc/solr-operator --set
> >>> image.tag=v0.7.0-rc1
> >>> helm install --verify example apache-solr-rc/solr
> >>>
> >>> You can run the full smoke tester directly with this command: (First
> >>> checkout the release-0.7 branch of the solr-operator)
> >>>
> >>> # First clear your go-mod cache to make sure old cache entries don't
> >> cause
> >>> smoke test failures
> >>> make mod-clean
> >>> ./hack/release/smoke_test/smoke_test.sh -v "v0.7.0" -s "0e16c6b" -i
> >>> "apache/solr-operator:v0.7.0-rc1" -g "98F3F6EC" \
> >>>   -l '
> >>>
> >>
> https://dist.apache.org/repos/dist/dev/solr/solr-operator/solr-operator-v0.7.0-RC1-rev0e16c6bd5cc12202c562188c2e55ef111d65a847
> >>> '
> >>>
> >>> If you want to run the smoke test with a specific version of
> kubernetes,
> >>> use the -k option with a full version tag. (e.g. -k v1.21.14)
> >>> If you want to run the smoke test with a custom version of solr, use
> the
> >> -t
> >>> option with an official Solr image version. (e.g. -t 8.11.2)
> >>> However, for this smoke test, you must use a solr version that supports
> >>> incremental backups. (i.e. 8.9+)
> >>>
> >>> Make sure you have the following installed before running the smoke
> test:
> >>> - Docker (Give it enough memory and CPU to run ~12 containers, 3 of
> >> which
> >>> are Solr nodes)
> >>>   More information on required resources can be found here:
> >>>
> >>
> https://kind.sigs.k8s.io/docs/user/quick-start/#settings-for-docker-desktop
> >>> - Go 1.19
> >>> - Kubectl
> >>> - GnuPG
> >>> - Helm v3.4.0+
> >>> - Kustomize (v4.0.0+) This will be installed for you, but NOT upgraded
> >> if
> >>> a lower version is already installed.
> >>> 

Re: SIP-18: A Solr Kubernetes Module for native integration

[Arrieta, Alejandro]

Hello team,

noob warning:
today I learned what SIP means. with SIP17 and 18 being very interesting
reads.
https://cwiki.apache.org/confluence/display/SOLR/Solr+Improvement+Proposals
Too many telephone references.
sorry for the interruption.
Alejandro Arrieta

On Thu, Apr 20, 2023 at 5:27 PM Houston Putman  wrote:

> Thanks for the questions Jason!
>
> So the general idea is that we'd add a Solr contrib/module, and that
> > module would have a dep on some sort of Kubernetes client so it could
> > manage certain Solr entities (e.g. security.json, configsets, etc.) as
> > Kubernetes resources (configmaps, etc.).  Am I understanding that
> > right?
> >
>
> Yes, absolutely. And possibly other things, like leverage Kubernetes'
> secrets managements to manage
> credentials for users. (Auto-import BasicAuth secrets with certain labels,
> integrate with Kubernetes ServiceAccounts, etc.)
>
> But yeah, generally the idea is to use Kubernetes state instead of
> Zookeeper state for certain features.
>
> One place there might be room for improvement in the writeup so far is
> > around the motivation/value-prop for some of these Solr->Kubernetes
> > integrations.  The value in some integrations (e.g.
> > KubernetesSSLCredentialsProvider) is relatively self-evident I think,
> > but others are a little less clear and could use spelled out
> > explicitly IMO.  e.g. What's the benefit of storing security.json or
> > configsets in Kubernetes configmaps over ZooKeeper?
> >
>
> This is a great question.
>
> Generally Solr has fairly good tool support for managing various things in
> Zookeeper.
>
> The "zkCli.sh" script and various "bin/solr" commands allow users to easily
> manage their Zookeeper state to setup
> Solr to run the way they need it to. This works very well for users running
> Solr on bare-metal, and manually running these commands.
>
> However, running these commands in Kubernetes is not very convenient and it
> does not really jive with
> the Kubernetes' idempotent model. Basically there isn't a good or easy way
> to run to run the
> solr/zk setup commands before a SolrCloud is created. And when we do it in
> things like an "initContainer",
> the commands have to be run every time a solr process is started (or
> restarted). This isn't really convenient
> and adds complexity that really makes running Solr on Kubernetes much less
> appealing.
>
> Another thing is state management. So let's say that the Solr Operator
> wants to enable auth by default when running Solr.
> It has to create a security.json for Solr to use, and generate passwords
> and secrets for users to use.
> However, it also needs to setup a user & password for itself (the operator)
> to use to interact with the cluster.
> But that's ok, it does it, and it can easily upload this file to zookeeper
> in the initContainer if no security.json already exists.
>
> However we need to allow users to update this file themselves to add more
> users, and do other stuff. So basically we
> can't let the Solr Operator make any changes to this file. So even if a
> user decides that they want to change the security.json secret
> they passed in the SolrCloud, the operator can't make that change happen,
> since it can't overwrite what already exists in zookeeper.
> This will always be a problem when there are two "sources of truth". One
> has to be prioritized.
>
> If we allow the security.json to be loaded from a kubernetes secret, then
> the secret that the user provides is the
> single source of truth. So no matter if the security.json is changed
> through the security UI, the changes will be reflected in
> the kubernetes secret. So users can be free to overwrite that secret if
> they want to, given that everyone knows its the current
> accepted state of the security.json file.
>
> The exact same issues exist with ConfigMaps. Many Solr Operator users want
> to manage their configMaps through
> Kubernetes, just like they manage their SolrClouds. It makes sense, keep
> all of your Solr infra managed together.
> However the operator cannot keep the configSets managed in Zookeeper
> updated with the configSets managed
> via Kube ConfigSets. It's two sources of truth.
>
> *TLDR*: Solr has many command line utilities that work well to setup Solr
> when its running on bare metal or a VM.
> However, these solutions do not work well in a cloud system like
> Kubernetes. If we try to make these things
> easier to setup in Kubernetes, it ultimately results in 2 sources of truth
> (Kubernetes and Zookeeper). If we make
> plugins that allow to load in these settings from Kubernetes instead of
> Zookeeper, we are back down to 1 source
> of truth. And this single source of truth (obviously) works well in
> Kubernetes, because they are native Kubernetes resources.
>
> - Houston
>
> On Tue, Apr 11, 2023 at 2:36 PM Jason Gerlowski 
> wrote:
>
> > Hi Houston,
> >
> > So the general idea is that we'd add a Solr contrib/module, and that
> > module would have a dep on some sort of 

Re: [VOTE] Release Solr 9.2.0 RC1

[Arrieta, Alejandro]

 1) Solr 9.2.0 RC1

SUCCESS! [0:25:45.706109]
virtualbox ubuntu 22.04 + ubuntu openjdk 11

+0 don't know if my vote counts.

2) Solr operator test (Thanks Houston Putman for the command to run the
solr operator tests)

Ran 6 of 6 Specs in 286.376 seconds
SUCCESS! -- 6 Passed | 0 Failed | 0 Pending | 0 Skipped

noob question warning ;-)

1) Do you need to be a Solr committer to have a valid vote?

2) You need dev-tools/scripts/smokeTestRelease.py to run the smoke tests.
I downloaded the solr src tgz from the artifacts folder, uncompress and
then ran the smoke test command.
Is this the correct way to do it?

3) What is the correct/recommended way to handle the trusted chain for this
output.
 verify trust
  GPG: gpg: WARNING: This key is not certified with a trusted signature!


Kind Regards,
Alejandro Arrieta

On Thu, Mar 23, 2023 at 11:21 AM Jason Gerlowski 
wrote:

> +1
> SUCCESS! [0:27:15.62963]
>
> On Thu, Mar 23, 2023 at 4:14 AM Jan Høydahl  wrote:
> >
> > Ran smoke tester and inspected the binary artifacts, release notes and
> CHANGES.
> >
> > SUCCESS! [0:35:32.006982]
> >
> > Only a few minors:
> >
> > * Mal-placed release notes in refguide, fixed in
> https://github.com/apache/solr/pull/1486
> > * Duplicate CHANGES entries in 9.2 section:
> > * SOLR-15787: FileSystemConfigSetService: implement the abstraction
> completely.  It could be useful
> >   for putting ConfigSets on a shared file system.  (Nazerke Seidan,
> David Smiley)
> > * SOLR-16665: The base docker image has been upgraded from Ubuntu 20
> (Focal) to Ubuntu 22 (Jammy). (Houston Putman)
> >
> > All in all good I believe, can fix the changes duplication if there is a
> re-spin.
> >
> > +1 (binding)
> >
> > Jan
> >
> > > 21. mar. 2023 kl. 16:25 skrev Houston Putman :
> > >
> > > Please vote for release candidate 1 for Solr 9.2.0
> > >
> > > The artifacts can be downloaded from:
> > >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.2.0-RC1-rev-92c5515e2918c22513f7aa527d6c6db943150fea
> > >
> > > You can run the smoke tester directly with this command:
> > >
> > > python3 -u dev-tools/scripts/smokeTestRelease.py \
> > >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.2.0-RC1-rev-92c5515e2918c22513f7aa527d6c6db943150fea
> > >
> > > You can build a release-candidate of the official docker image using
> the
> > > following command:
> > >
> > > DIST_BASE=https://dist.apache.org/repos/dist/dev/solr && \
> > >  RC_FOLDER=solr-9.2.0-RC1-rev-92c5515e2918c22513f7aa527d6c6db943150fea
> && \
> > >  docker build $DIST_BASE/$RC_FOLDER/solr/docker/Dockerfile.official \
> > >  --build-arg
> SOLR_DOWNLOAD_URL=$DIST_BASE/$RC_FOLDER/solr/solr-9.2.0.tgz \
> > >  -t solr-rc:9.2.0-1
> > >
> > > The vote will be open for at least 72 hours i.e. until 2023-03-24
> 16:00 UTC.
> > >
> > > [ ] +1  approve
> > > [ ] +0  no opinion
> > > [ ] -1  disapprove (and reason why)
> > >
> > > Here is my +1
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org
> > For additional commands, e-mail: dev-h...@solr.apache.org
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org
> For additional commands, e-mail: dev-h...@solr.apache.org
>
>

Solr documentation questions

[Arrieta, Alejandro]

Hello Team,

I want to help with Solr documentation and  I have some newbie questions:

-Changes in documentation in Solr git repo, do they  need a doc bug ticket
filled?
-If making more than one change to documentation, do you need one PR for
all of them or each change on a separate PR. If a doc bug ticket is needed
one per PR?
-Are there other test(s) to run apart from compiling, seeing that
documentation finished correctly and checking your change display correctly
in your local copy?
-For proposed changes in the Solr wiki, how is this handled? Does anyone
check the changes before publishing them? How do I get edit permits?

I see the Solr git repo has these branches:
main -> generates Solr 10 ( not yet released ) documentation
branch_9x -> generates Solr 9.2 (not yet released) documentation
If I want to make a change in documentation, where is the correct branch to
do it? main (Solr 10), branch_9x (Solr 9.2), both?

Kind Regards,
Alejandro Arrieta Rios

jira account request

[Arrieta, Alejandro]

Hello team,

If possible I want to request a Jira account for the Solr project.

Kind Regards,
Alejandro Arrieta Rios