Uploaded image for project: 'Apache Hop'
  1. Apache Hop
  2. HOP-3258

Kafka consumer input sub-pipeline cannot be run transactional

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Critical
    • Resolution: Not A Bug
    • None
    • 1.0.0
    • None
    • None

    Description

      There isn't any way to specify that the kafka consumer input transform must start a sub-pipeline with transactions management enabled and this is strongly needed for certain use-cases. 

      It would be also enough if the sub-pipeline started by the kafka consumer transform could inherit the transactional flag from the pipeline that started the kafka consumer itself.

      Attachments

        Activity

          People

            sramazzina Sergio Ramazzina
            sramazzina Sergio Ramazzina
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: