Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-17594

Deserialize custom headers in Kafka Kamelet source

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • camel-k-1.6.4-GA
    • camel-k-1.6-GA
    • Camel-K
    • None
    • False
    • False
    • % %
    • +
    • Automated
    • Hide

      See upstream YAKS test: https://github.com/openshift-integration/kamelet-catalog/blob/kamelet-catalog-1.6/test/kafka/kafka-source.feature#L35

      Test adds a custom header to the Kafka message and verifies the header on the sink. At the moment the header is not deserialized properly but forwarded as a byte[] to String representation.

      To verify the fix change the header verification step from expected "@notNull@" to the expected deserialized value.

      Show
      See upstream YAKS test:  https://github.com/openshift-integration/kamelet-catalog/blob/kamelet-catalog-1.6/test/kafka/kafka-source.feature#L35 Test adds a custom header to the Kafka message and verifies the header on the sink. At the moment the header is not deserialized properly but forwarded as a byte[] to String representation. To verify the fix change the header verification step from expected "@notNull@" to the expected deserialized value.

      The Kafka Kamelet source should automatically deserialize all custom header entries. By default Kafka headers are serialized as byte[] value. The source should provide a deserialized value to the sink similar to what is done with the body content.

       

              christoph.deppisch Christoph Deppisch
              christoph.deppisch Christoph Deppisch
              Andrej Vano Andrej Vano
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: