Clarify timestamp behavior in protocol documentation #219
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SimonWoolf
approved these changes
Nov 13, 2024
Updated the description of the timestamp field to indicate that it reflects the time at which the message was first received by the system, and will not be updated on subsequent message updates.
splindsay-92
force-pushed
the
materialisation/update-publish-timestamp-spec
branch
from
5f9af09 to
063d72a
Compare
splindsay-92
deleted the
materialisation/update-publish-timestamp-spec
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updated the description of the timestamp field to indicate that it reflects the time at which the message was first received by the system, and will not be updated on subsequent message updates.
It seems this area of the spec is pretty out-of-date, what is our view towards supporting this?