Skip to content

NIFI-16195 Wrote part headers into attributes - #11631

Open
dan-s1 wants to merge 1 commit into
apache:mainfrom
dan-s1:NIFI-16195
Open

NIFI-16195 Wrote part headers into attributes#11631
dan-s1 wants to merge 1 commit into
apache:mainfrom
dan-s1:NIFI-16195

Conversation

@dan-s1

@dan-s1 dan-s1 commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

Summary

NIFI-16195

Tracking

Please complete the following tracking steps prior to pull request creation.

Issue Tracking

Pull Request Tracking

  • Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
  • Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000
  • Pull request contains commits signed with a registered key indicating Verified status

Pull Request Formatting

  • Pull Request based on current revision of the main branch
  • Pull Request refers to a feature branch with one commit containing changes

Verification

Please indicate the verification steps performed prior to pull request creation.

Build

  • Build completed using ./mvnw clean install -P contrib-check
    • JDK 21
    • JDK 25

Licensing

  • New dependencies are compatible with the Apache License 2.0 according to the License Policy
  • New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

  • Documentation formatting appears as expected in rendered files

runner.assertTransferCount(ExtractEmailAttachments.REL_ATTACHMENTS, 0);
}

private void assertAttachmentHeaderAttributes(MockFlowFile split) {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Can the tests assert the exact header attribute names and values, and cover body, inline image, and attachment parts to verify the behavior described in NIFI-16195?

}

for (Map.Entry<String, String> entry : attachment.headers().entrySet()) {
final String headerAttributeName = ATTACHMENT_HEADER_ATTRIBUTE_PREFIX + entry.getKey();

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Should the header name be lowercased when building the attribute name, as ExtractEmailHeaders does, so downstream flows can rely on stable attribute names?

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