[jira] [Updated] (NIFI-5034) Error in Controller Service with dynamic property in Cluster environment

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

[jira] [Resolved] (NIFI-5043) TailFile opens and never closes readers in Multiple Files mode

[ https://issues.apache.org/jira/browse/NIFI-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne resolved NIFI-5043. -- Resolution: Fixed Fix Version/s: 1.7.0 > TailFile opens and never closes readers in Multiple Files

[jira] [Resolved] (NIFI-4149) Indicate if EL is evaluated against FFs or not

[ https://issues.apache.org/jira/browse/NIFI-4149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne resolved NIFI-4149. -- Resolution: Fixed Fix Version/s: 1.7.0 > Indicate if EL is evaluated against FFs or not >

[jira] [Updated] (NIFI-4857) Record components do not support String <-> byte[] conversions

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

[jira] [Commented] (NIFI-5060) UpdateRecord substringAfter and substringAfterLast only increments by 1

[ https://issues.apache.org/jira/browse/NIFI-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16431092#comment-16431092 ] Mark Payne commented on NIFI-5060: -- [~greenCee] thanks for reporting the bug. I think you

[jira] [Created] (NIFI-5096) When Primary Node changes, occasionally both the new and old primary nodes continue running processors

Mark Payne created NIFI-5096: Summary: When Primary Node changes, occasionally both the new and old primary nodes continue running processors Key: NIFI-5096 URL: https://issues.apache.org/jira/browse/NIFI-5096

[jira] [Updated] (NIFI-5096) When Primary Node changes, occasionally both the new and old primary nodes continue running processors

[ https://issues.apache.org/jira/browse/NIFI-5096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-5096: - Status: Patch Available (was: Open) > When Primary Node changes, occasionally both the new and old primary

[jira] [Updated] (NIFI-5075) Funnels with no outgoing relationship error

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

[jira] [Updated] (NIFI-5075) Funnels with no outgoing relationship error and excessive CPU utilization

[ https://issues.apache.org/jira/browse/NIFI-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-5075: - Summary: Funnels with no outgoing relationship error and excessive CPU utilization (was: Funnels with no o

[jira] [Updated] (NIFI-4185) Add XML record reader & writer services

[ https://issues.apache.org/jira/browse/NIFI-4185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-4185: - Attachment: 0001-NIFI-4185-Minor-tweaks.patch > Add XML record reader & writer services > -

[jira] [Created] (NIFI-5110) Memory Leak when adding/removing processors

Mark Payne created NIFI-5110: Summary: Memory Leak when adding/removing processors Key: NIFI-5110 URL: https://issues.apache.org/jira/browse/NIFI-5110 Project: Apache NiFi Issue Type: Bug

[jira] [Created] (NIFI-5111) When cluster coordinator is changed, it can kick nodes out of the cluster

Mark Payne created NIFI-5111: Summary: When cluster coordinator is changed, it can kick nodes out of the cluster Key: NIFI-5111 URL: https://issues.apache.org/jira/browse/NIFI-5111 Project: Apache NiFi

[jira] [Created] (NIFI-5112) Inefficiency in replicating requests across cluster

Mark Payne created NIFI-5112: Summary: Inefficiency in replicating requests across cluster Key: NIFI-5112 URL: https://issues.apache.org/jira/browse/NIFI-5112 Project: Apache NiFi Issue Type: Bug

[jira] [Updated] (NIFI-4185) Add XML record reader

[ https://issues.apache.org/jira/browse/NIFI-4185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-4185: - Summary: Add XML record reader (was: Add XML record reader & writer services) > Add XML record reader > -

[jira] [Resolved] (NIFI-4185) Add XML record reader & writer services

[ https://issues.apache.org/jira/browse/NIFI-4185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne resolved NIFI-4185. -- Resolution: Fixed Fix Version/s: 1.7.0 > Add XML record reader & writer services > ---

[jira] [Commented] (NIFI-5112) Inefficiency in replicating requests across cluster

[ https://issues.apache.org/jira/browse/NIFI-5112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448772#comment-16448772 ] Mark Payne commented on NIFI-5112: -- I did not capture specific measurements. I did perform

[jira] [Commented] (NIFI-5113) Add XML record writer

[ https://issues.apache.org/jira/browse/NIFI-5113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16452573#comment-16452573 ] Mark Payne commented on NIFI-5113: -- Yeah, that's the biggest issue with dealing with Recor

[jira] [Commented] (NIFI-5119) Pulling changes from Registry does not respect sensitive Informations on Destination

[ https://issues.apache.org/jira/browse/NIFI-5119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16452799#comment-16452799 ] Mark Payne commented on NIFI-5119: -- [~jomach] what version of NiFi are you running into th

[jira] [Updated] (NIFI-5109) AbstractListProcessor stop callING performListing after primary node reelection

[ https://issues.apache.org/jira/browse/NIFI-5109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-5109: - Summary: AbstractListProcessor stop callING performListing after primary node reelection (was: AbstractLis

[jira] [Updated] (NIFI-5109) AbstractListProcessor stop calling performListing after primary node reelection

[ https://issues.apache.org/jira/browse/NIFI-5109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-5109: - Summary: AbstractListProcessor stop calling performListing after primary node reelection (was: AbstractLis

[jira] [Updated] (NIFI-5066) Support enable and disable component action when multiple components selected or when selecting a process group.

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

[jira] [Commented] (NIFI-5119) Pulling changes from Registry does not respect sensitive Informations on Destination

[ https://issues.apache.org/jira/browse/NIFI-5119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16452899#comment-16452899 ] Mark Payne commented on NIFI-5119: -- OK great, [~jomach], I'm glad that you're able to get

[jira] [Updated] (NIFI-1295) Add UI option to interrupt a running processor

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

[jira] [Created] (NIFI-5138) JSON Record Readers providing wrong schema to sub-records when there is a CHOICE of multiple RECORD types

Mark Payne created NIFI-5138: Summary: JSON Record Readers providing wrong schema to sub-records when there is a CHOICE of multiple RECORD types Key: NIFI-5138 URL: https://issues.apache.org/jira/browse/NIFI-5138

[jira] [Updated] (NIFI-5138) JSON Record Readers providing wrong schema to sub-records when there is a CHOICE of multiple RECORD types

[ https://issues.apache.org/jira/browse/NIFI-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-5138: - Description: When the JSON Record Reader is used, if the schema provides a CHOICE of two different RECORD

[jira] [Created] (NIFI-5141) ValidateRecord considers a record invalid if it has an integer value and schema says double, even if strict type checking is disabled

Mark Payne created NIFI-5141: Summary: ValidateRecord considers a record invalid if it has an integer value and schema says double, even if strict type checking is disabled Key: NIFI-5141 URL: https://issues.apache.or

[jira] [Updated] (NIFI-5141) ValidateRecord considers a record invalid if it has an integer value and schema says double, even if strict type checking is disabled

[ https://issues.apache.org/jira/browse/NIFI-5141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-5141: - Labels: Record beginner newbie validation (was: ) > ValidateRecord considers a record invalid if it has an

[jira] [Created] (NIFI-5142) If funnel is made both the source and destination of a connection, connection cannot be removed

Mark Payne created NIFI-5142: Summary: If funnel is made both the source and destination of a connection, connection cannot be removed Key: NIFI-5142 URL: https://issues.apache.org/jira/browse/NIFI-5142 P

[jira] [Updated] (NIFI-5142) If funnel is made both the source and destination of a connection, connection cannot be removed

[ https://issues.apache.org/jira/browse/NIFI-5142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-5142: - Fix Version/s: 1.7.0 Status: Patch Available (was: Open) > If funnel is made both the source an

[jira] [Updated] (NIFI-5138) JSON Record Readers providing wrong schema to sub-records when there is a CHOICE of multiple RECORD types

[ https://issues.apache.org/jira/browse/NIFI-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-5138: - Fix Version/s: 1.7.0 Status: Patch Available (was: Open) > JSON Record Readers providing wrong

[jira] [Updated] (NIFI-4456) Update JSON Record Reader / Writer to allow for 'json per line' format

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

[jira] [Updated] (NIFI-5153) When a node fails to perform a mutable request, it should be asked to rejoin cluster instead of being disconnected

[ https://issues.apache.org/jira/browse/NIFI-5153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-5153: - Issue Type: Improvement (was: Bug) > When a node fails to perform a mutable request, it should be asked to

[jira] [Created] (NIFI-5153) When a node fails to perform a mutable request, it should be asked to rejoin cluster instead of being disconnected

Mark Payne created NIFI-5153: Summary: When a node fails to perform a mutable request, it should be asked to rejoin cluster instead of being disconnected Key: NIFI-5153 URL: https://issues.apache.org/jira/browse/NIFI-

[jira] [Commented] (NIFI-5150) ProcessSession.append resulting in content from wrong FlowFile

[ https://issues.apache.org/jira/browse/NIFI-5150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16464065#comment-16464065 ] Mark Payne commented on NIFI-5150: -- [~peterr] thanks for pointing this out! Definitely an

[jira] [Updated] (NIFI-5150) ProcessSession.append resulting in content from wrong FlowFile

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

[jira] [Updated] (NIFI-5153) When a node fails to perform a mutable request, it should be asked to rejoin cluster instead of being disconnected

[ https://issues.apache.org/jira/browse/NIFI-5153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-5153: - Fix Version/s: 1.7.0 Status: Patch Available (was: Open) > When a node fails to perform a mutab

[jira] [Created] (NIFI-5154) Out of Scope processors can block Controller Services

Mark Payne created NIFI-5154: Summary: Out of Scope processors can block Controller Services Key: NIFI-5154 URL: https://issues.apache.org/jira/browse/NIFI-5154 Project: Apache NiFi Issue Type: B

[jira] [Updated] (NIFI-5154) Out of Scope processors can block Controller Services

[ https://issues.apache.org/jira/browse/NIFI-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-5154: - Fix Version/s: 1.7.0 > Out of Scope processors can block Controller Services >

[jira] [Updated] (NIFI-5154) Out of Scope processors can block Controller Services

[ https://issues.apache.org/jira/browse/NIFI-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-5154: - Status: Patch Available (was: Open) > Out of Scope processors can block Controller Services >

[jira] [Resolved] (NIFI-5069) NiFi clustering: When a node is disconnected due to a failed mutable request it should attempt to rejoin

[ https://issues.apache.org/jira/browse/NIFI-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne resolved NIFI-5069. -- Resolution: Duplicate > NiFi clustering: When a node is disconnected due to a failed mutable request > i

[jira] [Updated] (NIFI-5141) ValidateRecord considers a record invalid if it has an integer value and schema says double, even if strict type checking is disabled

[ https://issues.apache.org/jira/browse/NIFI-5141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-5141: - Fix Version/s: 1.7.0 > ValidateRecord considers a record invalid if it has an integer value and > schema s

[jira] [Updated] (NIFI-5141) ValidateRecord considers a record invalid if it has an integer value and schema says double, even if strict type checking is disabled

[ https://issues.apache.org/jira/browse/NIFI-5141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-5141: - Assignee: Mark Payne Status: Patch Available (was: Open) > ValidateRecord considers a record invalid

[jira] [Updated] (NIFI-5136) Leaked component references preventing GC of components and class loaders

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

[jira] [Created] (NIFI-5181) Update default Provenance Repository to WriteAheadProvenanceRepository

Mark Payne created NIFI-5181: Summary: Update default Provenance Repository to WriteAheadProvenanceRepository Key: NIFI-5181 URL: https://issues.apache.org/jira/browse/NIFI-5181 Project: Apache NiFi

[jira] [Commented] (NIFI-5177) Failed to merge Journal Files leads to LockObtainFailedException: Lock obtain timed out exception

[ https://issues.apache.org/jira/browse/NIFI-5177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470429#comment-16470429 ] Mark Payne commented on NIFI-5177: -- [~AmitC15] I would recommend that you update your inst

[jira] [Created] (NIFI-5194) ConsumeKafka processor can occasionally hang

Mark Payne created NIFI-5194: Summary: ConsumeKafka processor can occasionally hang Key: NIFI-5194 URL: https://issues.apache.org/jira/browse/NIFI-5194 Project: Apache NiFi Issue Type: Bug

[jira] [Updated] (NIFI-5194) ConsumeKafka processor can occasionally hang

[ https://issues.apache.org/jira/browse/NIFI-5194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-5194: - Status: Patch Available (was: Open) > ConsumeKafka processor can occasionally hang > -

[jira] [Resolved] (NIFI-5113) Add XML record writer

[ https://issues.apache.org/jira/browse/NIFI-5113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne resolved NIFI-5113. -- Resolution: Fixed Fix Version/s: 1.7.0 > Add XML record writer > - > >

[jira] [Commented] (NIFI-5200) Nested ProcessSession.read resulting in outer stream being closed.

[ https://issues.apache.org/jira/browse/NIFI-5200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477405#comment-16477405 ] Mark Payne commented on NIFI-5200: -- No, this is not the expected behavior. Will look into

[jira] [Commented] (NIFI-5200) Nested ProcessSession.read resulting in outer stream being closed.

[ https://issues.apache.org/jira/browse/NIFI-5200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477491#comment-16477491 ] Mark Payne commented on NIFI-5200: -- [~peterr] thanks for reporting this. I can confirm tha

[jira] [Updated] (NIFI-5200) Nested ProcessSession.read resulting in outer stream being closed.

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

[jira] [Created] (NIFI-5202) TestListDatabaseTables timing issue

Mark Payne created NIFI-5202: Summary: TestListDatabaseTables timing issue Key: NIFI-5202 URL: https://issues.apache.org/jira/browse/NIFI-5202 Project: Apache NiFi Issue Type: Bug Compo

[jira] [Created] (NIFI-5203) When node is disconnected due to not satisfying a request, logs do not give enough information

Mark Payne created NIFI-5203: Summary: When node is disconnected due to not satisfying a request, logs do not give enough information Key: NIFI-5203 URL: https://issues.apache.org/jira/browse/NIFI-5203 Pr

[jira] [Created] (NIFI-5204) When node joins cluster, if a processor is stopping but cluster says the state is disabled, node ends up in inconsistent state

Mark Payne created NIFI-5204: Summary: When node joins cluster, if a processor is stopping but cluster says the state is disabled, node ends up in inconsistent state Key: NIFI-5204 URL: https://issues.apache.org/jira/

[jira] [Updated] (NIFI-5204) When node joins cluster, if a processor is stopping but cluster says the state is disabled, node ends up in inconsistent state

[ https://issues.apache.org/jira/browse/NIFI-5204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-5204: - Description: In order to make this "easy" to replicate, I did the following: 1) Create a 2-node cluster.

[jira] [Updated] (NIFI-5204) When node joins cluster, if a processor is stopping but cluster says the state is disabled, node ends up in inconsistent state

[ https://issues.apache.org/jira/browse/NIFI-5204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-5204: - Status: Patch Available (was: Open) > When node joins cluster, if a processor is stopping but cluster says

[jira] [Created] (NIFI-5222) With validation being performed asynchronously, updating a processor causes validation to occur 3 times instead of once

Mark Payne created NIFI-5222: Summary: With validation being performed asynchronously, updating a processor causes validation to occur 3 times instead of once Key: NIFI-5222 URL: https://issues.apache.org/jira/browse/

[jira] [Updated] (NIFI-5222) With validation being performed asynchronously, updating a processor causes validation to occur 3 times instead of once

[ https://issues.apache.org/jira/browse/NIFI-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-5222: - Fix Version/s: 1.7.0 Status: Patch Available (was: Open) > With validation being performed asyn

[jira] [Commented] (NIFI-5186) Update UI to account for asynchronous validation

[ https://issues.apache.org/jira/browse/NIFI-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16483881#comment-16483881 ] Mark Payne commented on NIFI-5186: -- Create Pull Request from wrong branch/Jira number. Clo

[jira] [Commented] (NIFI-5225) Leak in RingBufferEventRepository for frequently updated flows

[ https://issues.apache.org/jira/browse/NIFI-5225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16483977#comment-16483977 ] Mark Payne commented on NIFI-5225: -- [~FrederikP] great find! And yes, i do agree there's a

[jira] [Created] (NIFI-5227) When node re-joins cluster, if a processor is in 'validating' state it may fail to start

Mark Payne created NIFI-5227: Summary: When node re-joins cluster, if a processor is in 'validating' state it may fail to start Key: NIFI-5227 URL: https://issues.apache.org/jira/browse/NIFI-5227 Project:

[jira] [Created] (NIFI-5228) Allow user to choose whether or not to add File Attributes as FlowFile Attributes when using FetchFile

Mark Payne created NIFI-5228: Summary: Allow user to choose whether or not to add File Attributes as FlowFile Attributes when using FetchFile Key: NIFI-5228 URL: https://issues.apache.org/jira/browse/NIFI-5228

[jira] [Updated] (NIFI-5228) Allow user to choose whether or not to add File Attributes as FlowFile Attributes when using FetchFile

[ https://issues.apache.org/jira/browse/NIFI-5228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-5228: - Fix Version/s: 1.7.0 Status: Patch Available (was: Open) > Allow user to choose whether or not

[jira] [Commented] (NIFI-5228) Allow user to choose whether or not to add File Attributes as FlowFile Attributes when using FetchFile

[ https://issues.apache.org/jira/browse/NIFI-5228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16484446#comment-16484446 ] Mark Payne commented on NIFI-5228: -- To follow up and close the loop on performance here, a

[jira] [Updated] (NIFI-5228) Allow user to choose whether or not to add File Attributes as FlowFile Attributes when using ListFile

[ https://issues.apache.org/jira/browse/NIFI-5228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-5228: - Summary: Allow user to choose whether or not to add File Attributes as FlowFile Attributes when using ListF

[jira] [Commented] (NIFI-5222) With validation being performed asynchronously, updating a processor causes validation to occur 3 times instead of once

[ https://issues.apache.org/jira/browse/NIFI-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16487537#comment-16487537 ] Mark Payne commented on NIFI-5222: -- [~joewitt] I have pushed another commit that I think w

[jira] [Commented] (NIFI-5225) Leak in RingBufferEventRepository for frequently updated flows

[ https://issues.apache.org/jira/browse/NIFI-5225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16487688#comment-16487688 ] Mark Payne commented on NIFI-5225: -- [~FrederikP] I think you're right - there is certainly

[jira] [Updated] (NIFI-5225) Leak in RingBufferEventRepository for frequently updated flows

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

[jira] [Commented] (NIFI-5171) YandexTranslate Processor Improvement

[ https://issues.apache.org/jira/browse/NIFI-5171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16489558#comment-16489558 ] Mark Payne commented on NIFI-5171: -- [~veteranbv] thanks for the improvement and the fix! C

[jira] [Updated] (NIFI-5171) YandexTranslate Processor Improvement

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

[jira] [Updated] (NIFI-4227) Create a ForkRecord processor

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

[jira] [Updated] (NIFI-5066) Support enable and disable component action when multiple components selected or when selecting a process group.

[ https://issues.apache.org/jira/browse/NIFI-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-5066: - Resolution: Fixed Status: Resolved (was: Patch Available) > Support enable and disable component a

[jira] [Resolved] (NIFI-543) Provide extensions a way to indicate that they can run only on primary node, if clustered

[ https://issues.apache.org/jira/browse/NIFI-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne resolved NIFI-543. - Resolution: Fixed Fix Version/s: 1.7.0 > Provide extensions a way to indicate that they can run only

[jira] [Commented] (NIFI-5222) With validation being performed asynchronously, updating a processor causes validation to occur 3 times instead of once

[ https://issues.apache.org/jira/browse/NIFI-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16491184#comment-16491184 ] Mark Payne commented on NIFI-5222: -- [~joewitt] thanks! Merged to master. > With validatio

[jira] [Updated] (NIFI-5222) With validation being performed asynchronously, updating a processor causes validation to occur 3 times instead of once

[ https://issues.apache.org/jira/browse/NIFI-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-5222: - Resolution: Fixed Status: Resolved (was: Patch Available) > With validation being performed asynch

[jira] [Created] (NIFI-5241) When calculating stats for components, use synchronized methods instead of atomic variables

Mark Payne created NIFI-5241: Summary: When calculating stats for components, use synchronized methods instead of atomic variables Key: NIFI-5241 URL: https://issues.apache.org/jira/browse/NIFI-5241 Proje

[jira] [Commented] (NIFI-4026) SiteToSite Partitioning

[ https://issues.apache.org/jira/browse/NIFI-4026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16496981#comment-16496981 ] Mark Payne commented on NIFI-4026: -- [~pvillard] thanks for bringing this up - it's a nice

[jira] [Updated] (NIFI-5241) When calculating stats for components, use synchronized methods instead of atomic variables

[ https://issues.apache.org/jira/browse/NIFI-5241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-5241: - Fix Version/s: 1.7.0 Status: Patch Available (was: Open) > When calculating stats for componen

[jira] [Reopened] (NIFI-5200) Nested ProcessSession.read resulting in outer stream being closed.

[ https://issues.apache.org/jira/browse/NIFI-5200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne reopened NIFI-5200: -- > Nested ProcessSession.read resulting in outer stream being closed. > -

[jira] [Commented] (NIFI-5200) Nested ProcessSession.read resulting in outer stream being closed.

[ https://issues.apache.org/jira/browse/NIFI-5200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16498116#comment-16498116 ] Mark Payne commented on NIFI-5200: -- Re-Opening Jira as it introduced a new bug. In the ca

[jira] [Updated] (NIFI-5200) Nested ProcessSession.read resulting in outer stream being closed.

[ https://issues.apache.org/jira/browse/NIFI-5200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-5200: - Status: Patch Available (was: Reopened) > Nested ProcessSession.read resulting in outer stream being clos

[jira] [Updated] (NIFI-5200) Nested ProcessSession.read resulting in outer stream being closed.

[ https://issues.apache.org/jira/browse/NIFI-5200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-5200: - Priority: Blocker (was: Minor) > Nested ProcessSession.read resulting in outer stream being closed. > ---

[jira] [Commented] (NIFI-5200) Nested ProcessSession.read resulting in outer stream being closed.

[ https://issues.apache.org/jira/browse/NIFI-5200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16498119#comment-16498119 ] Mark Payne commented on NIFI-5200: -- I've submitted a new PR to address the issue that I n

[jira] [Commented] (NIFI-5200) Nested ProcessSession.read resulting in outer stream being closed.

[ https://issues.apache.org/jira/browse/NIFI-5200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16498121#comment-16498121 ] Mark Payne commented on NIFI-5200: -- Also changed Priority to Blocker, since NiFi should n

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

Mark Payne created NIFI-5265: Summary: Externalize templates from flow.xml.gz Key: NIFI-5265 URL: https://issues.apache.org/jira/browse/NIFI-5265 Project: Apache NiFi Issue Type: Improvement

[jira] [Commented] (NIFI-4026) SiteToSite Partitioning

[ https://issues.apache.org/jira/browse/NIFI-4026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16504800#comment-16504800 ] Mark Payne commented on NIFI-4026: -- [~pvillard] re: persistence of the cluster topology -

[jira] [Created] (NIFI-5279) Wait a bit for components to finish validation on updates

Mark Payne created NIFI-5279: Summary: Wait a bit for components to finish validation on updates Key: NIFI-5279 URL: https://issues.apache.org/jira/browse/NIFI-5279 Project: Apache NiFi Issue Typ

[jira] [Updated] (NIFI-5279) Wait a bit for components to finish validation on updates

[ https://issues.apache.org/jira/browse/NIFI-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-5279: - Description: When a Processor, Reporting Task, or Controller Service is updated, it is now validated async

[jira] [Updated] (NIFI-5279) Wait a bit for components to finish validation on updates

[ https://issues.apache.org/jira/browse/NIFI-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-5279: - Status: Patch Available (was: Open) > Wait a bit for components to finish validation on updates > ---

[jira] [Updated] (NIFI-5279) Wait a bit for components to finish validation on updates

[ https://issues.apache.org/jira/browse/NIFI-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-5279: - Fix Version/s: 1.7.0 > Wait a bit for components to finish validation on updates > ---

[jira] [Created] (NIFI-5281) JSON RecordSetWriter throws NullPointerException if value is not valid according to the schema's CHOICE type

Mark Payne created NIFI-5281: Summary: JSON RecordSetWriter throws NullPointerException if value is not valid according to the schema's CHOICE type Key: NIFI-5281 URL: https://issues.apache.org/jira/browse/NIFI-5281

[jira] [Updated] (NIFI-5281) JSON RecordSetWriter throws NullPointerException if value is not valid according to the schema's CHOICE type

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

[jira] [Assigned] (NIFI-4508) AMQP Processor that uses basicConsume

[ https://issues.apache.org/jira/browse/NIFI-4508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne reassigned NIFI-4508: Assignee: Mark Payne > AMQP Processor that uses basicConsume >

[jira] [Commented] (NIFI-3671) GenerateFlowFile throws NPE in FileSystemRepository

[ https://issues.apache.org/jira/browse/NIFI-3671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15956895#comment-15956895 ] Mark Payne commented on NIFI-3671: -- [~jskora] - thanks for reporting this. I'm hoping that

[jira] [Commented] (NIFI-1280) Create QueryFlowFile Processor

[ https://issues.apache.org/jira/browse/NIFI-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15959473#comment-15959473 ] Mark Payne commented on NIFI-1280: -- I've created a PR that I think is sufficient. There ar

[jira] [Updated] (NIFI-1280) Create QueryFlowFile Processor

[ https://issues.apache.org/jira/browse/NIFI-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-1280: - Attachment: QueryFlowFile_Record_Reader-Writer_Examples.xml > Create QueryFlowFile Processor >

[jira] [Commented] (NIFI-1280) Create QueryFlowFile Processor

[ https://issues.apache.org/jira/browse/NIFI-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15959520#comment-15959520 ] Mark Payne commented on NIFI-1280: -- I've also attached a Template to aid in testing, since

[jira] [Created] (NIFI-3678) NiFi may fail to startup if shutdown while FlowFile Repository partition is full

Mark Payne created NIFI-3678: Summary: NiFi may fail to startup if shutdown while FlowFile Repository partition is full Key: NIFI-3678 URL: https://issues.apache.org/jira/browse/NIFI-3678 Project: Apache

[jira] [Updated] (NIFI-3678) NiFi may fail to startup if shutdown while FlowFile Repository partition is full

[ https://issues.apache.org/jira/browse/NIFI-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-3678: - Description: A user from the users list posted that they are seeing the following stack trace when trying

[jira] [Updated] (NIFI-3678) NiFi may fail to startup if shutdown while FlowFile Repository partition is full

[ https://issues.apache.org/jira/browse/NIFI-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-3678: - Description: A user from the users list posted that they are seeing the following stack trace when trying

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