[
https://issues.apache.org/jira/browse/SOLR-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493466
]
J.J. Larrea commented on SOLR-212:
----------------------------------
One issue which comes up both DirectSolrConnection.java and the
http://wiki.apache.org/solr/EmbeddedSolr technique (which I have started using
for a custom indexer) is that the SolrCore constructor will always create an
initial searcher, and doing so will execute any warming SolrEventListeners
defined in the config, whether or not the application needs it. Besides
delaying startup and wasting cycles, it can cause the allocation of significant
amounts of memory for sort FieldCaches, Solr caches, and the like, none of
which will be used for a non-search application. And
Other than maintaining 2 sets of config files differening only in whether
warmup queries are defined, does anyone have any ideas for how warmup can be
selectively enabled based on the calling context?
> Embeddable class to call solr directly
> --------------------------------------
>
> Key: SOLR-212
> URL: https://issues.apache.org/jira/browse/SOLR-212
> Project: Solr
> Issue Type: Improvement
> Reporter: Ryan McKinley
> Assigned To: Ryan McKinley
> Priority: Minor
> Fix For: 1.2
>
> Attachments: embeddedSolr.zip, SOLR-212-DirectSolrConnection.patch,
> SOLR-212-DirectSolrConnection.patch, SOLR-212-DirectSolrConnection.patch,
> SOLR-212-DirectSolrConnection.patch, SOLR-212-DirectSolrConnection.patch
>
>
> For some embedded applications, it is useful to call solr without running an
> HTTP server. This class mimics the behavior you would get if you sent the
> request through an HTTP connection. It is designed to work nicely (ie
> simple) with JNI
> the main function is:
> public class DirectSolrConnection
> {
> String request( String pathAndParams, String body ) throws Exception
> {
> ...
> }
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
