-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
[pip][design] PIP-278: Support pluggable topic compaction service #20624
Conversation
pip/pip-278.md
Outdated
|
||
* Rename `CompactorSubscription` to `PulsarCompactorSubscription`, since it is only applicable to the implementation of Pulsar. | ||
|
||
* For CompactorMetrics keep the current implementation and it only support `PulsarTopicCompactionService` currently , in the future will use the `Otel` API or other mertics API instead, and customize compactedService should implement it. |
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.
Hi,@asafm
I remember you have been working on the metrics lately. What do you think of the place? thanks! :)
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.
It's better not to use an implementation class in the interface. Why do you use PositionImpl
instead of Position
?
Oh, because when implementing it, I found that the caller needs to compare the |
I push PR for implementation: #20626 |
It cannot explain why must we return a |
Just |
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.
Cool, just left a minor comment.
It looks good to me to go to the VOTE stage.
pip/pip-278.md
Outdated
Apache Pulsar is a distributed messaging system that supports multiple messaging protocols and storage methods. | ||
Among them, Pulsar Topic Compaction provides a key-based data retention mechanism that allows you only to keep the most recent message associated with that key to reduce storage space and improve system efficiency. | ||
|
||
Another, the Topic Compaction of new load balancer changed the strategy of compaction, it will only to keep the first value of the key. |
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.
Please help add a link of the proposal of new load balancer so that users can go to the proposal to check the details.
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.
The Class Diagram should be updated since you have changed the method name
Thanks, I fixed it. |
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.
LGTM
@Anonymitaet please help take a look at this proposal. thanks a lot! |
434f5a6
to
6df3ee3
Compare
Co-authored-by: Penghui Li <penghui@apache.org>
Please bear in mind if for one PIP we have 0.5mb image, imaging the size over time in the repo. We could have used https://mermaid.js.org/syntax/classDiagram.html |
@asafm Thanks for reminding. I removed pip images and used mermaid instead: #20682 BTW, we can add this suggestion to the documentation of the pip process. |
Motivation & Modifications
Start a PIP: Support pluggable topic compaction service
Documentation
doc
doc-required
doc-not-needed
doc-complete