-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feat][doc] Sync 2.9.4-specific updates to 2.9.x docs #18830
Conversation
This reverts commit fd4684a.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting. Does it mean that we add new configure option even in a patch release?
Seems true and there is no boundary clarified on this as far as I know. Maybe it was added for specific users to fix their needs with an upgrade. |
# When using the InMemoryDelayedDeliveryTrackerFactory (the default DelayedDeliverTrackerFactory), whether | ||
# the deliverAt time is strictly followed. When false (default), messages may be sent to consumers before the deliverAt | ||
# time by as much as the tickTimeMillis. This can reduce the overhead on the broker of maintaining the delayed index | ||
# for a potentially very short time period. When true, messages will not be sent to consumer until the deliverAt time |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# for a potentially very short time period. When true, messages will not be sent to consumer until the deliverAt time | |
# for a potentially very short time period. When true, messages are not sent to consumers until the deliverAt time |
Since the docs have been migrated to the Pulsar-site repo, so I've replicated the updates in apache/pulsar-site#350 and closed this PR. |
Modifications
Sync 2.9.4-specific updates to 2.9.x docs as per
Documentation
doc
doc-required
doc-not-needed
doc-complete