[jira] [Resolved] (NIFI-13487) ConsumeKinesisStream initial stream position handling error after AWS SDK 2.x migration
[ https://issues.apache.org/jira/browse/NIFI-13487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock resolved NIFI-13487. Fix Version/s: 2.0.0-M5 Resolution: Fixed > ConsumeKinesisStream initial stream position handling error after AWS SDK 2.x > migration > --- > > Key: NIFI-13487 > URL: https://issues.apache.org/jira/browse/NIFI-13487 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 2.0.0-M4 >Reporter: Zsihovszki Krisztina >Assignee: Zsihovszki Krisztina >Priority: Major > Fix For: 2.0.0-M5 > > Time Spent: 20m > Remaining Estimate: 0h > > Noticed a changed behaviour for ConsumeKinesisStream processor when > "Initial Stream Position" is set to "TRIM_HORIZON". > ConsumeKinesisStream consumes only records which were inserted to Kinesis > stream after the processor start and it does not consume the records which > were insterted before processor start. > In case of "TRIM_HORIZON" the records inserted before processor start (app > registration) should be consumed as well. > > The processor behaved as it used "LATEST" initial stream position. > The issue occurs for NiFi 2.0 only and the root cause seems to be related to > NIFI-8531: Upgrading Kinesis processors to AWS SDK 2.x > > According to > [https://docs.aws.amazon.com/streams/latest/dev/kcl-migration.html,] setting > initialPositionInStreamExtended was moved from LeaseManagementConfig to > RetrievalConfig. > The [existing > implementation|https://github.com/apache/nifi/blob/main/nifi-extension-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/kinesis/stream/ConsumeKinesisStream.java] > sets the value still in LeaseManagementConfig, this is the reason why the > default value, "LATEST" was used as initial position. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13437) Properties Parameter Provider
[ https://issues.apache.org/jira/browse/NIFI-13437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17860178#comment-17860178 ] Joe Gresock commented on NIFI-13437: To reduce future confusion, I've submitted https://issues.apache.org/jira/browse/NIFI-13454 to rename FileParameterProvider to KubernetesSecretParameterProvider in NiFi 2. > Properties Parameter Provider > - > > Key: NIFI-13437 > URL: https://issues.apache.org/jira/browse/NIFI-13437 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Jim Steinebrey >Priority: Major > > Create a Parameter Provider that can take as input a .properties file and > create parameters for the property lines in the file. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13454) Rename FileParameterProvider to KubernetesSecretParameterProvider
[ https://issues.apache.org/jira/browse/NIFI-13454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock updated NIFI-13454: --- Status: Patch Available (was: Open) > Rename FileParameterProvider to KubernetesSecretParameterProvider > - > > Key: NIFI-13454 > URL: https://issues.apache.org/jira/browse/NIFI-13454 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M4 >Reporter: Joe Gresock >Assignee: Joe Gresock >Priority: Major > > The FileParameterProvider was designed specifically to support Kubernetes > mounted Secrets, with a single K8s secret being represented by a single file, > mapped to a single parameter. However, the name of the parameter provider > obscures its use case, and makes it seem like a general purpose file-based > parameter provider. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13454) Rename FileParameterProvider to KubernetesSecretParameterProvider
[ https://issues.apache.org/jira/browse/NIFI-13454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17860177#comment-17860177 ] Joe Gresock commented on NIFI-13454: https://github.com/apache/nifi/pull/9008 > Rename FileParameterProvider to KubernetesSecretParameterProvider > - > > Key: NIFI-13454 > URL: https://issues.apache.org/jira/browse/NIFI-13454 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M4 >Reporter: Joe Gresock >Assignee: Joe Gresock >Priority: Major > > The FileParameterProvider was designed specifically to support Kubernetes > mounted Secrets, with a single K8s secret being represented by a single file, > mapped to a single parameter. However, the name of the parameter provider > obscures its use case, and makes it seem like a general purpose file-based > parameter provider. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13454) Rename FileParameterProvider to KubernetesSecretParameterProvider
Joe Gresock created NIFI-13454: -- Summary: Rename FileParameterProvider to KubernetesSecretParameterProvider Key: NIFI-13454 URL: https://issues.apache.org/jira/browse/NIFI-13454 Project: Apache NiFi Issue Type: Improvement Affects Versions: 2.0.0-M4 Reporter: Joe Gresock Assignee: Joe Gresock The FileParameterProvider was designed specifically to support Kubernetes mounted Secrets, with a single K8s secret being represented by a single file, mapped to a single parameter. However, the name of the parameter provider obscures its use case, and makes it seem like a general purpose file-based parameter provider. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-13191) Deprecate InvokeAWSGatewayApi Processor
[ https://issues.apache.org/jira/browse/NIFI-13191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock reassigned NIFI-13191: -- Assignee: Joe Gresock > Deprecate InvokeAWSGatewayApi Processor > --- > > Key: NIFI-13191 > URL: https://issues.apache.org/jira/browse/NIFI-13191 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Gresock >Assignee: Joe Gresock >Priority: Minor > > Similar to the other AWS client library upgrade issues, this targets the > InvokeAWSGatewayApi processor. > Note: After discussing with [~exceptionfactory] and [~otto], we agree that > this processor can be deprecated, and removed in NiFi 2.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-13194) Remove InvokeAWSGatewayApi processor from NiFi 2
[ https://issues.apache.org/jira/browse/NIFI-13194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock reassigned NIFI-13194: -- Assignee: Joe Gresock > Remove InvokeAWSGatewayApi processor from NiFi 2 > > > Key: NIFI-13194 > URL: https://issues.apache.org/jira/browse/NIFI-13194 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Gresock >Assignee: Joe Gresock >Priority: Major > > Based on the discussion in NIFI-13191. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13194) Remove InvokeAWSGatewayApi processor from NiFi 2
Joe Gresock created NIFI-13194: -- Summary: Remove InvokeAWSGatewayApi processor from NiFi 2 Key: NIFI-13194 URL: https://issues.apache.org/jira/browse/NIFI-13194 Project: Apache NiFi Issue Type: Improvement Reporter: Joe Gresock Based on the discussion in NIFI-13191. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13191) Deprecate InvokeAWSGatewayApi Processor
[ https://issues.apache.org/jira/browse/NIFI-13191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock updated NIFI-13191: --- Description: Similar to the other AWS client library upgrade issues, this targets the InvokeAWSGatewayApi processor. Note: After discussing with [~exceptionfactory] and [~otto], we agree that this processor can be deprecated, and removed in NiFi 2.0. was:Similar to the other AWS client library upgrade issues, this targets the InvokeAWSGatewayApi processor. > Deprecate InvokeAWSGatewayApi Processor > --- > > Key: NIFI-13191 > URL: https://issues.apache.org/jira/browse/NIFI-13191 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Gresock >Priority: Minor > > Similar to the other AWS client library upgrade issues, this targets the > InvokeAWSGatewayApi processor. > Note: After discussing with [~exceptionfactory] and [~otto], we agree that > this processor can be deprecated, and removed in NiFi 2.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13191) Deprecate InvokeAWSGatewayApi Processor
[ https://issues.apache.org/jira/browse/NIFI-13191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock updated NIFI-13191: --- Summary: Deprecate InvokeAWSGatewayApi Processor (was: Upgrade InvokeAWSGatewayApi Processor to use AWS 2.x library) > Deprecate InvokeAWSGatewayApi Processor > --- > > Key: NIFI-13191 > URL: https://issues.apache.org/jira/browse/NIFI-13191 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Gresock >Priority: Minor > > Similar to the other AWS client library upgrade issues, this targets the > InvokeAWSGatewayApi processor. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13191) Upgrade InvokeAWSGatewayApi Processor to use AWS 2.x library
[ https://issues.apache.org/jira/browse/NIFI-13191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844983#comment-17844983 ] Joe Gresock commented on NIFI-13191: Thanks for the context here, [~exceptionfactory], this demonstrates the need for evaluating this soon, so that could be removed for 2.0 if that's the case. I'll report my findings here. > Upgrade InvokeAWSGatewayApi Processor to use AWS 2.x library > > > Key: NIFI-13191 > URL: https://issues.apache.org/jira/browse/NIFI-13191 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Gresock >Priority: Minor > > Similar to the other AWS client library upgrade issues, this targets the > InvokeAWSGatewayApi processor. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (NIFI-13191) Upgrade InvokeAWSGatewayApi Processor to use AWS 2.x library
[ https://issues.apache.org/jira/browse/NIFI-13191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844983#comment-17844983 ] Joe Gresock edited comment on NIFI-13191 at 5/9/24 1:09 PM: Thanks for the context here, [~exceptionfactory], this demonstrates the need for evaluating this soon, so it could be removed for 2.0 if that's the case. I'll report my findings here. was (Author: jgresock): Thanks for the context here, [~exceptionfactory], this demonstrates the need for evaluating this soon, so that could be removed for 2.0 if that's the case. I'll report my findings here. > Upgrade InvokeAWSGatewayApi Processor to use AWS 2.x library > > > Key: NIFI-13191 > URL: https://issues.apache.org/jira/browse/NIFI-13191 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Gresock >Priority: Minor > > Similar to the other AWS client library upgrade issues, this targets the > InvokeAWSGatewayApi processor. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13192) Upgrade AWS S3 Processors to use AWS 2.x libraries
[ https://issues.apache.org/jira/browse/NIFI-13192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock updated NIFI-13192: --- Description: It looks like AWS recently began supporting client side encryption in the v2 SDK: https://github.com/aws/aws-sdk-java-v2/issues/34 This will enable us to upgrade the S3 processors without losing functionality. was:This upgrade task will be a bit more involved, because Client Side Encryption is not currently available in the AWS v2 SDK. https://levelup.gitconnected.com/aws-client-side-encryption-with-kms-using-java-v2-sdk-and-s3-upload-73b525314a5b has some details on how this might be implemented, and https://github.com/aws/amazon-s3-encryption-client-java could also provide some examples. > Upgrade AWS S3 Processors to use AWS 2.x libraries > -- > > Key: NIFI-13192 > URL: https://issues.apache.org/jira/browse/NIFI-13192 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Gresock >Priority: Minor > > It looks like AWS recently began supporting client side encryption in the v2 > SDK: https://github.com/aws/aws-sdk-java-v2/issues/34 > This will enable us to upgrade the S3 processors without losing functionality. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13192) Upgrade AWS S3 Processors to use AWS 2.x libraries
Joe Gresock created NIFI-13192: -- Summary: Upgrade AWS S3 Processors to use AWS 2.x libraries Key: NIFI-13192 URL: https://issues.apache.org/jira/browse/NIFI-13192 Project: Apache NiFi Issue Type: Improvement Reporter: Joe Gresock This upgrade task will be a bit more involved, because Client Side Encryption is not currently available in the AWS v2 SDK. https://levelup.gitconnected.com/aws-client-side-encryption-with-kms-using-java-v2-sdk-and-s3-upload-73b525314a5b has some details on how this might be implemented, and https://github.com/aws/amazon-s3-encryption-client-java could also provide some examples. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13191) Upgrade InvokeAWSGatewayApi Processor to use AWS 2.x library
Joe Gresock created NIFI-13191: -- Summary: Upgrade InvokeAWSGatewayApi Processor to use AWS 2.x library Key: NIFI-13191 URL: https://issues.apache.org/jira/browse/NIFI-13191 Project: Apache NiFi Issue Type: Improvement Reporter: Joe Gresock Similar to the other AWS client library upgrade issues, this targets the InvokeAWSGatewayApi processor. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13008) CLI command to upgrade all instances of a versioned flow
[ https://issues.apache.org/jira/browse/NIFI-13008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock updated NIFI-13008: --- Fix Version/s: 2.0.0-M3 1.26.0 Resolution: Fixed Status: Resolved (was: Patch Available) > CLI command to upgrade all instances of a versioned flow > > > Key: NIFI-13008 > URL: https://issues.apache.org/jira/browse/NIFI-13008 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Reporter: Pierre Villard >Assignee: Pierre Villard >Priority: Major > Labels: backport-needed > Fix For: 2.0.0-M3, 1.26.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Add a CLI command allowing someone to upgrade all the instances of a given > versioned flow. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13121) FetchHDFS handles runtime exceptions incorrectly
[ https://issues.apache.org/jira/browse/NIFI-13121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock updated NIFI-13121: --- Resolution: Fixed Status: Resolved (was: Patch Available) > FetchHDFS handles runtime exceptions incorrectly > > > Key: NIFI-13121 > URL: https://issues.apache.org/jira/browse/NIFI-13121 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Reporter: Matt Burgess >Assignee: Matt Burgess >Priority: Major > Fix For: 2.0.0-M3, 1.26.0 > > Time Spent: 20m > Remaining Estimate: 0h > > FetchHDFS does not catch runtime exceptions and does not route the incoming > flowfile to failure or yield as a result. This causes FetchHDFS to run over > and over (especially if the Run Schedule is 0 seconds) and can cause NiFi to > be unresponsive. > This happened to the AWS processors in NIFI-6367, the same fix needs to be > applied to FetchHDFS -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-13103) Make AutoCommit default to no value set in PutDatabaseRecord
[ https://issues.apache.org/jira/browse/NIFI-13103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock resolved NIFI-13103. Fix Version/s: 2.0.0-M3 1.26.0 Resolution: Fixed > Make AutoCommit default to no value set in PutDatabaseRecord > > > Key: NIFI-13103 > URL: https://issues.apache.org/jira/browse/NIFI-13103 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: Jim Steinebrey >Assignee: Jim Steinebrey >Priority: Minor > Fix For: 2.0.0-M3, 1.26.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Make AutoCommit default to no values set in PutDatabaseRecord so the database > connection's autoCommit mode is left unchanged by default. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-13118) ChunkDocument python processor not works with Split code - 'NoneType' object has no attribute 'getValue'
[
https://issues.apache.org/jira/browse/NIFI-13118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Gresock resolved NIFI-13118.
Fix Version/s: 2.0.0-M3
Resolution: Fixed
> ChunkDocument python processor not works with Split code - 'NoneType' object
> has no attribute 'getValue'
>
>
> Key: NIFI-13118
> URL: https://issues.apache.org/jira/browse/NIFI-13118
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 2.0.0-M1, 2.0.0-M2, 2.0.0-M3
>Reporter: Zoltán Kornél Török
>Assignee: Zoltán Kornél Török
>Priority: Major
> Labels: python
> Fix For: 2.0.0-M3
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When you want to use ChunkDocument with split code settings we got :
> {code:java}
> PythonProcessor[type=ChunkDocument, id=e1f5691a-4845-3529-9b8b-052300f15375]
> Failed to transform FlowFile[filename=1ad079db-cb83-49bc-8208-c1e35c5d8c52]:
> py4j.Py4JException: An exception was raised by the Python Proxy. Return
> Message: Traceback (most recent call last):
> File "/opt/nifi/nifi-current/python/framework/py4j/java_gateway.py", line
> 2466, in _call_proxy
> return_value = getattr(self.pool[obj_id], method)(*params)
> File "/opt/nifi/nifi-current/python/api/nifiapi/flowfiletransform.py", line
> 33, in transformFlowFile
> return self.transform(self.process_context, flowfile)
> File "/opt/nifi/nifi-current/./python/extensions/ChunkDocument.py", line
> 281, in transform
> split_docs = self.split_docs(context, flowfile, documents)
> File "/opt/nifi/nifi-current/./python/extensions/ChunkDocument.py", line
> 212, in split_docs
> language=context.getProperty(self.LANGUAGE).getValue(),
> AttributeError: 'NoneType' object has no attribute 'getValue' {code}
> It seems the LANGUAGE property is missing from the property_descriptors list,
> and because of that it is not appear on the ui and the default value also not
> initialize properly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (NIFI-10657) When multiple CLOB columns in a table are configured for processing in Oracle, NIFI is throwing Out of Memory exception.
[
https://issues.apache.org/jira/browse/NIFI-10657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Gresock resolved NIFI-10657.
Fix Version/s: 2.0.0-M3
1.26.0
Resolution: Fixed
> When multiple CLOB columns in a table are configured for processing in
> Oracle, NIFI is throwing Out of Memory exception.
>
>
> Key: NIFI-10657
> URL: https://issues.apache.org/jira/browse/NIFI-10657
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework, Docker
>Affects Versions: 1.17.0
> Environment: Docker container
>Reporter: Shiv
>Assignee: Jim Steinebrey
>Priority: Major
> Labels: performance
> Fix For: 2.0.0-M3, 1.26.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> This issue is happening because Nifi Processor PutDatabaseRecord is not
> clearing CLOBs once the data is written to the databases. The Nifi Processor
> code needs to be modified to clear CLOB before closing Resultsets.
> Table being processed has four CLOB data type columns. Average row size is
> 10K, and each CLOB column average length is 2K
> I don't have the permission to create a branch.. The below code change is
> needed to fix the issue *(tested against rel/nifi-1.17.0 branch)*
> {code:java}
> diff --git
> a/nifi-nar-bundles/nifi-extension-utils/nifi-database-utils/src/main/java/org/apache/nifi/util/db/JdbcCommon.java
>
> b/nifi-nar-bundles/nifi-extension-utils/nifi-database-utils/src/main/java/org/apache/nifi/util/db/JdbcCommon.java
> index b78408c912..bfc5328603 100644
> ---
> a/nifi-nar-bundles/nifi-extension-utils/nifi-database-utils/src/main/java/org/apache/nifi/util/db/JdbcCommon.java
> +++
> b/nifi-nar-bundles/nifi-extension-utils/nifi-database-utils/src/main/java/org/apache/nifi/util/db/JdbcCommon.java
> @@ -280,6 +280,11 @@ public class JdbcCommon {
> }
> }
> rec.put(i - 1, sb.toString());
> + try {
> + clob.free();
> + } catch (SQLFeatureNotSupportedException sfnse) {
> + // The driver doesn't support free, but allow
> processing to continue
> + }
> } else {
> rec.put(i - 1, null);
> } {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-12636) Upgrade dependencies for Pinecone, ChromaDB and OpenAI processors
[ https://issues.apache.org/jira/browse/NIFI-12636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock updated NIFI-12636: --- Fix Version/s: 2.0.0 Resolution: Fixed Status: Resolved (was: Patch Available) > Upgrade dependencies for Pinecone, ChromaDB and OpenAI processors > - > > Key: NIFI-12636 > URL: https://issues.apache.org/jira/browse/NIFI-12636 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 2.0.0-M1 > Environment: Mac, JDK 21, python 3.10 >Reporter: Timothy J Spann >Assignee: Pierre Villard >Priority: Minor > Fix For: 2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Upgrade langchain to 0.1.2 (from 0.0.331) > Upgrade openai to 1.9.0 (from 0.28.1) > Upgrade chromadb to 0.4.22 (from 0.4.14) > Upgrade pinecone-client to 3.0.1 > Removed some unused imports -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-12648) Refactor components in elasticsearch bundle using current API methods
[
https://issues.apache.org/jira/browse/NIFI-12648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Gresock resolved NIFI-12648.
Fix Version/s: 2.0.0
Resolution: Fixed
> Refactor components in elasticsearch bundle using current API methods
> -
>
> Key: NIFI-12648
> URL: https://issues.apache.org/jira/browse/NIFI-12648
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: endzeit
>Assignee: endzeit
>Priority: Minor
> Fix For: 2.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Based on improvements to support for {{DescribedValue}} in NiFi API and other
> improvements in Java 21, the _elasticsearch_ bundle components should be
> updated to use current methods.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-12610) Typo for 'default_value' in Python developer documentation
[
https://issues.apache.org/jira/browse/NIFI-12610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Gresock updated NIFI-12610:
---
Status: Patch Available (was: Open)
> Typo for 'default_value' in Python developer documentation
> --
>
> Key: NIFI-12610
> URL: https://issues.apache.org/jira/browse/NIFI-12610
> Project: Apache NiFi
> Issue Type: Bug
> Components: Documentation Website
>Affects Versions: 2.0.0-M1
>Reporter: Joe Gresock
>Assignee: Joe Gresock
>Priority: Trivial
> Fix For: 2.0.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In the Python developer guide, the section on creating a property descriptor
> has a typo: defaultValue should actually be default_value. The result of
> pasting this example in a Python processor is that the property descriptors
> will not load.
> {code:java}
> numspaces = PropertyDescriptor(name="Number of Spaces",
> description="Number of spaces to use for pretty-printing",
> validators=[StandardValidators.POSITIVE_INTEGER_VALIDATOR],
> defaultValue="4",
> required=True)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (NIFI-12610) Typo for 'default_value' in Python developer documentation
Joe Gresock created NIFI-12610:
--
Summary: Typo for 'default_value' in Python developer documentation
Key: NIFI-12610
URL: https://issues.apache.org/jira/browse/NIFI-12610
Project: Apache NiFi
Issue Type: Bug
Components: Documentation Website
Affects Versions: 2.0.0-M1
Reporter: Joe Gresock
Assignee: Joe Gresock
Fix For: 2.0.0
In the Python developer guide, the section on creating a property descriptor
has a typo: defaultValue should actually be default_value. The result of
pasting this example in a Python processor is that the property descriptors
will not load.
{code:java}
numspaces = PropertyDescriptor(name="Number of Spaces",
description="Number of spaces to use for pretty-printing",
validators=[StandardValidators.POSITIVE_INTEGER_VALIDATOR],
defaultValue="4",
required=True)
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-12530) Support CREATE TABLE for Oracle databases
[ https://issues.apache.org/jira/browse/NIFI-12530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock updated NIFI-12530: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Support CREATE TABLE for Oracle databases > - > > Key: NIFI-12530 > URL: https://issues.apache.org/jira/browse/NIFI-12530 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: Matt Burgess >Assignee: Matt Burgess >Priority: Major > Fix For: 1.25.0, 2.0.0 > > Time Spent: 50m > Remaining Estimate: 0h > > The UpdateDatabaseTable processor has the capability to create a target table > if it does not exist in the target database. However the database adapter > used must support it, and the Oracle database adapters do not. Even though it > would likely be a PL/SQL function, this is done "under the hood" and so could > be supported by Oracle. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12263) Upgrade AWS Machine Learning Processors to use AWS 2.x libraries
[ https://issues.apache.org/jira/browse/NIFI-12263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock updated NIFI-12263: --- Attachment: Machine_Learning.json > Upgrade AWS Machine Learning Processors to use AWS 2.x libraries > > > Key: NIFI-12263 > URL: https://issues.apache.org/jira/browse/NIFI-12263 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Gresock >Assignee: Joe Gresock >Priority: Minor > Fix For: 2.latest > > Attachments: Machine_Learning.json > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12263) Upgrade AWS Machine Learning Processors to use AWS 2.x libraries
Joe Gresock created NIFI-12263: -- Summary: Upgrade AWS Machine Learning Processors to use AWS 2.x libraries Key: NIFI-12263 URL: https://issues.apache.org/jira/browse/NIFI-12263 Project: Apache NiFi Issue Type: Improvement Reporter: Joe Gresock Assignee: Joe Gresock Fix For: 2.latest -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12243) Refactor encrypt-config Command Implementation
[
https://issues.apache.org/jira/browse/NIFI-12243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Gresock updated NIFI-12243:
---
Fix Version/s: 2.0.0
(was: 2.latest)
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Refactor encrypt-config Command Implementation
> --
>
> Key: NIFI-12243
> URL: https://issues.apache.org/jira/browse/NIFI-12243
> Project: Apache NiFi
> Issue Type: Improvement
> Components: NiFi Registry, Tools and Build
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
> Fix For: 2.0.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The {{encrypt-config}} command in {{nifi-toolkit-encrypt-config}} supports
> protection of sensitive properties in multiple application configuration
> files. The current implementation supports NiFi and NiFi Registry with
> similar capabilities.
> The existing implementation is written in Groovy and includes some amount of
> duplication between operating modes.
> The command supports capabilities unique to NiFi for protection for specific
> property values in application properties and flow configuration files.
> The {{encrypt-config}} command components should be refactored using the
> [picocli|https://picocli.info/] framework to streamline the implementation.
> This refactoring should focus on supporting existing command arguments to
> provide compatibility with existing usage patterns. Separate efforts could
> consider a redesigned approach with different arguments and sub-commands, but
> refactoring the current implementation will provide a more maintainable
> solution.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (NIFI-12212) Upgrade AWS DynamoDB Processors to use AWS 2.x libraries
Joe Gresock created NIFI-12212: -- Summary: Upgrade AWS DynamoDB Processors to use AWS 2.x libraries Key: NIFI-12212 URL: https://issues.apache.org/jira/browse/NIFI-12212 Project: Apache NiFi Issue Type: Improvement Reporter: Joe Gresock Assignee: Joe Gresock Fix For: 2.latest -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12144) Restructure AWS processors
[ https://issues.apache.org/jira/browse/NIFI-12144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock updated NIFI-12144: --- Fix Version/s: 2.0.0 (was: 2.latest) Resolution: Fixed Status: Resolved (was: Patch Available) > Restructure AWS processors > -- > > Key: NIFI-12144 > URL: https://issues.apache.org/jira/browse/NIFI-12144 > Project: Apache NiFi > Issue Type: Task > Components: Extensions >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Major > Fix For: 2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > There are a total of 93 deprecation warnings in the nifi-aws-bundle alone. > These need to be cleaned up. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11985) Implement a processor to consume documents from Elasticsearch indices
[
https://issues.apache.org/jira/browse/NIFI-11985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Gresock updated NIFI-11985:
---
Fix Version/s: 2.0.0
1.24.0
(was: 1.latest)
(was: 2.latest)
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Implement a processor to consume documents from Elasticsearch indices
> -
>
> Key: NIFI-11985
> URL: https://issues.apache.org/jira/browse/NIFI-11985
> Project: Apache NiFi
> Issue Type: New Feature
>Reporter: Chris Sampson
>Assignee: Chris Sampson
>Priority: Minor
> Fix For: 2.0.0, 1.24.0
>
> Attachments: NIFI-11985_Flow.json
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> It is possible to use Elasticsearch to store series data, i.e. data is
> continually added to an Elasticsearch index over time, with a {{date}} or a
> 1-up numeric {{long}} field.
> This is more likely with the advent of [Data
> Streams|https://www.elastic.co/guide/en/elasticsearch/reference/current/data-streams.html]
> or the recent [Time Series Data
> Streams|https://www.elastic.co/guide/en/elasticsearch/reference/current/tsds.html],
> both of which use a {{@timestamp}} field to indicate when a document was
> added to the stream.
> There are use cases where NiFi users may want to consume new data from the
> Elasticsearch index/data stream after it's arrived, then pass it to another
> service.
> NiFi would need to:
> * know which field to use as the "series field" (e.g. {{@timestamp}})
> * track the last read "series field" value via State so that the same
> documents are not retrieved from Elasticsearch multiple times
> * allow for the optional specification of the "last read" field value, e.g.
> if a user wants to offset the start of the documents to be read (this value
> should only be used if a value doesn't also exist within the processor's
> State)
> * allow for the fact that the "last read" vlaue will be blank when the
> processor is first run (and the value is not otherwise specified), meaning we
> want to retrieve all existing data
> * allow for users to specify an optional Query Filter to apply to the search
> within Elasticsearch when finding documents to retrieve
> Possible implementations should consider using the {{SearchElasticsearch}}
> processor as a basis, which already uses State tracking between processor
> executions and allows for the retrieval of Elasticsearch documents in a
> paginated manner (thus avoiding pulling too much data in a single request).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-11016) Consider providing a query-builder set of properties for the UpdateByQueryElasticsearch processor
[
https://issues.apache.org/jira/browse/NIFI-11016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Gresock updated NIFI-11016:
---
Fix Version/s: 2.0.0
1.24.0
(was: 1.latest)
(was: 2.latest)
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Consider providing a query-builder set of properties for the
> UpdateByQueryElasticsearch processor
> -
>
> Key: NIFI-11016
> URL: https://issues.apache.org/jira/browse/NIFI-11016
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: Chris Sampson
>Assignee: Chris Sampson
>Priority: Minor
> Fix For: 2.0.0, 1.24.0
>
>
> While it is already possible to send a {{script}} field as part of the
> {{Query}} parameter in the {{UpdateByQueryElasticsearch}} processor, [there
> is question|https://github.com/apache/nifi/pull/6628#issuecomment-1308972782]
> about whether this is sufficiently clear to NiFi users or a "query builder"
> kind of experience would be preferred, e.g. if the {{query}} field were
> specified via one processor property and {{script}} via another
> One thing to be careful of with any changes is to retain the [current
> (default)
> behaviour|https://github.com/apache/nifi/pull/6628#issuecomment-1308978863]
> of the {{Query}} parameter of the processor so as to be backwards
> compatible/for anyone already specifying the whole Elasticsearch Update/Query
> DSL via the existing parameters
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (NIFI-12189) Upgrade AWS Cloudwatch Processors to use AWS 2.x libraries
Joe Gresock created NIFI-12189: -- Summary: Upgrade AWS Cloudwatch Processors to use AWS 2.x libraries Key: NIFI-12189 URL: https://issues.apache.org/jira/browse/NIFI-12189 Project: Apache NiFi Issue Type: Improvement Components: Extensions Reporter: Joe Gresock Assignee: Joe Gresock Fix For: 2.latest -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12149) Separate RedisUtils into a separate module
[ https://issues.apache.org/jira/browse/NIFI-12149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock updated NIFI-12149: --- Fix Version/s: 2.0.0 1.24.0 Resolution: Fixed Status: Resolved (was: Patch Available) > Separate RedisUtils into a separate module > -- > > Key: NIFI-12149 > URL: https://issues.apache.org/jira/browse/NIFI-12149 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.23.2 >Reporter: Bryan Bende >Assignee: Bryan Bende >Priority: Major > Fix For: 2.0.0, 1.24.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Currently the RedisUtils class and some other utility code is embedded into > the nifi-redis-extensions module which makes it not easy to reuse anywhere > since depending on it would bring in extensions. It should be in a separate > module like nifi-redis-utils. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12174) Upgrade AWS Lambda Processors to use AWS 2.x libraries
Joe Gresock created NIFI-12174: -- Summary: Upgrade AWS Lambda Processors to use AWS 2.x libraries Key: NIFI-12174 URL: https://issues.apache.org/jira/browse/NIFI-12174 Project: Apache NiFi Issue Type: Improvement Components: Extensions Reporter: Joe Gresock Assignee: Joe Gresock Fix For: 2.latest -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12146) Update nifi cli command list
Joe Gresock created NIFI-12146: -- Summary: Update nifi cli command list Key: NIFI-12146 URL: https://issues.apache.org/jira/browse/NIFI-12146 Project: Apache NiFi Issue Type: Improvement Reporter: Joe Gresock Assignee: Joe Gresock A couple of the commands in the listing of the toolkit documentation don't align with actual commands. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12119) Update Kinesis processor integration tests
Joe Gresock created NIFI-12119: -- Summary: Update Kinesis processor integration tests Key: NIFI-12119 URL: https://issues.apache.org/jira/browse/NIFI-12119 Project: Apache NiFi Issue Type: Improvement Components: Extensions Reporter: Joe Gresock The Kinesis integration tests have not passed for several versions now. This ticket is to investigate and fix the integration tests. Ideally they could be rewritten using TestContainers to launch LocalStack and run everything in a consistent environment. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11895) Remove Deprecated Repository Encryption Configuration
[ https://issues.apache.org/jira/browse/NIFI-11895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock updated NIFI-11895: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Remove Deprecated Repository Encryption Configuration > - > > Key: NIFI-11895 > URL: https://issues.apache.org/jira/browse/NIFI-11895 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Previous refactoring of Repository Encryption support deprecated application > properties for configuring specific repositories in favor of a shared > configuration that applied to all repositories. The refactored implementation > also deprecated static encryption keys in favor of using KeyStores for > reading encryption keys. > The deprecated application properties, along with associated documentation > and implementation code should be removed as part of streamlining efforts for > the next major release version. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11781) Azure AD SSO with OIDC fails in NiFi 1.21.0 and 1.22.0
[
https://issues.apache.org/jira/browse/NIFI-11781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Gresock updated NIFI-11781:
---
Fix Version/s: 2.0.0
(was: 1.latest)
(was: 2.latest)
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Azure AD SSO with OIDC fails in NiFi 1.21.0 and 1.22.0
> --
>
> Key: NIFI-11781
> URL: https://issues.apache.org/jira/browse/NIFI-11781
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 1.21.0, 1.22.0
> Environment: Docker container from
> https://hub.docker.com/r/apache/nifi tags v1.21, v1.22
>Reporter: Evgenity
>Assignee: David Handermann
>Priority: Blocker
> Fix For: 2.0.0, 1.23.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I have successfully applied [the instructions
> |https://github.com/benkelly/NiFi-Authentication-with-Azure-Active-Directory-Setup-Guide]for
> NiFi 1.19, 1.20. It works perfectly for upn claim.
> After changing docker image to 1.21, 1.22 I faced an issue with accounts
> which {+}do not have *emails* assigned in Azure AD{+}.
> In the NiFi release notes I see 'Refactored OpenID Connect integration with
> support for Refresh Tokens' -
> [https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.21.0]
> Isn't this a case?
> With accounts that have 'email' property in Azure AD AND
> nifi.security.user.oidc.claim.identifying.user=email everything works fine.
> NiFi is configured as follows:
> nifi.properties:
> {code:java}
> # OpenId Connect SSO Properties #
> nifi.security.user.oidc.discovery.url=https://login.microsoftonline.com/{{tenantid}}/v2.0/.well-known/openid-configuration
> nifi.security.user.oidc.connect.timeout=5 secs
> nifi.security.user.oidc.read.timeout=5 secs
> nifi.security.user.oidc.client.id=
> nifi.security.user.oidc.client.secret=
> nifi.security.user.oidc.preferred.jwsalgorithm=
> nifi.security.user.oidc.claim.identifying.user=upn
> nifi.security.user.oidc.additional.scopes=profile{code}
> authorizers.xml:
> {code:java}
>
> aad-user-group-provider
>
> 5 mins
> https://login.microsoftonline.com
> {{.Values.auth.oidc.tenantId}}
> {{.Values.auth.oidc.clientId}}
> {{.Values.auth.oidc.clientSecret}}
> PR
> 100
> {code}
> app logs output:
>
> {code:java}
> HTTP ERROR
> 500 java.lang.IllegalArgumentException: Missing attribute 'upn' in
> attributes
> URI: | /nifi-api/access/oidc/callback
> -- | --
> 500
> java.lang.IllegalArgumentException: Missing attribute 'upn' in attributes
> jerseySpring
> java.lang.IllegalArgumentException: Missing attribute 'upn' in attributes
> Caused
> by:java.lang.IllegalArgumentException: Missing attribute 'upn' in
> attributes
> at
> org.springframework.security.oauth2.core.user.DefaultOAuth2User.init(DefaultOAuth2User.java:72)
> at
> org.springframework.security.oauth2.client.userinfo.DefaultOAuth2UserService.loadUser(DefaultOAuth2UserService.java:116)
> at
> org.springframework.security.oauth2.client.oidc.userinfo.OidcUserService.loadUser(OidcUserService.java:109)
> at
> org.springframework.security.oauth2.client.oidc.userinfo.OidcUserService.loadUser(OidcUserService.java:66)
> at
> org.springframework.security.oauth2.client.oidc.authentication.OidcAuthorizationCodeAuthenticationProvider.authenticate(OidcAuthorizationCodeAuthenticationProvider.java:156)
> at
> org.springframework.security.authentication.ProviderManager.authenticate(ProviderManager.java:182)
> at
> org.springframework.security.oauth2.client.web.OAuth2LoginAuthenticationFilter.attemptAuthentication(OAuth2LoginAuthenticationFilter.java:195)
> at
> org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:231)
> at
> org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:221)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:361)
> at
> org.springframework.security.oauth2.server.resource.web.authentication.BearerTokenAuthenticationFilter.doFilterInternal(BearerTokenAuthenticationFilter.java:132)
> at
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:117)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:361)
> at
> org.apache.nifi.web.security.NiFiAuthenticationFilter.authenticate(NiFiAuthenticationFilter.java:94)
> at
> org.apache.nifi.web.security.NiFiAuthenticationFilter.doFilter(NiFiAuthenticationFilter.java:56)
>
[jira] [Updated] (NIFI-11714) Add General Error Handling for Jetty Framework Server
[ https://issues.apache.org/jira/browse/NIFI-11714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock updated NIFI-11714: --- Fix Version/s: 2.0.0 1.23.0 (was: 1.latest) (was: 2.latest) Resolution: Fixed Status: Resolved (was: Patch Available) > Add General Error Handling for Jetty Framework Server > - > > Key: NIFI-11714 > URL: https://issues.apache.org/jira/browse/NIFI-11714 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Fix For: 2.0.0, 1.23.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The Jetty server that supports framework operations should be updated to > include generalized error handling that avoids writing stack traces. > Application REST resources support error handling and simplified messages, > but Jetty handles some exceptions that can result from malformed HTTP > requests. Implementing fallback error handling for Jetty will avoid providing > stack trace information and other information to HTTP clients. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-8531) Upgrade Kinesis Client Library to 2.x
[
https://issues.apache.org/jira/browse/NIFI-8531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Gresock reassigned NIFI-8531:
-
Assignee: Joe Gresock
> Upgrade Kinesis Client Library to 2.x
> -
>
> Key: NIFI-8531
> URL: https://issues.apache.org/jira/browse/NIFI-8531
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: Chris Sampson
>Assignee: Joe Gresock
>Priority: Major
>
> The Kinesis Client Library [KCL] version 1.x is used by the
> {{ConsumeKinesisStream}} processor (NIFI-2892).
> It would be better to upgrade to KCL 2.x as it is more up-to-date and
> provides more advanced features.
> For example, the {{WorkerStateChangeListener}} in 2.x has an
> {{onAllInitializationAttemptsFailed}} method that could be used to better
> track {{Worker}} startup issues (instead of relying on checking for
> unexpected {{WorkerState}} values in our processor's {{onTrigger}} method).
> There are also more configuration options available that would be worth
> considering as processor properties/noting in the processor documentation.
> N.B. upgrading to KCL 2.x relies upon upgrading to AWS Java SDK 2.x first
> (NIFI-8287).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-10797) ElasticSearchClientImpl should allow configuration of useful Elasticsearch RestClient options
[
https://issues.apache.org/jira/browse/NIFI-10797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Gresock updated NIFI-10797:
---
Fix Version/s: 1.22.0
> ElasticSearchClientImpl should allow configuration of useful Elasticsearch
> RestClient options
> -
>
> Key: NIFI-10797
> URL: https://issues.apache.org/jira/browse/NIFI-10797
> Project: Apache NiFi
> Issue Type: Improvement
>Affects Versions: 1.18.0
>Reporter: Chris Sampson
>Assignee: Chris Sampson
>Priority: Major
> Fix For: 2.0.0, 1.22.0
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> The ElasticSearchClientImpl Controller Service should expose and make use of
> useful [Elasticsearch
> RestClient|https://www.elastic.co/guide/en/elasticsearch/client/java-rest/7.13/java-rest-low.html]
> configuration options, such as:
> *
> [Sniffer|https://www.elastic.co/guide/en/elasticsearch/client/java-rest/7.13/_usage.html]
> ** Sniff on connect
> ** Sniff on failure
> * Compression
> * Path Prefix
> * Node Selection: {{Any}} or {{Skip Dedicated Master}}
> The documentation for this controller should probably also indicate that it
> is using version {{7.13.4}} of the Elasticsearch low-level Rest Client
> library so as to remain open source and avoid the library's validation of
> connections being made to Elastic-based services (i.e. the current setup
> within NiFi *should* allow users to connect with Elasticsearch alternatives,
> such as AWS OpenSearch).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-11558) Apply Security Headers to All Responses from Registry
[ https://issues.apache.org/jira/browse/NIFI-11558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock updated NIFI-11558: --- Fix Version/s: 2.0.0 1.22.0 (was: 1.latest) (was: 2.latest) Resolution: Fixed Status: Resolved (was: Patch Available) > Apply Security Headers to All Responses from Registry > - > > Key: NIFI-11558 > URL: https://issues.apache.org/jira/browse/NIFI-11558 > Project: Apache NiFi > Issue Type: Improvement > Components: NiFi Registry, Security >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Fix For: 2.0.0, 1.22.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > NiFi Registry has a common set of filters that apply several standard > security-related HTTP headers to responses. The Jetty Server configuration > applies these headers to the Registry API and UI applications, but requests > to the root path do not return these headers, which can be misleading to some > automated security scanners. For a consistent approach, the security-related > headers should be applied using a Jetty Handler that works for all requests > and responses. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11566) CLI set-param command can timeout in some cases
Joe Gresock created NIFI-11566: -- Summary: CLI set-param command can timeout in some cases Key: NIFI-11566 URL: https://issues.apache.org/jira/browse/NIFI-11566 Project: Apache NiFi Issue Type: Bug Components: Tools and Build Affects Versions: 1.21.0 Reporter: Joe Gresock Assignee: Joe Gresock In cases where controller services take a long time to disable/enable, the NIFI CLI command 'set-param' can timeout, causing problems for client code. This command currently has a hard-coded 60-second timeout, which needs to be configurable. An update timeout should be added as an argument to the command. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11563) Versioned component synchronizer does not stop source connectable for new connection
Joe Gresock created NIFI-11563: -- Summary: Versioned component synchronizer does not stop source connectable for new connection Key: NIFI-11563 URL: https://issues.apache.org/jira/browse/NIFI-11563 Project: Apache NiFi Issue Type: Bug Components: Core Framework Affects Versions: 1.21.0 Reporter: Joe Gresock Assignee: Joe Gresock Although this cannot be reproduced directly in NiFi, if any external tools use the StandardVersionedComponentSynchronizer to synchronize a flow, then adding a connection with an already-running source throws an exception. This is because although upstream connections are restarted for existing connections, they are not restarted for new connections. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-3262) PutElasticsearch support for _routing/_parent
[ https://issues.apache.org/jira/browse/NIFI-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock updated NIFI-3262: -- Fix Version/s: 1.22.0 > PutElasticsearch support for _routing/_parent > - > > Key: NIFI-3262 > URL: https://issues.apache.org/jira/browse/NIFI-3262 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Josh Harrison >Assignee: Chris Sampson >Priority: Major > Fix For: 2.0.0, 1.22.0 > > > Due to the structure of the current nifi Elasticsearch indexing processors, > it doesn't appear possible to specify explicit _routing or _parent fields > when using any of the PutElasticsearch processors (PutElasticsearch, > PutElasticsearchHTTP, PutElasticsearch5). > The ability to optionally specify the _parent and/or _routing parameters that > can be present in a normal bulk index request would be really valuable. > An alternative to adding a handled attribute would be adding support for the > bulk indexing syntax as defined on > https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-bulk.html > - a two line structure where line one contains the indexing instructions in > a JSON object, and line two contains the content of the object. Each line > ends with an explicit newline character (\n). This would allow bulk indexing, > update, delete, etc operations to be carried out through nifi. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-10067) Support script in Elasticsearch update operation
[
https://issues.apache.org/jira/browse/NIFI-10067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Gresock updated NIFI-10067:
---
Fix Version/s: 1.22.0
> Support script in Elasticsearch update operation
>
>
> Key: NIFI-10067
> URL: https://issues.apache.org/jira/browse/NIFI-10067
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: Stijn Caerts
>Assignee: Chris Sampson
>Priority: Major
> Labels: elasticsearch
> Fix For: 2.0.0, 1.22.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Right now, all update operations on Elasticsearch with the
> PutElasticsearchRecord/Json processors use [the partial document update
> approach|https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-update.html#_update_part_of_a_document].
> The content of the flow file is added as the {{doc}} in the update request
> by the
> [ElasticSearchClientServiceImpl|https://github.com/apache/nifi/blob/d79b3908360265eb0d50a5ce298a00c3054cdf82/nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-client-service/src/main/java/org/apache/nifi/elasticsearch/ElasticSearchClientServiceImpl.java#L281].
> Can there also be provided an option to [add a script to the update
> request|https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-update.html#update-api-desc]?
> Using script updates [is supported in the Elasticsearch {{_bulk}}
> API|https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-bulk.html#bulk-update],
> so it should be possible to add this feature.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-3262) PutElasticsearch support for _routing/_parent
[ https://issues.apache.org/jira/browse/NIFI-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock updated NIFI-3262: -- Fix Version/s: 2.0.0 Resolution: Fixed Status: Resolved (was: Patch Available) > PutElasticsearch support for _routing/_parent > - > > Key: NIFI-3262 > URL: https://issues.apache.org/jira/browse/NIFI-3262 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Josh Harrison >Assignee: Chris Sampson >Priority: Major > Fix For: 2.0.0 > > > Due to the structure of the current nifi Elasticsearch indexing processors, > it doesn't appear possible to specify explicit _routing or _parent fields > when using any of the PutElasticsearch processors (PutElasticsearch, > PutElasticsearchHTTP, PutElasticsearch5). > The ability to optionally specify the _parent and/or _routing parameters that > can be present in a normal bulk index request would be really valuable. > An alternative to adding a handled attribute would be adding support for the > bulk indexing syntax as defined on > https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-bulk.html > - a two line structure where line one contains the indexing instructions in > a JSON object, and line two contains the content of the object. Each line > ends with an explicit newline character (\n). This would allow bulk indexing, > update, delete, etc operations to be carried out through nifi. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-10067) Support script in Elasticsearch update operation
[
https://issues.apache.org/jira/browse/NIFI-10067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Gresock updated NIFI-10067:
---
Fix Version/s: 2.0.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Support script in Elasticsearch update operation
>
>
> Key: NIFI-10067
> URL: https://issues.apache.org/jira/browse/NIFI-10067
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: Stijn Caerts
>Assignee: Chris Sampson
>Priority: Major
> Labels: elasticsearch
> Fix For: 2.0.0
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Right now, all update operations on Elasticsearch with the
> PutElasticsearchRecord/Json processors use [the partial document update
> approach|https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-update.html#_update_part_of_a_document].
> The content of the flow file is added as the {{doc}} in the update request
> by the
> [ElasticSearchClientServiceImpl|https://github.com/apache/nifi/blob/d79b3908360265eb0d50a5ce298a00c3054cdf82/nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-client-service/src/main/java/org/apache/nifi/elasticsearch/ElasticSearchClientServiceImpl.java#L281].
> Can there also be provided an option to [add a script to the update
> request|https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-update.html#update-api-desc]?
> Using script updates [is supported in the Elasticsearch {{_bulk}}
> API|https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-bulk.html#bulk-update],
> so it should be possible to add this feature.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-8287) Upgrade AWS SQS Processors to use AWS 2.x libraries
[ https://issues.apache.org/jira/browse/NIFI-8287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock updated NIFI-8287: -- Attachment: NIFI-8287.json > Upgrade AWS SQS Processors to use AWS 2.x libraries > --- > > Key: NIFI-8287 > URL: https://issues.apache.org/jira/browse/NIFI-8287 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Chris Sampson >Assignee: Joe Gresock >Priority: Major > Attachments: NIFI-8287.json > > > AWS has updated many of their libraries to version 2.x. NiFi should look to > make use of these, potentially enabling access to new features, performance > and bug improvements. > To enable an incremental review process, this issue will focus on upgrading > just the SQS processors to use library version 2.x. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-8287) Upgrade AWS SQS Processors to use AWS 2.x libraries
[ https://issues.apache.org/jira/browse/NIFI-8287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock updated NIFI-8287: -- Description: AWS has updated many of their libraries to version 2.x. NiFi should look to make use of these, potentially enabling access to new features, performance and bug improvements. To enable an incremental review process, this issue will focus on upgrading just the SQS processors to use library version 2.x. was: AWS has updated many of their libraries to version 2.x. NiFi should look to make use of these, potentially enabling access to new features, performance and bug improvements. There will be need to update the general AWS libraries, but potentially related libraries used by the individual AWS-related processors (for example, the Kinesis processors where they use the Kinesis Client Library). > Upgrade AWS SQS Processors to use AWS 2.x libraries > --- > > Key: NIFI-8287 > URL: https://issues.apache.org/jira/browse/NIFI-8287 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Chris Sampson >Assignee: Joe Gresock >Priority: Major > Attachments: NIFI-8287.json > > > AWS has updated many of their libraries to version 2.x. NiFi should look to > make use of these, potentially enabling access to new features, performance > and bug improvements. > To enable an incremental review process, this issue will focus on upgrading > just the SQS processors to use library version 2.x. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-8287) Upgrade AWS SQS Processors to use AWS 2.x libraries
[ https://issues.apache.org/jira/browse/NIFI-8287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock updated NIFI-8287: -- Summary: Upgrade AWS SQS Processors to use AWS 2.x libraries (was: Upgrade AWS Processors to use AWS 2.x libraries) > Upgrade AWS SQS Processors to use AWS 2.x libraries > --- > > Key: NIFI-8287 > URL: https://issues.apache.org/jira/browse/NIFI-8287 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Chris Sampson >Assignee: Joe Gresock >Priority: Major > > AWS has updated many of their libraries to version 2.x. NiFi should look to > make use of these, potentially enabling access to new features, performance > and bug improvements. > There will be need to update the general AWS libraries, but potentially > related libraries used by the individual AWS-related processors (for example, > the Kinesis processors where they use the Kinesis Client Library). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11276) Upgrade nifi-toolkit-api to Swagger Codegen 3
[
https://issues.apache.org/jira/browse/NIFI-11276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Gresock updated NIFI-11276:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Upgrade nifi-toolkit-api to Swagger Codegen 3
> -
>
> Key: NIFI-11276
> URL: https://issues.apache.org/jira/browse/NIFI-11276
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Tools and Build
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Minor
> Fix For: 2.latest
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The {{nifi-toolkit-api}} provides generated Java classes for NiFi REST API
> resources and models using the [Swagger
> Codegen|https://swagger.io/docs/open-source-tools/swagger-codegen/] Maven
> Plugin. The plugin should be updated from version 2 to version 3, which
> provides compatibility with current Swagger specifications and supports the
> latest OpenAPI specification.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (NIFI-11336) Add CapabilityDescription for PutAccumuloRecord
Joe Gresock created NIFI-11336: -- Summary: Add CapabilityDescription for PutAccumuloRecord Key: NIFI-11336 URL: https://issues.apache.org/jira/browse/NIFI-11336 Project: Apache NiFi Issue Type: Improvement Components: Extensions Affects Versions: 1.20.0 Reporter: Joe Gresock Assignee: Joe Gresock Fix For: 2.0.0, 1.21.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11330) StandardVersionedComponentSynchronizer improperly restarts controller services when parameter is changed
Joe Gresock created NIFI-11330: -- Summary: StandardVersionedComponentSynchronizer improperly restarts controller services when parameter is changed Key: NIFI-11330 URL: https://issues.apache.org/jira/browse/NIFI-11330 Project: Apache NiFi Issue Type: Bug Components: Core Framework Affects Versions: 1.20.0 Reporter: Joe Gresock Assignee: Joe Gresock Fix For: 2.0.0, 1.21.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11291) EventIterator leak in PartitionedEventStore
Joe Gresock created NIFI-11291: -- Summary: EventIterator leak in PartitionedEventStore Key: NIFI-11291 URL: https://issues.apache.org/jira/browse/NIFI-11291 Project: Apache NiFi Issue Type: Bug Reporter: Joe Gresock Assignee: Joe Gresock If an exception is thrown at SequentialRecordReaderEventIterator.java:121, the EventIterator is not closed, resulting in a leak. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-11231) Stateless Nifi Supports Sensitive Parameter Context Variables
[ https://issues.apache.org/jira/browse/NIFI-11231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17698592#comment-17698592 ] Joe Gresock commented on NIFI-11231: Just to follow up, sensitive parameters are supported in stateless flows using ParameterValueProviders, including the built-in EnvironmentVariableParameterValueProvider. This is the preferred approach rather than using ParameterProviders, which are currently not supported by design in Stateless. If other use cases are needed, I'd recommend submitting another ticket. > Stateless Nifi Supports Sensitive Parameter Context Variables > - > > Key: NIFI-11231 > URL: https://issues.apache.org/jira/browse/NIFI-11231 > Project: Apache NiFi > Issue Type: Bug > Components: NiFi Stateless >Affects Versions: 1.20.0 >Reporter: Dye357 >Assignee: Stephanie Ambrose >Priority: Major > Time Spent: 1h 40m > Remaining Estimate: 0h > > Currently Sensitive Parameter Context Variables are not supported in > Stateless Nifi - this is due to StatelessFlowManager being stubbed to throw a > "Not Implemented" exception when providing a process group configured with a > secure Parameter Context variable. > Desired functionality: Sensitive Parameter Context Variables can be used with > stateless Nifi. If a process group contains a Sensitive Parameter Context > Variable the context is used to hydrate all parameters within the provided > flow including any marked sensitive. > Acceptance Criteria: Process Groups using secure parameters can be used in > stateless Nifi. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11262) Correct test scope for Bouncy Castle in nifi-security-kerberos
[
https://issues.apache.org/jira/browse/NIFI-11262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Gresock updated NIFI-11262:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Correct test scope for Bouncy Castle in nifi-security-kerberos
> --
>
> Key: NIFI-11262
> URL: https://issues.apache.org/jira/browse/NIFI-11262
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.19.0, 1.20.0, 1.19.1
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
> Fix For: 2.0.0, 1.21.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Changes introduced when upgrading to Bouncy Castle 1.71 inadvertently changed
> the scope of {{bcprov-jdk18on}} in the {{nifi-security-kerberos}} module,
> resulting in unnecessary packaging of the Bouncy Castle library in multiple
> modules.
> The Bouncy Castle Provider library should be a test dependency in
> {{nifi-security-kerberos}}. The {{bcprov-jdk18on}} library is necessary only
> for the {{hadoop-minikdc}} test dependency.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-11247) Fetch Parameters fails when Parameter Context name is different from group name
[
https://issues.apache.org/jira/browse/NIFI-11247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Gresock updated NIFI-11247:
---
Summary: Fetch Parameters fails when Parameter Context name is different
from group name (was: Parameter Context Provider - parameterSensitivities is
not set)
> Fetch Parameters fails when Parameter Context name is different from group
> name
> ---
>
> Key: NIFI-11247
> URL: https://issues.apache.org/jira/browse/NIFI-11247
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework, Core UI
>Reporter: Pierre Villard
>Priority: Major
>
> Running main. Have a File Parameter Provider (plain text for encoding).
> If changing the content of one of my files, and trying to update my PC,
> clicking the button has no action and will result in an always spinning
> circle.
> Stacktrace in browser console:
> {code:java}
> Uncaught TypeError: Cannot read properties of undefined (reading
> 'parameterSensitivities')
> at Object. (nf-canvas-all.js?2.0.0-SNAPSHOT:59:13821)
> at Function.each (jquery.min.js:2:3003)
> at b.each (jquery.each.js:1:96)
> at e (nf-canvas-all.js?2.0.0-SNAPSHOT:59:13625)
> at Object. (nf-canvas-all.js?2.0.0-SNAPSHOT:59:9624)
> at c (jquery.min.js:2:28327)
> at Object.fireWith [as resolveWith] (jquery.min.js:2:29072)
> at l (jquery.min.js:2:79901)
> at XMLHttpRequest. (jquery.min.js:2:82355) {code}
> However I do see this in nifi-app.log
> {code:java}
> 2023-03-03 20:42:47,268 INFO [NiFi Web Server-91]
> o.a.nifi.parameter.FileParameterProvider
> FileParameterProvider[id=a8f40c9c-0186-1000-cba7-779a450a7c44] Fetched 6
> parameters. Group names: [parameters] {code}
> But the parameters are not updated in my parameter context.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (NIFI-11238) Exception importing Inherited provided parameter contexts
Joe Gresock created NIFI-11238: -- Summary: Exception importing Inherited provided parameter contexts Key: NIFI-11238 URL: https://issues.apache.org/jira/browse/NIFI-11238 Project: Apache NiFi Issue Type: Bug Affects Versions: 1.20.0 Reporter: Joe Gresock Assignee: Joe Gresock If a process group with an inherited, provided parameter context is imported and the parameter provider does not already exist, an exception is thrown: "Could not configure Parameter Provider , which could not be found" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11195) Refactor Identity Mapping to nifi-security-identity
[
https://issues.apache.org/jira/browse/NIFI-11195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Gresock updated NIFI-11195:
---
Fix Version/s: 2.0.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Refactor Identity Mapping to nifi-security-identity
> ---
>
> Key: NIFI-11195
> URL: https://issues.apache.org/jira/browse/NIFI-11195
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
> Fix For: 2.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The {{nifi-security-utils}} module has several classes for translating
> identity information based on application properties. This classes are not
> related to other cryptographic operations in {{nifi-security-utils}} and
> should be moved to separate module to reduce transitive dependencies.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-11211) Remove SSLContextService.createSSLContext Methods
[
https://issues.apache.org/jira/browse/NIFI-11211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Gresock updated NIFI-11211:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Remove SSLContextService.createSSLContext Methods
> -
>
> Key: NIFI-11211
> URL: https://issues.apache.org/jira/browse/NIFI-11211
> Project: Apache NiFi
> Issue Type: Task
> Components: Extensions
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
> Fix For: 2.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The {{SSLContextService}} has two deprecated {{createSSLContext}} methods
> that are not used in project components. These methods were deprecated in
> NiFi 1.13.0 and should be removed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-10797) ElasticSearchClientImpl should allow configuration of useful Elasticsearch RestClient options
[
https://issues.apache.org/jira/browse/NIFI-10797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Gresock updated NIFI-10797:
---
Fix Version/s: 2.0.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> ElasticSearchClientImpl should allow configuration of useful Elasticsearch
> RestClient options
> -
>
> Key: NIFI-10797
> URL: https://issues.apache.org/jira/browse/NIFI-10797
> Project: Apache NiFi
> Issue Type: Improvement
>Affects Versions: 1.18.0
>Reporter: Chris Sampson
>Assignee: Chris Sampson
>Priority: Major
> Fix For: 2.0.0
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> The ElasticSearchClientImpl Controller Service should expose and make use of
> useful [Elasticsearch
> RestClient|https://www.elastic.co/guide/en/elasticsearch/client/java-rest/7.13/java-rest-low.html]
> configuration options, such as:
> *
> [Sniffer|https://www.elastic.co/guide/en/elasticsearch/client/java-rest/7.13/_usage.html]
> ** Sniff on connect
> ** Sniff on failure
> * Compression
> * Path Prefix
> * Node Selection: {{Any}} or {{Skip Dedicated Master}}
> The documentation for this controller should probably also indicate that it
> is using version {{7.13.4}} of the Elasticsearch low-level Rest Client
> library so as to remain open source and avoid the library's validation of
> connections being made to Elastic-based services (i.e. the current setup
> within NiFi *should* allow users to connect with Elasticsearch alternatives,
> such as AWS OpenSearch).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (NIFI-11122) Unable to inherit AWS Provided parameter context into User-defined context
[ https://issues.apache.org/jira/browse/NIFI-11122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock reassigned NIFI-11122: -- Assignee: Joe Gresock > Unable to inherit AWS Provided parameter context into User-defined context > -- > > Key: NIFI-11122 > URL: https://issues.apache.org/jira/browse/NIFI-11122 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.19.1 >Reporter: Dmitry >Assignee: Joe Gresock >Priority: Minor > Attachments: image-2023-01-31-16-56-54-672.png > > > I can manually create a user-defined Param Context and create inheritance > with AWS Secrets-based context ONLY while I'm "Creating the context". > I can remove inheritance with AWS Secrets-based context from user-defined > contexts, but I cannot add anything there. > I cannot add inheritance with AWS Secrets-based context to any present or > already created user-defined contexts. > > !image-2023-01-31-16-56-54-672.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11100) Cannot update controller service property of an inner process group when changing version
Joe Gresock created NIFI-11100: -- Summary: Cannot update controller service property of an inner process group when changing version Key: NIFI-11100 URL: https://issues.apache.org/jira/browse/NIFI-11100 Project: Apache NiFi Issue Type: Bug Affects Versions: 1.19.1 Reporter: Joe Gresock Assignee: Joe Gresock To reproduce: # Create a process group, and add a CSVReader controller service to that group, named "Outer" # Create a process group inside that group, and add a CSVReader controller service the inner group, named "Inner" # Add a CalculateRecordStats processor (or any with a reader property) and select the Inner service. # Version control the outer group. # Change the property to point to Inner. # Save the version. # Change the version back to 1: the property will have remained unchanged -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11032) NPE during Import from Registry
[
https://issues.apache.org/jira/browse/NIFI-11032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Gresock updated NIFI-11032:
---
Status: Patch Available (was: Open)
> NPE during Import from Registry
> ---
>
> Key: NIFI-11032
> URL: https://issues.apache.org/jira/browse/NIFI-11032
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 1.19.1
>Reporter: Bryan Bende
>Assignee: Joe Gresock
>Priority: Minor
> Fix For: 1.20.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {color:#1d1c1d}upgraded NiFi and NiFi Registry from 1.16.0 to 1.19.1{color}
> {code:java}
> 2023-01-06 23:43:55,879 ERROR [NiFi Web Server-153]
> o.a.nifi.web.api.config.ThrowableMapper An unexpected error has occurred:
> java.lang.NullPointerException. Returning Internal Server Error
> response.java.lang.NullPointerException: null at
> org.apache.nifi.web.api.FlowResource.populateRemainingRegistryClientEntityContent(FlowResource.java:1649)
> at
> org.apache.nifi.web.api.FlowResource.populateRemainingRegistryClientEntityContent(FlowResource.java:1661)
> at
> org.apache.nifi.web.api.FlowResource.getRegistryClients(FlowResource.java:1637)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498) at {code}
> {color:#1d1c1d}I do not get this error when I use the "Administrator"
> account.{color} {color:#1d1c1d}I think I solved it by adding the user account
> to the Access Policy "access the controller" with View permissions. The
> Administrator was already there. {color}{color:#1d1c1d}The error no longer
> occurs.{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (NIFI-11089) Import from registry can create duplicate parameter providers
[ https://issues.apache.org/jira/browse/NIFI-11089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock reassigned NIFI-11089: -- Assignee: Joe Gresock > Import from registry can create duplicate parameter providers > - > > Key: NIFI-11089 > URL: https://issues.apache.org/jira/browse/NIFI-11089 > Project: Apache NiFi > Issue Type: Bug >Reporter: Bryan Bende >Assignee: Joe Gresock >Priority: Minor > > While testing the fix for NIFI-11039, I created a scenario that created > duplicate providers when importing from registry, when the intent was for > them to be the same provider. > Scenario: > * Create FileParameterProvider with two directories specified (group1, > group2) > * Create parameter contexts from each group > * Create a flow with parent pg and child pg > * Configure parent to use group1 context > * Configure child to use group2 context > * Save flow to registry > * Delete everything from nifi (PGs, contexts, provider) > * Import PG from registry > Import succeeds because of the issue resolved in NIFI-11039, but note that > now two instances of FileParameterProvider were created, when the snapshot > from registry only has one instance. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-11032) NPE during Import from Registry
[
https://issues.apache.org/jira/browse/NIFI-11032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Gresock reassigned NIFI-11032:
--
Assignee: Joe Gresock
> NPE during Import from Registry
> ---
>
> Key: NIFI-11032
> URL: https://issues.apache.org/jira/browse/NIFI-11032
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 1.19.1
>Reporter: Bryan Bende
>Assignee: Joe Gresock
>Priority: Minor
>
> {color:#1d1c1d}upgraded NiFi and NiFi Registry from 1.16.0 to 1.19.1{color}
> {code:java}
> 2023-01-06 23:43:55,879 ERROR [NiFi Web Server-153]
> o.a.nifi.web.api.config.ThrowableMapper An unexpected error has occurred:
> java.lang.NullPointerException. Returning Internal Server Error
> response.java.lang.NullPointerException: null at
> org.apache.nifi.web.api.FlowResource.populateRemainingRegistryClientEntityContent(FlowResource.java:1649)
> at
> org.apache.nifi.web.api.FlowResource.populateRemainingRegistryClientEntityContent(FlowResource.java:1661)
> at
> org.apache.nifi.web.api.FlowResource.getRegistryClients(FlowResource.java:1637)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498) at {code}
> {color:#1d1c1d}I do not get this error when I use the "Administrator"
> account.{color} {color:#1d1c1d}I think I solved it by adding the user account
> to the Access Policy "access the controller" with View permissions. The
> Administrator was already there. {color}{color:#1d1c1d}The error no longer
> occurs.{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-11039) Importing flow should handle missing parameter provider
[
https://issues.apache.org/jira/browse/NIFI-11039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Gresock updated NIFI-11039:
---
Status: Patch Available (was: Open)
> Importing flow should handle missing parameter provider
> ---
>
> Key: NIFI-11039
> URL: https://issues.apache.org/jira/browse/NIFI-11039
> Project: Apache NiFi
> Issue Type: Improvement
>Affects Versions: 1.19.1, 1.19.0, 1.18.0
>Reporter: Bryan Bende
>Assignee: Joe Gresock
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> From Apache Slack:
> {color:#1d1c1d}We have been using deployment of Parameter Contexts using
> Parameter Providers in Nifi v1.18.0. We are also using the NiFi registry to
> save Processor Groups and restore them into the current flow. There is an
> issue where if a Process Group is saved with a Parameter Context, that has
> been created via a Parameter Provider and the Provider has been deleted, the
> flow fails to deploy saying the provider does not exist. I guess I would
> expect the behavior to create the Parameter Provider if it doesn't exist,
> just like when the Parameter Contexts, Controller Services ect. Even if the
> desired behavior is to not create Parameter Providers, the import from the
> registry should still fail gracefully and allow the remaining flow to be
> imported, ignoring the missing Provider. If I get a flow into this state, I
> either have to find an older version of the flow in the registry to recover,
> or I need to manually download, modify and re-upload the PG in order to get
> the flow deployed.{color}
> {color:#1d1c1d}Stacktrace:{color}
> {code:java}
> 2023-01-10 19:35:02,293 INFO [NiFi Web Server-43]
> o.a.n.w.a.c.IllegalArgumentExceptionMapper
> java.lang.IllegalArgumentException: Could not configure Parameter Provider
> 985860cf-0185-1000-dcb9-6a2c63edbdbf, which could not be found}. Returning
> Bad Request} response.java.lang.IllegalArgumentException: Could not configure
> Parameter Provider 985860cf-0185-1000-dcb9-6a2c63edbdbf, which could not be
> foundat
> org.apache.nifi.parameter.StandardParameterContext.configureParameterProvider(StandardParameterContext.java:482)
> at
> org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.addMissingConfiguration(StandardVersionedComponentSynchronizer.java:2093)
> at
> org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.selectParameterContext(StandardVersionedComponentSynchronizer.java:2056)
> at
> org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.lambda$addMissingConfiguration$30(StandardVersionedComponentSynchronizer.java:2089)
> at
> java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195)
> at
> java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1655)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (NIFI-11076) NiFi build locks up in stateless nifi tests due to deadlock
[ https://issues.apache.org/jira/browse/NIFI-11076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock reassigned NIFI-11076: -- Assignee: Joe Gresock > NiFi build locks up in stateless nifi tests due to deadlock > --- > > Key: NIFI-11076 > URL: https://issues.apache.org/jira/browse/NIFI-11076 > Project: Apache NiFi > Issue Type: Bug > Environment: windows/osx. Env seems not important >Reporter: Joe Witt >Assignee: Joe Gresock >Priority: Blocker > Fix For: 1.20.0 > > Attachments: hung-nifi-other.txt, hung-nifi.txt > > > Will attach two thread dumps from the running build processes/forked > execution which show deadlock. Likely the same problem hit on github ci the > other day too for the windows build > https://github.com/apache/nifi/actions/runs/3958072460/jobs/6779197263 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-11039) Importing flow should handle missing parameter provider
[
https://issues.apache.org/jira/browse/NIFI-11039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Gresock reassigned NIFI-11039:
--
Assignee: Joe Gresock
> Importing flow should handle missing parameter provider
> ---
>
> Key: NIFI-11039
> URL: https://issues.apache.org/jira/browse/NIFI-11039
> Project: Apache NiFi
> Issue Type: Improvement
>Affects Versions: 1.18.0, 1.19.0, 1.19.1
>Reporter: Bryan Bende
>Assignee: Joe Gresock
>Priority: Major
>
> From Apache Slack:
> {color:#1d1c1d}We have been using deployment of Parameter Contexts using
> Parameter Providers in Nifi v1.18.0. We are also using the NiFi registry to
> save Processor Groups and restore them into the current flow. There is an
> issue where if a Process Group is saved with a Parameter Context, that has
> been created via a Parameter Provider and the Provider has been deleted, the
> flow fails to deploy saying the provider does not exist. I guess I would
> expect the behavior to create the Parameter Provider if it doesn't exist,
> just like when the Parameter Contexts, Controller Services ect. Even if the
> desired behavior is to not create Parameter Providers, the import from the
> registry should still fail gracefully and allow the remaining flow to be
> imported, ignoring the missing Provider. If I get a flow into this state, I
> either have to find an older version of the flow in the registry to recover,
> or I need to manually download, modify and re-upload the PG in order to get
> the flow deployed.{color}
> {color:#1d1c1d}Stacktrace:{color}
> {code:java}
> 2023-01-10 19:35:02,293 INFO [NiFi Web Server-43]
> o.a.n.w.a.c.IllegalArgumentExceptionMapper
> java.lang.IllegalArgumentException: Could not configure Parameter Provider
> 985860cf-0185-1000-dcb9-6a2c63edbdbf, which could not be found}. Returning
> Bad Request} response.java.lang.IllegalArgumentException: Could not configure
> Parameter Provider 985860cf-0185-1000-dcb9-6a2c63edbdbf, which could not be
> foundat
> org.apache.nifi.parameter.StandardParameterContext.configureParameterProvider(StandardParameterContext.java:482)
> at
> org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.addMissingConfiguration(StandardVersionedComponentSynchronizer.java:2093)
> at
> org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.selectParameterContext(StandardVersionedComponentSynchronizer.java:2056)
> at
> org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.lambda$addMissingConfiguration$30(StandardVersionedComponentSynchronizer.java:2089)
> at
> java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195)
> at
> java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1655)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-10987) Add default implementation of AWS SDK V2 credentials in AWSCredentialsProviderService
[
https://issues.apache.org/jira/browse/NIFI-10987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Gresock updated NIFI-10987:
---
Fix Version/s: 1.20.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Add default implementation of AWS SDK V2 credentials in
> AWSCredentialsProviderService
> -
>
> Key: NIFI-10987
> URL: https://issues.apache.org/jira/browse/NIFI-10987
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
>Reporter: Peter Turcsanyi
>Assignee: Peter Turcsanyi
>Priority: Minor
> Fix For: 1.20.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> NIFI-10791 introduced support for AWS SDK V2 credentials
> ({{{}AwsCredentialsProviderService.getAwsCredentialsProvider(){}}}).
> {{AWSCredentialsProviderService}} extends this interface and
> {{AWSCredentialsProviderControllerService}} implements the new method but
> other 3rd party implementors (that are not part of the Apache NiFi code base)
> would break with this change due to the new interface method.
> Add default implementation throwing {{UnsupportedOperationException}} to
> provide backward compatibility at source level.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-10866) Refactor Kafka 1.0 and 2.0 Components using nifi-kafka-shared
[
https://issues.apache.org/jira/browse/NIFI-10866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Gresock updated NIFI-10866:
---
Fix Version/s: 1.19.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Refactor Kafka 1.0 and 2.0 Components using nifi-kafka-shared
> -
>
> Key: NIFI-10866
> URL: https://issues.apache.org/jira/browse/NIFI-10866
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Minor
> Fix For: 1.19.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The Kafka 1.0 and 2.0 components should be refactored to use property and
> validation components in {{nifi-kafka-shared}}.
> This refactoring will reduce duplicate code and also bring additional
> security measures to the validation of custom sasl.jaas.config properties
> across all Kafka components
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-10819) Restrict Modules in sasl.jaas.config Kafka Client Property
[
https://issues.apache.org/jira/browse/NIFI-10819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Gresock updated NIFI-10819:
---
Fix Version/s: 1.19.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Restrict Modules in sasl.jaas.config Kafka Client Property
> --
>
> Key: NIFI-10819
> URL: https://issues.apache.org/jira/browse/NIFI-10819
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Minor
> Fix For: 1.19.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Kafka components support dynamic properties to provide additional client
> settings beyond the scope of standard component settings.
> The {{sasl.jaas.config}} Kafka client property supports specifying a complete
> JAAS configuration with custom Login Modules, some of which are not
> supported. The standard Kafka client configuration methods should be updated
> to reject unsupported modules.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-7862) Add UpdateDatabaseTable processor to optionally create the target table and/or columns if they don't exist
[ https://issues.apache.org/jira/browse/NIFI-7862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock updated NIFI-7862: -- Fix Version/s: 1.19.0 Resolution: Fixed Status: Resolved (was: Patch Available) > Add UpdateDatabaseTable processor to optionally create the target table > and/or columns if they don't exist > -- > > Key: NIFI-7862 > URL: https://issues.apache.org/jira/browse/NIFI-7862 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: Matt Burgess >Assignee: Matt Burgess >Priority: Major > Fix For: 1.19.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > As part of NIFI-6934, the "Database Type" property was added, allowing for > DB-specific SQL/DML to be generated. That property could be used with a new > true/false property "Create Table" that would create the target table if it > didn't already exist. mapping the NiFi Record datatypes to DB-specific column > types and generating/executing a DB-specific CREATE TABLE statement. If > "Create Table" is set to true and an error occurs while attempting to create > the table, the flowfile should be routed to failure or rolled back (depending > on the setting of the "Rollback on Failure" property). > Also it could support some schema migration (adding columns, e.g.) with an > additional value in the "Unmatched Field Behavior" property for "Create > Column on Unmatched Fields". The use case here is for feature parity with > UpdateHiveTable (see NIFI-7989) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-9697) Azure Key Vault Parameter Provider
[ https://issues.apache.org/jira/browse/NIFI-9697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock resolved NIFI-9697. --- Fix Version/s: 1.19.0 Resolution: Fixed > Azure Key Vault Parameter Provider > -- > > Key: NIFI-9697 > URL: https://issues.apache.org/jira/browse/NIFI-9697 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: Joe Gresock >Assignee: Emilio Setiadarma >Priority: Major > Fix For: 1.19.0 > > Time Spent: 3h 10m > Remaining Estimate: 0h > > Once NIFI-9003 is complete, implement an Azure Key Vault Parameter Provider. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-10791) Add AWS V2 SDK implementation to AWSCredentialsProviderControllerService
Joe Gresock created NIFI-10791: -- Summary: Add AWS V2 SDK implementation to AWSCredentialsProviderControllerService Key: NIFI-10791 URL: https://issues.apache.org/jira/browse/NIFI-10791 Project: Apache NiFi Issue Type: Improvement Reporter: Joe Gresock Assignee: Joe Gresock In anticipation of upgrading various AWS processors to use the v2 SDK, it would be good to add support for retrieving a v2 AWS credentials provider to the existing AWSCredentialsProviderControllerService. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-10770) Remove unnecessary parameter fetch upon startup
Joe Gresock created NIFI-10770: -- Summary: Remove unnecessary parameter fetch upon startup Key: NIFI-10770 URL: https://issues.apache.org/jira/browse/NIFI-10770 Project: Apache NiFi Issue Type: Improvement Affects Versions: 1.18.0 Reporter: Joe Gresock Assignee: Joe Gresock Fix For: 1.19.0 Parameters are automatically fetched upon startup, which is unnecessary because in order to interact with the fetched parameters, the Fetch Parameters dialog must be opened, and this fetches them anyway. If dependent controller services are still ENABLING at the time of the startup fetch, this can lead to confusing warnings. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-10643) AwsSecretsManagerParameterProvider only retrieves first page of secrets
Joe Gresock created NIFI-10643: -- Summary: AwsSecretsManagerParameterProvider only retrieves first page of secrets Key: NIFI-10643 URL: https://issues.apache.org/jira/browse/NIFI-10643 Project: Apache NiFi Issue Type: Bug Components: Extensions Affects Versions: 1.18.0 Reporter: Joe Gresock Assignee: Joe Gresock Fix For: 1.19.0 The Secrets listing must be paged through in order to retrieve all matching secrets. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-10641) Typo in ParameterProvider warning message
Joe Gresock created NIFI-10641:
--
Summary: Typo in ParameterProvider warning message
Key: NIFI-10641
URL: https://issues.apache.org/jira/browse/NIFI-10641
Project: Apache NiFi
Issue Type: Bug
Components: Core Framework
Affects Versions: 1.18.0
Reporter: Joe Gresock
Assignee: Joe Gresock
Fix For: 1.19.0
This error message has an extra } character that should be removed. "Skipping
parameter [{}}], whose name has invalid characters."
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-10633) ParameterProvider and/or ControllerService only support HashiCorp Vault KV v1
[ https://issues.apache.org/jira/browse/NIFI-10633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock updated NIFI-10633: --- Status: Patch Available (was: In Progress) > ParameterProvider and/or ControllerService only support HashiCorp Vault KV v1 > - > > Key: NIFI-10633 > URL: https://issues.apache.org/jira/browse/NIFI-10633 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation Website >Affects Versions: 1.18.0 >Reporter: Chris Scheib >Assignee: Joe Gresock >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The documentation for the HashiCorp Vault ParameterProvider > (HashiCorpVaultParameterProvider) and Controller Service > (StandardHashiCorpVaultClientService) don't denote that they currently only > support secret stores of type KV v1. Integration fails with type of KV v2. > KV v2 supports secrets versioning and has a slightly different API. > Please update the documentation to reflect supported secret stores. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-10633) ParameterProvider and/or ControllerService only support HashiCorp Vault KV v1
[ https://issues.apache.org/jira/browse/NIFI-10633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock reassigned NIFI-10633: -- Assignee: Joe Gresock > ParameterProvider and/or ControllerService only support HashiCorp Vault KV v1 > - > > Key: NIFI-10633 > URL: https://issues.apache.org/jira/browse/NIFI-10633 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation Website >Affects Versions: 1.18.0 >Reporter: Chris Scheib >Assignee: Joe Gresock >Priority: Major > > The documentation for the HashiCorp Vault ParameterProvider > (HashiCorpVaultParameterProvider) and Controller Service > (StandardHashiCorpVaultClientService) don't denote that they currently only > support secret stores of type KV v1. Integration fails with type of KV v2. > KV v2 supports secrets versioning and has a slightly different API. > Please update the documentation to reflect supported secret stores. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-10564) UI - Update the "access the controller" access policy help text
[ https://issues.apache.org/jira/browse/NIFI-10564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock resolved NIFI-10564. Resolution: Fixed > UI - Update the "access the controller" access policy help text > --- > > Key: NIFI-10564 > URL: https://issues.apache.org/jira/browse/NIFI-10564 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Affects Versions: 1.18.0 >Reporter: Andrew M. Lim >Assignee: Andrew M. Lim >Priority: Minor > Fix For: 1.19.0 > > Attachments: image-2022-09-29-17-38-45-226.png > > > Now that we have Management Controller Services and Parameter Providers > available in the NiFi Settings dialog, we should update the help text for the > related access policy. > Current: > !image-2022-09-29-17-38-45-226.png! > Proposed change: > Allows users to view and modify the controller including Management > Controller Services, Reporting Tasks, Registry Clients, Parameter Providers > and nodes in the cluster -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-10564) UI - Update the "access the controller" access policy help text
[ https://issues.apache.org/jira/browse/NIFI-10564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock updated NIFI-10564: --- Fix Version/s: 1.19.0 > UI - Update the "access the controller" access policy help text > --- > > Key: NIFI-10564 > URL: https://issues.apache.org/jira/browse/NIFI-10564 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Affects Versions: 1.18.0 >Reporter: Andrew M. Lim >Assignee: Andrew M. Lim >Priority: Minor > Fix For: 1.19.0 > > Attachments: image-2022-09-29-17-38-45-226.png > > > Now that we have Management Controller Services and Parameter Providers > available in the NiFi Settings dialog, we should update the help text for the > related access policy. > Current: > !image-2022-09-29-17-38-45-226.png! > Proposed change: > Allows users to view and modify the controller including Management > Controller Services, Reporting Tasks, Registry Clients, Parameter Providers > and nodes in the cluster -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-10572) Adding an external variable can get an inner version controlled group into an unrevertable state
[
https://issues.apache.org/jira/browse/NIFI-10572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17612245#comment-17612245
]
Joe Gresock commented on NIFI-10572:
Two things going on here. First, the StandardVersionedComponentSynchronizer
does not remove variables when changing versions, only adds them. Second,
there is a mismatch between detecting local changes and being able to revert
them when an inherited variable is added/updated/removed.
> Adding an external variable can get an inner version controlled group into an
> unrevertable state
>
>
> Key: NIFI-10572
> URL: https://issues.apache.org/jira/browse/NIFI-10572
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 1.17.0
>Reporter: Joe Gresock
>Assignee: Joe Gresock
>Priority: Major
>
> 1. Create a process group, ‘APG’
> 2. Create a process group inside ‘APG’, called ‘BPG’.
> 3. Create a processor (I used InvokeHTTP) inside BPG, add a dynamic property:
> test = ${test}
> 4. Version control BPG
> 5. Add a variable ‘test’ in APG
> 6. Move BPG, and it will instantly indicate a local change. Now you are in
> the state where you cannot revert changes to BPG, but it still thinks it has
> local changes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (NIFI-10572) Adding an external variable can get an inner version controlled group into an unrevertable state
[
https://issues.apache.org/jira/browse/NIFI-10572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Gresock reassigned NIFI-10572:
--
Assignee: Joe Gresock
> Adding an external variable can get an inner version controlled group into an
> unrevertable state
>
>
> Key: NIFI-10572
> URL: https://issues.apache.org/jira/browse/NIFI-10572
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 1.17.0
>Reporter: Joe Gresock
>Assignee: Joe Gresock
>Priority: Major
>
> 1. Create a process group, ‘APG’
> 2. Create a process group inside ‘APG’, called ‘BPG’.
> 3. Create a processor (I used InvokeHTTP) inside BPG, add a dynamic property:
> test = ${test}
> 4. Version control BPG
> 5. Add a variable ‘test’ in APG
> 6. Move BPG, and it will instantly indicate a local change. Now you are in
> the state where you cannot revert changes to BPG, but it still thinks it has
> local changes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (NIFI-10501) Add/update documentation for new Parameter Providers feature
[ https://issues.apache.org/jira/browse/NIFI-10501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock resolved NIFI-10501. Resolution: Fixed > Add/update documentation for new Parameter Providers feature > > > Key: NIFI-10501 > URL: https://issues.apache.org/jira/browse/NIFI-10501 > Project: Apache NiFi > Issue Type: Sub-task > Components: Documentation Website >Reporter: Andrew M. Lim >Assignee: Andrew M. Lim >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-10572) Adding an external variable can get an inner version controlled group into an unrevertable state
Joe Gresock created NIFI-10572:
--
Summary: Adding an external variable can get an inner version
controlled group into an unrevertable state
Key: NIFI-10572
URL: https://issues.apache.org/jira/browse/NIFI-10572
Project: Apache NiFi
Issue Type: Bug
Components: Core Framework
Affects Versions: 1.17.0
Reporter: Joe Gresock
1. Create a process group, ‘APG’
2. Create a process group inside ‘APG’, called ‘BPG’.
3. Create a processor (I used InvokeHTTP) inside BPG, add a dynamic property:
test = ${test}
4. Version control BPG
5. Add a variable ‘test’ in APG
6. Move BPG, and it will instantly indicate a local change. Now you are in the
state where you cannot revert changes to BPG, but it still thinks it has local
changes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (NIFI-10566) Management Controller Service referencing component link doesn't go to Parameter Providers list
Joe Gresock created NIFI-10566: -- Summary: Management Controller Service referencing component link doesn't go to Parameter Providers list Key: NIFI-10566 URL: https://issues.apache.org/jira/browse/NIFI-10566 Project: Apache NiFi Issue Type: Bug Components: Core UI Reporter: Joe Gresock When a management controller service, like DBCPConnectionPool, is referenced by a parameter provider, like DatabaseParameterProvider, clicking the parameter provider name in the Referencing Components list takes you to the management controller service list instead of the parameter provider list. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-10561) Trouble building detached on ARM due to HDFS Processors
[
https://issues.apache.org/jira/browse/NIFI-10561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17611252#comment-17611252
]
Joe Gresock commented on NIFI-10561:
I get the same failure with the following system specs, when running a maven
build from the root
{code:java}
Darwin 10445 21.6.0 Darwin Kernel Version 21.6.0: Sat Jun 18 17:07:25 PDT 2022;
root:xnu-8020.140.41~1/RELEASE_X86_64 x86_64
openjdk version "1.8.0_292"
OpenJDK Runtime Environment (Zulu 8.54.0.21-CA-macosx) (build 1.8.0_292-b10)
OpenJDK 64-Bit Server VM (Zulu 8.54.0.21-CA-macosx) (build 25.292-b10, mixed
mode)
{code}
> Trouble building detached on ARM due to HDFS Processors
> ---
>
> Key: NIFI-10561
> URL: https://issues.apache.org/jira/browse/NIFI-10561
> Project: Apache NiFi
> Issue Type: Task
> Environment: Maven home: /opt/homebrew/Cellar/maven/3.8.6/libexec
> Java version: 1.8.0_345, vendor: Azul Systems, Inc., runtime:
> /Library/Java/JavaVirtualMachines/zulu-8.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "12.6", arch: "aarch64", family: "mac"
>Reporter: Joe Witt
>Priority: Major
>
> This is while trying to build nifi from sources outside of Git. Haven't dug
> in for further details but haven't had build issues otherwise.
> [ERROR] Tests run: 12, Failures: 5, Errors: 0, Skipped: 0, Time elapsed:
> 0.051 s <<< FAILURE! - in org.apache.nifi.processors.hadoop.GetHDFSTest
> [ERROR]
> org.apache.nifi.processors.hadoop.GetHDFSTest.testFileExtensionNotACompressionCodec
> Time elapsed: 0.008 s <<< FAILURE!
> org.opentest4j.AssertionFailedError: expected: <1> but was: <0>
> at
> org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
> at
> org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
> at
> org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197)
> at
> org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:150)
> at
> org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:145)
> at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:527)
> at
> org.apache.nifi.processors.hadoop.GetHDFSTest.testFileExtensionNotACompressionCodec(GetHDFSTest.java:217)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:727)
> at
> org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
> at
> org.junit.jupiter.engine.execution.InvocationInterceptorChain$ValidatingInvocation.proceed(InvocationInterceptorChain.java:131)
> at
> org.junit.jupiter.engine.extension.TimeoutExtension.intercept(TimeoutExtension.java:156)
> at
> org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestableMethod(TimeoutExtension.java:147)
> at
> org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestMethod(TimeoutExtension.java:86)
> at
> org.junit.jupiter.engine.execution.InterceptingExecutableInvoker$ReflectiveInterceptorCall.lambda$ofVoidMethod$0(InterceptingExecutableInvoker.java:103)
> at
> org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.lambda$invoke$0(InterceptingExecutableInvoker.java:93)
> at
> org.junit.jupiter.engine.execution.InvocationInterceptorChain$InterceptedInvocation.proceed(InvocationInterceptorChain.java:106)
> at
> org.junit.jupiter.engine.execution.InvocationInterceptorChain.proceed(InvocationInterceptorChain.java:64)
> at
> org.junit.jupiter.engine.execution.InvocationInterceptorChain.chainAndInvoke(InvocationInterceptorChain.java:45)
> at
> org.junit.jupiter.engine.execution.InvocationInterceptorChain.invoke(InvocationInterceptorChain.java:37)
> at
> org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.invoke(InterceptingExecutableInvoker.java:92)
> at
> org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.invoke(InterceptingExecutableInvoker.java:86)
> at
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeTestMethod$7(TestMethodTestDescriptor.java:217)
> at
> org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
> at
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeTestMethod(TestMethodTestDescriptor.java:213)
> at
>
[jira] [Created] (NIFI-10518) ScheduledStateChangeListener should include intended ScheduledState
Joe Gresock created NIFI-10518: -- Summary: ScheduledStateChangeListener should include intended ScheduledState Key: NIFI-10518 URL: https://issues.apache.org/jira/browse/NIFI-10518 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Reporter: Joe Gresock Assignee: Joe Gresock Since some state changes in the StandardVersionedComponentSynchronizer are asynchronous, the ScheduledState of the components passed in the ScheduledStateChangeCallback methods may become outdated once the asynchronous methods complete. To remedy this, the intended ScheduledState should be passed along with the components in these methods. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-10515) StandardVersionedComponentSynchronizer restarting controller service when proposal is to be disabled
[
https://issues.apache.org/jira/browse/NIFI-10515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Gresock resolved NIFI-10515.
Fix Version/s: 1.18.0
Resolution: Fixed
> StandardVersionedComponentSynchronizer restarting controller service when
> proposal is to be disabled
>
>
> Key: NIFI-10515
> URL: https://issues.apache.org/jira/browse/NIFI-10515
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Minor
> Fix For: 1.18.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In the StandardVersionedComponentSynchronizer, when {{synchronize}} is called
> with a Controller Service, and the proposed VersionedControllerService has a
> ScheduledState of DISABLED, the service is disabled, along with all of its
> dependencies.
> However, if the service has any other controller services referencing it,
> they all end up being restarted, along with the service itself.
> This does not affect any services that are updated via the UI, REST API, or
> when syncing with cluster. This affects only calls going through
> StandardVersionedComponentSynchronizer.synchronize(ControllerService, ...)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (NIFI-10487) Sporadic System Test Failures for ClusteredVerifiableParameterProviderSystemIT
Joe Gresock created NIFI-10487: -- Summary: Sporadic System Test Failures for ClusteredVerifiableParameterProviderSystemIT Key: NIFI-10487 URL: https://issues.apache.org/jira/browse/NIFI-10487 Project: Apache NiFi Issue Type: Bug Components: Tools and Build Reporter: Joe Gresock ClusteredVerifiableParameterProviderSystemIT is hitting the same failure as described in NIFI-9751. The relevant line should be commented out for now, and resolved in NIFI-9717 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-9402) Database Parameter Provider
[ https://issues.apache.org/jira/browse/NIFI-9402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock updated NIFI-9402: -- Status: Patch Available (was: Open) > Database Parameter Provider > --- > > Key: NIFI-9402 > URL: https://issues.apache.org/jira/browse/NIFI-9402 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: Joe Gresock >Assignee: Joe Gresock >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Implement a Parameter Provider that pulls parameters from a DB table. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-9402) Database Parameter Provider
[ https://issues.apache.org/jira/browse/NIFI-9402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock reassigned NIFI-9402: - Assignee: Joe Gresock > Database Parameter Provider > --- > > Key: NIFI-9402 > URL: https://issues.apache.org/jira/browse/NIFI-9402 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: Joe Gresock >Assignee: Joe Gresock >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Implement a Parameter Provider that pulls parameters from a DB table. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-9401) HashiCorp Vault Parameter Provider
[ https://issues.apache.org/jira/browse/NIFI-9401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock updated NIFI-9401: -- Status: Patch Available (was: Open) > HashiCorp Vault Parameter Provider > -- > > Key: NIFI-9401 > URL: https://issues.apache.org/jira/browse/NIFI-9401 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: Joe Gresock >Assignee: Joe Gresock >Priority: Major > Time Spent: 1h > Remaining Estimate: 0h > > Implement a ParameterProvider that pulls parameter groups from K/V Secrets. > Include a HashiCorpVaultControllerService to back the parameter provider. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-10473) Parameter Provider Fetch REST call authorization check is too restrictive
Joe Gresock created NIFI-10473: -- Summary: Parameter Provider Fetch REST call authorization check is too restrictive Key: NIFI-10473 URL: https://issues.apache.org/jira/browse/NIFI-10473 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Reporter: Joe Gresock Assignee: Joe Gresock Fix For: 1.18.0 When bringing up the Fetch Parameters dialog, if the user is not authorized on any referencing component, the dialog fails to load. This is overly restrictive, as NiFi already prevents applying the parameters in this scenario. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-10431) Improve logging/exceptions that pertain to individual components
[ https://issues.apache.org/jira/browse/NIFI-10431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Gresock updated NIFI-10431: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Improve logging/exceptions that pertain to individual components > > > Key: NIFI-10431 > URL: https://issues.apache.org/jira/browse/NIFI-10431 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Major > Fix For: 1.18.0 > > Time Spent: 20m > Remaining Estimate: 0h > > There are many Exceptions/log statements that state something like "Cannot > enable Processor because it is not disabled." However, the message doesn't > indicate which Processor cannot be enabled. While this Exception makes sense > in the context of the UI most of the time, it makes little sense when reading > logs. > We need to include the toString() of the object that the message pertains to. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-10401) Add FlowSynchronizationCallback to StandardVersionedComponentSynchronizer
Joe Gresock created NIFI-10401: -- Summary: Add FlowSynchronizationCallback to StandardVersionedComponentSynchronizer Key: NIFI-10401 URL: https://issues.apache.org/jira/browse/NIFI-10401 Project: Apache NiFi Issue Type: Improvement Reporter: Joe Gresock The StandardVersionedComponentSynchronizer currently makes several automatic updates to the flow when components are modified (such as stopping upstream components). In order to facilitate code that wants to be aware of such changes, a FlowSynchronizationCallback could be added that alerts the client code. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-10320) Parameter Context does not exist when checking out next flow from NiFi registry
[ https://issues.apache.org/jira/browse/NIFI-10320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17576090#comment-17576090 ] Joe Gresock commented on NIFI-10320: Hi [~KO86], I tried a couple flows that I hoped would match your description, but was not able to reproduce the issue. Can you attach a dataflow that demonstrates the problem? > Parameter Context does not exist when checking out next flow from NiFi > registry > --- > > Key: NIFI-10320 > URL: https://issues.apache.org/jira/browse/NIFI-10320 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.16.3 >Reporter: Kevin J O'Connor >Priority: Major > > Parameter Context does not exist when checking out next flow from NiFi > registry. I am checking out a flow that contains several nested versioned > flows. I have found when one of these multi-nested Processor groups is not > version and contains a different parameter context I am getting below. > > "Proposed parameter context name 'configuration' does not exist in set of > available parameter contexts [[common]]" -- This message was sent by Atlassian Jira (v8.20.10#820010)
