Should I register a new API endpoint.

[Joshua Ouma]

Hi all ,
I'm working on creating a v2 equivalent of v1 CLUSTERSTATUS-

I have created an endpoint @EndPoint(method = GET, path =
"/cluster/cluster-status", permission = COLL_READ_PERM) of the ClusterAPI.

After running ./gradlew assemble and starting solr from the dev folder I
tested the endpoint using curl -X GET
http://localhost:8983/api/cluster/cluster-status/ but I'm getting the error
{"metadata":{"error-class":"org.apache.solr.common.SolrException","root-error-class":"org.apache.solr.common.SolrException"},"msg":"Cannot
find API for the path: /cluster/cluster-status/"}

Am I missing something?

Regards,
Joshua Ouma

Re: Should I register a new API endpoint.

[Joshua Ouma]

Actually I have found the solution. To run solr from dev folder I should
use the build command ./gradlew dev and not ./gradlew assemble

Regard,
Joshua Ouma

On Wed, Oct 12, 2022 at 11:39 AM Joshua Ouma  wrote:

> Hi all ,
> I'm working on creating a v2 equivalent of v1 CLUSTERSTATUS-
>
> I have created an endpoint @EndPoint(method = GET, path =
> "/cluster/cluster-status", permission = COLL_READ_PERM) of the ClusterAPI.
>
> After running ./gradlew assemble and starting solr from the dev folder I
> tested the endpoint using curl -X GET
> http://localhost:8983/api/cluster/cluster-status/ but I'm getting the
> error
> {"metadata":{"error-class":"org.apache.solr.common.SolrException","root-error-class":"org.apache.solr.common.SolrException"},"msg":"Cannot
> find API for the path: /cluster/cluster-status/"}
>
> Am I missing something?
>
> Regards,
> Joshua Ouma
>

Re: Should I register a new API endpoint.

[Eric Pugh]

Have you seen the FAQ entries?  
https://github.com/apache/solr/blob/main/dev-docs/FAQ.adoc#whats-the-fastest-build-lifecycle-for-frontend-work-on-solr-admin
 


That FAQ is specific to the solr admin, but probably applies to any development 
cycle!

I’d love to see any other candidate FAQ entries that you discover based on 
learning how Solr works.

> On Oct 12, 2022, at 5:58 AM, Joshua Ouma  wrote:
> 
> Actually I have found the solution. To run solr from dev folder I should
> use the build command ./gradlew dev and not ./gradlew assemble
> 
> Regard,
> Joshua Ouma
> 
> On Wed, Oct 12, 2022 at 11:39 AM Joshua Ouma  wrote:
> 
>> Hi all ,
>> I'm working on creating a v2 equivalent of v1 CLUSTERSTATUS-
>> 
>> I have created an endpoint @EndPoint(method = GET, path =
>> "/cluster/cluster-status", permission = COLL_READ_PERM) of the ClusterAPI.
>> 
>> After running ./gradlew assemble and starting solr from the dev folder I
>> tested the endpoint using curl -X GET
>> http://localhost:8983/api/cluster/cluster-status/ but I'm getting the
>> error
>> {"metadata":{"error-class":"org.apache.solr.common.SolrException","root-error-class":"org.apache.solr.common.SolrException"},"msg":"Cannot
>> find API for the path: /cluster/cluster-status/"}
>> 
>> Am I missing something?
>> 
>> Regards,
>> Joshua Ouma
>> 

___
Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467 | 
http://www.opensourceconnections.com  | 
My Free/Busy   
Co-Author: Apache Solr Enterprise Search Server, 3rd Ed 


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.

Re: New branch and feature freeze for Solr 9.1.0

[Christine Poerschke (BLOOMBERG/ LONDON)]

I'd like to also include https://github.com/apache/solr/pull/1050 for 
https://issues.apache.org/jira/browse/SOLR-16439 bug fix please if that is okay?

Christine

From: dev@solr.apache.org At: 10/11/22 20:11:10 UTC+1:00To:  dev@solr.apache.org
Subject: Re: New branch and feature freeze for Solr 9.1.0

Sure Kevin, please go ahead. Noble and I are debugging a critical test
failure related to overseer (SOLR-16440) and kind of blocked at the moment
for the release.

On Tue, 11 Oct, 2022, 10:51 pm Kevin Risden,  wrote:

> Ishan I'm hoping to get these two jiras in for 9.1, the PRs are up there
> waiting for reviews and they need to run through tests. The two are
> related.
> * https://issues.apache.org/jira/browse/SOLR-16457 - solr.data.home set to
> empty string in bin/solr
> * https://issues.apache.org/jira/browse/SOLR-16433 - Solr SQL isn't
> working
> w/ security manager enabled
>
> Kevin Risden
>
>
> On Mon, Oct 10, 2022 at 1:41 AM Ishan Chattopadhyaya <
> ichattopadhy...@gmail.com> wrote:
>
> >
> >
> 
https://issues.apache.org/jira/browse/SOLR-16453?jql=project%20%3D%20SOLR%20AND%
20(fixVersion%20%3D%209.1)%20AND%20priority%20%3D%20Blocker%20AND%20resolution%2
0%3D%20Unresolved
> >
> > On Mon, Oct 10, 2022 at 11:10 AM Ishan Chattopadhyaya <
> > ichattopadhy...@gmail.com> wrote:
> >
> > > There were lots of Blocker issues with affectsVersion as 9.1. I assume
> > the
> > > intention was to have them be available in 9.1? I've changed them to
> > > fixVersion = 9.1 (blocker).
> > >
> > > On Fri, Oct 7, 2022 at 5:17 PM Christine Poerschke (BLOOMBERG/ LONDON)
> <
> > > cpoersc...@bloomberg.net> wrote:
> > >
> > >> Thanks! Merging and backporting is now complete.
> > >>
> > >> From: dev@solr.apache.org At: 10/07/22 04:07:31 UTC+1:00To:
> Christine
> > >> Poerschke (BLOOMBERG/ LONDON ) ,  dev@solr.apache.org
> > >> Subject: Re: New branch and feature freeze for Solr 9.1.0
> > >>
> > >> Sure, please go ahead.
> > >>
> > >> On Fri, 7 Oct, 2022, 12:15 am Christine Poerschke (BLOOMBERG/
> LONDON), <
> > >> cpoersc...@bloomberg.net> wrote:
> > >>
> > >> > I'd like to include https://github.com/apache/solr/pull/1051 for
> > >> > https://issues.apache.org/jira/browse/SOLR-13219 bug fix please if
> > that
> > >> > is okay?
> > >> >
> > >> > Christine
> > >> >
> > >> > From: dev@solr.apache.org At: 10/04/22 12:33:03 UTC+1:00To:
> > >> > dev@solr.apache.org
> > >> > Subject: Re: New branch and feature freeze for Solr 9.1.0
> > >> >
> > >> > Sure, please go ahead.
> > >> >
> > >> >
> > >> > I'm concerned about the intermittent test failures. Noble is looking
> > at
> > >> it,
> > >> > will hold off the release for now. Also, I'm out on vacation for
> next
> > 3
> > >> > days (Dusshera holidays in India). Will resume the release process
> > once
> > >> I'm
> > >> > back.
> > >> >
> > >> >
> > >> > On Tue, 4 Oct, 2022, 12:01 am Tomás Fernández Löbbe, <
> > >> > tomasflo...@gmail.com>
> > >> > wrote:
> > >> >
> > >> > > I'd like to merge the PR for SOLR-16229 (
> > >> > > https://github.com/apache/solr/pull/1047) to 9.1 branch if that's
> > OK.
> > >> > >
> > >> > > Tomás
> > >> > >
> > >> > > On Mon, Sep 26, 2022 at 11:12 PM Ishan Chattopadhyaya <
> > >> > > ichattopadhy...@gmail.com> wrote:
> > >> > >
> > >> > > > NOTICE:
> > >> > > >
> > >> > > > Branch branch_9_1 has been cut and versions updated to 9.2 on
> > stable
> > >> > > > branch.
> > >> > > >
> > >> > > > Please note the following:
> > >> > > >
> > >> > > > * No new features may be committed to the branch without
> > discussion
> > >> on
> > >> > > the
> > >> > > > dev-list.
> > >> > > > * Documentation patches, build patches and serious bug fixes may
> > be
> > >> > > >   committed to the branch. However, you should submit all
> patches
> > >> you
> > >> > > >   want to commit to Jira first to give others the chance to
> review
> > >> > > >   and possibly vote against the patch. Keep in mind that it is
> our
> > >> > > >   main intention to keep the branch as stable as possible.
> > >> > > > * All patches that are intended for the branch should first be
> > >> > committed
> > >> > > >   to the unstable branch, merged into the stable branch, and
> then
> > >> into
> > >> > > >   the current release branch.
> > >> > > > * Normal unstable and stable branch development may continue as
> > >> usual.
> > >> > > > * Only Jira issues with Fix version 9.1 and priority "Blocker"
> > will
> > >> > delay
> > >> > > >   a release candidate build.
> > >> > > >
> > >> > >
> > >> >
> > >> >
> > >> >
> > >>
> > >>
> > >>
> >
>

Re: Should I register a new API endpoint.

[Joshua Ouma]

I had not seen the FAQs. Sure I'll update the FAQs with what I discover
while learning how Solr works.

Regards,
Joshua Ouma

On Wed, Oct 12, 2022 at 2:47 PM Eric Pugh 
wrote:

> Have you seen the FAQ entries?
> https://github.com/apache/solr/blob/main/dev-docs/FAQ.adoc#whats-the-fastest-build-lifecycle-for-frontend-work-on-solr-admin
> <
> https://github.com/apache/solr/blob/main/dev-docs/FAQ.adoc#whats-the-fastest-build-lifecycle-for-frontend-work-on-solr-admin
> >
>
> That FAQ is specific to the solr admin, but probably applies to any
> development cycle!
>
> I’d love to see any other candidate FAQ entries that you discover based on
> learning how Solr works.
>
> > On Oct 12, 2022, at 5:58 AM, Joshua Ouma  wrote:
> >
> > Actually I have found the solution. To run solr from dev folder I should
> > use the build command ./gradlew dev and not ./gradlew assemble
> >
> > Regard,
> > Joshua Ouma
> >
> > On Wed, Oct 12, 2022 at 11:39 AM Joshua Ouma 
> wrote:
> >
> >> Hi all ,
> >> I'm working on creating a v2 equivalent of v1 CLUSTERSTATUS-
> >>
> >> I have created an endpoint @EndPoint(method = GET, path =
> >> "/cluster/cluster-status", permission = COLL_READ_PERM) of the
> ClusterAPI.
> >>
> >> After running ./gradlew assemble and starting solr from the dev folder I
> >> tested the endpoint using curl -X GET
> >> http://localhost:8983/api/cluster/cluster-status/ but I'm getting the
> >> error
> >>
> {"metadata":{"error-class":"org.apache.solr.common.SolrException","root-error-class":"org.apache.solr.common.SolrException"},"msg":"Cannot
> >> find API for the path: /cluster/cluster-status/"}
> >>
> >> Am I missing something?
> >>
> >> Regards,
> >> Joshua Ouma
> >>
>
> ___
> 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.
>
>

Re: New branch and feature freeze for Solr 9.1.0

[Ishan Chattopadhyaya]

Sure, please go ahead. Thanks!

On Wed, 12 Oct, 2022, 5:27 pm Christine Poerschke (BLOOMBERG/ LONDON), <
cpoersc...@bloomberg.net> wrote:

> I'd like to also include https://github.com/apache/solr/pull/1050 for
> https://issues.apache.org/jira/browse/SOLR-16439 bug fix please if that
> is okay?
>
> Christine
>
> From: dev@solr.apache.org At: 10/11/22 20:11:10 UTC+1:00To:
> dev@solr.apache.org
> Subject: Re: New branch and feature freeze for Solr 9.1.0
>
> Sure Kevin, please go ahead. Noble and I are debugging a critical test
> failure related to overseer (SOLR-16440) and kind of blocked at the moment
> for the release.
>
> On Tue, 11 Oct, 2022, 10:51 pm Kevin Risden,  wrote:
>
> > Ishan I'm hoping to get these two jiras in for 9.1, the PRs are up there
> > waiting for reviews and they need to run through tests. The two are
> > related.
> > * https://issues.apache.org/jira/browse/SOLR-16457 - solr.data.home set
> to
> > empty string in bin/solr
> > * https://issues.apache.org/jira/browse/SOLR-16433 - Solr SQL isn't
> > working
> > w/ security manager enabled
> >
> > Kevin Risden
> >
> >
> > On Mon, Oct 10, 2022 at 1:41 AM Ishan Chattopadhyaya <
> > ichattopadhy...@gmail.com> wrote:
> >
> > >
> > >
> >
>
> https://issues.apache.org/jira/browse/SOLR-16453?jql=project%20%3D%20SOLR%20AND%
>
> 20(fixVersion%20%3D%209.1)%20AND%20priority%20%3D%20Blocker%20AND%20resolution%2
> 0%3D%20Unresolved
> > >
> > > On Mon, Oct 10, 2022 at 11:10 AM Ishan Chattopadhyaya <
> > > ichattopadhy...@gmail.com> wrote:
> > >
> > > > There were lots of Blocker issues with affectsVersion as 9.1. I
> assume
> > > the
> > > > intention was to have them be available in 9.1? I've changed them to
> > > > fixVersion = 9.1 (blocker).
> > > >
> > > > On Fri, Oct 7, 2022 at 5:17 PM Christine Poerschke (BLOOMBERG/
> LONDON)
> > <
> > > > cpoersc...@bloomberg.net> wrote:
> > > >
> > > >> Thanks! Merging and backporting is now complete.
> > > >>
> > > >> From: dev@solr.apache.org At: 10/07/22 04:07:31 UTC+1:00To:
> > Christine
> > > >> Poerschke (BLOOMBERG/ LONDON ) ,  dev@solr.apache.org
> > > >> Subject: Re: New branch and feature freeze for Solr 9.1.0
> > > >>
> > > >> Sure, please go ahead.
> > > >>
> > > >> On Fri, 7 Oct, 2022, 12:15 am Christine Poerschke (BLOOMBERG/
> > LONDON), <
> > > >> cpoersc...@bloomberg.net> wrote:
> > > >>
> > > >> > I'd like to include https://github.com/apache/solr/pull/1051 for
> > > >> > https://issues.apache.org/jira/browse/SOLR-13219 bug fix please
> if
> > > that
> > > >> > is okay?
> > > >> >
> > > >> > Christine
> > > >> >
> > > >> > From: dev@solr.apache.org At: 10/04/22 12:33:03 UTC+1:00To:
> > > >> > dev@solr.apache.org
> > > >> > Subject: Re: New branch and feature freeze for Solr 9.1.0
> > > >> >
> > > >> > Sure, please go ahead.
> > > >> >
> > > >> >
> > > >> > I'm concerned about the intermittent test failures. Noble is
> looking
> > > at
> > > >> it,
> > > >> > will hold off the release for now. Also, I'm out on vacation for
> > next
> > > 3
> > > >> > days (Dusshera holidays in India). Will resume the release process
> > > once
> > > >> I'm
> > > >> > back.
> > > >> >
> > > >> >
> > > >> > On Tue, 4 Oct, 2022, 12:01 am Tomás Fernández Löbbe, <
> > > >> > tomasflo...@gmail.com>
> > > >> > wrote:
> > > >> >
> > > >> > > I'd like to merge the PR for SOLR-16229 (
> > > >> > > https://github.com/apache/solr/pull/1047) to 9.1 branch if
> that's
> > > OK.
> > > >> > >
> > > >> > > Tomás
> > > >> > >
> > > >> > > On Mon, Sep 26, 2022 at 11:12 PM Ishan Chattopadhyaya <
> > > >> > > ichattopadhy...@gmail.com> wrote:
> > > >> > >
> > > >> > > > NOTICE:
> > > >> > > >
> > > >> > > > Branch branch_9_1 has been cut and versions updated to 9.2 on
> > > stable
> > > >> > > > branch.
> > > >> > > >
> > > >> > > > Please note the following:
> > > >> > > >
> > > >> > > > * No new features may be committed to the branch without
> > > discussion
> > > >> on
> > > >> > > the
> > > >> > > > dev-list.
> > > >> > > > * Documentation patches, build patches and serious bug fixes
> may
> > > be
> > > >> > > >   committed to the branch. However, you should submit all
> > patches
> > > >> you
> > > >> > > >   want to commit to Jira first to give others the chance to
> > review
> > > >> > > >   and possibly vote against the patch. Keep in mind that it is
> > our
> > > >> > > >   main intention to keep the branch as stable as possible.
> > > >> > > > * All patches that are intended for the branch should first be
> > > >> > committed
> > > >> > > >   to the unstable branch, merged into the stable branch, and
> > then
> > > >> into
> > > >> > > >   the current release branch.
> > > >> > > > * Normal unstable and stable branch development may continue
> as
> > > >> usual.
> > > >> > > > * Only Jira issues with Fix version 9.1 and priority "Blocker"
> > > will
> > > >> > delay
> > > >> > > >   a release candidate build.
> > > >> > > >
> > > >> > >
> > > >> >
> > > >> >
> > > >> >
> > > >>
> > > >>
> > > >>
> > >
> >
>
>
>

Re: New branch and feature freeze for Solr 9.1.0

[Christine Poerschke (BLOOMBERG/ LONDON)]

Merging and backporting is now complete. Thank you.

From: dev@solr.apache.org At: 10/12/22 17:01:02 UTC+1:00To:  Christine 
Poerschke (BLOOMBERG/ LONDON ) ,  dev@solr.apache.org
Subject: Re: New branch and feature freeze for Solr 9.1.0

Sure, please go ahead. Thanks!

On Wed, 12 Oct, 2022, 5:27 pm Christine Poerschke (BLOOMBERG/ LONDON), <
cpoersc...@bloomberg.net> wrote:

> I'd like to also include https://github.com/apache/solr/pull/1050 for
> https://issues.apache.org/jira/browse/SOLR-16439 bug fix please if that
> is okay?
>
> Christine
>
> From: dev@solr.apache.org At: 10/11/22 20:11:10 UTC+1:00To:
> dev@solr.apache.org
> Subject: Re: New branch and feature freeze for Solr 9.1.0
>
> Sure Kevin, please go ahead. Noble and I are debugging a critical test
> failure related to overseer (SOLR-16440) and kind of blocked at the moment
> for the release.
>
> On Tue, 11 Oct, 2022, 10:51 pm Kevin Risden,  wrote:
>
> > Ishan I'm hoping to get these two jiras in for 9.1, the PRs are up there
> > waiting for reviews and they need to run through tests. The two are
> > related.
> > * https://issues.apache.org/jira/browse/SOLR-16457 - solr.data.home set
> to
> > empty string in bin/solr
> > * https://issues.apache.org/jira/browse/SOLR-16433 - Solr SQL isn't
> > working
> > w/ security manager enabled
> >
> > Kevin Risden
> >
> >
> > On Mon, Oct 10, 2022 at 1:41 AM Ishan Chattopadhyaya <
> > ichattopadhy...@gmail.com> wrote:
> >
> > >
> > >
> >
>
> 
https://issues.apache.org/jira/browse/SOLR-16453?jql=project%20%3D%20SOLR%20AND%
>
> 
20(fixVersion%20%3D%209.1)%20AND%20priority%20%3D%20Blocker%20AND%20resolution%2
> 0%3D%20Unresolved
> > >
> > > On Mon, Oct 10, 2022 at 11:10 AM Ishan Chattopadhyaya <
> > > ichattopadhy...@gmail.com> wrote:
> > >
> > > > There were lots of Blocker issues with affectsVersion as 9.1. I
> assume
> > > the
> > > > intention was to have them be available in 9.1? I've changed them to
> > > > fixVersion = 9.1 (blocker).
> > > >
> > > > On Fri, Oct 7, 2022 at 5:17 PM Christine Poerschke (BLOOMBERG/
> LONDON)
> > <
> > > > cpoersc...@bloomberg.net> wrote:
> > > >
> > > >> Thanks! Merging and backporting is now complete.
> > > >>
> > > >> From: dev@solr.apache.org At: 10/07/22 04:07:31 UTC+1:00To:
> > Christine
> > > >> Poerschke (BLOOMBERG/ LONDON ) ,  dev@solr.apache.org
> > > >> Subject: Re: New branch and feature freeze for Solr 9.1.0
> > > >>
> > > >> Sure, please go ahead.
> > > >>
> > > >> On Fri, 7 Oct, 2022, 12:15 am Christine Poerschke (BLOOMBERG/
> > LONDON), <
> > > >> cpoersc...@bloomberg.net> wrote:
> > > >>
> > > >> > I'd like to include https://github.com/apache/solr/pull/1051 for
> > > >> > https://issues.apache.org/jira/browse/SOLR-13219 bug fix please
> if
> > > that
> > > >> > is okay?
> > > >> >
> > > >> > Christine
> > > >> >
> > > >> > From: dev@solr.apache.org At: 10/04/22 12:33:03 UTC+1:00To:
> > > >> > dev@solr.apache.org
> > > >> > Subject: Re: New branch and feature freeze for Solr 9.1.0
> > > >> >
> > > >> > Sure, please go ahead.
> > > >> >
> > > >> >
> > > >> > I'm concerned about the intermittent test failures. Noble is
> looking
> > > at
> > > >> it,
> > > >> > will hold off the release for now. Also, I'm out on vacation for
> > next
> > > 3
> > > >> > days (Dusshera holidays in India). Will resume the release process
> > > once
> > > >> I'm
> > > >> > back.
> > > >> >
> > > >> >
> > > >> > On Tue, 4 Oct, 2022, 12:01 am Tomás Fernández Löbbe, <
> > > >> > tomasflo...@gmail.com>
> > > >> > wrote:
> > > >> >
> > > >> > > I'd like to merge the PR for SOLR-16229 (
> > > >> > > https://github.com/apache/solr/pull/1047) to 9.1 branch if
> that's
> > > OK.
> > > >> > >
> > > >> > > Tomás
> > > >> > >
> > > >> > > On Mon, Sep 26, 2022 at 11:12 PM Ishan Chattopadhyaya <
> > > >> > > ichattopadhy...@gmail.com> wrote:
> > > >> > >
> > > >> > > > NOTICE:
> > > >> > > >
> > > >> > > > Branch branch_9_1 has been cut and versions updated to 9.2 on
> > > stable
> > > >> > > > branch.
> > > >> > > >
> > > >> > > > Please note the following:
> > > >> > > >
> > > >> > > > * No new features may be committed to the branch without
> > > discussion
> > > >> on
> > > >> > > the
> > > >> > > > dev-list.
> > > >> > > > * Documentation patches, build patches and serious bug fixes
> may
> > > be
> > > >> > > >   committed to the branch. However, you should submit all
> > patches
> > > >> you
> > > >> > > >   want to commit to Jira first to give others the chance to
> > review
> > > >> > > >   and possibly vote against the patch. Keep in mind that it is
> > our
> > > >> > > >   main intention to keep the branch as stable as possible.
> > > >> > > > * All patches that are intended for the branch should first be
> > > >> > committed
> > > >> > > >   to the unstable branch, merged into the stable branch, and
> > then
> > > >> into
> > > >> > > >   the current release branch.
> > > >> > > > * Normal unstable and stable branch development may continue
> as
> > > >> usual.
> > > >> > > > * Only Ji

Re: New branch and feature freeze for Solr 9.1.0

[Kevin Risden]

>
> * https://issues.apache.org/jira/browse/SOLR-16457 - solr.data.home set
> to empty string in bin/solr
> * https://issues.apache.org/jira/browse/SOLR-16433 - Solr SQL isn't
> working w/ security manager enabled
>

Merged and backported to branch_9_1


Kevin Risden


On Wed, Oct 12, 2022 at 12:32 PM Christine Poerschke (BLOOMBERG/ LONDON) <
cpoersc...@bloomberg.net> wrote:

> Merging and backporting is now complete. Thank you.
>
> From: dev@solr.apache.org At: 10/12/22 17:01:02 UTC+1:00To:  Christine
> Poerschke (BLOOMBERG/ LONDON ) ,  dev@solr.apache.org
> Subject: Re: New branch and feature freeze for Solr 9.1.0
>
> Sure, please go ahead. Thanks!
>
> On Wed, 12 Oct, 2022, 5:27 pm Christine Poerschke (BLOOMBERG/ LONDON), <
> cpoersc...@bloomberg.net> wrote:
>
> > I'd like to also include https://github.com/apache/solr/pull/1050 for
> > https://issues.apache.org/jira/browse/SOLR-16439 bug fix please if that
> > is okay?
> >
> > Christine
> >
> > From: dev@solr.apache.org At: 10/11/22 20:11:10 UTC+1:00To:
> > dev@solr.apache.org
> > Subject: Re: New branch and feature freeze for Solr 9.1.0
> >
> > Sure Kevin, please go ahead. Noble and I are debugging a critical test
> > failure related to overseer (SOLR-16440) and kind of blocked at the
> moment
> > for the release.
> >
> > On Tue, 11 Oct, 2022, 10:51 pm Kevin Risden,  wrote:
> >
> > > Ishan I'm hoping to get these two jiras in for 9.1, the PRs are up
> there
> > > waiting for reviews and they need to run through tests. The two are
> > > related.
> > > * https://issues.apache.org/jira/browse/SOLR-16457 - solr.data.home
> set
> > to
> > > empty string in bin/solr
> > > * https://issues.apache.org/jira/browse/SOLR-16433 - Solr SQL isn't
> > > working
> > > w/ security manager enabled
> > >
> > > Kevin Risden
> > >
> > >
> > > On Mon, Oct 10, 2022 at 1:41 AM Ishan Chattopadhyaya <
> > > ichattopadhy...@gmail.com> wrote:
> > >
> > > >
> > > >
> > >
> >
> >
>
> https://issues.apache.org/jira/browse/SOLR-16453?jql=project%20%3D%20SOLR%20AND%
> >
> >
>
> 20(fixVersion%20%3D%209.1)%20AND%20priority%20%3D%20Blocker%20AND%20resolution%2
> > 0%3D%20Unresolved
> > > >
> > > > On Mon, Oct 10, 2022 at 11:10 AM Ishan Chattopadhyaya <
> > > > ichattopadhy...@gmail.com> wrote:
> > > >
> > > > > There were lots of Blocker issues with affectsVersion as 9.1. I
> > assume
> > > > the
> > > > > intention was to have them be available in 9.1? I've changed them
> to
> > > > > fixVersion = 9.1 (blocker).
> > > > >
> > > > > On Fri, Oct 7, 2022 at 5:17 PM Christine Poerschke (BLOOMBERG/
> > LONDON)
> > > <
> > > > > cpoersc...@bloomberg.net> wrote:
> > > > >
> > > > >> Thanks! Merging and backporting is now complete.
> > > > >>
> > > > >> From: dev@solr.apache.org At: 10/07/22 04:07:31 UTC+1:00To:
> > > Christine
> > > > >> Poerschke (BLOOMBERG/ LONDON ) ,  dev@solr.apache.org
> > > > >> Subject: Re: New branch and feature freeze for Solr 9.1.0
> > > > >>
> > > > >> Sure, please go ahead.
> > > > >>
> > > > >> On Fri, 7 Oct, 2022, 12:15 am Christine Poerschke (BLOOMBERG/
> > > LONDON), <
> > > > >> cpoersc...@bloomberg.net> wrote:
> > > > >>
> > > > >> > I'd like to include https://github.com/apache/solr/pull/1051
> for
> > > > >> > https://issues.apache.org/jira/browse/SOLR-13219 bug fix please
> > if
> > > > that
> > > > >> > is okay?
> > > > >> >
> > > > >> > Christine
> > > > >> >
> > > > >> > From: dev@solr.apache.org At: 10/04/22 12:33:03 UTC+1:00To:
> > > > >> > dev@solr.apache.org
> > > > >> > Subject: Re: New branch and feature freeze for Solr 9.1.0
> > > > >> >
> > > > >> > Sure, please go ahead.
> > > > >> >
> > > > >> >
> > > > >> > I'm concerned about the intermittent test failures. Noble is
> > looking
> > > > at
> > > > >> it,
> > > > >> > will hold off the release for now. Also, I'm out on vacation for
> > > next
> > > > 3
> > > > >> > days (Dusshera holidays in India). Will resume the release
> process
> > > > once
> > > > >> I'm
> > > > >> > back.
> > > > >> >
> > > > >> >
> > > > >> > On Tue, 4 Oct, 2022, 12:01 am Tomás Fernández Löbbe, <
> > > > >> > tomasflo...@gmail.com>
> > > > >> > wrote:
> > > > >> >
> > > > >> > > I'd like to merge the PR for SOLR-16229 (
> > > > >> > > https://github.com/apache/solr/pull/1047) to 9.1 branch if
> > that's
> > > > OK.
> > > > >> > >
> > > > >> > > Tomás
> > > > >> > >
> > > > >> > > On Mon, Sep 26, 2022 at 11:12 PM Ishan Chattopadhyaya <
> > > > >> > > ichattopadhy...@gmail.com> wrote:
> > > > >> > >
> > > > >> > > > NOTICE:
> > > > >> > > >
> > > > >> > > > Branch branch_9_1 has been cut and versions updated to 9.2
> on
> > > > stable
> > > > >> > > > branch.
> > > > >> > > >
> > > > >> > > > Please note the following:
> > > > >> > > >
> > > > >> > > > * No new features may be committed to the branch without
> > > > discussion
> > > > >> on
> > > > >> > > the
> > > > >> > > > dev-list.
> > > > >> > > > * Documentation patches, build patches and serious bug fixes
> > may
> > > > be
> > > > >> > > >   committed to the bran

Deprecation/Backcompat for Internal+Undocumented APIs

[Jason Gerlowski]

Hi all,

Does our normal deprecation and backcompat policy around APIs, i.e.
deprecate in major version (N-1) in order to remove/modify in major version
N, apply to undocumented/internal APIs?

I stumbled across an internal core-admin API (/admin/cores?action=INVOKE)
on 'main' recently that was added in support of the "snitch" functionality
in the Rule Based Replica Placement functionality that was removed in 9.0.
The API eluded removal as a part of that ticket I guess, so now I'm
wondering whether we're stuck with it until 10.0, or whether this is a
reasonable exception to our normal backcompat policy? [1] [2]

Best,

Jason

[1] https://issues.apache.org/jira/browse/SOLR-14930 - removal of RBRP in
9.0
[2] https://issues.apache.org/jira/browse/SOLR-16459 - proposed removal of
INVOKE API

Understanding CLUSTERPROP APIs

[Jason Gerlowski]

Hi all,

I noticed recently that Solr has several overlapping APIs for modifying
what it calls "CLUSTERPROPS".  I think I understand the purpose of each of
these, but wanted to check here in case anyone had context to confirm or
correct me:

/admin/collections?action=CLUSTERPROP (or POST /api/cluster {set-property:
{...}} in v2 parlance) updates /clusterprops.json in ZooKeeper and can only
be used to modify cluster properties one-at-a-time. [1] [2]

POST /api/cluster {"set-obj-property": {...}} on the other hand (which has
no v1 equivalent) also updates the /clusterprops.json node in ZooKeeper,
but can be used to atomically update multiple properties simultaneously. [3]

My understanding is that there's no difference in these APIs, other than
the latter's ability to update multiple properties atomically - is that
correct?  If so, is there any reason to ever use
/admin/collections?action=CLUSTERPROP over its alternative, or do we see
the latter "set-obj-property" API as eventually supercedeing its
predecessor?

Best,

Jason

[1]
https://github.com/apache/solr/blob/02a1ff4b41d4d7abd0c017adc8d49f1a61e1e45b/solr/core/src/java/org/apache/solr/handler/admin/CollectionsHandler.java#L1041
[2]
https://github.com/apache/solr/blob/f1f32d39ff715ddd325d873203e685655aa268d0/solr/core/src/java/org/apache/solr/handler/ClusterAPI.java#L299
[3]
https://github.com/apache/solr/blob/f1f32d39ff715ddd325d873203e685655aa268d0/solr/core/src/java/org/apache/solr/handler/ClusterAPI.java#L286

Re: Understanding CLUSTERPROP APIs

[Noble Paul]

they are essentially trying to achieve the same thing . however the v2 API
can actually set deeply nested objects and the v2 API can only touch the
single value attributes at the top level.



On Thu, Oct 13, 2022 at 12:37 PM Jason Gerlowski 
wrote:

> Hi all,
>
> I noticed recently that Solr has several overlapping APIs for modifying
> what it calls "CLUSTERPROPS".  I think I understand the purpose of each of
> these, but wanted to check here in case anyone had context to confirm or
> correct me:
>
> /admin/collections?action=CLUSTERPROP (or POST /api/cluster {set-property:
> {...}} in v2 parlance) updates /clusterprops.json in ZooKeeper and can only
> be used to modify cluster properties one-at-a-time. [1] [2]
>
> POST /api/cluster {"set-obj-property": {...}} on the other hand (which has
> no v1 equivalent) also updates the /clusterprops.json node in ZooKeeper,
> but can be used to atomically update multiple properties simultaneously.
> [3]
>
> My understanding is that there's no difference in these APIs, other than
> the latter's ability to update multiple properties atomically - is that
> correct?  If so, is there any reason to ever use
> /admin/collections?action=CLUSTERPROP over its alternative, or do we see
> the latter "set-obj-property" API as eventually supercedeing its
> predecessor?
>
> Best,
>
> Jason
>
> [1]
>
> https://github.com/apache/solr/blob/02a1ff4b41d4d7abd0c017adc8d49f1a61e1e45b/solr/core/src/java/org/apache/solr/handler/admin/CollectionsHandler.java#L1041
> [2]
>
> https://github.com/apache/solr/blob/f1f32d39ff715ddd325d873203e685655aa268d0/solr/core/src/java/org/apache/solr/handler/ClusterAPI.java#L299
> [3]
>
> https://github.com/apache/solr/blob/f1f32d39ff715ddd325d873203e685655aa268d0/solr/core/src/java/org/apache/solr/handler/ClusterAPI.java#L286
>


-- 
-
Noble Paul

Re: Deprecation/Backcompat for Internal+Undocumented APIs

[Noble Paul]

They are internal/undocumented APIs .IMHO we shoould not wait until 10.0

On Thu, Oct 13, 2022 at 6:26 AM Jason Gerlowski 
wrote:

> Hi all,
>
> Does our normal deprecation and backcompat policy around APIs, i.e.
> deprecate in major version (N-1) in order to remove/modify in major version
> N, apply to undocumented/internal APIs?
>
> I stumbled across an internal core-admin API (/admin/cores?action=INVOKE)
> on 'main' recently that was added in support of the "snitch" functionality
> in the Rule Based Replica Placement functionality that was removed in 9.0.
> The API eluded removal as a part of that ticket I guess, so now I'm
> wondering whether we're stuck with it until 10.0, or whether this is a
> reasonable exception to our normal backcompat policy? [1] [2]
>
> Best,
>
> Jason
>
> [1] https://issues.apache.org/jira/browse/SOLR-14930 - removal of RBRP in
> 9.0
> [2] https://issues.apache.org/jira/browse/SOLR-16459 - proposed removal of
> INVOKE API
>


-- 
-
Noble Paul