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

Allow either subscribe or assign in RdKafkaConsumer #508

Merged
merged 2 commits into from
Aug 20, 2018

Conversation

Engerim
Copy link
Contributor

@Engerim Engerim commented Aug 16, 2018

With assign it is not possible to use the rebalancing from Kafka. So if no offset is set we use subscribe and rebalancing is possible and otherwise if a offset is set we are using assign.

With `assign` it is not possible to use the rebalancing from Kafka. So if no offset is set we use `subscribe` and rebalancing is possible and otherwise if a offset is set we are using assign.
* add test that when a offset is set we use assign
@makasim
Copy link
Member

makasim commented Aug 16, 2018

@Engerim LGTM, could be merged?

@makasim makasim merged commit 60b4693 into php-enqueue:master Aug 20, 2018
@Engerim Engerim deleted the allow-subscribe-or-assign branch August 20, 2018 11:00
@mente
Copy link

mente commented Sep 24, 2018

@makasim when do you plan to release this bug to stable?

@makasim
Copy link
Member

makasim commented Sep 24, 2018

@mente not sure it happens in near future. I think a backport for 0.8 is a better option.

@mente
Copy link

mente commented Sep 24, 2018

Oh, i wasn't aware of release cycle. Is it coming in 0.9 version then? When 0.9 is planned to be released?

@makasim
Copy link
Member

makasim commented Oct 11, 2018

I was almost ready to release a stable version (3-5 days left). Now I am involved in a project development. Not sure when it happens.

ASKozienko pushed a commit that referenced this pull request Nov 2, 2018
Allow either subscribe or assign in RdKafkaConsumer
@makasim makasim added this to the 0.9 milestone Nov 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants