So...., we may have a problem with the way we use "configset" too. We are using it to mean a template from which a new collection can be created (default, techproducts, etc).
But also, if I remember correctly, we allow to share configuration between live cores using configset parameter in core.properties. And that is not a template use, because both cores may modify the same files through API (oops). Though, now that I look at the documentation, we seem to have collapsed those two. This collapse may actually be wrong.... https://lucene.apache.org/solr/guide/8_8/defining-core-properties.html For paramsets, the cool thing is that you can refer to them for update operations as well. So, they could be used for A/B indexing tests, etc. Regards, Alex. On Mon, 8 Feb 2021 at 13:03, Erik Hatcher <erik.hatc...@gmail.com> wrote: > > > > > On Feb 6, 2021, at 9:48 AM, Eric Pugh <ep...@opensourceconnections.com> > > wrote: > > > > “paramsets”, which I think is a really powerful feature that most people > > don’t know about. > > Agreed on that! (see the old example/files for my early paramset usage as I > explored that cool capability) > > > I’m thinking that we rename request-parameters-api.adoc —> paramsets.adoc, > > and rewrite the page to highlight that this feature is called “paramset”, > > in the same way we use the term “configset”. > > +1 > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
