DanielLeens commented on issue #11304: URL: https://github.com/apache/seatunnel/issues/11304#issuecomment-5541752101
Thanks @CryoThrust. This is now narrow enough to progress as a design-first Phase 1 proposal: one connector-local Mem0-compatible sink, source-to-memory only, explicit upsert/delete semantics, and no core or SPI abstraction. I found no active Mem0 implementation PR, so please turn this outline into the STIP-style design before starting connector code. The design needs to make three items testable: the exact option and row-path contract, including invalid combinations; the delivery claim for each operation, especially when the backend lacks an idempotency-header guarantee; and the per-record/batch failure boundary, including which outcomes are retried, surfaced, or acknowledged. Do not infer scope deletion from null data or claim exactly-once without a backend-supported stable request identity. The implementation proposal should also name the existing HTTP-base extension points it will use, keep backend response bodies sanitized, and define a deterministic mock-server test matrix before deciding whether a full Mem0 Testcontainers profile is viable. -- 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]
