[
https://issues.apache.org/jira/browse/DERBY-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13242320#comment-13242320
]
Kristian Waagan commented on DERBY-5083:
----------------------------------------
Thanks, Kim.
There is an inconsistency regarding the value of indexStats.trace for not
tracing anything. The source mentions both "none" and "off", but the latter
seems to be the dominant one. I corrected the comment in revision 1307392, and
I also removed two TODOs.
Tracing and logging is completely separate, yes.
The changes look good to me, +1 to commit.
There is one trick that may be useful in rare cases, since the properties are
static, and that is to generate a stack trace and look for the daemon thread to
determine if the daemon is active or not. I don't think it belongs in the docs
- hopefully people will find this comment instead ;)
> Document automatic update and creation of index cardinality statistics (istat)
> ------------------------------------------------------------------------------
>
> Key: DERBY-5083
> URL: https://issues.apache.org/jira/browse/DERBY-5083
> Project: Derby
> Issue Type: Task
> Components: Documentation
> Affects Versions: 10.8.1.2
> Reporter: Kim Haase
> Assignee: Kim Haase
> Attachments: DERBY-5083.diff, DERBY-5083.stat, DERBY-5083.zip
>
>
> Documentation is needed for the automatic index statistics feature
> (DERBY-4934). It appears that a change is needed to the Tuning Guide topic
> "When cardinality statistics are automatically updated", at least.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
