[
https://issues.apache.org/jira/browse/SOLR-6919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14302354#comment-14302354
]
Gregory Chanan commented on SOLR-6919:
--------------------------------------
bq. We might want to consider making this a special log object like Lucene's
IndexWriter Info Logger. Having to turn on DEBUG for the whole SolrCore class
means it's fairly likely that you could inadvertently add a lot of debug
chatter in the logs in the future when you really just want to turn on logging
the query before it's executed.
Seems reasonable, do you have a pointer to the Lucene IndexWriter Info Logger?
FWIW, I only see one other debug statement in SolrCore trunk, and it's in an
unexpected situation. So I don't think this is high priority.
> Log REST info before executing
> ------------------------------
>
> Key: SOLR-6919
> URL: https://issues.apache.org/jira/browse/SOLR-6919
> Project: Solr
> Issue Type: Improvement
> Components: search
> Reporter: Mike Drob
> Assignee: Gregory Chanan
> Priority: Minor
> Fix For: Trunk, 5.1
>
> Attachments: SOLR-6919.patch, SOLR-6919.patch, SOLR-6919.patch
>
>
> We should log request info (path, parameters, etc...) before attempting to
> execute a query. This is helpful in cases where we get a bad query that
> causes OOM or something else catastrophic, and are doing post-event triage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
