[
https://issues.apache.org/jira/browse/JENA-691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13994924#comment-13994924
]
Rob Vesse commented on JENA-691:
--------------------------------
One possibility would simply to switch the internals of explanation printing to
use sl4j (if they don't already) and simply have callers to the explain
machinery provide a logging level parameter (or call specific overloads e.g.
{{Explain.info()}} vs {{Explain.debug()}} thus using the standard logging
levels people are used to.
Log messages would then (presumably) originate out of a single central
{{Explain}} class and users could specify their logging configuration for this
separately from other logging configuration to have this turned up/down as
desired.
Queries would probably be {{INFO}} level, algebra information as {{DEBUG}}
level, execution as {{DEBUG}} level, remote requests at {{INFO}}/{{DEBUG}}
(with {{WARN}} for execution errors when {{SILENT}} is specified)
> "Explain" Categories
> --------------------
>
> Key: JENA-691
> URL: https://issues.apache.org/jira/browse/JENA-691
> Project: Apache Jena
> Issue Type: Improvement
> Reporter: Andy Seaborne
>
> "Explain" capabilities in ARQ are provided like logging levels with levels
> ALL, INFO, FINE and NONE. For example, Algebra is printed at level FINE but
> that implies level INFO, which includes queries.
> Instead, categories would be better so that a "mix and match" of various
> explanations could be set to give a more focused output.
> This JIRA is for collecting suggestions, requests and contributions for a
> more extensive "Explain" capability.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
