[
https://issues.apache.org/jira/browse/SOLR-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492522
]
Brian Whitman commented on SOLR-212:
------------------------------------
Since the main use case of SOLR-212 is to embed it in client applications, we
should be careful about logging. As of now SOLR-212 will spit stuff all over
stderr.
I suggest putting this
System.setProperty("java.util.logging.config.file",
instanceDir+"/conf/logging.properties");
near line 79 of DirectSolrConnection.java. That way, if a developer/user
chooses, they can put a logging.prop file in conf and set direct logging of
Solr requests either to their own application logs or a file. If the
conf/logging.properties file does not exist, I believe the default
logging.properties will be used (which is what happens now.)
> 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
> Priority: Minor
> Attachments: 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.
