You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Paolo Patierno (JIRA)" <ji...@apache.org> on 2017/06/27 12:13:00 UTC

[jira] [Created] (KAFKA-5525) Streams reset tool should have same console output with or without dry-run

Paolo Patierno created KAFKA-5525:
-------------------------------------

             Summary: Streams reset tool should have same console output with or without dry-run
                 Key: KAFKA-5525
                 URL: https://issues.apache.org/jira/browse/KAFKA-5525
             Project: Kafka
          Issue Type: Improvement
            Reporter: Paolo Patierno
            Priority: Minor


Hi,
I see that the Streams reset tool provides a console output a little bit different when you execute it using "dry-run" (so without executing any real action) or without it.
With dry-run :

{code}
----Dry run displays the actions which will be performed when running Streams Reset Tool----
Following input topics offsets will be reset to beginning (for consumer group streams-wordcount)
Topic: streams-file-input
Done.
Deleting all internal/auto-created topics for application streams-wordcount
Topic: streams-wordcount-Counts-repartition
Topic: streams-wordcount-Counts-changelog
Done.
{code}

without dry-run :

{code}
Seek-to-beginning for input topics [streams-file-input]
Done.
Deleting all internal/auto-created topics for application streams-wordcount
Topic streams-wordcount-Counts-repartition is marked for deletion.
Note: This will have no impact if delete.topic.enable is not set to true.
Topic streams-wordcount-Counts-changelog is marked for deletion.
Note: This will have no impact if delete.topic.enable is not set to true.
Done.
{code}

I think that the version with dry-run related to show "Seek-to-beginning for input topics [streams-file-input]" could be used even for version without dry-run.
The output should be consistent and the only difference should be on executing real actions or not.
I'm working on a trivial PR for a proposal.

Thanks,
Paolo



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)