rosemarYuan commented on PR #887:
URL: https://github.com/apache/flink-agents/pull/887#issuecomment-4922191769
Thanks for the design pass @zxs1633079383 — agreed, and that is exactly the
boundary I want to keep.
For this PR, the memory event payload under `attributes: { key, value }`
stays observation-only: it only describes the memory content/effect being
observed. No #841 lineage or run-identity fields such as `runId`,
`sourceEventId`, or `emittingAction` should be added inside the memory event
`value`/`attributes` map.
On the lineage direction, we are aligned. If/when the event-log lineage
schema lands, those fields should be carried as event-log
metadata/envelope-level information and apply uniformly to logged events,
memory events included. The exact carrier shape, for example whether it is a
separate `lineage` object on the log record or another context/envelope
mechanism, belongs in the lineage design thread rather than this PR.
Same principle you described: memory events expose memory observation data;
lineage stays outside the user-facing event payload.
--
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]
