[ 
https://issues.apache.org/jira/browse/SOLR-18179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eric Pugh updated SOLR-18179:
-----------------------------
    Description: Following up on this message in a dev list thread 
[https://lists.apache.org/thread/rcm372jwzmnmpjno9ygto82z8hptvkw1] about the 
names of things, I noticed that we bury our "These are what cluster types" are 
page deep in ref guide, not up front.  Yet choosing Cloud versus User Managed 
is a key decision right at the beginning, not a  "and we are going to prod" 
decision.  At least with todays split in the apis etc ;)  (was: Following up on 
this message in a dev list thread about the names of things, I noticed that we 
bury our "These are what cluster types" are page deep in ref guide, not up 
front.  Yet choosing Cloud versus User Managed is a key decision right at the 
beginning, not a  "and we are going to prod" decision.  At least with todays 
split in the apis etc ;))

> Update Concepts and Glossary Ref Guide pages around Cloud/Cluster concepts
> --------------------------------------------------------------------------
>
>                 Key: SOLR-18179
>                 URL: https://issues.apache.org/jira/browse/SOLR-18179
>             Project: Solr
>          Issue Type: Improvement
>          Components: documentation
>            Reporter: Eric Pugh
>            Priority: Minor
>
> Following up on this message in a dev list thread 
> [https://lists.apache.org/thread/rcm372jwzmnmpjno9ygto82z8hptvkw1] about the 
> names of things, I noticed that we bury our "These are what cluster types" 
> are page deep in ref guide, not up front.  Yet choosing Cloud versus User 
> Managed is a key decision right at the beginning, not a  "and we are going to 
> prod" decision.  At least with todays split in the apis etc ;)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to