[jira] [Comment Edited] (SOLR-16295) Modernize and Standardize Solr description across all platforms

["Gus Heck (Jira)" <ji...@apache.org>]

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

Gus Heck edited comment on SOLR-16295 at 8/20/22 3:48 PM:
----------------------------------------------------------

To me "platform" without "server" qualifier would involve us having a production ready system for getting arbitrary documents/data in as well as out. Right now, we have great features for serving, and several ways to input data in a formats that only very very rarely are 1:1 with the user's native format unless they designed the upstream system with Solr in mind. Thus users have very little to do to get results out, but a lot of work to do to get documents in. DIH and SolrCell were in the platform direction but we regularly identify these as not supported, not production ready or not good for non-trivial use cases.

If you're ambitious, come poke at JesterJ and tell me what's good/bad about it. (or fix stuff). ;) if it became popular on it's own I'd have no issue with it being a related project or even donating it to the project (though I see that as an unlikely path due to small code overlap). Back in the very early days I called it "SolrSystem" (which would have run afoul of trademarks) with the idea of it being a one-touch install that provided document ingestion, and search serving in a tomcat container (back when we were a .war file). I've narrowed the scope to document ingestion since then, and recognize the need to have ingestion on separate hardware for non-trivial use cases of course, but the lack of a good, standard solution to put arbitrary documents into solr is something I've felt for almost a decade now. 

Anyway just my 0.02... I certainly won't object further whichever way this naming goes.


was (Author: gus_heck):
To me "platform" without "server" qualifier would involve us having a production ready system for getting arbitrary documents/data in as well as out. Right now, we have great features for serving, and several ways to input data in a formats that only very very rarely are 1:1 with the user's native format unless they designed the upstream system with Solr in mind. Thus users have very little to do to get results out, but a lot of work to do to get documents in. DIH and SolrCell were in the platform direction but we regularly 

If you're ambitious, come poke at JesterJ and tell me what's good/bad about it. (or fix stuff). ;) if it became popular on it's own I'd have no issue with it being a related project or even donating it to the project (though I see that as an unlikely path due to small code overlap). Back in the very early days I called it "SolrSystem" (which would have run afoul of trademarks) with the idea of it being a one-touch install that provided document ingestion, and search serving in a tomcat container (back when we were a .war file). I've narrowed the scope to document ingestion since then, and recognize the need to have ingestion on separate hardware for non-trivial use cases of course, but the lack of a good, standard solution to put arbitrary documents into solr is something I've felt for almost a decade now. 

Anyway just my 0.02... I certainly won't object further whichever way this naming goes.

> Modernize and Standardize Solr description across all platforms
> ---------------------------------------------------------------
>
>                 Key: SOLR-16295
>                 URL: https://issues.apache.org/jira/browse/SOLR-16295
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: documentation
>            Reporter: Houston Putman
>            Assignee: Eric Pugh
>            Priority: Major
>
> Currently everywhere we have a page on "Solr", we have a short description on what the project/product is. They are all roughly the same, but we should try to improve this language and standardize it everywhere.
> The places I can think of currently are:
> * [solr.apache.org|https://solr.apache.org/]
> * [Ref Guide|https://solr.apache.org/guide/solr/latest/]
> * [Github - Solr|https://github.com/apache/solr]
> * [DockerHub - Solr|https://hub.docker.com/_/solr]
> * [ArtifactHub - Solr|https://artifacthub.io/packages/helm/apache-solr/solr]
> The Solr Operator pages don't really give a Solr description, which is fine.
> Please comment if I forgot any, so that we can have a comprehensive list.
> Once we agree on the standardized language, we can then update it everywhere it needs to go (since the above list are managed in a variety of places).



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org