[
https://issues.apache.org/jira/browse/JENA-1441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16272435#comment-16272435
]
ASF GitHub Bot commented on JENA-1441:
--------------------------------------
Github user afs commented on the issue:
https://github.com/apache/jena/pull/318
FYI: On a PR branch, you can do all sorts of git stuff on your local repo
like reset to remove a commit, rebasing, and squashing. Then do a force push
to your PR branch at GH and it will all appear here with the updated state. GH
even tracks revisions and hides comments no longer relevant. (Use all this
with care!)
> jena-text tracing for development
> ---------------------------------
>
> Key: JENA-1441
> URL: https://issues.apache.org/jira/browse/JENA-1441
> Project: Apache Jena
> Issue Type: New Feature
> Components: Jena
> Affects Versions: Jena 3.6.0
> Reporter: Code Ferret
> Priority: Trivial
>
> This issue is for the addition of some log4j tracing and a configuration item
> associated with development in jena-text. The tracing is in TextQueryPF and
> TextIndexLucene to track calls to exec and the subsequent processing as well
> as the add, update and delete of Lucene documents.
> The _trace-level_ is used so as to not interfere with the current
> _debug-level_ items that are familiar to developers.
> The configuration item {{text:cacheQueries false ;}} on
> {{text:TextIndexLucene}} allows to bypass use of the {{queryCache}} in
> TextQueryPF.query(...) during development. This configuration item is not for
> general use and need not be documented further.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
