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

[Feature] Implement PushConsumer for Rust SDK #683

Closed
lizhanhui opened this issue Feb 21, 2024 · 4 comments · Fixed by #767
Closed

[Feature] Implement PushConsumer for Rust SDK #683

lizhanhui opened this issue Feb 21, 2024 · 4 comments · Fixed by #767
Labels
no stale This will never be considered stale type/new feature

Comments

@lizhanhui
Copy link
Contributor

Programming Language of the Client

Rust

Is Your Feature Request Related to a Problem?

We need to align features with Java/C++/...

Describe the Solution You'd Like

N/A

Describe Alternatives You've Considered

N/A

Additional Context

N/A

@glcrazier
Copy link
Contributor

I'd like to take a shot. Is there anything required before I submit the PR?

@lizhanhui
Copy link
Contributor Author

I'd like to take a shot. Is there anything required before I submit the PR?

Implementing this feature would result in a large change set, in order to make the development community-friendly, it would be better to divide the effort into multiple stages, thus produce multiple smaller pull requests each time.

For example, stage-1: build push-consumer for standard messages; stage-2: build push-consumer for FIFO messages; stage-3: support consume message verification and other miscellaneous tasks.

@glcrazier
Copy link
Contributor

I'd like to take a shot. Is there anything required before I submit the PR?

Implementing this feature would result in a large change set, in order to make the development community-friendly, it would be better to divide the effort into multiple stages, thus produce multiple smaller pull requests each time.

For example, stage-1: build push-consumer for standard messages; stage-2: build push-consumer for FIFO messages; stage-3: support consume message verification and other miscellaneous tasks.

No problem. I'll tackle this feature incrementally.

Copy link

This issue is stale because it has been open for 30 days with no activity. It will be closed in 3 days if no further activity occurs.

@github-actions github-actions bot added the stale Pull request is stale label Mar 24, 2024
@lizhanhui lizhanhui added no stale This will never be considered stale and removed stale Pull request is stale labels Mar 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no stale This will never be considered stale type/new feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants