[ 
https://issues.apache.org/jira/browse/SOLR-18179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18076001#comment-18076001
 ] 

ASF subversion and git services commented on SOLR-18179:
--------------------------------------------------------

Commit 79e18af99325377e025e48ba84ee5dd5bd3cff41 in solr's branch 
refs/heads/branch_10x from Eric Pugh
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=79e18af9932 ]

SOLR-18179: Better highlight and expand upon our Cluster concepts in the Ref 
Guide (#4246)

Co-authored-by: copilot-swe-agent[bot] 
<[email protected]>
Co-authored-by: epugh <[email protected]>

> 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
>              Labels: pull-request-available
>          Time Spent: 3h 50m
>  Remaining Estimate: 0h
>
> 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 PR is to work on getting consistency of terms across the Ref Guide.  
> Bonus points if it helps with consistency in both the new Solr UI, and maybe 
> in the old Solr Admin.
> Less concerned about any naming ramifications in source code...



--
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