[jira] [Updated] (NIFI-10279) Increase timeouts in automated tests around NiFi Stateless

[ https://issues.apache.org/jira/browse/NIFI-10279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-10279: -- Status: Patch Available (was: Open) > Increase timeouts in automated tests around NiFi Stateless >

[jira] [Created] (NIFI-10279) Increase timeouts in automated tests around NiFi Stateless

Mark Payne created NIFI-10279: - Summary: Increase timeouts in automated tests around NiFi Stateless Key: NIFI-10279 URL: https://issues.apache.org/jira/browse/NIFI-10279 Project: Apache NiFi

[jira] [Updated] (NIFI-10262) When user chooses to "Enable Controller Services" if any fails to enable, the rest also fail

[ https://issues.apache.org/jira/browse/NIFI-10262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-10262: -- Fix Version/s: 1.17.0 Status: Patch Available (was: Open) > When user chooses to "Enable

[jira] [Updated] (NIFI-10261) When comparing local flow to cluster, all sensitive parameters are detected as changed

[ https://issues.apache.org/jira/browse/NIFI-10261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-10261: -- Fix Version/s: 1.17.0 Status: Patch Available (was: Open) > When comparing local flow to

[jira] [Created] (NIFI-10262) When user chooses to "Enable Controller Services" if any fails to enable, the rest also fail

Mark Payne created NIFI-10262: - Summary: When user chooses to "Enable Controller Services" if any fails to enable, the rest also fail Key: NIFI-10262 URL: https://issues.apache.org/jira/browse/NIFI-10262

[jira] [Created] (NIFI-10261) When comparing local flow to cluster, all sensitive parameters are detected as changed

Mark Payne created NIFI-10261: - Summary: When comparing local flow to cluster, all sensitive parameters are detected as changed Key: NIFI-10261 URL: https://issues.apache.org/jira/browse/NIFI-10261

[jira] [Updated] (NIFI-10246) Node may fail to reconnect to cluster if controller service is in DISABLING state

[ https://issues.apache.org/jira/browse/NIFI-10246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-10246: -- Fix Version/s: 1.17.0 Status: Patch Available (was: Open) > Node may fail to reconnect to

[jira] [Commented] (NIFI-10245) Implement SuperCSV's StrReplace function in the ValidateCsv Processor

[ https://issues.apache.org/jira/browse/NIFI-10245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17568161#comment-17568161 ] Mark Payne commented on NIFI-10245: --- [~john.wise] I would recommend using UpdateRecord for this. Add a

[jira] [Created] (NIFI-10246) Node may fail to reconnect to cluster if controller service is in DISABLING state

Mark Payne created NIFI-10246: - Summary: Node may fail to reconnect to cluster if controller service is in DISABLING state Key: NIFI-10246 URL: https://issues.apache.org/jira/browse/NIFI-10246 Project:

[jira] [Commented] (NIFI-10236) ByteArrayContentRepository in core framework

[ https://issues.apache.org/jira/browse/NIFI-10236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17567381#comment-17567381 ] Mark Payne commented on NIFI-10236: --- Yeah I think it makes more sense to move the

[jira] [Updated] (NIFI-10231) Scripted controller services throw error on configuration restored

[ https://issues.apache.org/jira/browse/NIFI-10231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-10231: -- Fix Version/s: 1.17.0 > Scripted controller services throw error on configuration restored >

[jira] [Updated] (NIFI-10231) Scripted controller services throw error on configuration restored

[ https://issues.apache.org/jira/browse/NIFI-10231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-10231: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Scripted controller services

[jira] [Commented] (NIFI-10203) Multi-connection relationship clone flowfile with same uuid

[ https://issues.apache.org/jira/browse/NIFI-10203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17566020#comment-17566020 ] Mark Payne commented on NIFI-10203: --- Just posted a second PR for this. It looks like the first one

[jira] [Commented] (NIFI-10203) Multi-connection relationship clone flowfile with same uuid

[ https://issues.apache.org/jira/browse/NIFI-10203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17564443#comment-17564443 ] Mark Payne commented on NIFI-10203: --- For clarification about what this affects: I was able to confirm

[jira] [Commented] (NIFI-10203) Multi-connection relationship clone flowfile with same uuid

[ https://issues.apache.org/jira/browse/NIFI-10203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17564437#comment-17564437 ] Mark Payne commented on NIFI-10203: --- Thanks for reporting [~super_dachuan] . I submitted a pull request

[jira] [Updated] (NIFI-10203) Multi-connection relationship clone flowfile with same uuid

[ https://issues.apache.org/jira/browse/NIFI-10203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-10203: -- Fix Version/s: 1.17.0 Status: Patch Available (was: Open) > Multi-connection relationship

[jira] [Assigned] (NIFI-10203) Multi-connection relationship clone flowfile with same uuid

[ https://issues.apache.org/jira/browse/NIFI-10203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne reassigned NIFI-10203: - Assignee: Mark Payne > Multi-connection relationship clone flowfile with same uuid >

[jira] [Updated] (NIFI-10203) Multi-connection relationship clone flowfile with same uuid

[ https://issues.apache.org/jira/browse/NIFI-10203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-10203: -- Priority: Blocker (was: Critical) > Multi-connection relationship clone flowfile with same uuid >

[jira] [Updated] (NIFI-10108) Processor scheduling via parameter

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

[jira] [Resolved] (NIFI-4670) when i start consumerKafka processor more than eleven,all of the processors get into an indefinite stuck state

Title: Message Title Mark Payne resolved

[jira] [Updated] (NIFI-10169) JoinEnrichment merged schema incorrect if first Enrichment record is null

[ https://issues.apache.org/jira/browse/NIFI-10169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-10169: -- Fix Version/s: 1.17.0 Status: Patch Available (was: Open) > JoinEnrichment merged schema

[jira] [Commented] (NIFI-10169) JoinEnrichment merged schema incorrect if first Enrichment record is null

[ https://issues.apache.org/jira/browse/NIFI-10169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17558792#comment-17558792 ] Mark Payne commented on NIFI-10169: --- Attached a Flow Definition (Enrich.json) that replicates the

[jira] [Updated] (NIFI-10169) JoinEnrichment merged schema incorrect if first Enrichment record is null

[ https://issues.apache.org/jira/browse/NIFI-10169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-10169: -- Attachment: Enrich.json > JoinEnrichment merged schema incorrect if first Enrichment record is null >

[jira] [Updated] (NIFI-10169) JoinEnrichment merged schema incorrect if first Enrichment record is null

[ https://issues.apache.org/jira/browse/NIFI-10169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-10169: -- Description: >From the users mailing list: {quote} I am performing some enrichments, and sometimes the

[jira] [Created] (NIFI-10169) JoinEnrichment merged schema incorrect if first Enrichment record is null

Mark Payne created NIFI-10169: - Summary: JoinEnrichment merged schema incorrect if first Enrichment record is null Key: NIFI-10169 URL: https://issues.apache.org/jira/browse/NIFI-10169 Project: Apache

[jira] [Created] (NIFI-10167) Allow tracking of detailed metrics such as CPU Usage by processors

Mark Payne created NIFI-10167: - Summary: Allow tracking of detailed metrics such as CPU Usage by processors Key: NIFI-10167 URL: https://issues.apache.org/jira/browse/NIFI-10167 Project: Apache NiFi

[jira] [Updated] (NIFI-9983) Add new attribute to indicate the routed relation in QueryRecord processor

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

[jira] [Updated] (NIFI-9996) ListFile does not list root directory when Recurse Subdirectories is active and Path Filter is specified

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

[jira] [Resolved] (NIFI-10106) Fix potential NPE in LookupRecord

[ https://issues.apache.org/jira/browse/NIFI-10106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne resolved NIFI-10106. --- Fix Version/s: 1.17.0 Resolution: Fixed > Fix potential NPE in LookupRecord >

[jira] [Updated] (NIFI-10109) Preserve Field Order in JsonTreeReader Map Records

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

[jira] [Updated] (NIFI-10141) JSONRecordSetWriter when unable to write record should convey its schema in log message

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

[jira] [Updated] (NIFI-10148) When Process Group has FlowFile Concurrency of "Single FlowFile Per Node", can occasionally let two FlowFiles in at the same time.

[ https://issues.apache.org/jira/browse/NIFI-10148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-10148: -- Status: Patch Available (was: Open) > When Process Group has FlowFile Concurrency of "Single FlowFile

[jira] [Updated] (NIFI-10148) When Process Group has FlowFile Concurrency of "Single FlowFile Per Node", can occasionally let two FlowFiles in at the same time.

[ https://issues.apache.org/jira/browse/NIFI-10148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-10148: -- Labels: SingleFlowFileConcurrency batch concurrency system-tests (was: ) > When Process Group has

[jira] [Created] (NIFI-10148) When Process Group has FlowFile Concurrency of "Single FlowFile Per Node", can occasionally let two FlowFiles in at the same time.

Mark Payne created NIFI-10148: - Summary: When Process Group has FlowFile Concurrency of "Single FlowFile Per Node", can occasionally let two FlowFiles in at the same time. Key: NIFI-10148 URL:

[jira] [Resolved] (NIFI-8751) Process Group concurrency configuration does not update when deploying to another environment

[ https://issues.apache.org/jira/browse/NIFI-8751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne resolved NIFI-8751. -- Resolution: Information Provided This appears to be due to running too old a version of NiFi Registry.

[jira] [Resolved] (NIFI-5265) Externalize templates from flow.xml.gz

[ https://issues.apache.org/jira/browse/NIFI-5265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne resolved NIFI-5265. -- Resolution: Won't Do Templates are expected to be removed in 2.0 > Externalize templates from

[jira] [Resolved] (NIFI-6900) Request to retrieve flow in clustered environment should be much less expensive

[ https://issues.apache.org/jira/browse/NIFI-6900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne resolved NIFI-6900. -- Fix Version/s: 1.15.0 Resolution: Fixed > Request to retrieve flow in clustered environment

[jira] [Resolved] (NIFI-9361) Node can fail to DELETE connection while others finish if upstream component is funnel

[ https://issues.apache.org/jira/browse/NIFI-9361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne resolved NIFI-9361. -- Resolution: Duplicate > Node can fail to DELETE connection while others finish if upstream component >

[jira] [Resolved] (NIFI-7940) Create a ScriptedPartitionRecord

[ https://issues.apache.org/jira/browse/NIFI-7940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne resolved NIFI-7940. -- Resolution: Duplicate > Create a ScriptedPartitionRecord > > >

[jira] [Created] (NIFI-10142) ListSFTP assumes that time on SFTP server is the same as the time on local server

Mark Payne created NIFI-10142: - Summary: ListSFTP assumes that time on SFTP server is the same as the time on local server Key: NIFI-10142 URL: https://issues.apache.org/jira/browse/NIFI-10142 Project:

[jira] [Created] (NIFI-10141) JSONRecordSetWriter when unable to write record should convey its schema in log message

Mark Payne created NIFI-10141: - Summary: JSONRecordSetWriter when unable to write record should convey its schema in log message Key: NIFI-10141 URL: https://issues.apache.org/jira/browse/NIFI-10141

[jira] [Updated] (NIFI-10141) JSONRecordSetWriter when unable to write record should convey its schema in log message

[ https://issues.apache.org/jira/browse/NIFI-10141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-10141: -- Issue Type: Improvement (was: Bug) > JSONRecordSetWriter when unable to write record should convey

[jira] [Updated] (NIFI-9347) Unreliable or brittle persistent provenance repo test

[ https://issues.apache.org/jira/browse/NIFI-9347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-9347: - Assignee: Mark Payne Status: Patch Available (was: Open) > Unreliable or brittle persistent

[jira] [Commented] (NIFI-10111) When unpacking NARs, provide ability to unpack into uber jar to avoid using too many open file handles

[ https://issues.apache.org/jira/browse/NIFI-10111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552869#comment-17552869 ] Mark Payne commented on NIFI-10111: --- For comparison purposes, running on {{main}} branch, with all nar

[jira] [Updated] (NIFI-10111) When unpacking NARs, provide ability to unpack into uber jar to avoid using too many open file handles

[ https://issues.apache.org/jira/browse/NIFI-10111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-10111: -- Fix Version/s: 1.17.0 > When unpacking NARs, provide ability to unpack into uber jar to avoid using >

[jira] [Updated] (NIFI-10111) When unpacking NARs, provide ability to unpack into uber jar to avoid using too many open file handles

[ https://issues.apache.org/jira/browse/NIFI-10111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-10111: -- Status: Patch Available (was: Open) > When unpacking NARs, provide ability to unpack into uber jar to

[jira] [Created] (NIFI-10111) When unpacking NARs, provide ability to unpack into uber jar to avoid using too many open file handles

Mark Payne created NIFI-10111: - Summary: When unpacking NARs, provide ability to unpack into uber jar to avoid using too many open file handles Key: NIFI-10111 URL: https://issues.apache.org/jira/browse/NIFI-10111

[jira] [Commented] (NIFI-10070) NiFi fails to delete/update component because it's still running, immediately after confirming that the component is stopped.

[ https://issues.apache.org/jira/browse/NIFI-10070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552373#comment-17552373 ] Mark Payne commented on NIFI-10070: --- After reviewing this, I think the {{ProcessorEntityMerger}} may

[jira] [Updated] (NIFI-10093) Automated Test Failure on SocketProtocolListenerTest

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

[jira] [Resolved] (NIFI-10074) PutSmbFile.customValidate may throw UnsupportedOperationException

[ https://issues.apache.org/jira/browse/NIFI-10074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne resolved NIFI-10074. --- Fix Version/s: 1.17.0 Resolution: Fixed > PutSmbFile.customValidate may throw

[jira] [Updated] (NIFI-10070) NiFi fails to delete/update component because it's still running, immediately after confirming that the component is stopped.

[ https://issues.apache.org/jira/browse/NIFI-10070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-10070: -- Labels: clustering entity merging response (was: ) > NiFi fails to delete/update component because

[jira] [Created] (NIFI-10070) NiFi fails to delete/update component because it's still running, immediately after confirming that the component is stopped.

Mark Payne created NIFI-10070: - Summary: NiFi fails to delete/update component because it's still running, immediately after confirming that the component is stopped. Key: NIFI-10070 URL:

[jira] [Commented] (NIFI-9825) Execution "Primary node" with incoming connections limitation bug

[ https://issues.apache.org/jira/browse/NIFI-9825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17544379#comment-17544379 ] Mark Payne commented on NIFI-9825: -- [~jzahner] ExecuteSQL will not route any FlowFile to 'failure' except

[jira] [Updated] (NIFI-10059) Controller service could incorrectly be removed from cache

[ https://issues.apache.org/jira/browse/NIFI-10059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-10059: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Controller service could

[jira] [Updated] (NIFI-10059) Controller service could incorrectly be removed from cache

[ https://issues.apache.org/jira/browse/NIFI-10059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-10059: -- Fix Version/s: 1.17.0 > Controller service could incorrectly be removed from cache >

[jira] [Created] (NIFI-10063) Intermittent test failure in RemoteProcessGroupIT

Mark Payne created NIFI-10063: - Summary: Intermittent test failure in RemoteProcessGroupIT Key: NIFI-10063 URL: https://issues.apache.org/jira/browse/NIFI-10063 Project: Apache NiFi Issue Type:

[jira] [Commented] (NIFI-10048) Apache Nifi Web Server keeps failing to start

[ https://issues.apache.org/jira/browse/NIFI-10048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17542060#comment-17542060 ] Mark Payne commented on NIFI-10048: --- [~andyadamides] any chance the flow is something that you can

[jira] [Updated] (NIFI-10052) Avoid obtaining any locks when creating/sending heartbeats

[ https://issues.apache.org/jira/browse/NIFI-10052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-10052: -- Labels: cluster heartbeat stability (was: ) > Avoid obtaining any locks when creating/sending

[jira] [Created] (NIFI-10052) Avoid obtaining any locks when creating/sending heartbeats

Mark Payne created NIFI-10052: - Summary: Avoid obtaining any locks when creating/sending heartbeats Key: NIFI-10052 URL: https://issues.apache.org/jira/browse/NIFI-10052 Project: Apache NiFi

[jira] [Updated] (NIFI-10050) When copying & pasting a Process Group, if a Controller Service references a parent group's CS, that reference is dropped

[ https://issues.apache.org/jira/browse/NIFI-10050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-10050: -- Fix Version/s: 1.17.0 Status: Patch Available (was: Open) > When copying & pasting a

[jira] [Updated] (NIFI-10051) When a Controller Service is removed, its state should be cleared in a background thread

[ https://issues.apache.org/jira/browse/NIFI-10051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-10051: -- Fix Version/s: 1.17.0 Assignee: Mark Payne Status: Patch Available (was: Open) >

[jira] [Created] (NIFI-10051) When a Controller Service is removed, its state should be cleared in a background thread

Mark Payne created NIFI-10051: - Summary: When a Controller Service is removed, its state should be cleared in a background thread Key: NIFI-10051 URL: https://issues.apache.org/jira/browse/NIFI-10051

[jira] [Created] (NIFI-10050) When copying & pasting a Process Group, if a Controller Service references a parent group's CS, that reference is dropped

Mark Payne created NIFI-10050: - Summary: When copying & pasting a Process Group, if a Controller Service references a parent group's CS, that reference is dropped Key: NIFI-10050 URL:

[jira] [Created] (NIFI-10049) Reporting Tasks can report a scheduled state of STOPPED with 0 threads and then get triggered

Mark Payne created NIFI-10049: - Summary: Reporting Tasks can report a scheduled state of STOPPED with 0 threads and then get triggered Key: NIFI-10049 URL: https://issues.apache.org/jira/browse/NIFI-10049

[jira] [Updated] (NIFI-9958) Add Framework Support for Sensitive Dynamic Properties

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

[jira] [Updated] (NIFI-10038) Add Java 17 Platform to System Tests Workflow

[ https://issues.apache.org/jira/browse/NIFI-10038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-10038: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Add Java 17 Platform to System

[jira] [Created] (NIFI-10037) Improve System Tests Resilience when one test fails

Mark Payne created NIFI-10037: - Summary: Improve System Tests Resilience when one test fails Key: NIFI-10037 URL: https://issues.apache.org/jira/browse/NIFI-10037 Project: Apache NiFi Issue

[jira] [Updated] (NIFI-10031) Downgrade Jakarta Mail to 1.6.7 in Bootstrap

[ https://issues.apache.org/jira/browse/NIFI-10031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-10031: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Downgrade Jakarta Mail to 1.6.7

[jira] [Resolved] (NIFI-9895) Allow parameters to reference controller services

[ https://issues.apache.org/jira/browse/NIFI-9895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne resolved NIFI-9895. -- Fix Version/s: 1.17.0 Assignee: Tamas Palfy Resolution: Fixed > Allow parameters to

[jira] [Commented] (NIFI-10015) PutHDFS has so many daemon thread "LeaseRenewer"

[ https://issues.apache.org/jira/browse/NIFI-10015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17537547#comment-17537547 ] Mark Payne commented on NIFI-10015: --- That would explain it. Looks like we are currently pointing to

[jira] [Updated] (NIFI-9853) On startup, and when importing flow from registry/file, component states not synchronized properly.

[ https://issues.apache.org/jira/browse/NIFI-9853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-9853: - Fix Version/s: 1.17.0 > On startup, and when importing flow from registry/file, component states not >

[jira] [Updated] (NIFI-10023) FileSystemRepository improperly tracks file archival count

[ https://issues.apache.org/jira/browse/NIFI-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-10023: -- Status: Patch Available (was: Open) > FileSystemRepository improperly tracks file archival count >

[jira] [Assigned] (NIFI-10023) FileSystemRepository improperly tracks file archival count

[ https://issues.apache.org/jira/browse/NIFI-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne reassigned NIFI-10023: - Assignee: Mark Payne > FileSystemRepository improperly tracks file archival count >

[jira] [Created] (NIFI-10023) FileSystemRepository improperly tracks file archival count

Mark Payne created NIFI-10023: - Summary: FileSystemRepository improperly tracks file archival count Key: NIFI-10023 URL: https://issues.apache.org/jira/browse/NIFI-10023 Project: Apache NiFi

[jira] [Commented] (NIFI-10015) PutHDFS has so many daemon thread "LeaseRenewer"

[ https://issues.apache.org/jira/browse/NIFI-10015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17534923#comment-17534923 ] Mark Payne commented on NIFI-10015: --- [~Hadi] how many Get/List/Fetch/Put HDFS processors do you

[jira] [Created] (NIFI-10004) Stateless NiFi does not allow loading of .class files in the root class loader

Mark Payne created NIFI-10004: - Summary: Stateless NiFi does not allow loading of .class files in the root class loader Key: NIFI-10004 URL: https://issues.apache.org/jira/browse/NIFI-10004 Project:

[jira] [Updated] (NIFI-9993) Processors cannot write to Content Repo: Unable to write flowfile content to content repository container default due to archive file size constraints; waiting for archive

[ https://issues.apache.org/jira/browse/NIFI-9993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-9993: - Fix Version/s: 1.17.0 Status: Patch Available (was: Open) > Processors cannot write to

[jira] [Commented] (NIFI-9993) Processors cannot write to Content Repo: Unable to write flowfile content to content repository container default due to archive file size constraints; waiting for archi

[ https://issues.apache.org/jira/browse/NIFI-9993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17532514#comment-17532514 ] Mark Payne commented on NIFI-9993: -- After analyzing, I have been able to draw the following conclusions:

[jira] [Created] (NIFI-9993) Processors cannot write to Content Repo: Unable to write flowfile content to content repository container default due to archive file size constraints; waiting for archive

Mark Payne created NIFI-9993: Summary: Processors cannot write to Content Repo: Unable to write flowfile content to content repository container default due to archive file size constraints; waiting for archive cleanup Key:

[jira] [Commented] (NIFI-4670) when i start consumerKafka processor more than eleven,all of the processors get into an indefinite stuck state

[ https://issues.apache.org/jira/browse/NIFI-4670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17532506#comment-17532506 ] Mark Payne commented on NIFI-4670: -- [~clearlove] just came across this Jira. Is 5 years old. Guessing

[jira] [Resolved] (NIFI-8340) If content repository is filling up, create bulletin when exerting backpressure

[ https://issues.apache.org/jira/browse/NIFI-8340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne resolved NIFI-8340. -- Fix Version/s: 1.16.0 Resolution: Fixed > If content repository is filling up, create bulletin

[jira] [Updated] (NIFI-8481) NIFI should display some warnings/errors when (a) all timer driven threads are blocked (b) Content Repository at 100%

[ https://issues.apache.org/jira/browse/NIFI-8481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-8481: - Fix Version/s: 1.16.0 > NIFI should display some warnings/errors when (a) all timer driven threads > are

[jira] [Commented] (NIFI-9981) Add Avro UUID support to the record API

[ https://issues.apache.org/jira/browse/NIFI-9981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531731#comment-17531731 ] Mark Payne commented on NIFI-9981: -- Hey [~mike.thomsen] can you explain the benefits / reasoning behind

[jira] [Updated] (NIFI-9615) Extending the capabilities of the NAR provider functionality

[ https://issues.apache.org/jira/browse/NIFI-9615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-9615: - Fix Version/s: 1.17.0 > Extending the capabilities of the NAR provider functionality >

[jira] [Updated] (NIFI-9938) Correct error message for PublishKafkaRecord_2_6 and PublishKafka_2_6

[ https://issues.apache.org/jira/browse/NIFI-9938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-9938: - Affects Version/s: 1.15.3 1.15.2 1.15.1

[jira] [Resolved] (NIFI-9938) Correct error message for PublishKafkaRecord_2_6 and PublishKafka_2_6

[ https://issues.apache.org/jira/browse/NIFI-9938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne resolved NIFI-9938. -- Fix Version/s: 1.17.0 Resolution: Fixed > Correct error message for PublishKafkaRecord_2_6

[jira] [Created] (NIFI-9940) Update the StandardProcessGroupSynchronizer so that it can synchronize other components

Mark Payne created NIFI-9940: Summary: Update the StandardProcessGroupSynchronizer so that it can synchronize other components Key: NIFI-9940 URL: https://issues.apache.org/jira/browse/NIFI-9940 Project:

[jira] [Updated] (NIFI-9926) Allow NiFi to automatically layout components within a Process Group

[ https://issues.apache.org/jira/browse/NIFI-9926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-9926: - Status: Patch Available (was: Open) > Allow NiFi to automatically layout components within a Process

[jira] [Created] (NIFI-9926) Allow NiFi to automatically layout components within a Process Group

Mark Payne created NIFI-9926: Summary: Allow NiFi to automatically layout components within a Process Group Key: NIFI-9926 URL: https://issues.apache.org/jira/browse/NIFI-9926 Project: Apache NiFi

[jira] [Updated] (NIFI-9893) Ensure orderly cluster node removal on node delete via UI

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

[jira] [Updated] (NIFI-9832) XMLReader: XML element's content disappears if the element has attribute

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

[jira] [Updated] (NIFI-9871) Error Messages Repeat Stack Trace Causes

[ https://issues.apache.org/jira/browse/NIFI-9871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-9871: - Fix Version/s: (was: 1.16.1) > Error Messages Repeat Stack Trace Causes >

[jira] [Updated] (NIFI-9871) Error Messages Repeat Stack Trace Causes

[ https://issues.apache.org/jira/browse/NIFI-9871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-9871: - Fix Version/s: 1.16.1 > Error Messages Repeat Stack Trace Causes >

[jira] [Updated] (NIFI-9871) Error Messages Repeat Stack Trace Causes

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

[jira] [Updated] (NIFI-9910) CSVRecordLookupService assumes key is a String

[ https://issues.apache.org/jira/browse/NIFI-9910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-9910: - Fix Version/s: 1.17.0 1.16.1 Status: Patch Available (was: Open) >

[jira] [Created] (NIFI-9910) CSVRecordLookupService assumes key is a String

Mark Payne created NIFI-9910: Summary: CSVRecordLookupService assumes key is a String Key: NIFI-9910 URL: https://issues.apache.org/jira/browse/NIFI-9910 Project: Apache NiFi Issue Type: Bug

[jira] [Commented] (NIFI-9903) LookupRecord doesn't add results to any Records if first Record doesn't have a match

[ https://issues.apache.org/jira/browse/NIFI-9903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17520746#comment-17520746 ] Mark Payne commented on NIFI-9903: -- [~Steve Hindmarch] no, the issue is that if the first record doesn't

[jira] [Updated] (NIFI-9903) LookupRecord doesn't add results to any Records if first Record doesn't have a match

[ https://issues.apache.org/jira/browse/NIFI-9903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-9903: - Status: Patch Available (was: Open) > LookupRecord doesn't add results to any Records if first Record

[jira] [Created] (NIFI-9903) LookupRecord doesn't add results to any Records if first Record doesn't have a match

Mark Payne created NIFI-9903: Summary: LookupRecord doesn't add results to any Records if first Record doesn't have a match Key: NIFI-9903 URL: https://issues.apache.org/jira/browse/NIFI-9903 Project:

[jira] [Updated] (NIFI-9903) LookupRecord doesn't add results to any Records if first Record doesn't have a match

[ https://issues.apache.org/jira/browse/NIFI-9903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-9903: - Fix Version/s: 1.16.1 > LookupRecord doesn't add results to any Records if first Record doesn't have > a

<    1   2   3   4   5   6   7   8   9   10   >