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

[Enhancement] Configure production compression type at the producer instance level instead of at the process level #8166

Closed
1 task done
humkum opened this issue May 20, 2024 · 0 comments · Fixed by #8167

Comments

@humkum
Copy link
Contributor

humkum commented May 20, 2024

Before Creating the Enhancement Request

  • I have confirmed that this should be classified as an enhancement rather than a bug/feature.

Summary

The current way to configure the producer compression type is through System.setProperty, which is process level.
When there are multiple topics in one process that need to produce messages, all topics will use the same type of compression method.

Motivation

When there are multiple topics in a process that need to produce messages, all topics will use the same type of compression method.So we can change compression configure at the producer instance level, user can create different producer instance to enable different type of compression.

Describe the Solution You'd Like

Configure production compression at the producer instance level instead of at the process level.

Describe Alternatives You've Considered

None.

Additional Context

No response

@humkum humkum changed the title [Enhancement] Configure production compression at the producer instance level instead of at the process level [Enhancement] Configure production compression type at the producer instance level instead of at the process level May 20, 2024
cserwen pushed a commit to cserwen/rocketmq that referenced this issue Jun 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant