+1 from me. Felix et al indicated that the various "2.2" JIRAs had no
further actions. I retargeted most of the other 2.2.0-targeted JIRAs that
didn't seem like they're must-do. We have no Blockers and I'm not aware of
any changes that must be in the 2.2 release that aren't.
These are the only rem
Can you explain in more detail what you mean by "distribute Kafka
topics among different instances of same consumer group"?
If you're trying to run multiple streams using the same consumer
group, it's already documented that you shouldn't do that.
On Thu, Jun 8, 2017 at 12:43 AM, Rastogi, Pankaj
Hi,
Thank you for your reply!
You got it right! I am trying to run multiple streams using the same
consumer, so that I can distribute different partitions among different
instances of the consumer group. I don¹t want to provide the list of
partitions in createDirectStream API. If I do that then i
I've never thought that docs are strictly part of a release and can't be
updated outside of one. Javadoc jars are included in releases with jars,
but that's more because they are produced by the build and are tied to the
source code. There is plenty of other documentation that isn't normally
includ
I agree that it seems completely fine to update the web version of the docs
after a release. What would not be fine is updating the downloadable package
for it without another vote (and another release number). When people voted on
a release, they voted that we should put up that package as "spa
