[
https://issues.apache.org/jira/browse/DERBY-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13241319#comment-13241319
]
Kim Haase commented on DERBY-5083:
----------------------------------
Thanks, Kristian, for the info about the properties.
I was looking in
java/engine/org/apache/derby/impl/sql/catalog/DataDictionaryImpl.java, and it
suggests that the default for derby.storage.indexStats.trace is "off" rather
than "none" -- is that correct? It also has a comment saying "// TODO: This
property may go away in production code." I gather that has not happened.
Also, are tracing and logging completely separate? That is, can you set
derby.storage.indexStats.trace if derby.storage.indexStats.log is not set to
true? The code implies that you can, but I thought I'd better check.
> 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
>
> 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
