TigerGraph provider

Nodal.TigerGraph accepts an externally managed HttpClient. This keeps connection pooling, handler lifetime, proxies, and resilience policies under host control.

var provider = new TigerGraphProvider(
    httpClient,
    new TigerGraphOptions
    {
        Endpoint = new Uri("https://example.i.tgcloud.io/"),
        AccessToken = "secret-token"
    },
    graphName: "SocialGraph");

Fixed traversals use stable GSQL Syntax V1 paths. Repeated-hop queries switch to Syntax V2 only when required. Atomic upserts use REST++; delete-containing plans use deterministic installed GSQL mutation queries.

Schema migrations and query installation require an ITigerGraphAdministrativeTransport. Self-managed deployments may use TigerGraphGsqlProcessTransport; managed environments can supply a transport suited to their control plane.

Analytics use explicitly configured installed GSQL queries. TigerGraphOptions.AnalyticsQueries maps each available GraphAnalyticsAlgorithm to its installed query name. This makes the capability set truthful across TigerGraph editions and deployments instead of assuming that every algorithm library has been installed.

Installed queries are unweighted by default. Add an algorithm to WeightedAnalyticsAlgorithms only when that query's declared parameters accept nodal_weight_property. The current live QA baseline is TigerGraph 4.2.4 Community; broader server-version compatibility is not yet a Nodal promise.