@triply/triplydb
    Preparing search index...

    Interface ServiceMetadata

    interface ServiceMetadata {
        capabilities: Capability[];
        config?: ServiceConfig;
        createdAt: string;
        endpoint?: string;
        error?: ErrorResponse;
        id: string;
        loadedAt?: string;
        name: string;
        numberOfGraphErrors?: number;
        numberOfGraphs?: number;
        numberOfLoadedGraphs?: number;
        numberOfLoadedStatements?: number;
        outOfSync?: boolean;
        status: ServiceStatus;
        timeoutInMs?: number;
        type: ServiceType;
        version: string;
    }
    Index
    capabilities config? createdAt endpoint? error? id loadedAt? name numberOfGraphErrors? numberOfGraphs? numberOfLoadedGraphs? numberOfLoadedStatements? outOfSync? status timeoutInMs? type version
    capabilities: Capability[]

    What this service can answer — SPARQL, the SPARQL API, Elasticsearch.

    config?: ServiceConfig

    Type-specific settings, such as an Elasticsearch index template.

    createdAt: string

    When the service was created.

    endpoint?: string

    URL to send queries to. Absent until the service is running.

    error?: ErrorResponse

    Present when the service failed, describing why.

    id: string

    Stable identifier, unchanged when the service is renamed.

    loadedAt?: string

    When the service last finished loading the dataset.

    name: string

    Short name, unique within the dataset and part of the service's URL.

    numberOfGraphErrors?: number

    Graphs that failed to load; a service can run while some of its graphs are missing.

    numberOfGraphs?: number

    Graphs the service is meant to hold once it has finished loading.

    numberOfLoadedGraphs?: number

    Graphs loaded so far, against numberOfGraphs.

    numberOfLoadedStatements?: number

    Statements the service holds, which lags the dataset's count while it is still loading.

    outOfSync?: boolean

    Whether the dataset has changed since this service loaded it.

    An out-of-sync service keeps answering queries from the older data, so a query can succeed and still be stale.

    status: ServiceStatus

    Where the service has got to — see ServiceStatus.

    timeoutInMs?: number

    How long a query may run before the service cuts it off.

    type: ServiceType

    Which kind of store backs this service — see ServiceType.

    version: string

    Version of the underlying store, which decides what the service can do.

    Settings

    On This Page
    Properties