The v2 examples that are in the Ref Guide already use the widget you mention.
See something like
https://lucene.apache.org/solr/guide/8_1/adding-custom-plugins-in-solrcloud-mode.html#config-api-commands-to-use-jars-as-runtime-libraries
for an example.
SOLR-11646 tracks the effort to add v2
We have places where there are curl/solrj alternatives in the examples.
Maybe a similar widget could be used for V1/V2 examples? or even better
v1/v2/solrj examples for collections api :)
On Mon, Jul 8, 2019 at 2:02 PM Gus Heck wrote:
> Also the Collections API docs are almost devoid of v2
Also the Collections API docs are almost devoid of v2 examples. Just fixing
this would provide a really good reminder to those implementing features to
check that it works in v2. (unless they add features without documenting
them... which usually doesn't happen)
On Sun, Jul 7, 2019 at 9:51 PM
This is a problem. V2 APIs need a lot more metadata and nobody is doing it.
This leads to a lot of technical debt
On Fri, May 17, 2019, 3:42 AM David Smiley wrote:
> I'm concerned about Solr's V2 API and the maintenance burden of attempting
> to maintain consistency with V1. For example upon
+1
Perhaps it’s possible to use forbiddenapis to block new test classes explicitly
calling v1 apis? (Look for “/solr/admin/.*”)? And of course make sure that
SolrJ commands map to v2...
Jan Høydahl
> 16. mai 2019 kl. 19:33 skrev David Smiley :
>
> I'm concerned about Solr's V2 API and the
I'm concerned about Solr's V2 API and the maintenance burden of attempting
to maintain consistency with V1. For example upon looking through the
release notes and seeing a new exciting REINDEXCOLLECTION command (a V1
reference), I see no corresponding adjustments in V2 --
