feat: 30.2 — unified api surface

Merged
VI
8mo ago
+248-133

Summary

  • Update Java SDK for the unified API from Story 30.1
  • BatchEnqueue RPC removed; Enqueue now accepts repeated EnqueueMessage
  • Ack/Nack now accept repeated AckMessage/NackMessage with per-item typed results
  • ConsumeResponse uses only repeated Message messages (singular message field removed)
  • batchEnqueue() replaced by enqueueMany() (no "batch" prefix)
  • BatchEnqueueResult renamed to EnqueueResult
  • Batcher updated to use unified Enqueue RPC for all batch sizes
  • All tests updated and passing (34/34 pass; 1 pre-existing TLS env failure)

Test plan

  • Unit tests: EnqueueResultTest, BatchModeTest, BuilderTest all pass
  • Integration tests: FilaClientTest (enqueue/consume/ack/nack lifecycle) passes
  • Integration tests: BatchClientTest (enqueueMany, auto/linger/disabled batching) passes
  • Verified TLS test failure is pre-existing (fails on main too)

Summary by cubic

Unifies the Java SDK and proto around a single enqueue/ack/nack API with per-item results and typed errors, removing the BatchEnqueue RPC. Adds StreamEnqueue, simplifies ConsumeResponse to messages[], renames client batch APIs to enqueueMany, and routes the batcher through the unified Enqueue.

  • Bug Fixes

    • ack()/nack() now validate exactly one per-item result and require explicit success; empty or unset results throw.
  • Migration

    • Replace FilaClient.batchEnqueue(...) with FilaClient.enqueueMany(...); use EnqueueResult (was BatchEnqueueResult).
    • Protos: remove BatchEnqueue; use EnqueueRequest.messages[], AckRequest.messages[], NackRequest.messages[]; read ConsumeResponse.messages[] only.
    • Handle typed errors: EnqueueError, AckError, NackError.