Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NIFI-13738 Add Max Inbound Message Body Size Property for AMQP #9776

Open
wants to merge 8 commits into
base: main
Choose a base branch
from

Conversation

hr-ireh
Copy link

@hr-ireh hr-ireh commented Mar 6, 2025

setMaxInboundMessageBodySize property would be configurable as a NiFi UI property.

@exceptionfactory exceptionfactory changed the title Bug with task number NIFI-13738 has been fixed. NIFI-13738 Add Max Inbound Message Body Size Property for AMQP Mar 6, 2025
Copy link
Contributor

@pvillard31 pvillard31 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In addition to the checkstyle violation mentioned in my previous comment, another comment: right now the new property is added to the common properties in the Abstract class, meaning that the property will also show in the PublishAMQP processor which does not really make sense. I think that it should not be added in PROPERTY_DESCRIPTORS of the Abstract class and instead added in PROPERTY_DESCRIPTORS of the Consume class. Thoughts?

@hr-ireh
Copy link
Author

hr-ireh commented Mar 7, 2025

It is true that the settings are related to the consumer, but like the port and IP, they must be set in the ConnectionFactory, which is created in the AbstractAMQPProcessor.
How to set MaxInboundMessageBodySize in ConsumeAMQP!

@pvillard31
Copy link
Contributor

The checkstyle validation needs to be fixed.

Regarding the property, what I'm saying is that you can remove it from the PROPERTY_DESCRIPTORS list of the Abstract class and be added into the PROPERTY_DESCRIPTORS list of the Consume processor. Everything else remains unchanged. This only affects where the property will be visible in the UI.

hr-ireh added 2 commits March 7, 2025 19:39
…SCRIPTORS list of the Abstract class and added into the PROPERTY_DESCRIPTORS list of the Consume processor.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants