[HOP-3258] Kafka consumer input sub-pipeline cannot be run transactional

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Not A Bug
• Fix Version/s: 1.0.0
• Assignee: Sergio Ramazzina
• Reporter: Sergio Ramazzina
• Created: 09/Sep/21 10:06
• Updated: 21/Sep/21 14:05
• Resolved: 09/Sep/21 13:11

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.