[
https://issues.apache.org/jira/browse/SOLR-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627580#action_12627580
]
Hoss Man commented on SOLR-713:
-------------------------------
i guess the distinction i was trying to draw is between the Solr administrator
configuring a max on how much he cares about see logged when the values for any
param name get really long, vs a RequestHandler specifying what param names
don't need to be logged because they aren't particularly useful for debugging.
If in the later case it makes sense to have the list of fields configured in
solrconfig.xml, then it should be as part of that RequestHandler's config.
(the wazbat param for one handler isn't necessarily the same as the wazbat
param for another handler, and you might care about logging the id params for
one instance of SearchHandler, but not for others)
> Differentiated request logging
> ------------------------------
>
> Key: SOLR-713
> URL: https://issues.apache.org/jira/browse/SOLR-713
> Project: Solr
> Issue Type: Improvement
> Components: search
> Affects Versions: 1.3
> Reporter: Lars Kotthoff
> Priority: Minor
> Attachments: SOLR-713.patch
>
>
> Currently the complete query string is logged for all search requests. When
> the query string is large, the logs tend to become hard to read. Worse, when
> using a sharded setup and faceting the query string during the facet count
> refine phase contains the IDs of all documents for which facet counts are
> requested, easily amounting to several GB of logs over the course of a day
> when the number of facets is large.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
