This is some great perspective, and I love you caught the two ways I wrote it.
I do the same with ConfigSets etc….
Plus, we have configoverlay.json out there that is slightly different. Is
there a common pattern, like config-overlay.json and request-parameters.json or
even
I have a slightly different view - the thing that creates a paramset, stored in
a file called params.json, is called the Request Params API, primarily driven
by RequestParams.java, which is why the page is called that. The discrepancy
between the naming of the API and the thing it creates has
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
> On Feb 6, 2021, at 9:48 AM, Eric Pugh 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
Eric, based on what you wrote, your proposal makes sense to me.
CC'ing Noble who added this feature originally, I think.
~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley
On Sat, Feb 6, 2021 at 9:56 AM Eric Pugh
wrote:
> I was reading through the ref
I was reading through the ref guide page on Implicit Request Handlers [1] and
saw a mention of “paramsets”, which I think is a really powerful feature that
most people don’t know about.
I then wanted to learn more about paramsets, and tried to find it in the ref
guide.. I’d learned about
