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

The prefix for the fields and headers can be a list instead of a string

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Done
    • Icon: Minor Minor
    • None
    • 1.2.2.Final
    • core-library
    • None
    • False
    • False
    • Undefined

      It is now possible to give the configurable string prefix for the fields and headers.

      • "add.fields.prefix" -> String with the default value of "__"
      • "add.headers.prefix" -> String with the default value of  "__"

      This makes all the fields and headers to have the same prefix.

      We can change this to a list of strings.
      Then each individual field and header can have different prefixes. 
      This might also be useful when anyone want to only prefix for few fields/headers and not all. 

      •  "add.fields.prefix" -> list of strings.
        • When given the # of prefixes MUST be equal to # of fields given in "add.fields". We can configure empty prefix as well.
      •  "add.headers.prefix" -> list of strings.
        • When given the # of prefixes MUST be equal to # of headers given in "add.headers". We can configure empty prefix as well.

       

            [DBZ-2695] The prefix for the fields and headers can be a list instead of a string

            Gunnar Morling added a comment -

            Ok, thanks for clarifying In that light, I'm going to close this issue for the time being. Let's see whether the requirement really comes up, then we can revisit. Thanks!

            Gunnar Morling added a comment - Ok, thanks for clarifying In that light, I'm going to close this issue for the time being. Let's see whether the requirement really comes up, then we can revisit. Thanks!

            Ganesh Ramasubramanian (Inactive) added a comment -

            It isn't my requirements. While doing the prefix I was wondering why to restrict the same prefix to all the fields and headers. If you think it isn't that much of value you can close it.

            Ganesh Ramasubramanian (Inactive) added a comment - It isn't my requirements. While doing the prefix I was wondering why to restrict the same prefix to all the fields and headers. If you think it isn't that much of value you can close it.

            Gunnar Morling added a comment -

            So is this an actual requirement you have, or rather some theoretic option? Not sure whether it'd pull its weight tbh.

            Gunnar Morling added a comment - So is this an actual requirement you have, or rather some theoretic option? Not sure whether it'd pull its weight tbh.

              Unassigned Unassigned
              rgannu Ganesh Ramasubramanian (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: