[
https://issues.apache.org/jira/browse/SOLR-16603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17655120#comment-17655120
]
Shawn Heisey commented on SOLR-16603:
-------------------------------------
The reason we don't recommend using it in production is because of its
limitations due to the fact that there is no HTTP access. So I would never use
it for anything mission-critical. But if you need it for something else where
if it happens to be down you can just start or restart it, it would be a great
fit.
> Create a public constructor for SolrCore
> ----------------------------------------
>
> Key: SOLR-16603
> URL: https://issues.apache.org/jira/browse/SOLR-16603
> Project: Solr
> Issue Type: Wish
> Security Level: Public(Default Security Level. Issues are Public)
> Components: clients - java
> Reporter: Jeb Nix
> Priority: Minor
> Attachments: NoHtmlUpdateProcessorFactory.java
>
>
> This will enable to use Solr's search with update processors and search
> components, without the need to deploy an actual Solr instance - e.g. Solr on
> the RAM of the Java application. This would be super useful to me for making
> external APIs that will support Solr, outside of the cluster. Lucene ain't
> good enough because of the configurations that I have on Solr.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
