XMLWordPrintableJSON

    Details

      Description

      Background
      EFO record consumption has configuration properties that are available to the connector via a properties map. The connector must deserialise (where applicable) these properties and validate they are correct.

      Scope

      • See FLIP for possible configuration options
      • Validate the configuration, see KinesisConfigUtil::validateConsumerConfiguration for existing validation routines
      • Provide a deserialisation mechanism to allow other EFO components to access properties without having to parse from string:
        • Suggest we create a new config class, FanOutProperties that accepts a Properties map and provides convenience methods, for example getConsumerName()

        Attachments

          Activity

            People

            • Assignee:
              heywxl roland
              Reporter:
              danny.cranmer Danny Cranmer
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: