Structsยง
- Create
Alter ๐Table Result - Result of
create_or_alter_tables_on_demand. - Flow
Mirror ๐Task - Inserter
- Instant
AndNormal Insert Requests - Split insert requests into normal and instant requests.
Enumsยง
- Auto
Create Table Type - Hint for the table type to create automatically.
Constantsยง
- SPLUNK_
PK_ METADATA_ ORDER_ KEY QueryContextextension key the Splunk HEC handler sets (to"true") on its identity path to request metadata-first primary-key ordering at table creation. It is absent for user-supplied pipelines, so their primary-key order is left untouched.
Functionsยง
- admit_
row_ insert_ batches - Admits all database totals before dispatching any batch of a finite request. Each batch keeps its own protocol options and target database.
- admit_
write - Admits a finite request before it is split into internal writes. The returned context preserves accounting while preventing a second row debit.
- apply_
per_ table_ semantic_ options - Folds the semantic keys of the table being created into
table_options. - build_
create_ table_ expr - count_
insert_ ๐rows - fill_
table_ options_ for_ create - Fill table options for a new table by create type.
- parse_
per_ table_ semantic_ index - Parses the per-table semantic index off the context extension. Call once per
create-planning round: a first write creating N tables would otherwise
re-parse the whole index N times.
Nonewhen the request carries no index (logs, traces, Prom RW v1) or it fails to parse. - reorder_
splunk_ ๐primary_ keys - Moves Splunkโs metadata tags (
host,source,sourcetype) to the front of the primary key, keeping the relative order of the remaining tags. - request_
is_ ๐native_ histogram - table_
is_ ๐native_ histogram - validate_
column_ ๐count_ match - validate_
trace_ table_ model - Rejects writes from a different built-in trace model before schema mutation. Unstamped, explicitly created tables remain subject to normal schema validation.
Type Aliasesยง
- Inserter
Ref - PerTable
Semantic Index - The parsed per-table semantic index:
{schema -> {table -> {key -> value}}}, produced by the OTLP metrics encode path (where one metric can fan out into several tables with distinct keys) and the Prometheus remote write v2 path (where per-series metadata declares type/unit, and a series may override its target schema).