[
https://issues.apache.org/jira/browse/JENA-691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13995048#comment-13995048
]
Andy Seaborne edited comment on JENA-691 at 5/12/14 1:00 PM:
-------------------------------------------------------------
What I am finding is that (and this is crossing the external/debug boundary but
in a complicated system the boundary is not clear cut to me) I want to turn
specific parts on and off, and the simple info/fine is too crude. At least,
there need to be more levels but, due to verbosity, it's nice to select output
of specific parts of the system. The local/remote case would be useful even
currently, or TDB vs in-memory (because various things use SPARQL on in-memory
datasets themselves internally).
At the moment, {{Explain}} messages go to an SLF4J logger at level info. There
is one logger for all {{Explain}}. Several loggers would be possible (with
some hackery because the messages are multi-line). Even so, an API to simply
manage this from within running code would be good. Use of SLF4J can be the
implementation.
was (Author: andy.seaborne):
What I am finding is that (and this is crossing the external/debug boundary but
in a complicated system the boundary is not clear cut to me) I want to turn
specific parts on and off, and the simple info/fine is too crude. At least,
there need to be more levels but, due to verbosity, it's nice to select output
of specific parts of the system. The local/remote case would be useful even
currently, or TDB vs in-memory (because various things use SPARQL on in-memory
datasets themselves internally).
At the moment, {{Explain}} messages go to an SLF4J logger at level info. There
is one logger for all {{Explain}}. Several loggers would be possible (with
some hackery because the messages are multi-line). Even so, an API to simple
manage this from within running code would be good. Use of SLF4J can be the
implementation.
> "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)
