Data Sources

WiredTiger provides access to data from a variety of sources. At the lowest level, data may be stored in a file using a tree structure. A relational schema supporting tables, indices and column groups is layered on top of file. Additional sources include LSM trees and statistics, and applications can further extend the supported types by implementing the WT_DATA_SOURCE interface.

Common operations on all data sources are performed using WT_CURSOR handles. See Cursor operations for a description of how to use cursors.

Builtin data sources

The following are the builtin basic cursor types:

URI	Type	Notes
table:<table name>[<projection>]	table cursor	table key, table value(s) with optional projection of columns
colgroup:<table name>:<column group name>	column group cursor	table key, column group value(s)
index:<table name>:<index name>[<projection>]	index cursor	key=index key, value=table value(s) with optional projection of columns

Some administrative tasks can be accomplished using the following special cursor types that give access to data managed by WiredTiger:

URI	Type	Notes
backup:	backup cursor	key=string, see Backups for details
log:	log cursor	key=(long fileID, long offset, int seqno), value=(uint64_t txnid, uint32_t rectype, uint32_t optype, uint32_t fileid, WT_ITEM key, WT_ITEM value), see Log cursors for details
metadata:	metadata cursor	key=string, value=string, see Reading WiredTiger Metadata for details
statistics:[<data source URI>]	database or data source statistics cursor	key=int id, value=(string description, string value, uint64_t value), see Statistics Data for details

Advanced applications may also open the following low-level cursor types:

URI	Type	Notes
file:<file name>	file cursor	file key, file value(s)
lsm:<name>	LSM cursor (key=LSM key, value=LSM value)	LSM key, LSM value, see Log-Structured Merge Trees

Raw Files

WiredTiger's schema layer can be bypassed by opening cursors with a "file:" URI, using the name of the underlying file. This can be useful for seeing the contents of a column group or index without reading all of the columns from the table.

For example, if an index becomes inconsistent with its primary, a file cursor can read from the index without errors (even though some of the keys that are returned may not exist in the primary).

Table Index data

When an index is created for a table, records are inserted into the index whenever the table is updated. These records use a different key to the primary table, as specified when the index is created with the WT_SESSION::create method.

A cursor opened on an index has the specified index columns as its key, accessed by WT_CURSOR::set_key and WT_CURSOR::get_key. The value columns default to returning the value columns from the table, but this can be overridden by configuring a projection cursor (see Projections), which can access the table key columns or a subset of the value columns.

Statistics Data

Statistics cursors can be used to retrieve run-time statistics about a WiredTiger database as well as statistics for individual data sources. The statistics are at two levels: per-database and per-individual data source. Database-wide statistics are retrieved with the "statistics:" URI; individual data source statistics are available by specifying "statistics:<data source URI>".

The statistic key is an integer from the list of keys in Statistics Keys. Statistics cursors return three values from the WT_CURSOR::get_value call: a printable description of the statistic, a printable version of the entry's value, and the entry's unsigned 64-bit integral value, respectively.

The following is an example of printing run-time statistics about the WiredTiger engine:

        if ((ret = session->open_cursor(session,
            "statistics:", NULL, NULL, &cursor)) != 0)
                return (ret);

        ret = print_cursor(cursor);
        ret = cursor->close(cursor);

The following is an example of printing statistics about a table:

        if ((ret = session->open_cursor(session,
            "statistics:table:access", NULL, NULL, &cursor)) != 0)
                return (ret);

        ret = print_cursor(cursor);
        ret = cursor->close(cursor);

Both examples can use a common display routine that iterates through the statistics until the cursor returns the end of the list.

int
print_cursor(WT_CURSOR *cursor)
{
        const char *desc, *pvalue;
        uint64_t value;
        int ret;

        while ((ret = cursor->next(cursor)) == 0 &&
            (ret = cursor->get_value(cursor, &desc, &pvalue, &value)) == 0)
                if (value != 0)
                        printf("%s=%s\n", desc, pvalue);

        return (ret == WT_NOTFOUND ? 0 : ret);
}

Individual statistics values can be retrieved by searching for the corresponding key, as shown in the following example:

        WT_CURSOR *cursor;
        const char *desc, *pvalue;
        uint64_t value;
        int ret;

        if ((ret = session->open_cursor(session,
            "statistics:table:access", NULL, NULL, &cursor)) != 0)
                return (ret);

        cursor->set_key(cursor, WT_STAT_DSRC_BTREE_OVERFLOW);
        ret = cursor->search(cursor);
        ret = cursor->get_value(cursor, &desc, &pvalue, &value);
        printf("%s=%s\n", desc, pvalue);

        ret = cursor->close(cursor);

See Performance monitoring with statistics for more examples of how statistics can be used.