[
https://issues.apache.org/jira/browse/SOLR-6919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303525#comment-14303525
]
Mark Miller commented on SOLR-6919:
-----------------------------------
I don't mean to use it's implementation. Just that it's kind of a special
logging object and we could make this the same.
AFAIK, you can just make a special logger name for this that controls it - like
org.apache.solr.queryprelog=DEBUG or whatever.
bq. How about we just create a child logger and use that?
Looking at the patch, yeah, that's what I meant. I don't know what the right
name is, but I think that's right implementation path.
> 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,
> 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: [email protected]
For additional commands, e-mail: [email protected]
