SEZ9 commented on issue #10753:
URL: https://github.com/apache/seatunnel/issues/10753#issuecomment-5381239004

   Thanks @goutamadwant — this is exactly the kind of first slice this tracker 
asks for: sink-only, on `dev`, with docs and E2E coverage included, and with 
the source side deliberately deferred until subscriber acknowledgements and 
checkpoint recovery get their own design. Keeping Pub/Sub Source as a separate 
follow-up is the right call.
   
   A few concrete asks so we can move #11877 forward:
   1. Please make sure the PR description links back to this umbrella tracker 
(#10753) so the claim stays visible here.
   2. In the PR, briefly note the intended V1 boundary (JSON / delimited text 
payloads, ADC / service account key / emulator auth, checkpoint-time flush) so 
reviewers can confirm scope without re-deriving it from the code.
   3. When you are ready for review, drop a short comment on the PR confirming 
the JDK 8/11 unit coverage and the Flink/Zeta/Spark emulator E2E coverage you 
described here — that summary will speed up the first review pass.
   
   Quick status check on the other in-flight claims under this tracker:
   - @SaiPande — any update on the Syslog Sink slice? The Source side remains 
tracked in #2649 / PR #10900, so the Sink is still the open Syslog item here.
   - @srijan-singh — did you settle on Azure Cosmos DB Sink? If so, please 
continue the scope alignment in #10443 before opening the PR, as discussed 
above.
   - @RaphaelAdewale — Splunk is still open under this tracker; a short note on 
your planned first slice (Source vs. Sink) would help avoid overlap.
   
   Thanks all for keeping the slices small and clearly claimed — it makes 
review much faster.
   
   <!-- streview-comment:453 -->


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to