You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (JIRA)" <ji...@apache.org> on 2017/12/01 19:10:01 UTC
[jira] [Resolved] (JENA-1441) jena-text tracing for development
[ https://issues.apache.org/jira/browse/JENA-1441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andy Seaborne resolved JENA-1441.
---------------------------------
Resolution: Done
Fix Version/s: Jena 3.6.0
> 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
> Assignee: Andy Seaborne
> Priority: Trivial
> Fix For: Jena 3.6.0
>
>
> 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)