I’m okay with /api….
I suspect by the time we do a v3.. well, It’s a completely new way of
interacting with things….
/graph?
/virtual_reality_instructions?
/chatbot?q=split the latest the shards that are too big for me with no
downtime
> On Dec 8, 2023, at
Personally I like "/v2". It's more "future-proof" than "/api", since it
acknowledges that we may want a "v3" someday. But in practice that day is
likely so far off that it's probably not a big deal either way. And I
think in some past discussions about this, "/api" was a mostly unanimous
consens
I think you will find that this is necessary to avoid /solr/api since all
the code lives under the /solr web app (and has to go throuh
SolrDispatchFilter). This sort of thing is why I would someday like to pick
apart our uber-swiss-army-kinfe-filter (SolrDispatchFilter) and make a
series of filters
While looking at our jett.xml, I noticed some rewrite rules including a
"/v2/*" mapping.
https://github.com/apache/solr/blob/b14505c19a76e833734dc0c75febc3601f633e37/solr/server/etc/jetty.xml#L142C35-L142C35
Is this considered a deprecated URL pattern for V2 which is now at "/api"
if I recall corr
