Github user kunickiaj closed the pull request at:
https://github.com/apache/kafka/pull/862
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user kunickiaj reopened a pull request:
https://github.com/apache/kafka/pull/858
KAFKA-3198: Ticket Renewal Thread exits prematurely due to inverted câ¦
KAFKA-3198: Ticket Renewal Thread exits prematurely due to inverted
comparison
The >= should be < since
Github user kunickiaj closed the pull request at:
https://github.com/apache/kafka/pull/858
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user kunickiaj opened a pull request:
https://github.com/apache/kafka/pull/862
KAFKA-3199: LoginManager should allow using an existing Subject
One possible solution which doesn't require a new configuration parameter:
But it assumes that if there is already a Subjec
GitHub user kunickiaj opened a pull request:
https://github.com/apache/kafka/pull/858
KAFKA-3198: Ticket Renewal Thread exits prematurely due to inverted câ¦
KAFKA-3198: Ticket Renewal Thread exits prematurely due to inverted
comparison
The >= should be < since
GitHub user kunickiaj opened a pull request:
https://github.com/apache/kafka/pull/850
KAFKA-3191: Improve offset committing JavaDoc in KafkaConsumer
Added an example clarifying the correct way to use explicit offsets with
commitSync().
You can merge this pull request into a Git