@honua/sdk-js
    Preparing search index...

    Type Alias QueryPlanRepresentationReasonExperimental

    QueryPlanRepresentationReason:
        | "explicit-pin"
        | "workload-above-threshold"
        | "workload-below-threshold"
        | "estimate-unavailable"
        | "protocol-not-columnar"
        | "encoding-not-columnar"
        | "aggregation-not-columnar"
        | "geometry-not-requested"

    Why the planner selected the representation it did. Every value is a deterministic function of declared source metadata plus QueryPlanningEstimates — never of result data.

    Type Declaration

    • "explicit-pin"

      The caller pinned the representation explicitly and the source can serve it.

    • "workload-above-threshold"

      Columnar is available and the caller's estimate reaches the columnar threshold.

    • "workload-below-threshold"

      Columnar is available but the estimated workload does not justify it.

    • "estimate-unavailable"

      Columnar is available but the caller supplied no estimate to justify it.

    • "protocol-not-columnar"

      No columnar producer exists for this protocol.

    • "encoding-not-columnar"

      The declared geometry encoding has no columnar producer.

    • "aggregation-not-columnar"

      Aggregate results are grouped rows, not a feature batch.

    • "geometry-not-requested"

      A columnar batch is a geometry batch; the query suppressed geometry.