[jira] [Updated] (NIFI-3554) Build does not work if pulling dependencies from a clean environment

[ https://issues.apache.org/jira/browse/NIFI-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pere Urbon-Bayes updated NIFI-3554: --- Status: Patch Available (was: Open) I submitted a patch for the affected maven file, please

[jira] [Updated] (NIFI-3554) Build does not work if pulling dependencies from a clean environment

[ https://issues.apache.org/jira/browse/NIFI-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pere Urbon-Bayes updated NIFI-3554: --- Attachment: 0001-NIFI-3554-Fixing-the-jBCrypt-dependency-name-from.patch > Build does not work

[jira] [Created] (NIFI-3554) Build does not work if pulling dependencies from a clean environment

Pere Urbon-Bayes created NIFI-3554: -- Summary: Build does not work if pulling dependencies from a clean environment Key: NIFI-3554 URL: https://issues.apache.org/jira/browse/NIFI-3554 Project: Apache

[jira] [Assigned] (NIFI-1503) Include timezone on NiFI log messages

[ https://issues.apache.org/jira/browse/NIFI-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre F de Miranda reassigned NIFI-1503: Assignee: (was: Andre F de Miranda) > Include timezone on NiFI log messages >

[jira] [Updated] (NIFI-1503) Include timezone on NiFI log messages

[ https://issues.apache.org/jira/browse/NIFI-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre F de Miranda updated NIFI-1503: - Fix Version/s: 2.0.0 > Include timezone on NiFI log messages >

[jira] [Commented] (NIFI-1449) PutEmail needs more unit tests

[ https://issues.apache.org/jira/browse/NIFI-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15895482#comment-15895482 ] ASF GitHub Bot commented on NIFI-1449: -- Github user trixpan commented on the issue:

[GitHub] nifi issue #1553: NIFI-1449 - Migrate PutEmail tests from Mock class to List...

Github user trixpan commented on the issue: https://github.com/apache/nifi/pull/1553 Thanks for the assistance previously, it should be ready for review. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project

[jira] [Commented] (NIFI-3497) ScanAttribute should support tagging a flowfile with metadata value from the supplied dictionary

[ https://issues.apache.org/jira/browse/NIFI-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15895479#comment-15895479 ] ASF GitHub Bot commented on NIFI-3497: -- Github user alopresto commented on a diff in the pull request:

[GitHub] nifi pull request #1536: NIFI-3497 ScanAttribute Tagging

Github user alopresto commented on a diff in the pull request: https://github.com/apache/nifi/pull/1536#discussion_r104277602 --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ScanAttribute.java --- @@

[jira] [Commented] (NIFI-3497) ScanAttribute should support tagging a flowfile with metadata value from the supplied dictionary

[ https://issues.apache.org/jira/browse/NIFI-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15895434#comment-15895434 ] ASF GitHub Bot commented on NIFI-3497: -- Github user alopresto commented on a diff in the pull request:

[GitHub] nifi pull request #1536: NIFI-3497 ScanAttribute Tagging

Github user alopresto commented on a diff in the pull request: https://github.com/apache/nifi/pull/1536#discussion_r104275792 --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ScanAttribute.java --- @@

[jira] [Commented] (NIFI-3497) ScanAttribute should support tagging a flowfile with metadata value from the supplied dictionary

[ https://issues.apache.org/jira/browse/NIFI-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15895425#comment-15895425 ] ASF GitHub Bot commented on NIFI-3497: -- Github user alopresto commented on a diff in the pull request:

[GitHub] nifi pull request #1536: NIFI-3497 ScanAttribute Tagging

Github user alopresto commented on a diff in the pull request: https://github.com/apache/nifi/pull/1536#discussion_r104275670 --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ScanAttribute.java --- @@

[jira] [Updated] (NIFI-3543) Add support for using EL when defining 'brokerURI' in jms-cf-service

[ https://issues.apache.org/jira/browse/NIFI-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelly Liu updated NIFI-3543: - Summary: Add support for using EL when defining 'brokerURI' in jms-cf-service (was: Add support for using

[jira] [Commented] (NIFI-3497) ScanAttribute should support tagging a flowfile with metadata value from the supplied dictionary

[ https://issues.apache.org/jira/browse/NIFI-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15895405#comment-15895405 ] ASF GitHub Bot commented on NIFI-3497: -- Github user joetrite commented on a diff in the pull request:

[GitHub] nifi pull request #1536: NIFI-3497 ScanAttribute Tagging

Github user joetrite commented on a diff in the pull request: https://github.com/apache/nifi/pull/1536#discussion_r104274990 --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ScanAttribute.java --- @@ -97,13

[GitHub] nifi pull request #1536: NIFI-3497 ScanAttribute Tagging

Github user alopresto commented on a diff in the pull request: https://github.com/apache/nifi/pull/1536#discussion_r104273923 --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ScanAttribute.java --- @@

[jira] [Commented] (NIFI-3497) ScanAttribute should support tagging a flowfile with metadata value from the supplied dictionary

[ https://issues.apache.org/jira/browse/NIFI-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15895393#comment-15895393 ] ASF GitHub Bot commented on NIFI-3497: -- Github user alopresto commented on a diff in the pull request:

[jira] [Commented] (NIFI-1750) Document ScanAttribute's dictionary refresh logic

[ https://issues.apache.org/jira/browse/NIFI-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15895387#comment-15895387 ] ASF subversion and git services commented on NIFI-1750: --- Commit

[jira] [Commented] (NIFI-1750) Document ScanAttribute's dictionary refresh logic

[ https://issues.apache.org/jira/browse/NIFI-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15895389#comment-15895389 ] ASF GitHub Bot commented on NIFI-1750: -- Github user alopresto commented on the issue:

[jira] [Commented] (NIFI-1750) Document ScanAttribute's dictionary refresh logic

[ https://issues.apache.org/jira/browse/NIFI-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15895388#comment-15895388 ] ASF GitHub Bot commented on NIFI-1750: -- Github user asfgit closed the pull request at:

[GitHub] nifi issue #1543: NIFI-1750 - updated dict file desc

Github user alopresto commented on the issue: https://github.com/apache/nifi/pull/1543 I cleaned up the git history and merged this change to master. Thanks for submitting. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] nifi pull request #1543: NIFI-1750 - updated dict file desc

Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/1543 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (NIFI-1750) Document ScanAttribute's dictionary refresh logic

[ https://issues.apache.org/jira/browse/NIFI-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15895279#comment-15895279 ] ASF GitHub Bot commented on NIFI-1750: -- Github user alopresto commented on the issue:

[GitHub] nifi issue #1543: NIFI-1750 - updated dict file desc

Github user alopresto commented on the issue: https://github.com/apache/nifi/pull/1543 Reviewing... --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if

[jira] [Commented] (NIFI-3456) UserAgentParser Processor

[ https://issues.apache.org/jira/browse/NIFI-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15895266#comment-15895266 ] Nicholas Carenza commented on NIFI-3456: Anyone have experiment with

[jira] [Commented] (NIFI-3456) UserAgentParser Processor

[ https://issues.apache.org/jira/browse/NIFI-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15895248#comment-15895248 ] Nicholas Carenza commented on NIFI-3456: Starting work on this > UserAgentParser Processor >

[jira] [Commented] (NIFI-3553) FetchFTP can successfully receive data from remote server, then route the updated FlowFIle to 'comms.failure'

[ https://issues.apache.org/jira/browse/NIFI-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894798#comment-15894798 ] ASF GitHub Bot commented on NIFI-3553: -- GitHub user markap14 opened a pull request:

[jira] [Updated] (NIFI-3553) FetchFTP can successfully receive data from remote server, then route the updated FlowFIle to 'comms.failure'

[ https://issues.apache.org/jira/browse/NIFI-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-3553: - Status: Patch Available (was: Open) > FetchFTP can successfully receive data from remote server, then

[jira] [Updated] (NIFI-3553) FetchFTP can successfully receive data from remote server, then route the updated FlowFIle to 'comms.failure'

[ https://issues.apache.org/jira/browse/NIFI-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-3553: - Fix Version/s: 1.2.0 > FetchFTP can successfully receive data from remote server, then route the >

[GitHub] nifi pull request #1562: NIFI-3553: If IOException is thrown when completing...

GitHub user markap14 opened a pull request: https://github.com/apache/nifi/pull/1562 NIFI-3553: If IOException is thrown when completing FTP transfer, do … …not update the FlowFile to point to the content that was streamed but instead leave FlowFile pointing to original version

[jira] [Created] (NIFI-3553) FetchFTP can successfully receive data from remote server, then route the updated FlowFIle to 'comms.failure'

Mark Payne created NIFI-3553: Summary: FetchFTP can successfully receive data from remote server, then route the updated FlowFIle to 'comms.failure' Key: NIFI-3553 URL: https://issues.apache.org/jira/browse/NIFI-3553

[jira] [Commented] (NIFI-3543) Add support for using EL when defining 'brokerURL' in jms-cf-service

[ https://issues.apache.org/jira/browse/NIFI-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894660#comment-15894660 ] ASF GitHub Bot commented on NIFI-3543: -- Github user olegz commented on the issue:

[GitHub] nifi issue #1548: NIFI-3543 Fixed a bug that nifi-jms-cf-service cannot have...

Github user olegz commented on the issue: https://github.com/apache/nifi/pull/1548 Thanks you @ShellyLC , will review and merge. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature

[jira] [Updated] (NIFI-3411) Latest "NiFi" Status History data point should only be reported when complete

[ https://issues.apache.org/jira/browse/NIFI-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Gresock updated NIFI-3411: - Fix Version/s: (was: 1.2.0) > Latest "NiFi" Status History data point should only be reported

[jira] [Commented] (NIFI-1449) PutEmail needs more unit tests

[ https://issues.apache.org/jira/browse/NIFI-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894527#comment-15894527 ] ASF GitHub Bot commented on NIFI-1449: -- Github user trixpan commented on a diff in the pull request:

[GitHub] nifi pull request #1553: NIFI-1449 - Migrate PutEmail tests from Mock class ...

Github user trixpan commented on a diff in the pull request: https://github.com/apache/nifi/pull/1553#discussion_r104170950 --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/test/java/org/apache/nifi/processors/standard/TestPutEmail.java --- @@ -230,27

[jira] [Created] (NIFI-3552) Allow migration of templates between process groups

Aldrin Piri created NIFI-3552: - Summary: Allow migration of templates between process groups Key: NIFI-3552 URL: https://issues.apache.org/jira/browse/NIFI-3552 Project: Apache NiFi Issue Type:

[jira] [Commented] (NIFI-3550) Error moving a connection to a PG or a RPG

[ https://issues.apache.org/jira/browse/NIFI-3550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894480#comment-15894480 ] ASF GitHub Bot commented on NIFI-3550: -- Github user asfgit closed the pull request at:

[jira] [Updated] (NIFI-3550) Error moving a connection to a PG or a RPG

[ https://issues.apache.org/jira/browse/NIFI-3550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-3550: -- Resolution: Fixed Fix Version/s: 1.2.0 Status: Resolved (was: Patch Available) >

[jira] [Commented] (NIFI-3550) Error moving a connection to a PG or a RPG

[ https://issues.apache.org/jira/browse/NIFI-3550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894481#comment-15894481 ] ASF GitHub Bot commented on NIFI-3550: -- Github user mcgilman commented on the issue:

[jira] [Commented] (NIFI-3550) Error moving a connection to a PG or a RPG

[ https://issues.apache.org/jira/browse/NIFI-3550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894479#comment-15894479 ] ASF subversion and git services commented on NIFI-3550: --- Commit

[GitHub] nifi issue #1560: [NIFI-3550] inject nf.ConnectionConfiguration into the nf....

Github user mcgilman commented on the issue: https://github.com/apache/nifi/pull/1560 Thanks @scottyaslan! This has been merged to master. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have

[GitHub] nifi pull request #1560: [NIFI-3550] inject nf.ConnectionConfiguration into ...

Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/1560 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Updated] (NIFI-3523) WriteAheadProvenanceRepository fails to initialize properly if it contains an invalid Provenance Event

[ https://issues.apache.org/jira/browse/NIFI-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Zhurakousky updated NIFI-3523: --- Resolution: Fixed Status: Resolved (was: Patch Available) >

[jira] [Commented] (NIFI-3523) WriteAheadProvenanceRepository fails to initialize properly if it contains an invalid Provenance Event

[ https://issues.apache.org/jira/browse/NIFI-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894448#comment-15894448 ] ASF subversion and git services commented on NIFI-3523: --- Commit

[jira] [Updated] (NIFI-3523) WriteAheadProvenanceRepository fails to initialize properly if it contains an invalid Provenance Event

[ https://issues.apache.org/jira/browse/NIFI-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Zhurakousky updated NIFI-3523: --- Fix Version/s: 1.2.0 > WriteAheadProvenanceRepository fails to initialize properly if it

[GitHub] nifi pull request #1542: NIFI-3523: Ensure that if we are unable to read Pro...

Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/1542 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Resolved] (NIFI-3548) Cluster Replication - Issue following MAX_REQUEST failures

[ https://issues.apache.org/jira/browse/NIFI-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-3548. --- Resolution: Fixed Assignee: Mark Payne > Cluster Replication - Issue following MAX_REQUEST

[jira] [Commented] (NIFI-3548) Cluster Replication - Issue following MAX_REQUEST failures

[ https://issues.apache.org/jira/browse/NIFI-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894440#comment-15894440 ] ASF GitHub Bot commented on NIFI-3548: -- Github user olegz commented on the issue:

[GitHub] nifi issue #1555: NIFI-3548: Fixed bug that caused failed requests to not ge...

Github user olegz commented on the issue: https://github.com/apache/nifi/pull/1555 Wow!, I was just about to hit merge myself ;) Race condition ;) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not

[jira] [Commented] (NIFI-3548) Cluster Replication - Issue following MAX_REQUEST failures

[ https://issues.apache.org/jira/browse/NIFI-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894432#comment-15894432 ] ASF subversion and git services commented on NIFI-3548: --- Commit

[GitHub] nifi issue #1555: NIFI-3548: Fixed bug that caused failed requests to not ge...

Github user mcgilman commented on the issue: https://github.com/apache/nifi/pull/1555 Thanks @markap14. This has been merged to master. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[jira] [Commented] (NIFI-3548) Cluster Replication - Issue following MAX_REQUEST failures

[ https://issues.apache.org/jira/browse/NIFI-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894434#comment-15894434 ] ASF GitHub Bot commented on NIFI-3548: -- Github user asfgit closed the pull request at:

[GitHub] nifi pull request #1555: NIFI-3548: Fixed bug that caused failed requests to...

Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/1555 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Updated] (NIFI-3517) If HandleHttpResponse cannot write response, remove entry from HttpContextMap

[ https://issues.apache.org/jira/browse/NIFI-3517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon DeVries updated NIFI-3517: -- Affects Version/s: 0.7.1 > If HandleHttpResponse cannot write response, remove entry from

[jira] [Commented] (NIFI-3550) Error moving a connection to a PG or a RPG

[ https://issues.apache.org/jira/browse/NIFI-3550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894381#comment-15894381 ] ASF GitHub Bot commented on NIFI-3550: -- Github user mcgilman commented on the issue:

[GitHub] nifi issue #1560: [NIFI-3550] inject nf.ConnectionConfiguration into the nf....

Github user mcgilman commented on the issue: https://github.com/apache/nifi/pull/1560 Will Review... --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if

[jira] [Commented] (NIFI-3035) URL to display a particular process group in UI

[ https://issues.apache.org/jira/browse/NIFI-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894380#comment-15894380 ] ASF GitHub Bot commented on NIFI-3035: -- Github user mcgilman commented on the issue:

[GitHub] nifi issue #1559: [NIFI-3035] add deep linking URL to canvas components and ...

Github user mcgilman commented on the issue: https://github.com/apache/nifi/pull/1559 Will Review... --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if

[jira] [Updated] (NIFI-3523) WriteAheadProvenanceRepository fails to initialize properly if it contains an invalid Provenance Event

[ https://issues.apache.org/jira/browse/NIFI-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-3523: - Status: Patch Available (was: In Progress) > WriteAheadProvenanceRepository fails to initialize properly

[jira] [Updated] (NIFI-3523) WriteAheadProvenanceRepository fails to initialize properly if it contains an invalid Provenance Event

[ https://issues.apache.org/jira/browse/NIFI-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-3523: - Status: Patch Available (was: Open) > WriteAheadProvenanceRepository fails to initialize properly if it

[jira] [Updated] (NIFI-3523) WriteAheadProvenanceRepository fails to initialize properly if it contains an invalid Provenance Event

[ https://issues.apache.org/jira/browse/NIFI-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-3523: - Status: Open (was: Patch Available) > WriteAheadProvenanceRepository fails to initialize properly if it

[jira] [Updated] (NIFI-3523) WriteAheadProvenanceRepository fails to initialize properly if it contains an invalid Provenance Event

[ https://issues.apache.org/jira/browse/NIFI-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-3523: - Status: Open (was: Patch Available) > WriteAheadProvenanceRepository fails to initialize properly if it

[jira] [Updated] (NIFI-3523) WriteAheadProvenanceRepository fails to initialize properly if it contains an invalid Provenance Event

[ https://issues.apache.org/jira/browse/NIFI-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-3523: - Status: Open (was: Patch Available) > WriteAheadProvenanceRepository fails to initialize properly if it

[jira] [Updated] (NIFI-3523) WriteAheadProvenanceRepository fails to initialize properly if it contains an invalid Provenance Event

[ https://issues.apache.org/jira/browse/NIFI-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-3523: - Status: Patch Available (was: Open) > WriteAheadProvenanceRepository fails to initialize properly if it

[jira] [Commented] (NIFI-3543) Add support for using EL when defining 'brokerURL' in jms-cf-service

[ https://issues.apache.org/jira/browse/NIFI-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894358#comment-15894358 ] Oleg Zhurakousky commented on NIFI-3543: [~Shelly_LC] I may have missed that but if documentation

[GitHub] nifi pull request #1553: NIFI-1449 - Migrate PutEmail tests from Mock class ...

Github user trixpan commented on a diff in the pull request: https://github.com/apache/nifi/pull/1553#discussion_r104143931 --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/test/java/org/apache/nifi/processors/standard/TestPutEmail.java --- @@ -230,27

[jira] [Commented] (NIFI-1449) PutEmail needs more unit tests

[ https://issues.apache.org/jira/browse/NIFI-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894250#comment-15894250 ] ASF GitHub Bot commented on NIFI-1449: -- Github user trixpan commented on a diff in the pull request:

[jira] [Commented] (NIFI-3204) delete hdfs processor throws an error stating transfer relationship not specified even when all relationships are present

[ https://issues.apache.org/jira/browse/NIFI-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894157#comment-15894157 ] François Prunier commented on NIFI-3204: Hi [~pvillard], Sure, see

[jira] [Commented] (NIFI-3204) delete hdfs processor throws an error stating transfer relationship not specified even when all relationships are present

[ https://issues.apache.org/jira/browse/NIFI-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894153#comment-15894153 ] ASF GitHub Bot commented on NIFI-3204: -- GitHub user francoisprunier opened a pull request:

[GitHub] nifi pull request #1561: NIFI-3204 fix handling deleting a path with a wildc...

GitHub user francoisprunier opened a pull request: https://github.com/apache/nifi/pull/1561 NIFI-3204 fix handling deleting a path with a wildcard when the processor is in… …ssor is invoqued via an incoming flowfile Thank you for submitting a contribution to Apache

[jira] [Commented] (NIFI-1449) PutEmail needs more unit tests

[ https://issues.apache.org/jira/browse/NIFI-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893970#comment-15893970 ] ASF GitHub Bot commented on NIFI-1449: -- Github user trixpan commented on a diff in the pull request:

[GitHub] nifi pull request #1553: NIFI-1449 - Migrate PutEmail tests from Mock class ...

Github user trixpan commented on a diff in the pull request: https://github.com/apache/nifi/pull/1553#discussion_r104114824 --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/test/java/org/apache/nifi/processors/standard/TestPutEmail.java --- @@ -230,27

[GitHub] nifi pull request #1553: NIFI-1449 - Migrate PutEmail tests from Mock class ...

Github user trixpan commented on a diff in the pull request: https://github.com/apache/nifi/pull/1553#discussion_r104113002 --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/test/java/org/apache/nifi/processors/standard/TestPutEmail.java --- @@ -230,27

[jira] [Commented] (NIFI-1449) PutEmail needs more unit tests

[ https://issues.apache.org/jira/browse/NIFI-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893953#comment-15893953 ] ASF GitHub Bot commented on NIFI-1449: -- Github user trixpan commented on a diff in the pull request: