NIFI-5317 - support non-ASCII X-Mailer header#2800
NIFI-5317 - support non-ASCII X-Mailer header#2800dtrodrigues wants to merge 1 commit intoapache:masterfrom
Conversation
|
This looks good, just two comments.
|
|
Header setting is now refactored into a function and there are tests for non-ascii headers |
| @@ -320,6 +320,15 @@ public void onScheduled(final ProcessContext context) { | |||
| this.attributeNamePattern = attributeNameRegex == null ? null : Pattern.compile(attributeNameRegex); | |||
| } | |||
|
|
|||
There was a problem hiding this comment.
We should include the header name in the message
| @@ -137,7 +137,7 @@ public void testOutgoingMessage() throws Exception { | |||
| public void testOutgoingMessageWithOptionalProperties() throws Exception { | |||
| // verifies that optional attributes are set on the outgoing Message correctly | |||
There was a problem hiding this comment.
I don't see the non-ascii, am I missing something?
There was a problem hiding this comment.
The test is for the non-ascii accented 'i' here in the first 'i' of "TestingNífi" on lines 140/167 as well as for the accented 'u' in "Búlk" https://github.com/apache/nifi/pull/2800/files/1325c094326eb0b89b4516a99c2065ef8b2d8009#diff-c1df47b56b59d9c7ef5e22043c7cd1a7R140
|
I updated the test X-Mailer header to be more explicit that it's non-ASCII |
|
Yikes, sorry. |
|
+1 LGTM, mvn install and contrib-check pass, use of MineType utility per best practices. |
|
+1, merging to master, thanks @dtrodrigues @ottobackwards |
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:
Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
Has your PR been rebased against the latest commit within the target branch (typically master)?
Is your initial contribution a single, squashed commit?
For code changes:
For documentation related changes:
Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.