[jira] [Assigned] (KAFKA-6764) ConsoleConsumer behavior inconsistent when specifying --partition with --from-beginning
[
https://issues.apache.org/jira/browse/KAFKA-6764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Larry McQueary reassigned KAFKA-6764:
-
Assignee: Larry McQueary
> ConsoleConsumer behavior inconsistent when specifying --partition with
> --from-beginning
>
>
> Key: KAFKA-6764
> URL: https://issues.apache.org/jira/browse/KAFKA-6764
> Project: Kafka
> Issue Type: Bug
> Components: consumer
>Reporter: Larry McQueary
>Assignee: Larry McQueary
>Priority: Minor
> Labels: newbie
>
> Per its usage statement, {{kafka-console-consumer.sh}} ignores
> {{\-\-from-beginning}} when the specified consumer group has committed
> offsets, and sets {{auto.offset.reset}} to {{latest}}. However, if
> {{\-\-partition}} is also specified, {{\-\-from-beginning}} is observed in
> all cases, whether there are committed offsets or not.
> This happens because when {{\-\-from-beginning}} is specified, {{offsetArg}}
> is set to {{OffsetRequest.EarliestTime}}. However, {{offsetArg}} is [only
> passed to the
> constructor|https://github.com/apache/kafka/blob/fedac0cea74fce529ee1c0cefd6af53ecbdd/core/src/main/scala/kafka/tools/ConsoleConsumer.scala#L76-L79]
> for {{NewShinyConsumer}} when {{\-\-partition}} is also specified.
> This case should either be handled consistently, or the usage statement
> should be modified to indicate the actual behavior/usage.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KAFKA-6764) ConsoleConsumer behavior inconsistent when specifying --partition with --from-beginning
[
https://issues.apache.org/jira/browse/KAFKA-6764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Larry McQueary updated KAFKA-6764:
--
Description:
Per its usage statement, {{kafka-console-consumer.sh}} ignores
{{\-\-from-beginning}} when the specified consumer group has committed offsets,
and sets {{auto.offset.reset}} to {{latest}}. However, if {{\-\-partition}} is
also specified, {{\-\-from-beginning}} is observed in all cases, whether there
are committed offsets or not.
This happens because when {{\-\-from-beginning}} is specified, {{offsetArg}} is
set to {{OffsetRequest.EarliestTime}}. However, {{offsetArg}} is [only passed
to the
constructor|https://github.com/apache/kafka/blob/fedac0cea74fce529ee1c0cefd6af53ecbdd/core/src/main/scala/kafka/tools/ConsoleConsumer.scala#L76-L79]
for {{NewShinyConsumer}} when {{\-\-partition}} is also specified. Hence, it
is honored in this case and not the other.
This case should either be handled consistently, or the usage statement should
be modified to indicate the actual behavior/usage.
was:
Per its usage statement, {{kafka-console-consumer.sh}} ignores
{{\-\-from-beginning}} when the specified consumer group has committed offsets,
and sets {{auto.offset.reset}} to {{latest}}. However, if {{\-\-partition}} is
also specified, {{\-\-from-beginning}} is observed in all cases, whether there
are committed offsets or not.
This happens because when {{\-\-from-beginning}} is specified, {{offsetArg}} is
set to {{OffsetRequest.EarliestTime}}. However, {{offsetArg}} is [only passed
to the
constructor|https://github.com/apache/kafka/blob/fedac0cea74fce529ee1c0cefd6af53ecbdd/core/src/main/scala/kafka/tools/ConsoleConsumer.scala#L76-L79]
for {{NewShinyConsumer}} when {{\-\-partition}} is also specified.
This case should either be handled consistently, or the usage statement should
be modified to indicate the actual behavior/usage.
> ConsoleConsumer behavior inconsistent when specifying --partition with
> --from-beginning
>
>
> Key: KAFKA-6764
> URL: https://issues.apache.org/jira/browse/KAFKA-6764
> Project: Kafka
> Issue Type: Bug
> Components: consumer
>Reporter: Larry McQueary
>Assignee: Larry McQueary
>Priority: Minor
> Labels: newbie
>
> Per its usage statement, {{kafka-console-consumer.sh}} ignores
> {{\-\-from-beginning}} when the specified consumer group has committed
> offsets, and sets {{auto.offset.reset}} to {{latest}}. However, if
> {{\-\-partition}} is also specified, {{\-\-from-beginning}} is observed in
> all cases, whether there are committed offsets or not.
> This happens because when {{\-\-from-beginning}} is specified, {{offsetArg}}
> is set to {{OffsetRequest.EarliestTime}}. However, {{offsetArg}} is [only
> passed to the
> constructor|https://github.com/apache/kafka/blob/fedac0cea74fce529ee1c0cefd6af53ecbdd/core/src/main/scala/kafka/tools/ConsoleConsumer.scala#L76-L79]
> for {{NewShinyConsumer}} when {{\-\-partition}} is also specified. Hence, it
> is honored in this case and not the other.
> This case should either be handled consistently, or the usage statement
> should be modified to indicate the actual behavior/usage.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KAFKA-6764) ConsoleConsumer behavior inconsistent when specifying --partition with --from-beginning
[
https://issues.apache.org/jira/browse/KAFKA-6764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Larry McQueary updated KAFKA-6764:
--
Summary: ConsoleConsumer behavior inconsistent when specifying --partition
with --from-beginning (was: ConsoleConsumer behavior inconsistent when
specifying --partition --from-beginning )
> ConsoleConsumer behavior inconsistent when specifying --partition with
> --from-beginning
>
>
> Key: KAFKA-6764
> URL: https://issues.apache.org/jira/browse/KAFKA-6764
> Project: Kafka
> Issue Type: Bug
> Components: consumer
>Reporter: Larry McQueary
>Priority: Minor
> Labels: newbie
>
> Per its usage statement, {{kafka-console-consumer.sh}} ignores
> {{\-\-from-beginning}} when the specified consumer group has committed
> offsets, and sets {{auto.offset.reset}} to {{latest}}. However, if
> {{\-\-partition}} is also specified, {{\-\-from-beginning}} is observed in
> all cases, whether there are committed offsets or not.
> This happens because when {{\-\-from-beginning}} is specified, {{offsetArg}}
> is set to {{OffsetRequest.EarliestTime}}. However, {{offsetArg}} is [only
> passed to the
> constructor|https://github.com/apache/kafka/blob/fedac0cea74fce529ee1c0cefd6af53ecbdd/core/src/main/scala/kafka/tools/ConsoleConsumer.scala#L76-L79]
> for {{NewShinyConsumer}} when {{\-\-partition}} is also specified.
> This case should either be handled consistently, or the usage statement
> should be modified to indicate the actual behavior/usage.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (KAFKA-6764) ConsoleConsumer behavior inconsistent when specifying --partition --from-beginning
Larry McQueary created KAFKA-6764:
-
Summary: ConsoleConsumer behavior inconsistent when specifying
--partition --from-beginning
Key: KAFKA-6764
URL: https://issues.apache.org/jira/browse/KAFKA-6764
Project: Kafka
Issue Type: Bug
Components: consumer
Reporter: Larry McQueary
Per its usage statement, {{kafka-console-consumer.sh}} ignores
{{\-\-from-beginning}} when the specified consumer group has committed offsets,
and sets {{auto.offset.reset}} to {{latest}}. However, if {{\-\-partition}} is
also specified, {{\-\-from-beginning}} is observed in all cases, whether there
are committed offsets or not.
This happens because when {{\-\-from-beginning}} is specified, {{offsetArg}} is
set to {{OffsetRequest.EarliestTime}}. However, {{offsetArg}} is [only passed
to the
constructor|https://github.com/apache/kafka/blob/fedac0cea74fce529ee1c0cefd6af53ecbdd/core/src/main/scala/kafka/tools/ConsoleConsumer.scala#L76-L79]
for {{NewShinyConsumer}} when {{\-\-partition}} is also specified.
This case should either be handled consistently, or the usage statement should
be modified to indicate the actual behavior/usage.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
