Uploaded image for project: 'Debezium'
  1. Debezium
  2. DBZ-1787

Outbox Quarkus Extension: Allow varied ExportedEvent parameter configurations within a single application

    XMLWordPrintable

Details

    • Task
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • None
    • None
    • core-library, outbox
    • None

    Description

      Presently the Outbox Quarkus extension requires that an application use the same parameter configuration for all implemented ExportedEvent types. We should look at ways to allow a single application to work with varied generic signatures.

      The big question is how would this be modeled at the database? With different types, this would mean the database table would be different for all variations and therefore would this mean we'd have different outbox database tables? If so, how do we coordinate their order or is that even a concern?

      Attachments

        Issue Links

          Activity

            People

              ccranfor@redhat.com Chris Cranford
              ccranfor@redhat.com Chris Cranford
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: