GitHub user vahidhashemian reopened a pull request:
https://github.com/apache/kafka/pull/922
KAFKA-3176: Add partition/offset options to both old and new console
consumers
With this pull request both old and new console consumers can be provided
with optional --partition and --offset arguments so messages from a particular
partition and starting from a particular offset are only consumed.
The following rules are also implemented to avoid invalid combinations of
arguments:
- If --partition is provided --topic has to be provided too.
- If --partition is provided --bootstrap-server (and not --zookeeper)
should be provided too.
- If --offset is provided --partition has to be provided too.
- --offset and --from-beginning cannot be used at the same time.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vahidhashemian/kafka KAFKA-3176
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/922.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #922
----
commit 5164a0d7ae344bb6cded0975849f6d36f9596982
Author: Vahid Hashemian <[email protected]>
Date: 2016-02-16T13:24:38Z
Add partition/offset options to both old and new console consumers
With this change both old and new console consumers can be provided with
optional --partition and --offset arguments so messages from a particular
partition and starting from a particular offset are only consumed.
The following rules are also implemented to avoid invalid combinations of
arguments:
- If --partition is provided --topic has to be provided too.
- If --partition is provided --bootstrap-server (and not --zookeeper)
should be provided too.
- If --offset is provided --partition has to be provided too.
- --offset and --from-beginning cannot be used at the same time.
----
---
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 enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
