Skip to content
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

[Doc] TableView should clarify tombstone behaviour #24007

Open
1 of 2 tasks
CoenraadS opened this issue Feb 20, 2025 · 0 comments
Open
1 of 2 tasks

[Doc] TableView should clarify tombstone behaviour #24007

CoenraadS opened this issue Feb 20, 2025 · 0 comments
Labels
doc-required Your PR changes impact docs and you will update later.

Comments

@CoenraadS
Copy link

Search before asking

  • I searched in the issues and found nothing similar.

What issue do you find in Pulsar docs?

https://pulsar.apache.org/docs/next/client-libraries-tableviews/

There are two methods for consuming table views:

// Register listeners for all existing and incoming messages
tv.forEachAndListen((key, value) -> /*operations on all existing and incoming messages*/)

// Register actions for all existing messages
tv.forEach((key, value) -> /*operations on all existing messages*/)

The docs do not specify if tombstone messages are propagated. I believe that forEach will not show them, but totally unsure about forEachAndListen

What is your suggestion?

Specify TombStone behaviour

Any reference?

No response

Are you willing to submit a PR?

  • I'm willing to submit a PR!
@CoenraadS CoenraadS added the doc-required Your PR changes impact docs and you will update later. label Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc-required Your PR changes impact docs and you will update later.
Projects
None yet
Development

No branches or pull requests

1 participant