[jira] [Updated] (NIFI-5997) If swap file written but FlowFile Repository fails to update, connection queue counts wrong and flowfiles are duplicated upon restart

[ https://issues.apache.org/jira/browse/NIFI-5997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall updated NIFI-5997: --- Affects Version/s: 1.8.0 1.7.1 > If swap file written but FlowFile Repo

[jira] [Commented] (NIFI-5997) If swap file written but FlowFile Repository fails to update, connection queue counts wrong and flowfiles are duplicated upon restart

[ https://issues.apache.org/jira/browse/NIFI-5997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16807789#comment-16807789 ] Joseph Percivall commented on NIFI-5997: Sounds good thanks [~markap14]. That alig

[jira] [Commented] (NIFI-5997) If swap file written but FlowFile Repository fails to update, connection queue counts wrong and flowfiles are duplicated upon restart

[ https://issues.apache.org/jira/browse/NIFI-5997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16801183#comment-16801183 ] Joseph Percivall commented on NIFI-5997: [~markap14] do you know which versions th

[jira] [Created] (NIFI-6096) ValidateRecord does not handle nested Map type correctly

Joseph Percivall created NIFI-6096: -- Summary: ValidateRecord does not handle nested Map type correctly Key: NIFI-6096 URL: https://issues.apache.org/jira/browse/NIFI-6096 Project: Apache NiFi

[jira] [Commented] (NIFI-5678) ValidateRecord does not handle Map type correctly

[ https://issues.apache.org/jira/browse/NIFI-5678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16782454#comment-16782454 ] Joseph Percivall commented on NIFI-5678: [~joewitt] yeah I debated about creating

[jira] [Assigned] (NIFIREG-232) Support in-place migration between flow persistence providers

[ https://issues.apache.org/jira/browse/NIFIREG-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall reassigned NIFIREG-232: Assignee: Joseph Percivall (was: Bryan Rosander) > Support in-place migration be

[jira] [Assigned] (NIFIREG-232) Support in-place migration between flow persistence providers

[ https://issues.apache.org/jira/browse/NIFIREG-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall reassigned NIFIREG-232: Assignee: Bryan Rosander > Support in-place migration between flow persistence pr

[jira] [Assigned] (NIFIREG-232) Support in-place migration between flow persistence providers

[ https://issues.apache.org/jira/browse/NIFIREG-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall reassigned NIFIREG-232: Assignee: Bryan Rosander (was: Joseph Percivall) > Support in-place migration be

[jira] [Commented] (NIFI-5678) ValidateRecord does not handle Map type correctly

[ https://issues.apache.org/jira/browse/NIFI-5678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16781299#comment-16781299 ] Joseph Percivall commented on NIFI-5678: [~mattyb149] I just attempted to do this

[jira] [Updated] (NIFI-5678) ValidateRecord does not handle Map type correctly

[ https://issues.apache.org/jira/browse/NIFI-5678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall updated NIFI-5678: --- Attachment: Nested_map_record_failing_validation.xml > ValidateRecord does not handle Map type

[jira] [Commented] (NIFI-6036) If a Processor is intended to be running but is invalid when NiFi starts, it cannot be udpated.

[ https://issues.apache.org/jira/browse/NIFI-6036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16775967#comment-16775967 ] Joseph Percivall commented on NIFI-6036: [~markap14] do we know the affects versio

[jira] [Updated] (NIFI-5172) PutElasticsearchHttpRecord does not handle failed records individually

[ https://issues.apache.org/jira/browse/NIFI-5172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall updated NIFI-5172: --- Summary: PutElasticsearchHttpRecord does not handle failed records individually (was: PutElas

[jira] [Updated] (NIFI-5172) PutElasticSearchRecord does to fail individual recods

[ https://issues.apache.org/jira/browse/NIFI-5172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall updated NIFI-5172: --- Status: Patch Available (was: Open) PR up here: https://github.com/apache/nifi/pull/3299 > P

[jira] [Assigned] (NIFI-5172) PutElasticSearchRecord does to fail individual recods

[ https://issues.apache.org/jira/browse/NIFI-5172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall reassigned NIFI-5172: -- Assignee: Joseph Percivall > PutElasticSearchRecord does to fail individual recods > --

[jira] [Commented] (NIFI-5922) NiFi-Fn, an alternative runtime for NiFi flows

[ https://issues.apache.org/jira/browse/NIFI-5922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16753689#comment-16753689 ] Joseph Percivall commented on NIFI-5922: For tracking, an initial discussion threa

[jira] [Created] (NIFI-5936) MockProcessSession remove() does not report a "DROP" provenance event

Joseph Percivall created NIFI-5936: -- Summary: MockProcessSession remove() does not report a "DROP" provenance event Key: NIFI-5936 URL: https://issues.apache.org/jira/browse/NIFI-5936 Project: Apache

[jira] [Resolved] (NIFI-5811) Need Scallable Open Source Platform

[ https://issues.apache.org/jira/browse/NIFI-5811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall resolved NIFI-5811. Resolution: Invalid > Need Scallable Open Source Platform >

[jira] [Commented] (NIFI-5172) PutElasticSearchRecord does to fail individual recods

[ https://issues.apache.org/jira/browse/NIFI-5172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16700967#comment-16700967 ] Joseph Percivall commented on NIFI-5172: I ran into this issue today and I assumed

[jira] [Commented] (NIFI-5775) DataTypeUtils "toString" incorrectly treats value as a "byte" when passing an array leading to ClassCastException

[ https://issues.apache.org/jira/browse/NIFI-5775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16679155#comment-16679155 ] Joseph Percivall commented on NIFI-5775: [~sivaprasanna] this can be replicated in

[jira] [Created] (NIFI-5775) DataTypeUtils "toString" incorrectly treats value as a "byte" when passing an array leading to ClassCastException

Joseph Percivall created NIFI-5775: -- Summary: DataTypeUtils "toString" incorrectly treats value as a "byte" when passing an array leading to ClassCastException Key: NIFI-5775 URL: https://issues.apache.org/jira/b

[jira] [Assigned] (NIFI-5765) WriteJsonResult fails with Class Cast Exception when Choice data type resolves to Array

[ https://issues.apache.org/jira/browse/NIFI-5765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall reassigned NIFI-5765: -- Assignee: Joseph Percivall > WriteJsonResult fails with Class Cast Exception when Choic

[jira] [Updated] (NIFI-5765) WriteJsonResult fails with Class Cast Exception when Choice data type resolves to Array

[ https://issues.apache.org/jira/browse/NIFI-5765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall updated NIFI-5765: --- Affects Version/s: 1.8.0 > WriteJsonResult fails with Class Cast Exception when Choice data ty

[jira] [Created] (NIFI-5765) WriteJsonResult fails with Class Cast Exception when Choice data type resolves to Array

Joseph Percivall created NIFI-5765: -- Summary: WriteJsonResult fails with Class Cast Exception when Choice data type resolves to Array Key: NIFI-5765 URL: https://issues.apache.org/jira/browse/NIFI-5765

[jira] [Commented] (NIFI-3792) A processor to facilitate retrying FlowFiles

[ https://issues.apache.org/jira/browse/NIFI-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16653813#comment-16653813 ] Joseph Percivall commented on NIFI-3792: Hey [~patricker], I actually have a worki

[jira] [Created] (NIFI-5703) SyslogParser regex fails to handle messages that end with Windows style new line

Joseph Percivall created NIFI-5703: -- Summary: SyslogParser regex fails to handle messages that end with Windows style new line Key: NIFI-5703 URL: https://issues.apache.org/jira/browse/NIFI-5703 Pro

[jira] [Commented] (NIFI-5694) StandardSSLContextService references configContext in a non-thread safe manner

[ https://issues.apache.org/jira/browse/NIFI-5694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16648112#comment-16648112 ] Joseph Percivall commented on NIFI-5694: FYI, I originally had another comment in

[jira] [Updated] (NIFI-5694) StandardSSLContextService references configContext in a non-thread safe manner

[ https://issues.apache.org/jira/browse/NIFI-5694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall updated NIFI-5694: --- Description: configContext is a variable which is accessed from many different threads (valid

[jira] [Created] (NIFI-5694) StandardSSLContextService references configContext in a non-thread safe manner

Joseph Percivall created NIFI-5694: -- Summary: StandardSSLContextService references configContext in a non-thread safe manner Key: NIFI-5694 URL: https://issues.apache.org/jira/browse/NIFI-5694 Projec

[jira] [Created] (NIFI-5692) InvokeHttp fails to initialize if SSL context doesn't have truststore set

Joseph Percivall created NIFI-5692: -- Summary: InvokeHttp fails to initialize if SSL context doesn't have truststore set Key: NIFI-5692 URL: https://issues.apache.org/jira/browse/NIFI-5692 Project: Ap

[jira] [Created] (NIFI-5606) UpdateRecord doesn't allow population of nested fields if input parent is null

Joseph Percivall created NIFI-5606: -- Summary: UpdateRecord doesn't allow population of nested fields if input parent is null Key: NIFI-5606 URL: https://issues.apache.org/jira/browse/NIFI-5606 Projec

[jira] [Updated] (NIFI-5084) Add GenerateRecord processor to create dummy data

[ https://issues.apache.org/jira/browse/NIFI-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall updated NIFI-5084: --- Summary: Add GenerateRecord processor to create dummy data (was: Add GenerateRecord processor

[jira] [Created] (NIFI-5509) Changing an RPG URL does not log a config change event

Joseph Percivall created NIFI-5509: -- Summary: Changing an RPG URL does not log a config change event Key: NIFI-5509 URL: https://issues.apache.org/jira/browse/NIFI-5509 Project: Apache NiFi

[jira] [Commented] (NIFI-5474) ReplaceText RegexReplace evaluates payload as Expression language

[ https://issues.apache.org/jira/browse/NIFI-5474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16564030#comment-16564030 ] Joseph Percivall commented on NIFI-5474: Yup, thanks [~ottobackwards] ! > Replace

[jira] [Commented] (NIFI-5474) ReplaceText RegexReplace evaluates payload as Expression language

[ https://issues.apache.org/jira/browse/NIFI-5474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16564014#comment-16564014 ] Joseph Percivall commented on NIFI-5474: Yup, the "embedded" EL in the content bei

[jira] [Created] (NIFI-5474) ReplaceText RegexReplace evaluates payload as Expression language

Joseph Percivall created NIFI-5474: -- Summary: ReplaceText RegexReplace evaluates payload as Expression language Key: NIFI-5474 URL: https://issues.apache.org/jira/browse/NIFI-5474 Project: Apache NiF

[jira] [Updated] (NIFI-4362) Prometheus Reporting Task

[ https://issues.apache.org/jira/browse/NIFI-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall updated NIFI-4362: --- Priority: Minor (was: Trivial) > Prometheus Reporting Task > - > >

[jira] [Updated] (NIFI-4362) Prometheus Reporting Task

[ https://issues.apache.org/jira/browse/NIFI-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall updated NIFI-4362: --- Issue Type: New Feature (was: Task) > Prometheus Reporting Task > - >

[jira] [Updated] (NIFI-4362) Prometheus Reporting Task

[ https://issues.apache.org/jira/browse/NIFI-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall updated NIFI-4362: --- Affects Version/s: (was: 1.3.0) > Prometheus Reporting Task > - >

[jira] [Resolved] (NIFI-5457) apache/nifi:1.7.1 Dockerhub image uses NiFi 1.7.0

[ https://issues.apache.org/jira/browse/NIFI-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall resolved NIFI-5457. Resolution: Fixed Not a problem, thanks for the assist [~aldrin] > apache/nifi:1.7.1 Docker

[jira] [Commented] (NIFI-5457) apache/nifi:1.7.1 Dockerhub image uses NiFi 1.7.0

[ https://issues.apache.org/jira/browse/NIFI-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16556402#comment-16556402 ] Joseph Percivall commented on NIFI-5457: [~aldrin] done > apache/nifi:1.7.1 Docke

[jira] [Commented] (NIFI-5457) apache/nifi:1.7.1 Dockerhub image uses NiFi 1.7.0

[ https://issues.apache.org/jira/browse/NIFI-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16556399#comment-16556399 ] Joseph Percivall commented on NIFI-5457: Ah yup, can do > apache/nifi:1.7.1 Docke

[jira] [Resolved] (NIFI-5457) apache/nifi:1.7.1 Dockerhub image uses NiFi 1.7.0

[ https://issues.apache.org/jira/browse/NIFI-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall resolved NIFI-5457. Resolution: Fixed > apache/nifi:1.7.1 Dockerhub image uses NiFi 1.7.0 >

[jira] [Commented] (NIFI-5457) apache/nifi:1.7.1 Dockerhub image uses NiFi 1.7.0

[ https://issues.apache.org/jira/browse/NIFI-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16556350#comment-16556350 ] Joseph Percivall commented on NIFI-5457: [~aldrin] I checked out rel/nifi-1.7.1, c

[jira] [Assigned] (NIFI-5457) apache/nifi:1.7.1 Dockerhub image uses NiFi 1.7.0

[ https://issues.apache.org/jira/browse/NIFI-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall reassigned NIFI-5457: -- Assignee: Joseph Percivall > apache/nifi:1.7.1 Dockerhub image uses NiFi 1.7.0 > --

[jira] [Commented] (NIFI-5457) apache/nifi:1.7.1 Dockerhub image uses NiFi 1.7.0

[ https://issues.apache.org/jira/browse/NIFI-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16556311#comment-16556311 ] Joseph Percivall commented on NIFI-5457: Ok cool, I'll work on overwriting the ima

[jira] [Commented] (NIFI-5457) apache/nifi:1.7.1 Dockerhub image uses NiFi 1.7.0

[ https://issues.apache.org/jira/browse/NIFI-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16556269#comment-16556269 ] Joseph Percivall commented on NIFI-5457: Looking at the release guide, it's not as

[jira] [Created] (NIFI-5457) apache/nifi:1.7.1 Dockerhub image uses NiFi 1.7.0

Joseph Percivall created NIFI-5457: -- Summary: apache/nifi:1.7.1 Dockerhub image uses NiFi 1.7.0 Key: NIFI-5457 URL: https://issues.apache.org/jira/browse/NIFI-5457 Project: Apache NiFi Issue

[jira] [Created] (NIFI-5259) Provenance repo "failed to perform background maintenance procedures" due failing to read schema

Joseph Percivall created NIFI-5259: -- Summary: Provenance repo "failed to perform background maintenance procedures" due failing to read schema Key: NIFI-5259 URL: https://issues.apache.org/jira/browse/NIFI-5259

[jira] [Commented] (NIFI-5259) Provenance repo "failed to perform background maintenance procedures" due failing to read schema

[ https://issues.apache.org/jira/browse/NIFI-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16498600#comment-16498600 ] Joseph Percivall commented on NIFI-5259: Talking on the Apache NiFi HipChat, [~mar

[jira] [Commented] (NIFI-5158) getStateValue function from NiFi expression language pads extra space in front of the returned value

[ https://issues.apache.org/jira/browse/NIFI-5158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16478056#comment-16478056 ] Joseph Percivall commented on NIFI-5158: FYI, I did some digging last night and cou

[jira] [Assigned] (NIFI-5158) getStateValue function from NiFi expression language pads extra space in front of the returned value

[ https://issues.apache.org/jira/browse/NIFI-5158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall reassigned NIFI-5158: -- Assignee: Joseph Percivall > getStateValue function from NiFi expression language pads e

[jira] [Updated] (NIFI-5165) PutElasticsearchHttp error handling doesn't properly extract ES6 error reason

[ https://issues.apache.org/jira/browse/NIFI-5165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall updated NIFI-5165: --- Issue Type: Bug (was: Improvement) > PutElasticsearchHttp error handling doesn't properly extr

[jira] [Created] (NIFI-5165) PutElasticsearchHttp error handling doesn't properly extract ES6 error reason

Joseph Percivall created NIFI-5165: -- Summary: PutElasticsearchHttp error handling doesn't properly extract ES6 error reason Key: NIFI-5165 URL: https://issues.apache.org/jira/browse/NIFI-5165 Project

[jira] [Commented] (NIFI-5162) Registry Client should throttle repeated failure calls

[ https://issues.apache.org/jira/browse/NIFI-5162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16466257#comment-16466257 ] Joseph Percivall commented on NIFI-5162: Yup, looking again that is what I'm seeing

[jira] [Created] (NIFI-5162) Registry Client should throttle repeated failure calls

Joseph Percivall created NIFI-5162: -- Summary: Registry Client should throttle repeated failure calls Key: NIFI-5162 URL: https://issues.apache.org/jira/browse/NIFI-5162 Project: Apache NiFi

[jira] [Created] (NIFI-5137) Cannot clear state of a controller service

Joseph Percivall created NIFI-5137: -- Summary: Cannot clear state of a controller service Key: NIFI-5137 URL: https://issues.apache.org/jira/browse/NIFI-5137 Project: Apache NiFi Issue Type:

[jira] [Updated] (NIFI-4795) AllowableValues for AccessPolicySummaryDTO are incorrect

[ https://issues.apache.org/jira/browse/NIFI-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall updated NIFI-4795: --- Affects Version/s: (was: 1.6.0) > AllowableValues for AccessPolicySummaryDTO are incorrect

[jira] [Updated] (NIFI-4893) Cannot convert Avro schemas to Record schemas with default value in arrays

[ https://issues.apache.org/jira/browse/NIFI-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall updated NIFI-4893: --- Affects Version/s: (was: 1.6.0) > Cannot convert Avro schemas to Record schemas with defaul

[jira] [Updated] (NIFI-5009) PutParquet processor requires "read filesystem" restricted component permission but should be "write filesystem" permission instead

[ https://issues.apache.org/jira/browse/NIFI-5009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall updated NIFI-5009: --- Affects Version/s: (was: 1.6.0) > PutParquet processor requires "read filesystem" restricte

[jira] [Updated] (NIFI-4958) Travis job will be successful when Maven build fails + add atlas profile

[ https://issues.apache.org/jira/browse/NIFI-4958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall updated NIFI-4958: --- Affects Version/s: (was: 1.6.0) > Travis job will be successful when Maven build fails + ad

[jira] [Updated] (NIFI-4959) HandleHttpRequest processor doesn't close/release incomplete message error

[ https://issues.apache.org/jira/browse/NIFI-4959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall updated NIFI-4959: --- Affects Version/s: (was: 1.6.0) > HandleHttpRequest processor doesn't close/release incompl

[jira] [Updated] (NIFI-5033) Cannot update variable referenced in restricted components

[ https://issues.apache.org/jira/browse/NIFI-5033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall updated NIFI-5033: --- Affects Version/s: (was: 1.6.0) > Cannot update variable referenced in restricted component

[jira] [Commented] (NIFI-1927) Improve documentation of property's ability to use Expression Languages

[ https://issues.apache.org/jira/browse/NIFI-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16442995#comment-16442995 ] Joseph Percivall commented on NIFI-1927: Actually [~mattyb149] I don't think it cov

[jira] [Updated] (NIFI-5085) InvokeHttp does not close the response in all cases

[ https://issues.apache.org/jira/browse/NIFI-5085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall updated NIFI-5085: --- Status: Patch Available (was: Open) > InvokeHttp does not close the response in all cases > --

[jira] [Updated] (NIFI-5085) InvokeHttp does not close the response in all cases

[ https://issues.apache.org/jira/browse/NIFI-5085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall updated NIFI-5085: --- Affects Version/s: (was: 0.7.4) (was: 1.3.0)

[jira] [Commented] (NIFI-5085) InvokeHttp does not close the response in all cases

[ https://issues.apache.org/jira/browse/NIFI-5085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440082#comment-16440082 ] Joseph Percivall commented on NIFI-5085: Removed the "affectsVersion" for all prior

[jira] [Commented] (NIFI-5085) InvokeHttp does not close the response in all cases

[ https://issues.apache.org/jira/browse/NIFI-5085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440074#comment-16440074 ] Joseph Percivall commented on NIFI-5085: Was curious why I didn't do this in the fi

[jira] [Created] (NIFI-5086) Many usages of AbstractElasticsearchHttpProcessor.sendRequestToElasticsearch aren't closed properly

Joseph Percivall created NIFI-5086: -- Summary: Many usages of AbstractElasticsearchHttpProcessor.sendRequestToElasticsearch aren't closed properly Key: NIFI-5086 URL: https://issues.apache.org/jira/browse/NIFI-50

[jira] [Updated] (NIFI-5086) Many usages of AbstractElasticsearchHttpProcessor.sendRequestToElasticsearch aren't closed properly

[ https://issues.apache.org/jira/browse/NIFI-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall updated NIFI-5086: --- Description: Similar to NIFI-5085, all OkHttp responses must be closed[1]. "AbstractElasticsea

[jira] [Created] (NIFI-5085) InvokeHttp does not close the response in all cases

Joseph Percivall created NIFI-5085: -- Summary: InvokeHttp does not close the response in all cases Key: NIFI-5085 URL: https://issues.apache.org/jira/browse/NIFI-5085 Project: Apache NiFi Iss

[jira] [Commented] (NIFI-3576) QueryElasticsearchHttp should have a "Not Found"/"Zero results" relationship

[ https://issues.apache.org/jira/browse/NIFI-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16419656#comment-16419656 ] Joseph Percivall commented on NIFI-3576: [~ottobackwards] I agree   [~panchicore]

[jira] [Commented] (NIFI-3576) QueryElasticsearchHttp should have a "Not Found"/"Zero results" relationship

[ https://issues.apache.org/jira/browse/NIFI-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16419631#comment-16419631 ] Joseph Percivall commented on NIFI-3576: Hmm, the attributes on a no-hits REL FF co

[jira] [Commented] (NIFI-3576) QueryElasticsearchHttp should have a "Not Found"/"Zero results" relationship

[ https://issues.apache.org/jira/browse/NIFI-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16419599#comment-16419599 ] Joseph Percivall commented on NIFI-3576: There are a couple examples, such as Route

[jira] [Commented] (NIFI-3576) QueryElasticsearchHttp should have a "Not Found"/"Zero results" relationship

[ https://issues.apache.org/jira/browse/NIFI-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16419555#comment-16419555 ] Joseph Percivall commented on NIFI-3576: Ah, I see your point about the FlowFile pe

[jira] [Commented] (NIFI-3576) QueryElasticsearchHttp should have a "Not Found"/"Zero results" relationship

[ https://issues.apache.org/jira/browse/NIFI-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16419524#comment-16419524 ] Joseph Percivall commented on NIFI-3576: So to summarize we have a couple of differ

[jira] [Resolved] (NIFI-4325) Create a new ElasticSearch processor that supports the JSON DSL

[ https://issues.apache.org/jira/browse/NIFI-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall resolved NIFI-4325. Resolution: Fixed Fix Version/s: 1.6.0 > Create a new ElasticSearch processor that sup

[jira] [Updated] (NIFI-4325) Create a new ElasticSearch processor that supports the JSON DSL

[ https://issues.apache.org/jira/browse/NIFI-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall updated NIFI-4325: --- Issue Type: New Feature (was: Improvement) > Create a new ElasticSearch processor that support

[jira] [Assigned] (NIFI-4325) Create a new ElasticSearch processor that supports the JSON DSL

[ https://issues.apache.org/jira/browse/NIFI-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall reassigned NIFI-4325: -- Assignee: Mike Thomsen > Create a new ElasticSearch processor that supports the JSON DSL

[jira] [Updated] (NIFI-4977) PutSyslog should support Expression Language for it's Sender properties

[ https://issues.apache.org/jira/browse/NIFI-4977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall updated NIFI-4977: --- Status: Patch Available (was: Open) > PutSyslog should support Expression Language for it's Se

[jira] [Created] (NIFI-4977) PutSyslog should support Expression Language for it's Sender properties

Joseph Percivall created NIFI-4977: -- Summary: PutSyslog should support Expression Language for it's Sender properties Key: NIFI-4977 URL: https://issues.apache.org/jira/browse/NIFI-4977 Project: Apac

[jira] [Commented] (NIFI-4936) NiFi parent pom dependency management forcing versions to align defeating classloader isolation

[ https://issues.apache.org/jira/browse/NIFI-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16394567#comment-16394567 ] Joseph Percivall commented on NIFI-4936: [~joewitt] is there anything we'll need to

[jira] [Commented] (NIFI-4956) Cannot import or upgrade versioned flow that includes a CRON_DRIVEN scheduling strategy

[ https://issues.apache.org/jira/browse/NIFI-4956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16393838#comment-16393838 ] Joseph Percivall commented on NIFI-4956: Whelp this is a little embarrassing, lol t

[jira] [Resolved] (NIFI-4956) Cannot import or upgrade versioned flow that includes a CRON_DRIVEN scheduling strategy

[ https://issues.apache.org/jira/browse/NIFI-4956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall resolved NIFI-4956. Resolution: Duplicate > Cannot import or upgrade versioned flow that includes a CRON_DRIVEN

[jira] [Created] (NIFI-4956) Cannot import or upgrade versioned flow that includes a CRON_DRIVEN scheduling strategy

Joseph Percivall created NIFI-4956: -- Summary: Cannot import or upgrade versioned flow that includes a CRON_DRIVEN scheduling strategy Key: NIFI-4956 URL: https://issues.apache.org/jira/browse/NIFI-4956

[jira] [Updated] (NIFI-4913) Specifying "run.as" in bootstrap.properties causes environment variables to not be passed to NiFi

[ https://issues.apache.org/jira/browse/NIFI-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall updated NIFI-4913: --- Labels: beginner (was: ) > Specifying "run.as" in bootstrap.properties causes environment vari

[jira] [Updated] (NIFI-4913) Specifying "run.as" in bootstrap.properties causes environment variables to not be passed to NiFi

[ https://issues.apache.org/jira/browse/NIFI-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall updated NIFI-4913: --- Component/s: (was: Tools and Build) Configuration > Specifying "run.as" in

[jira] [Resolved] (NIFI-4874) RPGs to flows that share the same flow and port UUIDs can cause non-deterministic FlowFile transmission

[ https://issues.apache.org/jira/browse/NIFI-4874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall resolved NIFI-4874. Resolution: Fixed I believe this to be fixed as part of NIFI-3155 > RPGs to flows that share

[jira] [Created] (NIFI-4874) RPGs to flows that share the same flow and port UUIDs can cause non-deterministic FlowFile transmission

Joseph Percivall created NIFI-4874: -- Summary: RPGs to flows that share the same flow and port UUIDs can cause non-deterministic FlowFile transmission Key: NIFI-4874 URL: https://issues.apache.org/jira/browse/NIFI

[jira] [Comment Edited] (NIFI-4871) Data Queuing at Process Group Input Port

[ https://issues.apache.org/jira/browse/NIFI-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16361231#comment-16361231 ] Joseph Percivall edited comment on NIFI-4871 at 2/12/18 6:31 PM:

[jira] [Commented] (NIFI-4871) Data Queuing at Process Group Input Port

[ https://issues.apache.org/jira/browse/NIFI-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16361231#comment-16361231 ] Joseph Percivall commented on NIFI-4871: This should probably be handled in the sam

[jira] [Updated] (NIFI-4837) Thread leak on HandleHTTPRequest processor

[ https://issues.apache.org/jira/browse/NIFI-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall updated NIFI-4837: --- Description: When you have multiple HandleHTTPRequest processors trying to listen on the same

[jira] [Created] (NIFI-4817) GetFile is missing a context.yield when using "Polling Interval", causing it to spin

Joseph Percivall created NIFI-4817: -- Summary: GetFile is missing a context.yield when using "Polling Interval", causing it to spin Key: NIFI-4817 URL: https://issues.apache.org/jira/browse/NIFI-4817

[jira] [Commented] (NIFIREG-77) Allow a user to see the changes created by the currently loaded version

[ https://issues.apache.org/jira/browse/NIFIREG-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16316807#comment-16316807 ] Joseph Percivall commented on NIFIREG-77: - [~bbende] when I originally created the

[jira] [Commented] (NIFIREG-77) Allow a user to see the changes created by the currently loaded version

[ https://issues.apache.org/jira/browse/NIFIREG-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16313361#comment-16313361 ] Joseph Percivall commented on NIFIREG-77: - Hey [~rmoran], Totally agree with the

[jira] [Closed] (NIFIREG-82) Properly handle when someone goes to registry but without the "/nifi-registry/" path

[ https://issues.apache.org/jira/browse/NIFIREG-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall closed NIFIREG-82. --- Resolution: Duplicate > Properly handle when someone goes to registry but without the > "/nif

[jira] [Assigned] (NIFIREG-89) Add a default URL handler for root '/' instead of returning a 404

[ https://issues.apache.org/jira/browse/NIFIREG-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall reassigned NIFIREG-89: --- Assignee: Danny Lane > Add a default URL handler for root '/' instead of returning a

[jira] [Created] (NIFIREG-82) Properly handle when someone goes to registry but without the "/nifi-registry/" path

Joseph Percivall created NIFIREG-82: --- Summary: Properly handle when someone goes to registry but without the "/nifi-registry/" path Key: NIFIREG-82 URL: https://issues.apache.org/jira/browse/NIFIREG-82

[jira] [Updated] (NIFIREG-77) Allow a user to see the changes created by the currently loaded version

[ https://issues.apache.org/jira/browse/NIFIREG-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall updated NIFIREG-77: Priority: Critical (was: Major) > Allow a user to see the changes created by the currently

[jira] [Created] (NIFIREG-81) Variable Registry properties that are expected for a versioned Flow should be tracked

Joseph Percivall created NIFIREG-81: --- Summary: Variable Registry properties that are expected for a versioned Flow should be tracked Key: NIFIREG-81 URL: https://issues.apache.org/jira/browse/NIFIREG-81

[jira] [Created] (NIFIREG-80) Flows and their versions should be exportable & importable from the UI

Joseph Percivall created NIFIREG-80: --- Summary: Flows and their versions should be exportable & importable from the UI Key: NIFIREG-80 URL: https://issues.apache.org/jira/browse/NIFIREG-80 Project: N

  1   2   3   4   5   6   >