AndrewJSchofield commented on code in PR #20673:
URL: https://github.com/apache/kafka/pull/20673#discussion_r2425926502


##########
tools/src/main/java/org/apache/kafka/tools/ConsoleProducer.java:
##########
@@ -230,6 +232,28 @@ public ConsoleProducerOptions(String[] args) {
                     .ofType(Integer.class)
                     .defaultsTo(1024 * 100);
             propertyOpt = parser.accepts("property",
+                            "(DEPRECATED) A mechanism to pass user-defined 
properties in the form key=value to the message reader. This allows custom 
configuration for a user-defined message reader." +
+                                    "\nDefault properties include:" +
+                                    "\n parse.key=false" +
+                                    "\n parse.headers=false" +
+                                    "\n ignore.error=false" +
+                                    "\n key.separator=\\t" +
+                                    "\n headers.delimiter=\\t" +
+                                    "\n headers.separator=," +
+                                    "\n headers.key.separator=:" +
+                                    "\n null.marker=   When set, any fields 
(key, value and headers) equal to this will be replaced by null" +
+                                    "\nDefault parsing pattern when:" +
+                                    "\n parse.headers=true and 
parse.key=true:" +
+                                    "\n  \"h1:v1,h2:v2...\\tkey\\tvalue\"" +
+                                    "\n parse.key=true:" +
+                                    "\n  \"key\\tvalue\"" +
+                                    "\n parse.headers=true:" +
+                                    "\n  \"h1:v1,h2:v2...\\tvalue\"" +
+                                    "This option will be removed in a future 
version. Use --reader-property instead.")

Review Comment:
   nit: Let's have a `\n` here to improve the usage message formatting.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to