feat: 30.2 — unified api surface
Merged
VI
8mo ago+248+248+012345678901234567890123456789-133-133-012345678901234567890123456789
Summary
- Update Java SDK for the unified API from Story 30.1
BatchEnqueueRPC removed;Enqueuenow acceptsrepeated EnqueueMessageAck/Nacknow acceptrepeated AckMessage/NackMessagewith per-item typed resultsConsumeResponseuses onlyrepeated Message messages(singularmessagefield removed)batchEnqueue()replaced byenqueueMany()(no "batch" prefix)BatchEnqueueResultrenamed toEnqueueResult- Batcher updated to use unified
EnqueueRPC 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(...)withFilaClient.enqueueMany(...); useEnqueueResult(wasBatchEnqueueResult). - Protos: remove
BatchEnqueue; useEnqueueRequest.messages[],AckRequest.messages[],NackRequest.messages[]; readConsumeResponse.messages[]only. - Handle typed errors:
EnqueueError,AckError,NackError.
- Replace