gerlowskija merged PR #1978:
URL: https://github.com/apache/solr/pull/1978
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@solr.apach
gerlowskija commented on PR #1978:
URL: https://github.com/apache/solr/pull/1978#issuecomment-1757673021
I think I'll go with "store" as the term for now. I kindof agree with Eric
that "resource" is maybe too generic? It's also an overloaded term, as
JAX-RS/Jersey calls API classes "resou
epugh commented on PR #1978:
URL: https://github.com/apache/solr/pull/1978#issuecomment-1749247433
These API's are all experimental and new, so introducing
`/collection/standalone/` into the "sorta classic" core urls is actually
allowed ;-). And think about it helping folks in the future
epugh commented on PR #1978:
URL: https://github.com/apache/solr/pull/1978#issuecomment-1749244086
I think in the balance, I'm leaning to towards "store", because resources
could mean many thing... "dataStoreType" and "dataStoreName" ?
Or, we could just rip the bandaid off and ge
HoustonPutman commented on PR #1978:
URL: https://github.com/apache/solr/pull/1978#issuecomment-1749182940
I'm also cool with resourceType and resourceName, but store is cool too.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHu
gerlowskija commented on PR #1978:
URL: https://github.com/apache/solr/pull/1978#issuecomment-1749083088
Haha, someone's enjoying their LLM's this morning 😛
"Store" is a tad generic for my tastes, but I like it better than "index" I
think? We would have "store type" (which could eit
epugh commented on PR #1978:
URL: https://github.com/apache/solr/pull/1978#issuecomment-1747659213
Index: An index is a common term used in information retrieval systems
to represent a structured collection of data for efficient searching and
retrieval. It implies a storage stru
epugh commented on PR #1978:
URL: https://github.com/apache/solr/pull/1978#issuecomment-1747647485
^ above was generated ;-). I never write like that. I think I like
anything BUT "index" because I think that is an overloaded term that has
specific meaning the closer to disk you get.. A C
epugh commented on PR #1978:
URL: https://github.com/apache/solr/pull/1978#issuecomment-1747642810
You know, if you want a single term in place of "core" and "collection" in
Apache Solr's RESTful URLs, here are some potential terms you could consider:
Index
Repository
epugh commented on PR #1978:
URL: https://github.com/apache/solr/pull/1978#issuecomment-1747488065
`corllection` ? Or, could we use the word `collection` everywhere, and
then just under the covers, if it's a Core then do something smart?Or, do
we need actually seperate routes? Would
gerlowskija commented on PR #1978:
URL: https://github.com/apache/solr/pull/1978#issuecomment-1747451445
❗ ❗ **Naming Emergency** ❗ ❗
Many v2 APIs are currently offered at two paths based on whether a user is
providing a core or a collection name. For example, schema APIs are availa
gerlowskija opened a new pull request, #1978:
URL: https://github.com/apache/solr/pull/1978
https://issues.apache.org/jira/browse/SOLR-16825
# Description
[SOLR-16825](https://issues.apache.org/jira/browse/SOLR-16825) added a new
gradle module, 'api', which holds v2 API definit
12 matches
Mail list logo
