@edenhill does this impact -K too? IIRC we discussed it but I can't find the issue, only this one. In this example : works fine but ± does not

Input:

[~/g/d/connect-jdbc] Robin@asgard02.moffatt.me  (connect-jdbc|…)
$ docker run --rm -it --network connect-jdbc_default confluentinc/cp-kafkacat \
      kafkacat -b kafka:29092 -t kc-test -P
no key
^C⏎                                                                                                                                                                                                          [~/g/d/connect-jdbc] Robin@asgard02.moffatt.me  (connect-jdbc|…)
$ docker run --rm -it --network connect-jdbc_default confluentinc/cp-kafkacat \
      kafkacat -b kafka:29092 -t kc-test -P -K:
1:key is 1, separator is :
[~/g/d/connect-jdbc] Robin@asgard02.moffatt.me  (connect-jdbc|…)
$ docker run --rm -it --network connect-jdbc_default confluentinc/cp-kafkacat \
      kafkacat -b kafka:29092 -t kc-test -P -K±
1±key is 1, separator is ±

Output:

$ docker run --rm -it --network connect-jdbc_default confluentinc/cp-kafkacat \
    kafkacat -b kafka:29092 -t kc-test -C -f '\nKey (%K bytes): %k\t\nValue (%S bytes): %s\nTimestamp: %T\tPartition: %p\tOffset: %o\n--\n'

Key (-1 bytes):
Value (6 bytes): no key
Timestamp: 1546602214489        Partition: 0    Offset: 0
--
% Reached end of topic kc-test [0] at offset 1

Key (1 bytes): 1
Value (24 bytes): key is 1, separator is :
Timestamp: 1546602254776        Partition: 0    Offset: 1
--
% Reached end of topic kc-test [0] at offset 2

Key (1 bytes): 1
Value (26 bytes): �key is 1, separator is ±
Timestamp: 1546602271123        Partition: 0    Offset: 2
--
% Reached end of topic kc-test [0] at offset 3

Note in the final message the value has an additional byte pre-pended to the actual value.

Multi-byte -D delimiters are buggy #140

Description

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions