ReadonlynameReadonlylibraryReturns a small facade over the underlying HTTP transport for
operations not wrapped here - there is no native driver client to
expose, since this store talks to TigerGraph over plain fetch.
Run an installed GSQL query: GET /query/{graph}/{queryName}?param=value
(simple/scalar params) or POST /query/{graph}/{queryName} with a JSON
body (complex params, e.g. sets/vertex lists). Confirmed endpoint
shape and response envelope ({version, error, message, results}).
POST /graph/{graph} - raw upsert matching TigerGraph's documented
wire format exactly (attribute values pre-wrapped as {value: x}).
Prefer upsertVertex/upsertVertices/upsertEdge/upsertEdges for
the common case of plain attribute values.
Upsert a single vertex with plain (unwrapped) attribute values.
Optionalgraph: stringUpsert multiple vertices of the same type in one round trip.
Optionalgraph: stringUpsert a single edge with plain (unwrapped) attribute values.
Optionalgraph: stringUpsert multiple edges (possibly spanning different types/vertices) in one round trip.
Optionalgraph: stringGET /graph/{graph}/vertices/{type}/{id} - fetch a single vertex by
ID. Confirmed endpoint/response shape. Returns null if the vertex
does not exist (TigerGraph reports this as error: true with a
"does not exist" message rather than an empty result set).
Optionalgraph: stringGET /graph/{graph}/vertices/{type} - list vertices of a type
(omitting the ID segment of the single-vertex endpoint above).
TigerGraph's built-in-endpoints documentation confirms the
single-vertex form; the list form (same resource without an ID, plus
an optional limit query parameter) follows the standard REST++
collection-resource pattern but its full parameter set (filter,
select, sort, etc.) was not independently re-verified while
building this store - only limit is wired up here (see README).
DELETE /graph/{graph}/vertices/{type}/{id} - delete a single vertex (and its incident edges). Returns the number of vertices deleted (0 or 1).
Optionalgraph: stringGET /graph/{graph}/edges/{fromType}/{fromId}/{edgeType}/{toType}/{toId}
Optionalgraph: stringGET /graph/{graph}/edges/{fromType}/{fromId}[/{edgeType}] - list all
edges (of the given type, if provided) originating from a vertex.
Same confidence note as getEdge()'s partial-path collection form.
OptionaledgeType: stringOptionalgraph: stringDELETE /graph/{graph}/edges/{fromType}/{fromId}/{edgeType}/{toType}/{toId} - delete a single edge. Returns the number of edges deleted.
Optionalgraph: stringPOST /gsql/v1/queries/interpret - compile and run a GSQL query
string on the fly, without installing it first. Confirmed endpoint,
auth (HTTP Basic, not the REST++ bearer token), and request shape:
the request body is the raw GSQL text (Content-Type: text/plain),
and GSQL query parameters are passed as URL query-string parameters.
The older path /gsqlserver/interpreted_query (used by some
pre-4.x deployments) is documented only in community sources, not in
TigerGraph's current official docs, and its exact request shape was
not independently confirmed - this store intentionally does not
implement that alias rather than guess at its shape. If you're on a
version that needs it, issue the request yourself via
getClient().restRequest()/gsqlRequest() (or plain fetch) once
you've confirmed the shape against your deployment.
GET /gsql/v1/schema/vertices?graph={graph} - list the graph's vertex types. Confirmed endpoint/response shape.
Optionalgraph: stringGET /gsql/v1/schema/edges?graph={graph} - list the graph's edge types. Confirmed endpoint/response shape.
Optionalgraph: string
TigerGraphStorewraps TigerGraph's REST++ and GSQL-server HTTP APIs behind a typed, promise-based interface: token-based auth, installed (pre-compiled GSQL) query execution, vertex/edge upsert and retrieval, ad-hoc interpreted queries, and vertex/edge-type schema introspection.