You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Jackson Ho (Jira)" <ji...@apache.org> on 2026/06/17 09:28:00 UTC

[jira] [Commented] (NIFI-14670) Support AMQP 1.0 alongside existing 0.9.1 in NiFi AMQP Processors

    [ https://issues.apache.org/jira/browse/NIFI-14670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18089607#comment-18089607 ] 

Jackson Ho commented on NIFI-14670:
-----------------------------------

I’m building a bridge between two message brokers using Apache NiFi with the ConsumeJMS and PublishJMS processors. However, I’ve noticed that the Content-Type header becomes null after the ConsumeJMS processor. Using a dedicated AMQP 1.0 processor might help avoid the limitations of JMS. Is there a pure AMQP 1.0 processor available?

> Support AMQP 1.0 alongside existing 0.9.1 in NiFi AMQP Processors
> -----------------------------------------------------------------
>
>                 Key: NIFI-14670
>                 URL: https://issues.apache.org/jira/browse/NIFI-14670
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>    Affects Versions: 2.4.0
>         Environment: Docker
>            Reporter: Mohammed Salim
>            Priority: Major
>
> Hi NiFi team!
> I'd like to propose adding AMQP 1.0 support to NiFi AMQP processors while keeping the current 0.9.1 support. This would be incredibly valuable because:
> 1. Many modern messaging systems now prefer AMQP 1.0 for its:
>    - Improved security features (authentication & authorization)
>    - Better performance with binary protocol support
>    - More flexible connection handling
> 2. We need both versions because:
>    - Some systems still use 0.9.1
>    - Having both options gives users flexibility
>    - Smooth transition path for upgrades
> This enhancement would help NiFi users better integrate with modern messaging systems while maintaining compatibility with existing implementations.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)