Skip to content

Preserve row-cap metadata through binary query APIs #9

Closed

Description

@jallegri

Priority

p0 — Known capped MessagePack results are represented without their cap signals.

Gap

PR #2 decoder explicitly reconstructs QueryResponse without rows_capped and row_cap, although both server baselines emit them. PR #6 adds model fields/defaults but leaves that decoder unchanged. This issue covers the residual binary transport gap, not duplicate JSON model work.

Decoder, producer. Unchanged decoder/constructor fixture confirms omitted keys; full MessagePack transport remains untested. Arrow exposes cap information in trailers, requiring separate transport investigation.

Acceptance

Tracking: https://github.com/Basekick-Labs/ops/issues/40. Analysis baselines: SDK main 46d3b66 and pending PRs #2/#3/#5/#6; Arc release e83bb1e (v26.09.3) and main a63f4a8. Implementation is unscheduled; the parent analysis deadline is 2026-10-30. No owner or delivery commitment is implied.

Verification must record exact versions/commands/results and separate Manual Test from IA Test. Require sync/async cases, negative authorization/validation cases, and existing-regression preservation. Local Docker is appropriate for end-to-end server checks; inventory and clean up only test resources.

Activity

  1. jallegri commented on Oct 30, 2026

    @jallegri
    ContributorAuthor

    Fixed and merged into main through #25. Sync/async coverage verifies row-cap and truncation metadata, lossless MessagePack timestamps, and Arrow completion metadata. Arrow transport limitations and DataFrame metadata handling are documented.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions