Skip to content
Original file line number Diff line number Diff line change
Expand Up @@ -704,7 +704,7 @@ private void completeBatch(ProducerBatch batch, ProduceResponse.PartitionRespons
"topic-partition may not exist or the user may not have Describe access to it",
batch.topicPartition);
} else {
log.warn("Received invalid metadata error in produce request on partition {} due to {}. Going " +
log.warn("Received invalid metadata error in produce request on partition {} due to {} Going " +
"to request metadata update now", batch.topicPartition,

@appchemist appchemist Feb 6, 2024

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some error have dot, while others don't.
So, When dot is absent, there is no dot before 'Going'.

See Errors.INCONSISTENT_TOPIC_ID for details.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you so much for your comment. I have made changes based on your review in the latest (4th) commit.

@appchemist appchemist Feb 10, 2024

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about including dot in Errors's defaultExceptionString that don't currently include dot?
I referred to Use grammatically correct error messages.
In addition, most Errors's defaultExceptionString already include dot.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This makes a lot of sense. Thank you so much @appchemist. It took me a while to understand the code. I will fix this in my next commit.

error.exception(response.errorMessage).toString());
}
Expand Down