Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-14932

Configuration of Reactive Messaging Kafka messages

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • 25.0.0.Beta1, 25.0.0.Final
    • None
    • None
    • None

    Description

      This needs to use https://github.com/smallrye/smallrye-reactive-messaging/blob/3.0.0/smallrye-reactive-messaging-kafka/src/main/java/io/smallrye/reactive/messaging/kafka/KafkaMessageMetadata.java which in turn uses the upcoming (probably RM spec 2.1) Message.getMetadata() method.

       

      It allows you to specify the key, partition etc. the Kafka messages should be sent to, allowing you finer-grained control of them.

      Attachments

        Issue Links

          blocks

          Feature Request - Feature requests from customers and/or users WFLY-15019 Full Support for RHOSAK Integration

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Feature Request - Feature requests from customers and/or users WFLY-15016 Provide full Support for MicroProfile Reactive Messaging for AMQ Streams (Kafka) integration

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open
          is related to

          Bug - A problem that impairs or prevents the functions of the product. WFLY-15299 Review the smallrye-reactive-messaging-kafka-api module visibility

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. WFLY-15300 Review the kafka-clients and vertx-kafka-client module

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              kkhan1@redhat.com Kabir Khan
              kkhan1@redhat.com Kabir Khan
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: