IndexStatisticsDaemonImpl
public interface IndexStatisticsDaemon
There are two modes of operation:
The modes differ in how the operation affects other operations in the running system, and also how errors are dealt with. The background mode will try to affect other operations as little as possible, and errors won't be reported unless they are severe. The explicit mode will do more to make sure the operation succeeds (for instance by using locks), and will report all errors.
Modifier and Type | Method | Description |
---|---|---|
void |
runExplicitly(LanguageConnectionContext lcc,
TableDescriptor td,
ConglomerateDescriptor[] cds,
java.lang.String runContext) |
Creates/updates index statistics for the specified conglomerates/indexes.
|
void |
schedule(TableDescriptor td) |
Schedules creation/update of the index statistics associated with the
specified table.
|
void |
stop() |
Stops the background daemon.
|
void runExplicitly(LanguageConnectionContext lcc, TableDescriptor td, ConglomerateDescriptor[] cds, java.lang.String runContext) throws StandardException
lcc
- connection used to carry out the worktd
- base tablecds
- index conglomerates (non-index conglomerates are ignored)runContext
- descriptive text for the context in which the work is
being run (i.e. ALTER TABLE)StandardException
- if something goes wrongvoid schedule(TableDescriptor td)
Note that the scheduling request may be denied. Typical situations where that will happen is if the work queue is full, or if work has already been scheduled for the specified table.
td
- base tablevoid stop()
Any ongoing tasks will be aborted as soon as possible, and it will not be possible to schedule new tasks. Note that runExplicitly can still be used.
Apache Derby V10.14 Internals - Copyright © 2004,2018 The Apache Software Foundation. All Rights Reserved.