Re: v2 API "Broader Changes" and Next Steps

@Shawn So, if we move towards an HTTP POST , PUT or DELETE based commands we will never be able to send a link to others over text format because they work only on HTTP GET. I think this is an artificial limitation that we are going to impose on anyone designing an API standard and against the wid

Re: v2 API "Broader Changes" and Next Steps

On 6/16/22 09:07, Gus Heck wrote: I'm all for standardizing on v2 (or something like it) but one key concern I have is that when the only access I have to a client's server is via a web browser, possibly from a machine they control and on which I can't install tools, I'd like the only barrier

Re: v2 API "Broader Changes" and Next Steps

The direction that we are headed for how you interact w Solr is via the admin UI. I am thinking of the security and schema designer additions for example. And some outstanding pr’s to add support for paramsets to the Admin UI. Personally I always found using the browser to be very clunky and da

Re: v2 API "Broader Changes" and Next Steps

I'm all for standardizing on v2 (or something like it) but one key concern I have is that when the only access I have to a client's server is via a web browser, possibly from a machine they control and on which I can't install tools, I'd like the only barrier to my running necessary admin commands

Re: v2 API "Broader Changes" and Next Steps

V2 has existed since v6.5 and has been documented in ref guide evner since. In 7.0 release announcement we said: The new v2 API, exposed at /api/ and also supported via SolrJ, is now the preferred API, but /solr/ continues to work. We have been showing v2 api commands in tabs for e.g. config ap

Re: v2 API "Broader Changes" and Next Steps

I suspect that #2 will inspire #1, once we start trying to use it everywhere in SolrJ and other areas we’ll see patterns and antipatterns emerge and guide us on what the API should be. On Thu, Jun 16, 2022 at 6:05 AM Jason Gerlowski wrote: > Hi all, > > I've been working over the last few months

Re: v2 API "Broader Changes" and Next Steps

I don’t have the link, but I think we agree that v2 *could* evolve, hence the whole experimental thing. I worry that the efforts of maintaining three versions of the api will stall us. Especially if the changes we want to make aren’t wholesale changes. Now if we introduced a graphql based api

Re: v2 API "Broader Changes" and Next Steps

HI, Thanks for having the guts to start such a journey! V2 has been around for several major releases and documented (it's in v6.6 guide https://solr.apache.org/guide/6_6/v2-api.html ) long enough that we must assume a certain user base already. T

Re: v2 API "Broader Changes" and Next Steps

Thanks Jason for spearheading this effort. I'll be biased because I built it. So, I refrain from a vote. However, I shall contribute constructively to the discussion On Thu, Jun 16, 2022 at 9:05 PM Jason Gerlowski wrote: > Hi all, > > I've been working over the last few months to get our "v2"

v2 API "Broader Changes" and Next Steps

Hi all, I've been working over the last few months to get our "v2" API into shape to eventually replace (and allow us to sunset) v1. At a high level the two biggest next-steps are to (1) make whatever changes we'd like to the v2 endpoints while they're still "experimental", and then (2) start usi