Hi,
Please bear with me if I'm completely lost in the forest. I don't have
much experience with what's currently called "JSON Request API" or "JSON
Facet API" as I'm mostly working on software that uses the (legacy
legacy?) GET request query string API. Which brings me to the point I'd
like
>
> If we're going to push for the JSON-style request DSL as well, do we need
> to come up with a shiny new name for that as well, or will JSON Request DSL
> work? It's basically a HTTP post with JSON instead of
> 'application/x-www-form-urlencoded'...
JSON Request DSL (or just JSON Request
Trying to sum up this discussion.
I agree that V2-facet-api is not so good a name after all.
So we basically have two main suggestions in this thread then:
A) "The Faceting API" and then the need to re-brand "The legacy Faceting API"
B) "The Aggregation API" vs whatever we called it before
Do
+1 to "Aggregation API"!
On Fri, 10 Mar 2023 at 21:02, Michael Gibney
wrote:
> I kind of like "Aggregation API" (or something similar).
> Facets/stats/analytics are all definitely "aggregations". As luck
> would have it, "aggregation" isn't yet used to mean something more
> specific in Solr
I kind of like "Aggregation API" (or something similar).
Facets/stats/analytics are all definitely "aggregations". As luck
would have it, "aggregation" isn't yet used to mean something more
specific in Solr (right?), so we wouldn't have the problem of "it used
to mean X, but now it means Y". The
Would be cool if the admin ui query screen had a feature for showing the JSON
equivalent of current ui input fields. And of course a brand new auto
completing JSON editor for the new syntax!
Jan Høydahl
> 18. feb. 2023 kl. 14:11 skrev Eric Pugh :
>
> Change the Admin UI to support the new
Change the Admin UI to support the new syntax?So folks who are new to Solr
learn the new way of doing things…. ??
> On Feb 17, 2023, at 3:46 PM, David Smiley wrote:
>
> +1 to Ishan's proposal. Make it *the* Faceting API, and rebrand the old
> one to legacy or classic. The surface of the
+1 to Ishan's proposal. Make it *the* Faceting API, and rebrand the old
one to legacy or classic. The surface of the API might live on for
simple/trivial faceting; so maybe the word "classic" could be used if it
continues.
~ David Smiley
Apache Lucene/Solr Search Developer
Hello,
Naming is not my favorite thing to do at all.
But, if I check the guide I have:
complex or nested facets
Checking thesaurus gives me:
grained, ingrained, deep,dwelt, dwelled, tree-ish, branched, flexible
composite, compound, multiplex (multifacets? ), tangled, combined.
Does anything
I'd prefer the JSON faceting API to be called just Faceting API, and the
other one as Legacy Faceting API (and deprecated).
The moment we deprecate it, usecases will emerge where legacy faceting is
faster or more functional, and we can work on supporting those going
forward.
In deprecated state,
In general, I dislike the V2, V3, V when rebranding a method or
a service as it doesn't add any semantic value to the name, on the other
hand, Json-API hints it has to do with JSON payloads.
Given that, I am +1 in rebranding them, but I have no idea at the moment
for a better name than what it's
V2 shouldn't be overloaded then *that* is a problem. Can we just call the
new JAX-RS stuff V3 and then voila, we call this V3 faceting API?
~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley
On Thu, Feb 16, 2023 at 11:42 AM Houston Putman wrote:
>
Thanks for bringing this up!
I agree the name of the API is bad. The thing is it's not only faceting,
it's also stats/analytics.
Maybe the "aggregation API"? but I'm not sure that's any better...
I do think "v2" is an already overloaded term that comes with a lot of
baggage, so I would
Hi devs,
Although it's been nagging me for a while, today it hit me that the "JSON
request API" has a terrible name.
I hope to start a discussion on re-branding it and somehow pitch it as the
(not-so-new) "V2" search / facet API. Good timing as part of the other V2
efforts.
That may in turn
14 matches
Mail list logo
