[
https://issues.apache.org/jira/browse/SOLR-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510550
]
Yonik Seeley commented on SOLR-267:
-----------------------------------
The double logging issue with the new update handler framework should be fixed
with whatever mechanism is created here.
Using the responseHeader as logging info is clever, but I'm not sure if we want
to be bound to return everything in the response that we want to be logged (for
updates, some may want all of the ids logged but not returned, and if they are
returned, not in the header).
So, what about either a "NamedList toLog;"on the SolrQueryResponse, or
SolrQueryRequest.getContext().get("log") => NamedList ?
> new patch to promote responseHeader from a defacto standard to an api
> standard in SolrQueryResponse.
I think that's probably OK
> log handler + query + hits
> --------------------------
>
> Key: SOLR-267
> URL: https://issues.apache.org/jira/browse/SOLR-267
> Project: Solr
> Issue Type: Improvement
> Components: search
> Affects Versions: 1.3
> Reporter: Will Johnson
> Priority: Minor
> Fix For: 1.3
>
> Attachments: LogQueryHitCounts.patch, LogQueryHitCounts.patch,
> LogQueryHitCounts.patch, LogQueryHitCounts.patch, LogQueryHitCounts.patch,
> LogQueryHitCounts.patch
>
>
> adds a logger to log handler, query string and hit counts for each query
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
