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 get rid of `/core/` ;-).
What if we had `/collection/{collectionName}/core/{coreName}` for cores?
I.e, if we can't come up with a great solution to the naming problem, let's
just change the problem statement to avoid a crummy answer... In SolrCloud,
why would I ever go direct to a core? I would always navigate through a
collection.. Heck, maybe it gives nicer answers. And, maybe in the future I
could get data about a core regardless of which physical node I'm talking to.
In legacy old should be retired and never spoken of again Solr, you just do
/collection/standalone/core/{coreName}. <--- I'm liking this more...
--
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.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
