[GitHub] [nifi] timeabarna commented on pull request #7353: NIFI-11658 Streamline using single parameter context for nested PGs
timeabarna commented on PR #7353: URL: https://github.com/apache/nifi/pull/7353#issuecomment-1608890622 Hello @exceptionfactory , Thank you ver much for your review, I've updated the PR based on your recommendation. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [nifi] dan-s1 commented on pull request #7442: NIFI-11754 Refactored Groovy test in nifi-jetty to Java (and JUnit 5)
dan-s1 commented on PR #7442: URL: https://github.com/apache/nifi/pull/7442#issuecomment-1608410856 @exceptionfactory I was able to refactor the unit test and test it locally but I am not sure why though when I run `mvn clean install -P contrib-check` the tests in the `nifi-jetty` are skipped. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (NIFI-11754) Refactor Groovy test in nifi-jetty to Java (and JUnit 5)
[ https://issues.apache.org/jira/browse/NIFI-11754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Stieglitz updated NIFI-11754: Status: Patch Available (was: Open) > Refactor Groovy test in nifi-jetty to Java (and JUnit 5) > > > Key: NIFI-11754 > URL: https://issues.apache.org/jira/browse/NIFI-11754 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Daniel Stieglitz >Assignee: Daniel Stieglitz >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [nifi] dan-s1 opened a new pull request, #7442: NIFI-11754 Refactored Groovy test in nifi-jetty to Java (and JUnit 5)
dan-s1 opened a new pull request, #7442: URL: https://github.com/apache/nifi/pull/7442 # Summary [NIFI-11754](https://issues.apache.org/jira/browse/NIFI-11754) # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [ ] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [ ] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [ ] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [ ] Pull Request based on current revision of the `main` branch - [ ] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [ ] Build completed using `mvn clean install -P contrib-check` - [ ] JDK 17 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Assigned] (NIFI-11480) PutElasticsearchRecord should have an option to output _bulk api response errors as flowfile attributes
[
https://issues.apache.org/jira/browse/NIFI-11480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Sampson reassigned NIFI-11480:
Assignee: Chris Sampson
> PutElasticsearchRecord should have an option to output _bulk api response
> errors as flowfile attributes
> ---
>
> Key: NIFI-11480
> URL: https://issues.apache.org/jira/browse/NIFI-11480
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: Chris Sampson
>Assignee: Chris Sampson
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> https://github.com/apache/nifi/pull/6903 for NIFI-1 introduced a
> [conversation|https://github.com/apache/nifi/pull/6903#issuecomment-1513872398]
> about outputting the response error details for Records that are not
> processed by Elasticsearch.
> The same PR introduces a new {{elasticsearch.bulk.error}} attribute for the
> {{PutElasticsearchJson}} processor, but explains why [it's not so simple for
> PutElasticsearchRecord|https://github.com/apache/nifi/pull/6903#issuecomment-1514554132]
> due to input FlowFiles potentially containing many Records and there being
> no obvious way of expressing error details for all such Records in the single
> output flowfile.
> One [suggested
> approach|https://github.com/apache/nifi/pull/6903#issuecomment-1517903668]
> would be to "partition" the output {{errors}} Records into multiple
> flowfiles, grouped by the error {{type}} provided by Elasticsearch. This
> {{type}} could then be added to the flowfile(s) as the
> {{elasticsearch.bulk.error}} attribute. Flows could then {{RouteOnAttribute}}
> if they wanted to handle certain Elasticsearch errors in particular ways.
> Leaving all errors flowfiles in the same output queue avoids the problem of
> the [large (and changing) number of potential Elasticsearch error
> types|https://github.com/apache/nifi/pull/6903#issuecomment-1517863606]
> Such output partitioning (if implemented) should be optional, driven by a
> processor property that maintains the current "all in one" flowfile output by
> default.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [nifi] ChrisSamo632 opened a new pull request, #7441: NIFI-11480 add option to group PutElasticsearchRecord errors by Elast…
ChrisSamo632 opened a new pull request, #7441: URL: https://github.com/apache/nifi/pull/7441 …icsearch _bulk error type # Summary [NIFI-0](https://issues.apache.org/jira/browse/NIFI-0) # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [ ] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [ ] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [ ] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [ ] Pull Request based on current revision of the `main` branch - [ ] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [ ] Build completed using `mvn clean install -P contrib-check` - [ ] JDK 17 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [nifi] exceptionfactory commented on a diff in pull request #7440: NIFI-11758: Added local file upload option in PutAzure*Storage proces…
exceptionfactory commented on code in PR #7440:
URL: https://github.com/apache/nifi/pull/7440#discussion_r1242782311
##
nifi-nar-bundles/nifi-extension-utils/nifi-data-upload/src/main/java/org/apache/nifi/processors/dataupload/DataUploadSource.java:
##
@@ -0,0 +1,48 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.dataupload;
+
+import org.apache.nifi.components.DescribedValue;
+
+public enum DataUploadSource implements DescribedValue {
+
+FLOWFILE_CONTENT("FlowFile's Content", "The content of the incoming
FlowFile will be uploaded."),
Review Comment:
Recommend avoiding the possessive and just naming this `FlowFile Content` if
this goes forward.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [nifi] turcsanyip opened a new pull request, #7440: NIFI-11758: Added local file upload option in PutAzure*Storage proces…
turcsanyip opened a new pull request, #7440: URL: https://github.com/apache/nifi/pull/7440 …sors # Summary [NIFI-11758](https://issues.apache.org/jira/browse/NIFI-11758) # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [ ] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [ ] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [ ] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [ ] Pull Request based on current revision of the `main` branch - [ ] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [ ] Build completed using `mvn clean install -P contrib-check` - [ ] JDK 17 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (NIFI-11758) Add local file upload option in PutAzure*Storage processors
[ https://issues.apache.org/jira/browse/NIFI-11758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Turcsanyi updated NIFI-11758: --- Description: There are cases when the files to be uploaded to Azure Storage are available on the local filesystem where NiFi is running. That is, the flow could read and upload the files directly from the filesystem without adding it in NiFi's content repo which is an overhead in this case (can be relevant for huge files). Add "Data to Upload" property with options "FlowFile's Content" (default, current behaviour) and "Local File". Using the latter, the user can by-pass the content repo and upload the file from the local filesystem to Azure Storage directly. was: There are cases when the files to be uploaded to Azure Storage are available on the local filesystem where NiFi is running. That is, the flow could read and upload the file directly from the filesystem without adding it in NiFi's content repo which is an overhead in this case (can be relevant for huge files). Add "Data to Upload" property with options "FlowFile's Content" (default, current behaviour) and "Local File". Using the latter, the user can by-pass the content repo and upload the file from the local filesystem to Azure Storage. > Add local file upload option in PutAzure*Storage processors > --- > > Key: NIFI-11758 > URL: https://issues.apache.org/jira/browse/NIFI-11758 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Peter Turcsanyi >Assignee: Peter Turcsanyi >Priority: Major > > There are cases when the files to be uploaded to Azure Storage are available > on the local filesystem where NiFi is running. That is, the flow could read > and upload the files directly from the filesystem without adding it in NiFi's > content repo which is an overhead in this case (can be relevant for huge > files). > Add "Data to Upload" property with options "FlowFile's Content" (default, > current behaviour) and "Local File". Using the latter, the user can by-pass > the content repo and upload the file from the local filesystem to Azure > Storage directly. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11758) Add local file upload option in PutAzure*Storage processors
Peter Turcsanyi created NIFI-11758: -- Summary: Add local file upload option in PutAzure*Storage processors Key: NIFI-11758 URL: https://issues.apache.org/jira/browse/NIFI-11758 Project: Apache NiFi Issue Type: Improvement Reporter: Peter Turcsanyi Assignee: Peter Turcsanyi There are cases when the files to be uploaded to Azure Storage are available on the local filesystem where NiFi is running. That is, the flow could read and upload the file directly from the filesystem without adding it in NiFi's content repo which is an overhead in this case (can be relevant for huge files). Add "Data to Upload" property with options "FlowFile's Content" (default, current behaviour) and "Local File". Using the latter, the user can by-pass the content repo and upload the file from the local filesystem to Azure Storage. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-11753) Remove Deprecated JRuby and Luaj Support
[ https://issues.apache.org/jira/browse/NIFI-11753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737341#comment-17737341 ] ASF subversion and git services commented on NIFI-11753: Commit c90625a3e8ca9de613a2f7039d4d91e47e0e7e8a in nifi's branch refs/heads/main from Matt Burgess [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=c90625a3e8 ] NIFI-11753: Remove deprecated JRuby and Luaj script engines This closes #7436 Signed-off-by: David Handermann > Remove Deprecated JRuby and Luaj Support > > > Key: NIFI-11753 > URL: https://issues.apache.org/jira/browse/NIFI-11753 > Project: Apache NiFi > Issue Type: Task > Components: Extensions >Reporter: Matt Burgess >Assignee: Matt Burgess >Priority: Major > Fix For: 2.latest > > Time Spent: 20m > Remaining Estimate: 0h > > Continuing the work of NIFI-11646 (and outlined in > https://cwiki.apache.org/confluence/display/NIFI/Deprecated+Components+and+Features), > the JRuby and Luaj script engines should be removed from the scripting > components. The engines are not often used and as they are not JVM-native > languages the capabilities for these engines are more limited than a > JVM-native language such as Groovy. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11753) Remove Deprecated JRuby and Luaj Support
[ https://issues.apache.org/jira/browse/NIFI-11753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-11753: Fix Version/s: 2.0.0 (was: 2.latest) Resolution: Fixed Status: Resolved (was: Patch Available) > Remove Deprecated JRuby and Luaj Support > > > Key: NIFI-11753 > URL: https://issues.apache.org/jira/browse/NIFI-11753 > Project: Apache NiFi > Issue Type: Task > Components: Extensions >Reporter: Matt Burgess >Assignee: Matt Burgess >Priority: Major > Fix For: 2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Continuing the work of NIFI-11646 (and outlined in > https://cwiki.apache.org/confluence/display/NIFI/Deprecated+Components+and+Features), > the JRuby and Luaj script engines should be removed from the scripting > components. The engines are not often used and as they are not JVM-native > languages the capabilities for these engines are more limited than a > JVM-native language such as Groovy. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-11750) Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide
[ https://issues.apache.org/jira/browse/NIFI-11750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann resolved NIFI-11750. - Fix Version/s: 2.0.0 1.23.0 Resolution: Fixed > Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide > > > Key: NIFI-11750 > URL: https://issues.apache.org/jira/browse/NIFI-11750 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation & Website >Reporter: Nandor Soma Abonyi >Assignee: Nandor Soma Abonyi >Priority: Minor > Fix For: 2.0.0, 1.23.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide > to reflect the current situation. > The main reasons that indicated the change: > - homebrew moved to /opt/homebrew from /usr/local/Cellar which changed the > config location of dnsmasq. > - nifi.sensitive.props.key wasn't part of the guide > - it is better to use a separate location to store configs instead of > littering the toolkit directory > - asciidoc supports formatting xml which is better than an image when we > need to copy paste the config > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-11750) Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide
[ https://issues.apache.org/jira/browse/NIFI-11750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737339#comment-17737339 ] ASF subversion and git services commented on NIFI-11750: Commit a5c67eb4805bad83a1c29dbc6133ff918e52d00a in nifi's branch refs/heads/support/nifi-1.x from Nandor Soma Abonyi [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=a5c67eb480 ] NIFI-11750 Updated the NiFi Cluster TLS Toolkit Guide This closes #7432 Signed-off-by: David Handermann (cherry picked from commit 5beb4cd9744414dec05a41e703c6dba96c9a8b4c) > Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide > > > Key: NIFI-11750 > URL: https://issues.apache.org/jira/browse/NIFI-11750 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation & Website >Reporter: Nandor Soma Abonyi >Assignee: Nandor Soma Abonyi >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide > to reflect the current situation. > The main reasons that indicated the change: > - homebrew moved to /opt/homebrew from /usr/local/Cellar which changed the > config location of dnsmasq. > - nifi.sensitive.props.key wasn't part of the guide > - it is better to use a separate location to store configs instead of > littering the toolkit directory > - asciidoc supports formatting xml which is better than an image when we > need to copy paste the config > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-11750) Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide
[ https://issues.apache.org/jira/browse/NIFI-11750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737338#comment-17737338 ] ASF subversion and git services commented on NIFI-11750: Commit 5beb4cd9744414dec05a41e703c6dba96c9a8b4c in nifi's branch refs/heads/main from Nandor Soma Abonyi [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=5beb4cd974 ] NIFI-11750 Updated the NiFi Cluster TLS Toolkit Guide This closes #7432 Signed-off-by: David Handermann > Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide > > > Key: NIFI-11750 > URL: https://issues.apache.org/jira/browse/NIFI-11750 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation & Website >Reporter: Nandor Soma Abonyi >Assignee: Nandor Soma Abonyi >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide > to reflect the current situation. > The main reasons that indicated the change: > - homebrew moved to /opt/homebrew from /usr/local/Cellar which changed the > config location of dnsmasq. > - nifi.sensitive.props.key wasn't part of the guide > - it is better to use a separate location to store configs instead of > littering the toolkit directory > - asciidoc supports formatting xml which is better than an image when we > need to copy paste the config > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [nifi] exceptionfactory closed pull request #7432: NIFI-11750 Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide
exceptionfactory closed pull request #7432: NIFI-11750 Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide URL: https://github.com/apache/nifi/pull/7432 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Resolved] (NIFI-11741) Ranger CredentialBuilder throws NoClassDefFoundException - com/google/common/base/Preconditions
[
https://issues.apache.org/jira/browse/NIFI-11741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann resolved NIFI-11741.
-
Fix Version/s: 2.0.0
1.23.0
(was: 1.latest)
(was: 2.latest)
Resolution: Fixed
> Ranger CredentialBuilder throws NoClassDefFoundException -
> com/google/common/base/Preconditions
> ---
>
> Key: NIFI-11741
> URL: https://issues.apache.org/jira/browse/NIFI-11741
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 1.22.0
>Reporter: Zoltán Kornél Török
>Assignee: Zoltán Kornél Török
>Priority: Major
> Fix For: 2.0.0, 1.23.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> In the past, there was a similar bug -
> https://issues.apache.org/jira/browse/NIFI-10552
> It seems some of the lib changes or something else caused, that google guava
> library is not included into ext/ranger/install/lib/, which cause the
> following error:
> {code}
> SLF4J: No SLF4J providers were found.
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See https://www.slf4j.org/codes.html#noProviders for further details.
> Exception in thread "main" java.lang.NoClassDefFoundError:
> com/google/common/base/Preconditions
> at
> org.apache.hadoop.conf.Configuration$DeprecationDelta.(Configuration.java:430)
> at
> org.apache.hadoop.conf.Configuration$DeprecationDelta.(Configuration.java:443)
> at org.apache.hadoop.conf.Configuration.(Configuration.java:525)
> at
> org.apache.ranger.credentialapi.CredentialReader.getDecryptedString(CredentialReader.java:41)
> at
> org.apache.ranger.credentialapi.buildks.createCredential(buildks.java:87)
> at org.apache.ranger.credentialapi.buildks.main(buildks.java:41)
> Caused by: java.lang.ClassNotFoundException:
> com.google.common.base.Preconditions
> at java.net.URLClassLoader.findClass(URLClassLoader.java:387)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
> ... 6 more
> {code}
> Command to reproduce:
> {code}
> java -cp
> "nifi-assembly/target/nifi-2.0.0-SNAPSHOT-bin/nifi-2.0.0-SNAPSHOT/ext/ranger/install/lib/*"
> org.apache.ranger.credentialapi.buildks create sslTrustStore -value "test"
> -provider "jceks://file/<>/test2.jceks"
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-11747) Refactor Groovy tests in nifi-web-api to Java (and JUnit 5)
[ https://issues.apache.org/jira/browse/NIFI-11747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-11747: Fix Version/s: 2.0.0 1.23.0 Resolution: Fixed Status: Resolved (was: Patch Available) > Refactor Groovy tests in nifi-web-api to Java (and JUnit 5) > > > Key: NIFI-11747 > URL: https://issues.apache.org/jira/browse/NIFI-11747 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Daniel Stieglitz >Assignee: Daniel Stieglitz >Priority: Minor > Fix For: 2.0.0, 1.23.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-11747) Refactor Groovy tests in nifi-web-api to Java (and JUnit 5)
[ https://issues.apache.org/jira/browse/NIFI-11747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737334#comment-17737334 ] ASF subversion and git services commented on NIFI-11747: Commit 207af04ea292cd61090eafb2842ca66c5ac78dcf in nifi's branch refs/heads/support/nifi-1.x from dan-s1 [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=207af04ea2 ] NIFI-11747 Refactored Groovy tests in nifi-web-api to Java (and JUnit 5) This closes #7434 Signed-off-by: David Handermann (cherry picked from commit 7748d9d1e5287c6b99c965ee0ed93ed154802def) > Refactor Groovy tests in nifi-web-api to Java (and JUnit 5) > > > Key: NIFI-11747 > URL: https://issues.apache.org/jira/browse/NIFI-11747 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Daniel Stieglitz >Assignee: Daniel Stieglitz >Priority: Minor > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-11741) Ranger CredentialBuilder throws NoClassDefFoundException - com/google/common/base/Preconditions
[
https://issues.apache.org/jira/browse/NIFI-11741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737335#comment-17737335
]
ASF subversion and git services commented on NIFI-11741:
Commit 920a586d2aba05f4be6430bb54bdc18e4e3f6c9f in nifi's branch
refs/heads/support/nifi-1.x from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=920a586d2a ]
NIFI-11741 Added Guava dependency to Ranger assembly includes
This closes #7423
Co-authored-by: Zoltan Kornel Torok
Co-authored-by: David Handermann
Signed-off-by: David Handermann
(cherry picked from commit 01fa3773fb32de9ced47f1c16100a0eff482213a)
> Ranger CredentialBuilder throws NoClassDefFoundException -
> com/google/common/base/Preconditions
> ---
>
> Key: NIFI-11741
> URL: https://issues.apache.org/jira/browse/NIFI-11741
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 1.22.0
>Reporter: Zoltán Kornél Török
>Assignee: Zoltán Kornél Török
>Priority: Major
> Fix For: 1.latest, 2.latest
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> In the past, there was a similar bug -
> https://issues.apache.org/jira/browse/NIFI-10552
> It seems some of the lib changes or something else caused, that google guava
> library is not included into ext/ranger/install/lib/, which cause the
> following error:
> {code}
> SLF4J: No SLF4J providers were found.
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See https://www.slf4j.org/codes.html#noProviders for further details.
> Exception in thread "main" java.lang.NoClassDefFoundError:
> com/google/common/base/Preconditions
> at
> org.apache.hadoop.conf.Configuration$DeprecationDelta.(Configuration.java:430)
> at
> org.apache.hadoop.conf.Configuration$DeprecationDelta.(Configuration.java:443)
> at org.apache.hadoop.conf.Configuration.(Configuration.java:525)
> at
> org.apache.ranger.credentialapi.CredentialReader.getDecryptedString(CredentialReader.java:41)
> at
> org.apache.ranger.credentialapi.buildks.createCredential(buildks.java:87)
> at org.apache.ranger.credentialapi.buildks.main(buildks.java:41)
> Caused by: java.lang.ClassNotFoundException:
> com.google.common.base.Preconditions
> at java.net.URLClassLoader.findClass(URLClassLoader.java:387)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
> ... 6 more
> {code}
> Command to reproduce:
> {code}
> java -cp
> "nifi-assembly/target/nifi-2.0.0-SNAPSHOT-bin/nifi-2.0.0-SNAPSHOT/ext/ranger/install/lib/*"
> org.apache.ranger.credentialapi.buildks create sslTrustStore -value "test"
> -provider "jceks://file/<>/test2.jceks"
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-11747) Refactor Groovy tests in nifi-web-api to Java (and JUnit 5)
[ https://issues.apache.org/jira/browse/NIFI-11747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737332#comment-17737332 ] ASF subversion and git services commented on NIFI-11747: Commit 7748d9d1e5287c6b99c965ee0ed93ed154802def in nifi's branch refs/heads/main from dan-s1 [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=7748d9d1e5 ] NIFI-11747 Refactored Groovy tests in nifi-web-api to Java (and JUnit 5) This closes #7434 Signed-off-by: David Handermann > Refactor Groovy tests in nifi-web-api to Java (and JUnit 5) > > > Key: NIFI-11747 > URL: https://issues.apache.org/jira/browse/NIFI-11747 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Daniel Stieglitz >Assignee: Daniel Stieglitz >Priority: Minor > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [nifi] exceptionfactory closed pull request #7423: NIFI-11741: Add guava lib to nifi-ranger-resource project, in order t…
exceptionfactory closed pull request #7423: NIFI-11741: Add guava lib to nifi-ranger-resource project, in order t… URL: https://github.com/apache/nifi/pull/7423 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (NIFI-11741) Ranger CredentialBuilder throws NoClassDefFoundException - com/google/common/base/Preconditions
[
https://issues.apache.org/jira/browse/NIFI-11741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737333#comment-17737333
]
ASF subversion and git services commented on NIFI-11741:
Commit 01fa3773fb32de9ced47f1c16100a0eff482213a in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=01fa3773fb ]
NIFI-11741 Added Guava dependency to Ranger assembly includes
This closes #7423
Co-authored-by: Zoltan Kornel Torok
Co-authored-by: David Handermann
Signed-off-by: David Handermann
> Ranger CredentialBuilder throws NoClassDefFoundException -
> com/google/common/base/Preconditions
> ---
>
> Key: NIFI-11741
> URL: https://issues.apache.org/jira/browse/NIFI-11741
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 1.22.0
>Reporter: Zoltán Kornél Török
>Assignee: Zoltán Kornél Török
>Priority: Major
> Fix For: 1.latest, 2.latest
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In the past, there was a similar bug -
> https://issues.apache.org/jira/browse/NIFI-10552
> It seems some of the lib changes or something else caused, that google guava
> library is not included into ext/ranger/install/lib/, which cause the
> following error:
> {code}
> SLF4J: No SLF4J providers were found.
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See https://www.slf4j.org/codes.html#noProviders for further details.
> Exception in thread "main" java.lang.NoClassDefFoundError:
> com/google/common/base/Preconditions
> at
> org.apache.hadoop.conf.Configuration$DeprecationDelta.(Configuration.java:430)
> at
> org.apache.hadoop.conf.Configuration$DeprecationDelta.(Configuration.java:443)
> at org.apache.hadoop.conf.Configuration.(Configuration.java:525)
> at
> org.apache.ranger.credentialapi.CredentialReader.getDecryptedString(CredentialReader.java:41)
> at
> org.apache.ranger.credentialapi.buildks.createCredential(buildks.java:87)
> at org.apache.ranger.credentialapi.buildks.main(buildks.java:41)
> Caused by: java.lang.ClassNotFoundException:
> com.google.common.base.Preconditions
> at java.net.URLClassLoader.findClass(URLClassLoader.java:387)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
> ... 6 more
> {code}
> Command to reproduce:
> {code}
> java -cp
> "nifi-assembly/target/nifi-2.0.0-SNAPSHOT-bin/nifi-2.0.0-SNAPSHOT/ext/ranger/install/lib/*"
> org.apache.ranger.credentialapi.buildks create sslTrustStore -value "test"
> -provider "jceks://file/<>/test2.jceks"
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-11752) Upgrade Spring Framework to 5.3.28 and Spring Security to 5.8.4
[ https://issues.apache.org/jira/browse/NIFI-11752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737326#comment-17737326 ] ASF subversion and git services commented on NIFI-11752: Commit 07e797a7c16ad7b61f19d89b53a347ad74e4c075 in nifi's branch refs/heads/main from David Handermann [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=07e797a7c1 ] NIFI-11752 Upgraded Spring Framework from 5.3.27 to 5.3.28 - Upgraded Spring Security from 5.8.3 to 5.8.4 - Upgraded Spring Boot from 2.7.12 to 2.7.13 for Registry Signed-off-by: Matt Burgess This closes #7435 > Upgrade Spring Framework to 5.3.28 and Spring Security to 5.8.4 > --- > > Key: NIFI-11752 > URL: https://issues.apache.org/jira/browse/NIFI-11752 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework, MiNiFi, NiFi Registry >Affects Versions: 1.latest, 2.latest >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Labels: dependency-upgrade > Fix For: 1.latest, 2.latest > > Time Spent: 0.5h > Remaining Estimate: 0h > > Spring Framework should be upgraded to > [5.3.28|https://github.com/spring-projects/spring-framework/releases/tag/v5.3.28] > and Spring Security should be upgraded to > [5.8.4|https://github.com/spring-projects/spring-security/releases/tag/5.8.4] > across current and support versions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11752) Upgrade Spring Framework to 5.3.28 and Spring Security to 5.8.4
[ https://issues.apache.org/jira/browse/NIFI-11752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated NIFI-11752: Fix Version/s: 2.0.0 1.23.0 (was: 1.latest) (was: 2.latest) Resolution: Fixed Status: Resolved (was: Patch Available) > Upgrade Spring Framework to 5.3.28 and Spring Security to 5.8.4 > --- > > Key: NIFI-11752 > URL: https://issues.apache.org/jira/browse/NIFI-11752 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework, MiNiFi, NiFi Registry >Affects Versions: 1.latest, 2.latest >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Labels: dependency-upgrade > Fix For: 2.0.0, 1.23.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Spring Framework should be upgraded to > [5.3.28|https://github.com/spring-projects/spring-framework/releases/tag/v5.3.28] > and Spring Security should be upgraded to > [5.8.4|https://github.com/spring-projects/spring-security/releases/tag/5.8.4] > across current and support versions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-11752) Upgrade Spring Framework to 5.3.28 and Spring Security to 5.8.4
[ https://issues.apache.org/jira/browse/NIFI-11752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737323#comment-17737323 ] ASF subversion and git services commented on NIFI-11752: Commit c104657bc013f3d292af3bb2f10f2921707fa7f6 in nifi's branch refs/heads/support/nifi-1.x from David Handermann [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=c104657bc0 ] NIFI-11752 Upgraded Spring Framework from 5.3.27 to 5.3.28 - Upgraded Spring Security from 5.8.3 to 5.8.4 - Upgraded Spring Boot from 2.7.12 to 2.7.13 for Registry Signed-off-by: Matt Burgess > Upgrade Spring Framework to 5.3.28 and Spring Security to 5.8.4 > --- > > Key: NIFI-11752 > URL: https://issues.apache.org/jira/browse/NIFI-11752 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework, MiNiFi, NiFi Registry >Affects Versions: 1.latest, 2.latest >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Labels: dependency-upgrade > Fix For: 1.latest, 2.latest > > Time Spent: 10m > Remaining Estimate: 0h > > Spring Framework should be upgraded to > [5.3.28|https://github.com/spring-projects/spring-framework/releases/tag/v5.3.28] > and Spring Security should be upgraded to > [5.8.4|https://github.com/spring-projects/spring-security/releases/tag/5.8.4] > across current and support versions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [nifi] exceptionfactory opened a new pull request, #7439: NIFI-11757 Upgrade Google Cloud Libraries from 26.15.0 to 26.17.0
exceptionfactory opened a new pull request, #7439: URL: https://github.com/apache/nifi/pull/7439 # Summary [NIFI-11757](https://issues.apache.org/jira/browse/NIFI-11757) Upgrades Google Cloud libraries from 26.15.0 to 26.17.0 for GCP extension components. # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [X] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [X] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [X] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [X] Pull Request based on current revision of the `main` branch - [X] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [ ] Build completed using `mvn clean install -P contrib-check` - [ ] JDK 17 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (NIFI-11757) Upgrade Google Cloud Libraries to 26.17.0
David Handermann created NIFI-11757: --- Summary: Upgrade Google Cloud Libraries to 26.17.0 Key: NIFI-11757 URL: https://issues.apache.org/jira/browse/NIFI-11757 Project: Apache NiFi Issue Type: Improvement Components: Extensions Reporter: David Handermann Assignee: David Handermann Fix For: 1.latest, 2.latest The Google Cloud Libraries BOM dependency should be upgraded from 26.15.0 to 26.17.0 to incorporate several bug fixes and improvements, including a resolution for issues related to gRPC serialization processing. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11756) Remove unused ROME Dependency from Registry Ranger
[ https://issues.apache.org/jira/browse/NIFI-11756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-11756: Status: Patch Available (was: Open) > Remove unused ROME Dependency from Registry Ranger > -- > > Key: NIFI-11756 > URL: https://issues.apache.org/jira/browse/NIFI-11756 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions, NiFi Registry >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Fix For: 1.latest, 2.latest > > Time Spent: 10m > Remaining Estimate: 0h > > The Registry Ranger plugin includes an unused dependency on the > [ROME|https://rometools.github.io/rome/] API. The NiFi Ranger plugin does not > use this dependency, which provides XML parsing for RSS and Atom feeds. This > dependency should be removed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [nifi] exceptionfactory opened a new pull request, #7438: NIFI-11756 Remove unused ROME Dependency from Registry Ranger Plugin
exceptionfactory opened a new pull request, #7438: URL: https://github.com/apache/nifi/pull/7438 # Summary [NIFI-11756](https://issues.apache.org/jira/browse/NIFI-11756) Removes the unused [ROME](https://rometools.github.io/rome/) dependency from the NiFi Registry Ranger plugin. The ROME API provides XML parsing for RSS and Atom feeds, and the dependency is not used in the standard NiFi Ranger plugin. # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [X] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [X] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [X] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [X] Pull Request based on current revision of the `main` branch - [X] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [X] Build completed using `mvn clean install -P contrib-check` - [X] JDK 17 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (NIFI-11755) Upgrade AWS SDK to 2.20.92 and 1.12.495
[ https://issues.apache.org/jira/browse/NIFI-11755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-11755: Fix Version/s: 1.latest 2.latest Status: Patch Available (was: Open) > Upgrade AWS SDK to 2.20.92 and 1.12.495 > --- > > Key: NIFI-11755 > URL: https://issues.apache.org/jira/browse/NIFI-11755 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Labels: dependency-upgrade > Fix For: 1.latest, 2.latest > > Time Spent: 10m > Remaining Estimate: 0h > > AWS SDK dependencies should be upgrade to > [1.12.495|https://github.com/aws/aws-sdk-java/blob/master/CHANGELOG.md] and > [2.20.92|https://github.com/aws/aws-sdk-java-v2/blob/master/CHANGELOG.md] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [nifi] exceptionfactory opened a new pull request, #7437: NIFI-11755 Upgrade AWS SDK to 1.12.495 and 2.20.92
exceptionfactory opened a new pull request, #7437: URL: https://github.com/apache/nifi/pull/7437 # Summary [NIFI-11755](https://issues.apache.org/jira/browse/NIFI-11755) Upgrades AWS SDK libraries from 1.12.478 to [1.12.195](https://github.com/aws/aws-sdk-java/blob/master/CHANGELOG.md) and from 2.20.75 to [2.20.92](https://github.com/aws/aws-sdk-java-v2/blob/master/CHANGELOG.md). # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [X] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [X] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [X] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [X] Pull Request based on current revision of the `main` branch - [X] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [X] Build completed using `mvn clean install -P contrib-check` - [X] JDK 17 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (NIFI-11756) Remove unused ROME Dependency from Registry Ranger
David Handermann created NIFI-11756: --- Summary: Remove unused ROME Dependency from Registry Ranger Key: NIFI-11756 URL: https://issues.apache.org/jira/browse/NIFI-11756 Project: Apache NiFi Issue Type: Improvement Components: Extensions, NiFi Registry Reporter: David Handermann Assignee: David Handermann Fix For: 1.latest, 2.latest The Registry Ranger plugin includes an unused dependency on the [ROME|https://rometools.github.io/rome/] API. The NiFi Ranger plugin does not use this dependency, which provides XML parsing for RSS and Atom feeds. This dependency should be removed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11755) Upgrade AWS SDK to 2.20.92 and 1.12.495
David Handermann created NIFI-11755: --- Summary: Upgrade AWS SDK to 2.20.92 and 1.12.495 Key: NIFI-11755 URL: https://issues.apache.org/jira/browse/NIFI-11755 Project: Apache NiFi Issue Type: Improvement Components: Extensions Reporter: David Handermann Assignee: David Handermann AWS SDK dependencies should be upgrade to [1.12.495|https://github.com/aws/aws-sdk-java/blob/master/CHANGELOG.md] and [2.20.92|https://github.com/aws/aws-sdk-java-v2/blob/master/CHANGELOG.md] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11753) Remove Deprecated JRuby and Luaj Support
[ https://issues.apache.org/jira/browse/NIFI-11753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated NIFI-11753: Status: Patch Available (was: In Progress) > Remove Deprecated JRuby and Luaj Support > > > Key: NIFI-11753 > URL: https://issues.apache.org/jira/browse/NIFI-11753 > Project: Apache NiFi > Issue Type: Task > Components: Extensions >Reporter: Matt Burgess >Assignee: Matt Burgess >Priority: Major > Fix For: 2.latest > > Time Spent: 10m > Remaining Estimate: 0h > > Continuing the work of NIFI-11646 (and outlined in > https://cwiki.apache.org/confluence/display/NIFI/Deprecated+Components+and+Features), > the JRuby and Luaj script engines should be removed from the scripting > components. The engines are not often used and as they are not JVM-native > languages the capabilities for these engines are more limited than a > JVM-native language such as Groovy. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [nifi] mattyb149 opened a new pull request, #7436: NIFI-11753: Remove deprecated JRuby and Luaj script engines
mattyb149 opened a new pull request, #7436: URL: https://github.com/apache/nifi/pull/7436 # Summary [NIFI-11753](https://issues.apache.org/jira/browse/NIFI-11753) This PR removes the JRuby and Luaj script engines from the scripted components, continuing the work of [NIFI-11646](https://issues.apache.org/jira/browse/NIFI-11646) but on the main (2.x) line. References to and tests for those engines are removed as well. # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [x] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [x] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [x] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [x] Pull Request based on current revision of the `main` branch - [x] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [ ] Build completed using `mvn clean install -P contrib-check` - [x] JDK 17 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [x] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [x] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Assigned] (NIFI-11754) Refactor Groovy test in nifi-jetty to Java (and JUnit 5)
[ https://issues.apache.org/jira/browse/NIFI-11754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Stieglitz reassigned NIFI-11754: --- Assignee: Daniel Stieglitz > Refactor Groovy test in nifi-jetty to Java (and JUnit 5) > > > Key: NIFI-11754 > URL: https://issues.apache.org/jira/browse/NIFI-11754 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Daniel Stieglitz >Assignee: Daniel Stieglitz >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11752) Upgrade Spring Framework to 5.3.28 and Spring Security to 5.8.4
[ https://issues.apache.org/jira/browse/NIFI-11752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated NIFI-11752: Fix Version/s: 1.latest 2.latest > Upgrade Spring Framework to 5.3.28 and Spring Security to 5.8.4 > --- > > Key: NIFI-11752 > URL: https://issues.apache.org/jira/browse/NIFI-11752 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework, MiNiFi, NiFi Registry >Affects Versions: 1.latest, 2.latest >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Labels: dependency-upgrade > Fix For: 1.latest, 2.latest > > Time Spent: 10m > Remaining Estimate: 0h > > Spring Framework should be upgraded to > [5.3.28|https://github.com/spring-projects/spring-framework/releases/tag/v5.3.28] > and Spring Security should be upgraded to > [5.8.4|https://github.com/spring-projects/spring-security/releases/tag/5.8.4] > across current and support versions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11754) Refactor Groovy test in nifi-jetty to Java (and JUnit 5)
Daniel Stieglitz created NIFI-11754: --- Summary: Refactor Groovy test in nifi-jetty to Java (and JUnit 5) Key: NIFI-11754 URL: https://issues.apache.org/jira/browse/NIFI-11754 Project: Apache NiFi Issue Type: Sub-task Reporter: Daniel Stieglitz -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-11753) Remove Deprecated JRuby and Luaj Support
[ https://issues.apache.org/jira/browse/NIFI-11753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess reassigned NIFI-11753: --- Assignee: Matt Burgess > Remove Deprecated JRuby and Luaj Support > > > Key: NIFI-11753 > URL: https://issues.apache.org/jira/browse/NIFI-11753 > Project: Apache NiFi > Issue Type: Task > Components: Extensions >Reporter: Matt Burgess >Assignee: Matt Burgess >Priority: Major > Fix For: 2.latest > > > Continuing the work of NIFI-11646 (and outlined in > https://cwiki.apache.org/confluence/display/NIFI/Deprecated+Components+and+Features), > the JRuby and Luaj script engines should be removed from the scripting > components. The engines are not often used and as they are not JVM-native > languages the capabilities for these engines are more limited than a > JVM-native language such as Groovy. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [nifi] dan-s1 commented on pull request #7434: NIFI-11747 Refactored Groovy tests in nifi-web-api to Java (and JUnit 5)
dan-s1 commented on PR #7434: URL: https://github.com/apache/nifi/pull/7434#issuecomment-1607920093 @exceptionfactory Sure thing. When doing that I noticed Intellij is flagging that the following dependency is duplicated as its in the nifi parent pom.xml ``` org.hamcrest hamcrest-all test ``` Should I remove this also? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (NIFI-11753) Remove Deprecated JRuby and Luaj Support
Matt Burgess created NIFI-11753: --- Summary: Remove Deprecated JRuby and Luaj Support Key: NIFI-11753 URL: https://issues.apache.org/jira/browse/NIFI-11753 Project: Apache NiFi Issue Type: Task Components: Extensions Reporter: Matt Burgess Fix For: 2.latest Continuing the work of NIFI-11646 (and outlined in https://cwiki.apache.org/confluence/display/NIFI/Deprecated+Components+and+Features), the JRuby and Luaj script engines should be removed from the scripting components. The engines are not often used and as they are not JVM-native languages the capabilities for these engines are more limited than a JVM-native language such as Groovy. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11747) Refactor Groovy tests in nifi-web-api to Java (and JUnit 5)
[ https://issues.apache.org/jira/browse/NIFI-11747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Stieglitz updated NIFI-11747: Status: Patch Available (was: In Progress) > Refactor Groovy tests in nifi-web-api to Java (and JUnit 5) > > > Key: NIFI-11747 > URL: https://issues.apache.org/jira/browse/NIFI-11747 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Daniel Stieglitz >Assignee: Daniel Stieglitz >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [nifi] exceptionfactory closed pull request #7433: NIFI-11751 Update spring.boot.version to 2.7.13
exceptionfactory closed pull request #7433: NIFI-11751 Update spring.boot.version to 2.7.13 URL: https://github.com/apache/nifi/pull/7433 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (NIFI-11752) Upgrade Spring Framework to 5.3.28 and Spring Security to 5.8.4
[ https://issues.apache.org/jira/browse/NIFI-11752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-11752: Affects Version/s: 1.latest 2.latest Status: Patch Available (was: Open) > Upgrade Spring Framework to 5.3.28 and Spring Security to 5.8.4 > --- > > Key: NIFI-11752 > URL: https://issues.apache.org/jira/browse/NIFI-11752 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework, MiNiFi, NiFi Registry >Affects Versions: 1.latest, 2.latest >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Labels: dependency-upgrade > Time Spent: 10m > Remaining Estimate: 0h > > Spring Framework should be upgraded to > [5.3.28|https://github.com/spring-projects/spring-framework/releases/tag/v5.3.28] > and Spring Security should be upgraded to > [5.8.4|https://github.com/spring-projects/spring-security/releases/tag/5.8.4] > across current and support versions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [nifi] exceptionfactory opened a new pull request, #7435: NIFI-11752 Upgrade Spring Framework from 5.3.27 to 5.3.28
exceptionfactory opened a new pull request, #7435: URL: https://github.com/apache/nifi/pull/7435 # Summary [NIFI-11752](https://issues.apache.org/jira/browse/NIFI-11752) Upgrades Spring Framework from 5.3.27 to [5.3.28](https://github.com/spring-projects/spring-framework/releases/tag/v5.3.28) and upgrades Spring Security from 5.8.3 to [5.8.4](https://github.com/spring-projects/spring-security/releases/tag/5.8.4). Changes also include upgrading Spring Boot from 2.7.12 to [2.7.13](https://github.com/spring-projects/spring-boot/releases/tag/v2.7.13) for Registry. # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [X] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [X] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [X] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [X] Pull Request based on current revision of the `main` branch - [X] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [X] Build completed using `mvn clean install -P contrib-check` - [X] JDK 17 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [nifi] dan-s1 opened a new pull request, #7434: NIFI-11747 Refactored Groovy tests in nifi-web-api to Java (and JUnit 5)
dan-s1 opened a new pull request, #7434: URL: https://github.com/apache/nifi/pull/7434 # Summary [NIFI-11747](https://issues.apache.org/jira/browse/NIFI-11747) # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [ ] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [ ] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [ ] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [ ] Pull Request based on current revision of the `main` branch - [ ] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [ ] Build completed using `mvn clean install -P contrib-check` - [ ] JDK 17 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (NIFI-11752) Upgrade Spring Framework to 5.3.28 and Spring Security to 5.8.4
David Handermann created NIFI-11752: --- Summary: Upgrade Spring Framework to 5.3.28 and Spring Security to 5.8.4 Key: NIFI-11752 URL: https://issues.apache.org/jira/browse/NIFI-11752 Project: Apache NiFi Issue Type: Improvement Components: Core Framework, MiNiFi, NiFi Registry Reporter: David Handermann Assignee: David Handermann Spring Framework should be upgraded to [5.3.28|https://github.com/spring-projects/spring-framework/releases/tag/v5.3.28] and Spring Security should be upgraded to [5.8.4|https://github.com/spring-projects/spring-security/releases/tag/5.8.4] across current and support versions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-11751) Update spring.boot.version to 2.7.13
[ https://issues.apache.org/jira/browse/NIFI-11751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike R reassigned NIFI-11751: - Assignee: Mike R > Update spring.boot.version to 2.7.13 > > > Key: NIFI-11751 > URL: https://issues.apache.org/jira/browse/NIFI-11751 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.22.0 >Reporter: Mike R >Assignee: Mike R >Priority: Major > > Update spring.boot.version to 2.7.13 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [nifi] mr1716 opened a new pull request, #7433: NIFI-11751 Update spring.boot.version to 2.7.13
mr1716 opened a new pull request, #7433: URL: https://github.com/apache/nifi/pull/7433 # Summary [NIFI-11751](https://issues.apache.org/jira/browse/NIFI-11751) # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [X] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI-11751) issue created ### Pull Request Tracking - [X] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [X] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [X] Pull Request based on current revision of the `main` branch - [X] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [ ] Build completed using `mvn clean install -P contrib-check` - [ ] JDK 17 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (NIFI-11751) Update spring.boot.version to 2.7.13
Mike R created NIFI-11751: - Summary: Update spring.boot.version to 2.7.13 Key: NIFI-11751 URL: https://issues.apache.org/jira/browse/NIFI-11751 Project: Apache NiFi Issue Type: Improvement Affects Versions: 1.22.0 Reporter: Mike R Update spring.boot.version to 2.7.13 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [nifi] exceptionfactory commented on a diff in pull request #7421: NIFI-11739: Add ability to ignore missing fields in PutIceberg
exceptionfactory commented on code in PR #7421:
URL: https://github.com/apache/nifi/pull/7421#discussion_r1242475244
##
nifi-nar-bundles/nifi-iceberg-bundle/nifi-iceberg-processors/src/test/java/org/apache/nifi/processors/iceberg/TestIcebergRecordConverter.java:
##
@@ -473,6 +516,103 @@ public void testPrimitives(FileFormat format) throws
IOException {
}
}
+@DisabledOnOs(WINDOWS)
+@ParameterizedTest
+@EnumSource(value = FileFormat.class, names = {"AVRO", "ORC", "PARQUET"})
Review Comment:
One general note on these tests, it it probably worth avoiding some of the
repeated tests in the interest of execution time. Several other tests ran
through all formats, requiring over a minute to exercise all cases. Keeping
unit test method runs under a second would be ideal, so these new tests may
need to be more narrowly scoped to avoid excessive running time.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Updated] (NIFI-11750) Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide
[ https://issues.apache.org/jira/browse/NIFI-11750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-11750: -- Description: Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide to reflect the current situation. The main reasons that indicated the change: - homebrew moved to /opt/homebrew from /usr/local/Cellar which changed the config location of dnsmasq. - nifi.sensitive.props.key wasn't part of the guide - it is better to use a separate location to store configs instead of littering the toolkit directory - asciidoc supports formatting xml which is better than an image when we need to copy paste the config was: Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide to reflect the current situation. The main reasons that indicated the change: - homebrew moved to /opt/homebrew from /usr/local/Cellar which changed the config location of dnsmasq. - nifi.sensitive.props.key wasn't part of the guide - it is better to use a separate location to store configs instead of littering the toolkit directory > Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide > > > Key: NIFI-11750 > URL: https://issues.apache.org/jira/browse/NIFI-11750 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation & Website >Reporter: Nandor Soma Abonyi >Assignee: Nandor Soma Abonyi >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide > to reflect the current situation. > The main reasons that indicated the change: > - homebrew moved to /opt/homebrew from /usr/local/Cellar which changed the > config location of dnsmasq. > - nifi.sensitive.props.key wasn't part of the guide > - it is better to use a separate location to store configs instead of > littering the toolkit directory > - asciidoc supports formatting xml which is better than an image when we > need to copy paste the config > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [nifi] nandorsoma opened a new pull request, #7432: NIFI-11750 Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide
nandorsoma opened a new pull request, #7432: URL: https://github.com/apache/nifi/pull/7432 # Summary [NIFI-11750](https://issues.apache.org/jira/browse/NIFI-11750) Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide to reflect the current situation. The main reasons that indicated the change: - homebrew moved to /opt/homebrew from /usr/local/Cellar which changed the config location of dnsmasq. - nifi.sensitive.props.key wasn't part of the guide - it is better to use a separate location to store configs instead of littering the toolkit directory - asciidoc supports formatting xml which is better than an image when we need to copy paste the config # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [x] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [x] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [x] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [x] Pull Request based on current revision of the `main` branch - [x] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [x] Build completed using `mvn clean install -P contrib-check` - [x] JDK 17 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [x] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (NIFI-11530) Disk full even with nifi.content.repository.archive.max.usage.percentage set to 50%
[ https://issues.apache.org/jira/browse/NIFI-11530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737230#comment-17737230 ] Joe Witt commented on NIFI-11530: - Right you will need some buffer for the rollover/shard development. I dont think you'll want to be so tight such that if you have 10GB you allow a max of 9GB. You will need to experiment a bit but at this point I do not believe you're dealing with a bug but rather finding an optimal configuration. > Disk full even with nifi.content.repository.archive.max.usage.percentage set > to 50% > --- > > Key: NIFI-11530 > URL: https://issues.apache.org/jira/browse/NIFI-11530 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.20.0 > Environment: Ubuntu 20.04.5 LTS >Reporter: Giovanni >Priority: Major > Attachments: 20230605_disk_usage.jpg, content_archive.jpg, > flowfile_archive.jpg, image-2023-06-26-11-13-19-289.png, > image-2023-06-26-11-15-00-379.png, image-2023-06-26-11-16-21-096.png, > image-2023-06-26-11-16-35-791.png, image-2023-06-26-11-16-48-186.png, > jvm.jpg, nifi1-app.log, nifi2-app.log, nifi3-app.log, nifi_bug.jpg, > provenance_archive.jpg > > > Nifi primary node reports disk full causing all nodes to stop working. > Restarting nifi service does not resolve. > Restarting the VM does not resolve. > The only way to fix is to clean te content_repository dir: > rm -rf ./nifi/content_repository/* > > Unfortunately I have no logs of the issue ongoing. > > UPDATE: > I'm having the problem again. > Every archive size is more than 50% on each node, with 70%+ peak on > coordinator node (see attachments). > I'm also attaching nifi-app.log this time. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-9206) Create a processor that is capable of removing fields from records
[
https://issues.apache.org/jira/browse/NIFI-9206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-9206:
---
Fix Version/s: 2.0.0
1.23.0
(was: 1.latest)
(was: 2.latest)
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Create a processor that is capable of removing fields from records
> --
>
> Key: NIFI-9206
> URL: https://issues.apache.org/jira/browse/NIFI-9206
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
>Reporter: Peter Gyori
>Assignee: Chris Sampson
>Priority: Major
> Fix For: 2.0.0, 1.23.0
>
> Attachments: NIFI-9206.json
>
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> A processor should be created that is capable of removing fields from records
> (RemoveRecordField might be a name for it).
> The processor should have 3 properties:
> * Record Reader (a Reader controller service could be specified)
> * Record Writer (a Writer controller service could be specified)
> * Field To Remove (expects a RecordPath that points to the field to be
> removed)
> The processor should be able to accept additional dynamic properties that
> specify further fields (by RecordPath) to be removed from the record.
> +*Example*+
> +input:+
> {code:java}
> {
> "id": 1,
> "name": "John",
> "address": {
> "zip": ,
> "street": "Main",
> "building": 11
> }
> }
> {code}
> +Field to remove:+ /address/building
> +output:+
> {code:java}
> {
> "id": 1,
> "name": "John",
> "address": {
> "zip": ,
> "street": "Main"
> }
> }
> {code}
> The record's schema should be modified accordingly (removing the
> /address/building field from the schema). Field removal should be permitted
> regardless of the field being nullable or not.
> Generally, the removal of a field should include the field's removal from the
> schema AND the data. The exception is if the removal is data-dependent (the
> field should be removed if its value equals "xyz"). In this case no schema
> modification should occur.
> The processor should be able to remove one or more elements from arrays
> (e.g.: /addresses[ 1 ] shoud remove the element from the addresses array from
> the 1st position). When removing a field from elements of an array, the
> array's schema should only be modified if the removal is applied to all
> elements of the array (i.e.: /addresses[ * ]/building should modify the
> schema of the array, but /addresses[ 1 ]/building should not).
> The same rule should be applied when handling Map datatype.
> If the record does not contain the field that is expected to be removed, the
> record should still be transferred to the 'success' relationship, with no
> modification. The expectation is that if /x/y is expected to be removed from
> the record, then the record leaving the processor should not contain /x/y
> field.
> If a certain field can be of different types (e.g. the address field can be
> "string" as well as "record" and possibly another "record" with a schema
> different from the former record type) then if /address/building is expected
> to be removed from the record, the processor is expected to remove the
> building field from the schema of all the possible types of the address field
> regardless of the address field being whatever concrete type in the
> particular record that is being processed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-9206) Create a processor that is capable of removing fields from records
[
https://issues.apache.org/jira/browse/NIFI-9206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737227#comment-17737227
]
ASF subversion and git services commented on NIFI-9206:
---
Commit 756f9d0fdb921b092315409ce674fd91f7c9dbe5 in nifi's branch
refs/heads/support/nifi-1.x from Chris Sampson
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=756f9d0fdb ]
NIFI-9206 Added RemoveRecordField Processor
This closes #6816
Co-authored-by: Peter Gyori
Co-authored-by: Chris Sampson
Signed-off-by: David Handermann
(cherry picked from commit 3f5ed2350476ea258b0d96b00987e5deb626af53)
> Create a processor that is capable of removing fields from records
> --
>
> Key: NIFI-9206
> URL: https://issues.apache.org/jira/browse/NIFI-9206
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
>Reporter: Peter Gyori
>Assignee: Chris Sampson
>Priority: Major
> Fix For: 1.latest, 2.latest
>
> Attachments: NIFI-9206.json
>
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> A processor should be created that is capable of removing fields from records
> (RemoveRecordField might be a name for it).
> The processor should have 3 properties:
> * Record Reader (a Reader controller service could be specified)
> * Record Writer (a Writer controller service could be specified)
> * Field To Remove (expects a RecordPath that points to the field to be
> removed)
> The processor should be able to accept additional dynamic properties that
> specify further fields (by RecordPath) to be removed from the record.
> +*Example*+
> +input:+
> {code:java}
> {
> "id": 1,
> "name": "John",
> "address": {
> "zip": ,
> "street": "Main",
> "building": 11
> }
> }
> {code}
> +Field to remove:+ /address/building
> +output:+
> {code:java}
> {
> "id": 1,
> "name": "John",
> "address": {
> "zip": ,
> "street": "Main"
> }
> }
> {code}
> The record's schema should be modified accordingly (removing the
> /address/building field from the schema). Field removal should be permitted
> regardless of the field being nullable or not.
> Generally, the removal of a field should include the field's removal from the
> schema AND the data. The exception is if the removal is data-dependent (the
> field should be removed if its value equals "xyz"). In this case no schema
> modification should occur.
> The processor should be able to remove one or more elements from arrays
> (e.g.: /addresses[ 1 ] shoud remove the element from the addresses array from
> the 1st position). When removing a field from elements of an array, the
> array's schema should only be modified if the removal is applied to all
> elements of the array (i.e.: /addresses[ * ]/building should modify the
> schema of the array, but /addresses[ 1 ]/building should not).
> The same rule should be applied when handling Map datatype.
> If the record does not contain the field that is expected to be removed, the
> record should still be transferred to the 'success' relationship, with no
> modification. The expectation is that if /x/y is expected to be removed from
> the record, then the record leaving the processor should not contain /x/y
> field.
> If a certain field can be of different types (e.g. the address field can be
> "string" as well as "record" and possibly another "record" with a schema
> different from the former record type) then if /address/building is expected
> to be removed from the record, the processor is expected to remove the
> building field from the schema of all the possible types of the address field
> regardless of the address field being whatever concrete type in the
> particular record that is being processed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-3065) Fine-grained logging in multi-tenant context
[ https://issues.apache.org/jira/browse/NIFI-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737226#comment-17737226 ] ASF subversion and git services commented on NIFI-3065: --- Commit cb76a62a141972aa5fa46fa8bd925a17e12f541a in nifi's branch refs/heads/support/nifi-1.x from David Handermann [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=cb76a62a14 ] NIFI-3065 Corrected TestStandardLoggingContext for Java 8 Signed-off-by: David Handermann > Fine-grained logging in multi-tenant context > > > Key: NIFI-3065 > URL: https://issues.apache.org/jira/browse/NIFI-3065 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Pierre Villard >Assignee: Timea Barna >Priority: Minor > Fix For: 2.0.0, 1.23.0 > > Time Spent: 5.5h > Remaining Estimate: 0h > > In a multi-tenant approach, it could be interesting to offer to users a way > to have a fine-grained logging capabilities per tenant. > Let's say that root process group is used to have one process group per > "project" accessed by different teams/users, it could be really useful to > have a log file per process group containing logs for all elements inside > this process group. > A first version could be to develop a custom log appender that would log each > message in a file dedicated to its process group parent. > This improvement will ease the logging management when there are hundreds of > processors separated between different teams and this will also prevent the > access to the logs concerning one team by another team (could be a security > issue). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11750) Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide
[ https://issues.apache.org/jira/browse/NIFI-11750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-11750: -- Description: Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide to reflect the current situation. The main reasons that indicated the change: - homebrew moved to /opt/homebrew from /usr/local/Cellar which changed the config location of dnsmasq. - nifi.sensitive.props.key wasn't part of the guide - it is better to use a separate location to store configs instead of littering the toolkit directory was: Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide to reflect the current situation. The main reasons that indicated the change: - homebrew moved to /opt/homebrew from /usr/local/Cellar which changed the config location of dnsmasq. - nifi.sensitive.props.key wasn't part of the guide > Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide > > > Key: NIFI-11750 > URL: https://issues.apache.org/jira/browse/NIFI-11750 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation & Website >Reporter: Nandor Soma Abonyi >Assignee: Nandor Soma Abonyi >Priority: Minor > > Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide > to reflect the current situation. > The main reasons that indicated the change: > - homebrew moved to /opt/homebrew from /usr/local/Cellar which changed the > config location of dnsmasq. > - nifi.sensitive.props.key wasn't part of the guide > - it is better to use a separate location to store configs instead of > littering the toolkit directory > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11750) Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide
Nandor Soma Abonyi created NIFI-11750: - Summary: Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide Key: NIFI-11750 URL: https://issues.apache.org/jira/browse/NIFI-11750 Project: Apache NiFi Issue Type: Improvement Components: Documentation & Website Reporter: Nandor Soma Abonyi Assignee: Nandor Soma Abonyi Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide to reflect the current situation. The main reasons that indicated the change: - homebrew moved to /opt/homebrew from /usr/local/Cellar which changed the config location of dnsmasq. - nifi.sensitive.props.key wasn't part of the guide -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (NIFI-11530) Disk full even with nifi.content.repository.archive.max.usage.percentage set to 50%
[
https://issues.apache.org/jira/browse/NIFI-11530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737221#comment-17737221
]
Giovanni edited comment on NIFI-11530 at 6/26/23 4:06 PM:
--
After I configured the volumes I also set the provenance max size to 9GB:
{code:java}
# Persistent Provenance Repository Properties
nifi.provenance.repository.directory.default=/var/nifi/provenance_repo/data
nifi.provenance.repository.max.storage.time=30 days
nifi.provenance.repository.max.storage.size=9 GB
nifi.provenance.repository.rollover.time=10 mins
nifi.provenance.repository.rollover.size=100 MB
nifi.provenance.repository.query.threads=2
nifi.provenance.repository.index.threads=2
nifi.provenance.repository.compress.on.rollover=true
nifi.provenance.repository.always.sync=false {code}
So 8.98GB could be a normal size according to the setting or should I expect
the repo size to be lower?
was (Author: JIRAUSER300198):
After I configured the volumes I also set the provenance max size to 9GB:
{code:java}
# Persistent Provenance Repository Properties
nifi.provenance.repository.directory.default=/var/nifi/provenance_repo/data
nifi.provenance.repository.max.storage.time=30 days
nifi.provenance.repository.max.storage.size=9 GB
nifi.provenance.repository.rollover.time=10 mins
nifi.provenance.repository.rollover.size=100 MB
nifi.provenance.repository.query.threads=2
nifi.provenance.repository.index.threads=2
nifi.provenance.repository.compress.on.rollover=true
nifi.provenance.repository.always.sync=false {code}
So 8.98GB could be a normal size according to the setting or should I expect
the repo size to be lower?
> Disk full even with nifi.content.repository.archive.max.usage.percentage set
> to 50%
> ---
>
> Key: NIFI-11530
> URL: https://issues.apache.org/jira/browse/NIFI-11530
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 1.20.0
> Environment: Ubuntu 20.04.5 LTS
>Reporter: Giovanni
>Priority: Major
> Attachments: 20230605_disk_usage.jpg, content_archive.jpg,
> flowfile_archive.jpg, image-2023-06-26-11-13-19-289.png,
> image-2023-06-26-11-15-00-379.png, image-2023-06-26-11-16-21-096.png,
> image-2023-06-26-11-16-35-791.png, image-2023-06-26-11-16-48-186.png,
> jvm.jpg, nifi1-app.log, nifi2-app.log, nifi3-app.log, nifi_bug.jpg,
> provenance_archive.jpg
>
>
> Nifi primary node reports disk full causing all nodes to stop working.
> Restarting nifi service does not resolve.
> Restarting the VM does not resolve.
> The only way to fix is to clean te content_repository dir:
> rm -rf ./nifi/content_repository/*
>
> Unfortunately I have no logs of the issue ongoing.
>
> UPDATE:
> I'm having the problem again.
> Every archive size is more than 50% on each node, with 70%+ peak on
> coordinator node (see attachments).
> I'm also attaching nifi-app.log this time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-11530) Disk full even with nifi.content.repository.archive.max.usage.percentage set to 50%
[
https://issues.apache.org/jira/browse/NIFI-11530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737221#comment-17737221
]
Giovanni commented on NIFI-11530:
-
After I configured the volumes I also set the provenance max size to 9GB:
{code:java}
# Persistent Provenance Repository Properties
nifi.provenance.repository.directory.default=/var/nifi/provenance_repo/data
nifi.provenance.repository.max.storage.time=30 days
nifi.provenance.repository.max.storage.size=9 GB
nifi.provenance.repository.rollover.time=10 mins
nifi.provenance.repository.rollover.size=100 MB
nifi.provenance.repository.query.threads=2
nifi.provenance.repository.index.threads=2
nifi.provenance.repository.compress.on.rollover=true
nifi.provenance.repository.always.sync=false {code}
So 8.98GB could be a normal size according to the setting or should I expect
the repo size to be lower?
> Disk full even with nifi.content.repository.archive.max.usage.percentage set
> to 50%
> ---
>
> Key: NIFI-11530
> URL: https://issues.apache.org/jira/browse/NIFI-11530
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 1.20.0
> Environment: Ubuntu 20.04.5 LTS
>Reporter: Giovanni
>Priority: Major
> Attachments: 20230605_disk_usage.jpg, content_archive.jpg,
> flowfile_archive.jpg, image-2023-06-26-11-13-19-289.png,
> image-2023-06-26-11-15-00-379.png, image-2023-06-26-11-16-21-096.png,
> image-2023-06-26-11-16-35-791.png, image-2023-06-26-11-16-48-186.png,
> jvm.jpg, nifi1-app.log, nifi2-app.log, nifi3-app.log, nifi_bug.jpg,
> provenance_archive.jpg
>
>
> Nifi primary node reports disk full causing all nodes to stop working.
> Restarting nifi service does not resolve.
> Restarting the VM does not resolve.
> The only way to fix is to clean te content_repository dir:
> rm -rf ./nifi/content_repository/*
>
> Unfortunately I have no logs of the issue ongoing.
>
> UPDATE:
> I'm having the problem again.
> Every archive size is more than 50% on each node, with 70%+ peak on
> coordinator node (see attachments).
> I'm also attaching nifi-app.log this time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-11530) Disk full even with nifi.content.repository.archive.max.usage.percentage set to 50%
[ https://issues.apache.org/jira/browse/NIFI-11530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737209#comment-17737209 ] Joe Witt commented on NIFI-11530: - The provenance settings from nifi.properties you shared a few weeks ago and the disk size for provenance shown would not work out. It says you want to keep 10GB but you have only 9.75GB of disk. Try cutting provenance storage in half. > Disk full even with nifi.content.repository.archive.max.usage.percentage set > to 50% > --- > > Key: NIFI-11530 > URL: https://issues.apache.org/jira/browse/NIFI-11530 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.20.0 > Environment: Ubuntu 20.04.5 LTS >Reporter: Giovanni >Priority: Major > Attachments: 20230605_disk_usage.jpg, content_archive.jpg, > flowfile_archive.jpg, image-2023-06-26-11-13-19-289.png, > image-2023-06-26-11-15-00-379.png, image-2023-06-26-11-16-21-096.png, > image-2023-06-26-11-16-35-791.png, image-2023-06-26-11-16-48-186.png, > jvm.jpg, nifi1-app.log, nifi2-app.log, nifi3-app.log, nifi_bug.jpg, > provenance_archive.jpg > > > Nifi primary node reports disk full causing all nodes to stop working. > Restarting nifi service does not resolve. > Restarting the VM does not resolve. > The only way to fix is to clean te content_repository dir: > rm -rf ./nifi/content_repository/* > > Unfortunately I have no logs of the issue ongoing. > > UPDATE: > I'm having the problem again. > Every archive size is more than 50% on each node, with 70%+ peak on > coordinator node (see attachments). > I'm also attaching nifi-app.log this time. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-3065) Fine-grained logging in multi-tenant context
[ https://issues.apache.org/jira/browse/NIFI-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737207#comment-17737207 ] ASF subversion and git services commented on NIFI-3065: --- Commit 0ab0ba2b8a5431448371b686d6c14c5f975d1751 in nifi's branch refs/heads/support/nifi-1.x from David Handermann [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=0ab0ba2b8a ] NIFI-3065 Corrected version to 1.23.0-SNAPSHOT for Process Group Logging Signed-off-by: David Handermann > Fine-grained logging in multi-tenant context > > > Key: NIFI-3065 > URL: https://issues.apache.org/jira/browse/NIFI-3065 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Pierre Villard >Assignee: Timea Barna >Priority: Minor > Fix For: 2.0.0, 1.23.0 > > Time Spent: 5.5h > Remaining Estimate: 0h > > In a multi-tenant approach, it could be interesting to offer to users a way > to have a fine-grained logging capabilities per tenant. > Let's say that root process group is used to have one process group per > "project" accessed by different teams/users, it could be really useful to > have a log file per process group containing logs for all elements inside > this process group. > A first version could be to develop a custom log appender that would log each > message in a file dedicated to its process group parent. > This improvement will ease the logging management when there are hundreds of > processors separated between different teams and this will also prevent the > access to the logs concerning one team by another team (could be a security > issue). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-9206) Create a processor that is capable of removing fields from records
[
https://issues.apache.org/jira/browse/NIFI-9206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737197#comment-17737197
]
ASF subversion and git services commented on NIFI-9206:
---
Commit 3f5ed2350476ea258b0d96b00987e5deb626af53 in nifi's branch
refs/heads/main from Chris Sampson
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=3f5ed23504 ]
NIFI-9206 Added RemoveRecordField Processor
This closes #6816
Co-authored-by: Peter Gyori
Co-authored-by: Chris Sampson
Signed-off-by: David Handermann
> Create a processor that is capable of removing fields from records
> --
>
> Key: NIFI-9206
> URL: https://issues.apache.org/jira/browse/NIFI-9206
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
>Reporter: Peter Gyori
>Assignee: Chris Sampson
>Priority: Major
> Fix For: 1.latest, 2.latest
>
> Attachments: NIFI-9206.json
>
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> A processor should be created that is capable of removing fields from records
> (RemoveRecordField might be a name for it).
> The processor should have 3 properties:
> * Record Reader (a Reader controller service could be specified)
> * Record Writer (a Writer controller service could be specified)
> * Field To Remove (expects a RecordPath that points to the field to be
> removed)
> The processor should be able to accept additional dynamic properties that
> specify further fields (by RecordPath) to be removed from the record.
> +*Example*+
> +input:+
> {code:java}
> {
> "id": 1,
> "name": "John",
> "address": {
> "zip": ,
> "street": "Main",
> "building": 11
> }
> }
> {code}
> +Field to remove:+ /address/building
> +output:+
> {code:java}
> {
> "id": 1,
> "name": "John",
> "address": {
> "zip": ,
> "street": "Main"
> }
> }
> {code}
> The record's schema should be modified accordingly (removing the
> /address/building field from the schema). Field removal should be permitted
> regardless of the field being nullable or not.
> Generally, the removal of a field should include the field's removal from the
> schema AND the data. The exception is if the removal is data-dependent (the
> field should be removed if its value equals "xyz"). In this case no schema
> modification should occur.
> The processor should be able to remove one or more elements from arrays
> (e.g.: /addresses[ 1 ] shoud remove the element from the addresses array from
> the 1st position). When removing a field from elements of an array, the
> array's schema should only be modified if the removal is applied to all
> elements of the array (i.e.: /addresses[ * ]/building should modify the
> schema of the array, but /addresses[ 1 ]/building should not).
> The same rule should be applied when handling Map datatype.
> If the record does not contain the field that is expected to be removed, the
> record should still be transferred to the 'success' relationship, with no
> modification. The expectation is that if /x/y is expected to be removed from
> the record, then the record leaving the processor should not contain /x/y
> field.
> If a certain field can be of different types (e.g. the address field can be
> "string" as well as "record" and possibly another "record" with a schema
> different from the former record type) then if /address/building is expected
> to be removed from the record, the processor is expected to remove the
> building field from the schema of all the possible types of the address field
> regardless of the address field being whatever concrete type in the
> particular record that is being processed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [nifi] exceptionfactory commented on a diff in pull request #7422: NIFI-11740: Added SnowflakeConfigurationService
exceptionfactory commented on code in PR #7422:
URL: https://github.com/apache/nifi/pull/7422#discussion_r1242364992
##
nifi-nar-bundles/nifi-snowflake-bundle/nifi-snowflake-services/src/main/java/org/apache/nifi/snowflake/service/util/SnowflakeConstants.java:
##
@@ -0,0 +1,29 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.snowflake.service.util;
+
+public final class SnowflakeConstants {
Review Comment:
That's a good point about the multiple types, in that case, `DEFAULT_PORT`
would need to return the String `443`.
Either way, I recommend renaming this to something like
`SnowflakePropertyValue`. On the other hand, as these values all relate to URI
construction, it may be better to refactor usage to something more focused as
opposed to creating an unconstrained location for global variables.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [nifi] nandorsoma commented on a diff in pull request #7422: NIFI-11740: Added SnowflakeConfigurationService
nandorsoma commented on code in PR #7422:
URL: https://github.com/apache/nifi/pull/7422#discussion_r1242070493
##
nifi-nar-bundles/nifi-snowflake-bundle/nifi-snowflake-services/src/main/java/org/apache/nifi/snowflake/service/StandardSnowflakeIngestManagerProviderService.java:
##
@@ -161,17 +188,44 @@ public void onEnabled(final ConfigurationContext context)
throws InitializationE
.getValue();
final String pipe =
context.getProperty(PIPE).evaluateAttributeExpressions().getValue();
fullyQualifiedPipeName = database + "." + schema + "." + pipe;
-final PrivateKeyService privateKeyService =
context.getProperty(PRIVATE_KEY_SERVICE)
-.asControllerService(PrivateKeyService.class);
-final PrivateKey privateKey = privateKeyService.getPrivateKey();
-
-final AccountIdentifierFormat accountIdentifierFormat =
AccountIdentifierFormat.forName(context.getProperty(ACCOUNT_IDENTIFIER_FORMAT)
-.getValue());
-final AccountIdentifierFormatParameters parameters =
getAccountIdentifierFormatParameters(context);
-final String account = accountIdentifierFormat.getAccount(parameters);
-final String host = accountIdentifierFormat.getHostname(parameters);
+
+final String user;
+final PrivateKey privateKey;
+final String account;
+final String accountUrl;
+
+final SnowflakeConfigurationService configurationService =
context.getProperty(SNOWFLAKE_CONFIGURATION_SERVICE).asControllerService(SnowflakeConfigurationService.class);
+if (configurationService != null) {
+final SnowflakeConfiguration configuration =
configurationService.getConfiguration();
+user = configuration.getUsername();
+privateKey = configuration.getPrivateKey();
+account = configuration.getAccount();
+accountUrl = configuration.getAccountUrl();
+} else {
+user =
context.getProperty(USER_NAME).evaluateAttributeExpressions().getValue();
+
+final PrivateKeyService privateKeyService =
context.getProperty(PRIVATE_KEY_SERVICE).asControllerService(PrivateKeyService.class);
+privateKey = privateKeyService.getPrivateKey();
+
+final AccountIdentifierFormat accountIdentifierFormat =
AccountIdentifierFormat.forName(context.getProperty(ACCOUNT_IDENTIFIER_FORMAT).getValue());
Review Comment:
I know that this PR didn't touch the forName method, but I wonder
`equalsIgnoreCase` is really needed.
##
nifi-nar-bundles/nifi-snowflake-bundle/nifi-snowflake-services/src/main/java/org/apache/nifi/snowflake/service/SnowflakeComputingConnectionPool.java:
##
@@ -135,6 +136,15 @@ public class SnowflakeComputingConnectionPool extends
AbstractDBCPConnectionPool
.description("The password for the Snowflake user.")
.build();
+public static final PropertyDescriptor SNOWFLAKE_DATABASE = new
PropertyDescriptor.Builder()
Review Comment:
It might worth adding a validation that the url doesn't contain db= when
this property has a value.
##
nifi-nar-bundles/nifi-snowflake-bundle/nifi-snowflake-services/src/main/java/org/apache/nifi/snowflake/service/util/ConnectionUrlFormat.java:
##
@@ -22,24 +22,26 @@
import java.util.stream.Stream;
import org.apache.nifi.components.DescribedValue;
+import static
org.apache.nifi.snowflake.service.util.SnowflakeConstants.SNOWFLAKE_HOST_SUFFIX;
+
public enum ConnectionUrlFormat implements DescribedValue {
-FULL_URL("full-url", "Full URL", "Provide connection URL in a single
property") {
+JDBC_URL("full-url", "JDBC URL", "Provide connection URL in a single
property") {
Review Comment:
Minor, probably JDBC url would be better in the description as well.
##
nifi-nar-bundles/nifi-snowflake-bundle/nifi-snowflake-services/src/main/java/org/apache/nifi/snowflake/service/StandardSnowflakeIngestManagerProviderService.java:
##
@@ -34,18 +36,38 @@
import org.apache.nifi.expression.ExpressionLanguageScope;
import org.apache.nifi.key.service.api.PrivateKeyService;
import org.apache.nifi.processor.util.StandardValidators;
+import org.apache.nifi.processors.snowflake.SnowflakeConfiguration;
+import org.apache.nifi.processors.snowflake.SnowflakeConfigurationService;
import
org.apache.nifi.processors.snowflake.SnowflakeIngestManagerProviderService;
import org.apache.nifi.reporting.InitializationException;
import org.apache.nifi.snowflake.service.util.AccountIdentifierFormat;
import
org.apache.nifi.snowflake.service.util.AccountIdentifierFormatParameters;
-import org.apache.nifi.snowflake.service.util.ConnectionUrlFormat;
import org.apache.nifi.processors.snowflake.util.SnowflakeProperties;
+import org.apache.nifi.snowflake.service.util.SnowflakeConstants;
-@Tags({"snowflake", "jdbc", "database", "connection"})
+@Tags({"snowflake", "snowpipe", "ingest"})
Review
[jira] [Resolved] (NIFI-11743) Restrict FlowRegistryClient API to not allow null returns
[ https://issues.apache.org/jira/browse/NIFI-11743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann resolved NIFI-11743. - Fix Version/s: 2.0.0 Resolution: Fixed > Restrict FlowRegistryClient API to not allow null returns > - > > Key: NIFI-11743 > URL: https://issues.apache.org/jira/browse/NIFI-11743 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Simon Bence >Assignee: Simon Bence >Priority: Minor > Fix For: 2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The current definition of FlowRegistryClient allows implementations to return > with a null value in cases such as list of buckets, flows or versions. In > practice, this will not happen, but future implementations of changes has > this option now. > This is something we want to eliminate both because it is considered as a bad > pattern and because NiFi expect a valid (but maybe empty) return value. From > code perspective this will not cause any change, but the document will be > extended accordingly and will communicate that null is not a valid return > value. > Even if this is not a code change and the current registry client behaves in > this manner, it is considered as a breaking change thus this will be part of > the 2.x line only. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11745) Update QuestDB to 7.2
[ https://issues.apache.org/jira/browse/NIFI-11745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-11745: Fix Version/s: 2.0.0 (was: 2.latest) Resolution: Fixed Status: Resolved (was: Patch Available) > Update QuestDB to 7.2 > - > > Key: NIFI-11745 > URL: https://issues.apache.org/jira/browse/NIFI-11745 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Affects Versions: 2.latest >Reporter: Simon Bence >Assignee: Simon Bence >Priority: Major > Fix For: 2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > As the 7.x line of QuestDB does not support Java 8, we could not move on with > upgrading this dependency but as of NiFi 2.x will not provide Java 8 support, > it is adventageous to update to the last stable release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-11745) Update QuestDB to 7.2
[ https://issues.apache.org/jira/browse/NIFI-11745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737183#comment-17737183 ] ASF subversion and git services commented on NIFI-11745: Commit c5946b2e6c809f8fed312398c4e7fb8163510f33 in nifi's branch refs/heads/main from Simon Bence [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=c5946b2e6c ] NIFI-11745 Upgraded QuestDB from 6.7 to 7.2 This closes #7430 Signed-off-by: David Handermann > Update QuestDB to 7.2 > - > > Key: NIFI-11745 > URL: https://issues.apache.org/jira/browse/NIFI-11745 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Affects Versions: 2.latest >Reporter: Simon Bence >Assignee: Simon Bence >Priority: Major > Fix For: 2.latest > > Time Spent: 10m > Remaining Estimate: 0h > > As the 7.x line of QuestDB does not support Java 8, we could not move on with > upgrading this dependency but as of NiFi 2.x will not provide Java 8 support, > it is adventageous to update to the last stable release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-11743) Restrict FlowRegistryClient API to not allow null returns
[ https://issues.apache.org/jira/browse/NIFI-11743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737182#comment-17737182 ] ASF subversion and git services commented on NIFI-11743: Commit 5c8f4bf70cd19c8d056217d864fdad5df7e746ae in nifi's branch refs/heads/main from Simon Bence [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=5c8f4bf70c ] NIFI-11743 Adding restrictions on return values of FlowRegistryClient This closes #7431 Signed-off-by: David Handermann > Restrict FlowRegistryClient API to not allow null returns > - > > Key: NIFI-11743 > URL: https://issues.apache.org/jira/browse/NIFI-11743 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Simon Bence >Assignee: Simon Bence >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > The current definition of FlowRegistryClient allows implementations to return > with a null value in cases such as list of buckets, flows or versions. In > practice, this will not happen, but future implementations of changes has > this option now. > This is something we want to eliminate both because it is considered as a bad > pattern and because NiFi expect a valid (but maybe empty) return value. From > code perspective this will not cause any change, but the document will be > extended accordingly and will communicate that null is not a valid return > value. > Even if this is not a code change and the current registry client behaves in > this manner, it is considered as a breaking change thus this will be part of > the 2.x line only. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [nifi] exceptionfactory closed pull request #7431: NIFI-11743 Adding restrictions on return values of FlowRegistryClient
exceptionfactory closed pull request #7431: NIFI-11743 Adding restrictions on return values of FlowRegistryClient URL: https://github.com/apache/nifi/pull/7431 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [nifi] exceptionfactory closed pull request #7430: NIFI-11745 Upgrade QuestDb to version 7
exceptionfactory closed pull request #7430: NIFI-11745 Upgrade QuestDb to version 7 URL: https://github.com/apache/nifi/pull/7430 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [nifi] exceptionfactory commented on a diff in pull request #7353: NIFI-11658 Streamline using single parameter context for nested PGs
exceptionfactory commented on code in PR #7353:
URL: https://github.com/apache/nifi/pull/7353#discussion_r1242201390
##
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-client-dto/src/main/java/org/apache/nifi/web/api/entity/ProcessGroupUpdateStrategy.java:
##
@@ -0,0 +1,22 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.web.api.entity;
+
+public enum ProcessGroupUpdateStrategy {
+UPDATE_PROCESS_GROUP_ONLY,
+UPDATE_PROCESS_GROUP_WITH_DESCENDANTS
Review Comment:
Instead of repeating the `UPDATE_PROCESS_GROUP` prefix, recommend changing
the naming to be more concise. What about `CURRENT_GROUP` and
`CURRENT_GROUP_WITH_CHILDREN`? Much of User Guide documentation mentions "Child
Process Groups".
##
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/java/org/apache/nifi/web/NiFiServiceFacade.java:
##
@@ -1209,9 +1209,10 @@ Set getControllerServiceTypes(final
String serviceType, final
* Gets all process groups in the specified parent group.
*
* @param parentGroupId The id of the parent group
- * @return process group
+ * @param includeDescendants if process groups from descendant groups
should be included
+ * @return List of process groups
*/
-Set getProcessGroups(String parentGroupId);
+Set getProcessGroups(String parentGroupId, boolean
includeDescendants);
Review Comment:
Instead of using a `boolean` here, why not pass the
`ProcessGroupUpdateStrategy`?
##
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/java/org/apache/nifi/web/dao/ProcessGroupDAO.java:
##
@@ -59,9 +59,10 @@ public interface ProcessGroupDAO {
* Gets all of the process groups.
*
* @param parentGroupId The parent group id
+ * @param includeDescendants if process groups from descendant groups
should be included
* @return The process groups
*/
-Set getProcessGroups(String parentGroupId);
+Set getProcessGroups(String parentGroupId, boolean
includeDescendants);
Review Comment:
See above note on using the `ProcessGroupUpdateStrategy` enum.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Updated] (MINIFICPP-1996) Remove recursive mutex in ProcessGroup
[ https://issues.apache.org/jira/browse/MINIFICPP-1996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gábor Gyimesi updated MINIFICPP-1996: - Description: ProcessGroup class has a std::recursive_mutex for protecting its members which is overused in large scopes. The scope of its usage could be decreased to make increase performance and the recursive_mutex could be replaced with a simple std::mutex. [https://github.com/apache/nifi-minifi-cpp/pull/1451#discussion_r1029325420] was: ProcessGroup class has a std::recursive_mutex for protecting its members which is overused in large scopes. The scope of its usage could be decreased to make increase performance and the recursive_mutex could be replaced with a simple std::mutex. https://github.com/apache/nifi-minifi-cpp/pull/1451#discussion_r1029325420 > Remove recursive mutex in ProcessGroup > -- > > Key: MINIFICPP-1996 > URL: https://issues.apache.org/jira/browse/MINIFICPP-1996 > Project: Apache NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Gábor Gyimesi >Priority: Minor > Labels: MiNiFi-CPP-Hygiene > > ProcessGroup class has a std::recursive_mutex for protecting its members > which is overused in large scopes. The scope of its usage could be decreased > to make increase performance and the recursive_mutex could be replaced with a > simple std::mutex. > [https://github.com/apache/nifi-minifi-cpp/pull/1451#discussion_r1029325420] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MINIFICPP-1996) Remove recursive mutex in ProcessGroup
[ https://issues.apache.org/jira/browse/MINIFICPP-1996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gábor Gyimesi updated MINIFICPP-1996: - Description: ProcessGroup class has a std::recursive_mutex for protecting its members which is overused in large scopes. The scope of its usage could be decreased to make increase performance and the recursive_mutex could be replaced with a simple std::mutex. https://github.com/apache/nifi-minifi-cpp/pull/1451#discussion_r1029325420 was:ProcessGroup class has a std::recursive_mutex for protecting its members which is overused in large scopes. The scope of its usage could be decreased to make increase performance and the recursive_mutex could be replaced with a simple std::mutex. > Remove recursive mutex in ProcessGroup > -- > > Key: MINIFICPP-1996 > URL: https://issues.apache.org/jira/browse/MINIFICPP-1996 > Project: Apache NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Gábor Gyimesi >Priority: Minor > Labels: MiNiFi-CPP-Hygiene > > ProcessGroup class has a std::recursive_mutex for protecting its members > which is overused in large scopes. The scope of its usage could be decreased > to make increase performance and the recursive_mutex could be replaced with a > simple std::mutex. > > https://github.com/apache/nifi-minifi-cpp/pull/1451#discussion_r1029325420 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MINIFICPP-2133) Add TLS 1.3 support
[ https://issues.apache.org/jira/browse/MINIFICPP-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gábor Gyimesi reassigned MINIFICPP-2133: Assignee: Gábor Gyimesi > Add TLS 1.3 support > --- > > Key: MINIFICPP-2133 > URL: https://issues.apache.org/jira/browse/MINIFICPP-2133 > Project: Apache NiFi MiNiFi C++ > Issue Type: New Feature >Reporter: Gábor Gyimesi >Assignee: Gábor Gyimesi >Priority: Major > > In MINIFICPP-1719 OpenSSL 3 is introduced that supports TLS 1.3 contrary to > the previous LibreSSL that only supported TLS up to version 1.2. After > OpenSSL 3 is introduced we should add TLS 1.3 support and tests to our > application. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [nifi] simonbence opened a new pull request, #7431: NIFI-11743 Adding restrictions on return values of FlowRegistryClient
simonbence opened a new pull request, #7431: URL: https://github.com/apache/nifi/pull/7431 # Summary [NIFI-11743](https://issues.apache.org/jira/browse/NIFI-11743) The current definition of FlowRegistryClient allows implementations to return with a null value in cases such as list of buckets, flows or versions. In practice, this will not happen, but future implementations of changes has this option now. This is something we want to eliminate both because it is considered as a bad pattern and because NiFi expect a valid (but maybe empty) return value. From code perspective this will not cause any change, but the document will be extended accordingly and will communicate that null is not a valid return value. Even if this is not a code change and the current registry client behaves in this manner, it is considered as a breaking change thus this will be part of the 2.x line only. # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [ ] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [ ] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [ ] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [ ] Pull Request based on current revision of the `main` branch - [ ] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [ ] Build completed using `mvn clean install -P contrib-check` - [ ] JDK 17 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] (NIFI-11231) Stateless Nifi Supports Sensitive Parameter Context Variables
[ https://issues.apache.org/jira/browse/NIFI-11231 ]
Stephanie Ambrose deleted comment on NIFI-11231:
--
was (Author: JIRAUSER299049):
[~jgresock] Remember, this was for overriding values in the
stateless.properties file, not for flow environment variables. For example, you
can't override this property via command line:
nifi.stateless.security.keystorePassword the same way your override some other
values in the flow and engine property files. I'd want to run something like:
command: ["/bin/sh", "-c", "/opt/nifi/nifi-current/bin/nifi-stateless.sh -c -p
\"nifi.stateless.security.keystorePasswd=${KEYSTORE_PASSWORD}\""]
> 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: 2h
> 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] [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&focusedCommentId=17737104#comment-17737104
]
Stephanie Ambrose commented on NIFI-11231:
--
[~jgresock] Remember, this was for overriding values in the
stateless.properties file, not for flow environment variables. For example, you
can't override this property via command line:
nifi.stateless.security.keystorePassword the same way your override some other
values in the flow and engine property files. I'd want to run something like:
command: ["/bin/sh", "-c", "/opt/nifi/nifi-current/bin/nifi-stateless.sh -c -p
\"nifi.stateless.security.keystorePasswd=${KEYSTORE_PASSWORD}\""]
> 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: 2h
> 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-11743) Restrict FlowRegistryClient API to not allow null returns
[ https://issues.apache.org/jira/browse/NIFI-11743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Bence updated NIFI-11743: --- Description: The current definition of FlowRegistryClient allows implementations to return with a null value in cases such as list of buckets, flows or versions. In practice, this will not happen, but future implementations of changes has this option now. This is something we want to eliminate both because it is considered as a bad pattern and because NiFi expect a valid (but maybe empty) return value. From code perspective this will not cause any change, but the document will be extended accordingly and will communicate that null is not a valid return value. Even if this is not a code change and the current registry client behaves in this manner, it is considered as a breaking change thus this will be part of the 2.x line only. was: The current definition of FlowRegisttryClient allows implementations to return with a null value in cases such as list of buckets, flows or versions. In practice, this will not happen, but future implementations of changes has this option now. This is something we want to eliminate both because it is considered as a bad pattern and because NiFi expect a valid (but maybe empty) return value. From code perspective this will not cause any change, but the document will be extended accordingly and will communicate that null is not a valid return value. Even if this is not a code change and the current registry client behaves in this manner, it is considered as a breaking change thus this will be part of the 2.x line only. > Restrict FlowRegistryClient API to not allow null returns > - > > Key: NIFI-11743 > URL: https://issues.apache.org/jira/browse/NIFI-11743 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Simon Bence >Assignee: Simon Bence >Priority: Minor > > The current definition of FlowRegistryClient allows implementations to return > with a null value in cases such as list of buckets, flows or versions. In > practice, this will not happen, but future implementations of changes has > this option now. > This is something we want to eliminate both because it is considered as a bad > pattern and because NiFi expect a valid (but maybe empty) return value. From > code perspective this will not cause any change, but the document will be > extended accordingly and will communicate that null is not a valid return > value. > Even if this is not a code change and the current registry client behaves in > this manner, it is considered as a breaking change thus this will be part of > the 2.x line only. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11745) Update QuestDB to 7.2
[ https://issues.apache.org/jira/browse/NIFI-11745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Bence updated NIFI-11745: --- Status: Patch Available (was: In Progress) https://github.com/apache/nifi/pull/7430 > Update QuestDB to 7.2 > - > > Key: NIFI-11745 > URL: https://issues.apache.org/jira/browse/NIFI-11745 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Affects Versions: 2.latest >Reporter: Simon Bence >Assignee: Simon Bence >Priority: Major > Fix For: 2.latest > > Time Spent: 10m > Remaining Estimate: 0h > > As the 7.x line of QuestDB does not support Java 8, we could not move on with > upgrading this dependency but as of NiFi 2.x will not provide Java 8 support, > it is adventageous to update to the last stable release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [nifi-minifi-cpp] lordgamez opened a new pull request, #1595: MINIFICPP-2137 Rewrite MiNiFi Controller to use asio
lordgamez opened a new pull request, #1595:
URL: https://github.com/apache/nifi-minifi-cpp/pull/1595
https://issues.apache.org/jira/browse/MINIFICPP-2137
Note: depends on https://github.com/apache/nifi-minifi-cpp/pull/1583 as
there was a compile issue with LibreSSL on Windows that does not appear with
OpenSSL. It seems to be due to some Windows specific macro definition. If we
plan to move to OpenSSL I don't think it's worth debugging.
```
2023-06-23T15:41:12.8423242Z
D:\a\nifi-minifi-cpp\b\thirdparty\libressl-install\include\openssl/x509v3.h(194):
error C2143: syntax error: missing ')' before 'constant'
2023-06-23T15:41:12.8558554Z
D:\a\nifi-minifi-cpp\b\thirdparty\libressl-install\include\openssl/x509v3.h(194):
error C2143: syntax error: missing ';' before 'constant'
2023-06-23T15:41:12.8582850Z
D:\a\nifi-minifi-cpp\b\thirdparty\libressl-install\include\openssl/x509v3.h(194):
error C2059: syntax error: ')'
2023-06-23T15:41:12.8727617Z
D:\a\nifi-minifi-cpp\b\thirdparty\libressl-install\include\openssl/x509v3.h(194):
error C2238: unexpected token(s) preceding ';'
2023-06-23T15:41:12.8746940Z
D:\a\nifi-minifi-cpp\b\thirdparty\libressl-install\include\openssl/x509v3.h(202):
error C2143: syntax error: missing ')' before 'constant'
2023-06-23T15:41:12.8752091Z
D:\a\nifi-minifi-cpp\b\thirdparty\libressl-install\include\openssl/x509v3.h(202):
error C2143: syntax error: missing ';' before 'constant'
2023-06-23T15:41:12.8754426Z
D:\a\nifi-minifi-cpp\b\thirdparty\libressl-install\include\openssl/x509v3.h(202):
error C2059: syntax error: ')'
2023-06-23T15:41:12.8876950Z
D:\a\nifi-minifi-cpp\b\thirdparty\libressl-install\include\openssl/x509v3.h(202):
error C2238: unexpected token(s) preceding ';'
2023-06-23T15:41:12.9189256Z
D:\a\nifi-minifi-cpp\b\thirdparty\libressl-install\include\openssl/x509v3.h(231):
error C2143: syntax error: missing ')' before 'constant'
2023-06-23T15:41:12.9220842Z
D:\a\nifi-minifi-cpp\b\thirdparty\libressl-install\include\openssl/x509v3.h(231):
error C2143: syntax error: missing ';' before 'constant'
2023-06-23T15:41:12.9268061Z
D:\a\nifi-minifi-cpp\b\thirdparty\libressl-install\include\openssl/x509v3.h(231):
error C2059: syntax error: ')'
2023-06-23T15:41:12.9314784Z
D:\a\nifi-minifi-cpp\b\thirdparty\libressl-install\include\openssl/x509v3.h(231):
error C2238: unexpected token(s) preceding ';'
2023-06-23T15:41:12.9378837Z
D:\a\nifi-minifi-cpp\b\thirdparty\libressl-install\include\openssl/x509v3.h(657):
error C2059: syntax error: '('
2023-06-23T15:41:12.9710560Z
D:\a\nifi-minifi-cpp\b\thirdparty\libressl-install\include\openssl/x509v3.h(657):
error C2143: syntax error: missing ',' before '*'
2023-06-23T15:41:12.9786697Z
D:\a\nifi-minifi-cpp\b\thirdparty\libressl-install\include\openssl/x509v3.h(657):
error C2143: syntax error: missing ';' before ')'
2023-06-23T15:41:12.9789902Z
D:\a\nifi-minifi-cpp\b\thirdparty\libressl-install\include\openssl/x509v3.h(657):
error C2059: syntax error: ')'
2023-06-23T15:41:12.9918377Z
D:\a\nifi-minifi-cpp\b\thirdparty\libressl-install\include\openssl/x509v3.h(837):
error C2065: 'nm': undeclared identifier
2023-06-23T15:41:12.9962902Z
D:\a\nifi-minifi-cpp\b\thirdparty\libressl-install\include\openssl/x509v3.h(837):
error C2226: syntax error: unexpected type 'stack_st_CONF_VALUE'
```
--
Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
- [ ] Does your PR title start with MINIFICPP- where is the JIRA
number you are trying to resolve? Pay particular attention to the hyphen "-"
character.
- [ ] Has your PR been rebased against the latest commit within the target
branch (typically main)?
- [ ] Is your initial contribution a single, squashed commit?
### For code changes:
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the LICENSE file?
- [ ] If applicable, have you updated the NOTICE file?
### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in which
it is rendered?
### Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI
results for build issues and submit an update to your PR as soon as possible.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org
[GitHub] [nifi] simonbence opened a new pull request, #7430: NIFI-11745 Upgrade QuestDb to version 7
simonbence opened a new pull request, #7430: URL: https://github.com/apache/nifi/pull/7430 # Summary The version is updated and the code has been changed according to the API changes. The tests are green and based on manual testing, NiFi still gathers metrics. Note: the way the `SqlExecutionContext` creation has been changes was done based on suggestion from the QuestDB community. [NIFI-11745](https://issues.apache.org/jira/browse/NIFI-11745) # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [ ] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [ ] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [ ] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [ ] Pull Request based on current revision of the `main` branch - [ ] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [ ] Build completed using `mvn clean install -P contrib-check` - [ ] JDK 17 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [nifi-minifi-cpp] fgerlits opened a new pull request, #1594: MINIFICPP-2145 Parallelize the clang-tidy CI job
fgerlits opened a new pull request, #1594: URL: https://github.com/apache/nifi-minifi-cpp/pull/1594 Also: enable the JNI extension in the `clang-tidy` CI job. Without this, clang-tidy fails if there are any changes in `extensions/jni`, even if there are no `clang-tidy` errors. --- Thank you for submitting a contribution to Apache NiFi - MiNiFi C++. In order to streamline the review of the contribution we ask you to ensure the following steps have been taken: ### For all changes: - [x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message? - [x] Does your PR title start with MINIFICPP- where is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character. - [x] Has your PR been rebased against the latest commit within the target branch (typically main)? - [x] Is your initial contribution a single, squashed commit? ### For code changes: - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [ ] If applicable, have you updated the LICENSE file? - [ ] If applicable, have you updated the NOTICE file? ### For documentation related changes: - [ ] Have you ensured that format looks appropriate for the output in which it is rendered? ### Note: Please ensure that once the PR is submitted, you check GitHub Actions CI results for build issues and submit an update to your PR as soon as possible. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (NIFI-11673) Remove Legacy TLS Versions from Shared Configuration
[
https://issues.apache.org/jira/browse/NIFI-11673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandor Soma Abonyi updated NIFI-11673:
--
Fix Version/s: 2.0.0
(was: 2.latest)
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Remove Legacy TLS Versions from Shared Configuration
>
>
> Key: NIFI-11673
> URL: https://issues.apache.org/jira/browse/NIFI-11673
> 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
>
> The {{TlsConfiguration}} interface and referencing components include logic
> specific to Java 8 and 11, in addition to referencing legacy version of the
> TLS protocol. Modern Java distributions disallow TLS 1.0 and 1.1 in the
> default {{java.security}} configuration, and with NiFi 2.0 removing support
> for Java 8, version-based protocol selection can be removed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-11673) Remove Legacy TLS Versions from Shared Configuration
[
https://issues.apache.org/jira/browse/NIFI-11673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737067#comment-17737067
]
ASF subversion and git services commented on NIFI-11673:
Commit 1f1c5df5a370a0a502a8dbaf17bcb20a1c258dc2 in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=1f1c5df5a3 ]
NIFI-11673 Removed Legacy TLS Configuration Versions
This closes #7367
Signed-off-by: Nandor Soma Abonyi
> Remove Legacy TLS Versions from Shared Configuration
>
>
> Key: NIFI-11673
> URL: https://issues.apache.org/jira/browse/NIFI-11673
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
> Fix For: 2.latest
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The {{TlsConfiguration}} interface and referencing components include logic
> specific to Java 8 and 11, in addition to referencing legacy version of the
> TLS protocol. Modern Java distributions disallow TLS 1.0 and 1.1 in the
> default {{java.security}} configuration, and with NiFi 2.0 removing support
> for Java 8, version-based protocol selection can be removed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-11530) Disk full even with nifi.content.repository.archive.max.usage.percentage set to 50%
[ https://issues.apache.org/jira/browse/NIFI-11530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giovanni updated NIFI-11530: Attachment: image-2023-06-26-11-16-48-186.png > Disk full even with nifi.content.repository.archive.max.usage.percentage set > to 50% > --- > > Key: NIFI-11530 > URL: https://issues.apache.org/jira/browse/NIFI-11530 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.20.0 > Environment: Ubuntu 20.04.5 LTS >Reporter: Giovanni >Priority: Major > Attachments: 20230605_disk_usage.jpg, content_archive.jpg, > flowfile_archive.jpg, image-2023-06-26-11-13-19-289.png, > image-2023-06-26-11-15-00-379.png, image-2023-06-26-11-16-21-096.png, > image-2023-06-26-11-16-35-791.png, image-2023-06-26-11-16-48-186.png, > jvm.jpg, nifi1-app.log, nifi2-app.log, nifi3-app.log, nifi_bug.jpg, > provenance_archive.jpg > > > Nifi primary node reports disk full causing all nodes to stop working. > Restarting nifi service does not resolve. > Restarting the VM does not resolve. > The only way to fix is to clean te content_repository dir: > rm -rf ./nifi/content_repository/* > > Unfortunately I have no logs of the issue ongoing. > > UPDATE: > I'm having the problem again. > Every archive size is more than 50% on each node, with 70%+ peak on > coordinator node (see attachments). > I'm also attaching nifi-app.log this time. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-11530) Disk full even with nifi.content.repository.archive.max.usage.percentage set to 50%
[ https://issues.apache.org/jira/browse/NIFI-11530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737060#comment-17737060 ] Giovanni commented on NIFI-11530: - Update: I reconfigured the repository to have a logical volume for each: !image-2023-06-26-11-13-19-289.png! The overall performance are improved. However the provenance repository is still problematic: !image-2023-06-26-11-15-00-379.png! The other repos are ok though: !image-2023-06-26-11-16-21-096.png! !image-2023-06-26-11-16-35-791.png! !image-2023-06-26-11-16-48-186.png! > Disk full even with nifi.content.repository.archive.max.usage.percentage set > to 50% > --- > > Key: NIFI-11530 > URL: https://issues.apache.org/jira/browse/NIFI-11530 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.20.0 > Environment: Ubuntu 20.04.5 LTS >Reporter: Giovanni >Priority: Major > Attachments: 20230605_disk_usage.jpg, content_archive.jpg, > flowfile_archive.jpg, image-2023-06-26-11-13-19-289.png, > image-2023-06-26-11-15-00-379.png, image-2023-06-26-11-16-21-096.png, > image-2023-06-26-11-16-35-791.png, image-2023-06-26-11-16-48-186.png, > jvm.jpg, nifi1-app.log, nifi2-app.log, nifi3-app.log, nifi_bug.jpg, > provenance_archive.jpg > > > Nifi primary node reports disk full causing all nodes to stop working. > Restarting nifi service does not resolve. > Restarting the VM does not resolve. > The only way to fix is to clean te content_repository dir: > rm -rf ./nifi/content_repository/* > > Unfortunately I have no logs of the issue ongoing. > > UPDATE: > I'm having the problem again. > Every archive size is more than 50% on each node, with 70%+ peak on > coordinator node (see attachments). > I'm also attaching nifi-app.log this time. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11530) Disk full even with nifi.content.repository.archive.max.usage.percentage set to 50%
[ https://issues.apache.org/jira/browse/NIFI-11530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giovanni updated NIFI-11530: Attachment: image-2023-06-26-11-16-21-096.png > Disk full even with nifi.content.repository.archive.max.usage.percentage set > to 50% > --- > > Key: NIFI-11530 > URL: https://issues.apache.org/jira/browse/NIFI-11530 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.20.0 > Environment: Ubuntu 20.04.5 LTS >Reporter: Giovanni >Priority: Major > Attachments: 20230605_disk_usage.jpg, content_archive.jpg, > flowfile_archive.jpg, image-2023-06-26-11-13-19-289.png, > image-2023-06-26-11-15-00-379.png, image-2023-06-26-11-16-21-096.png, > image-2023-06-26-11-16-35-791.png, image-2023-06-26-11-16-48-186.png, > jvm.jpg, nifi1-app.log, nifi2-app.log, nifi3-app.log, nifi_bug.jpg, > provenance_archive.jpg > > > Nifi primary node reports disk full causing all nodes to stop working. > Restarting nifi service does not resolve. > Restarting the VM does not resolve. > The only way to fix is to clean te content_repository dir: > rm -rf ./nifi/content_repository/* > > Unfortunately I have no logs of the issue ongoing. > > UPDATE: > I'm having the problem again. > Every archive size is more than 50% on each node, with 70%+ peak on > coordinator node (see attachments). > I'm also attaching nifi-app.log this time. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11530) Disk full even with nifi.content.repository.archive.max.usage.percentage set to 50%
[ https://issues.apache.org/jira/browse/NIFI-11530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giovanni updated NIFI-11530: Attachment: image-2023-06-26-11-16-35-791.png > Disk full even with nifi.content.repository.archive.max.usage.percentage set > to 50% > --- > > Key: NIFI-11530 > URL: https://issues.apache.org/jira/browse/NIFI-11530 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.20.0 > Environment: Ubuntu 20.04.5 LTS >Reporter: Giovanni >Priority: Major > Attachments: 20230605_disk_usage.jpg, content_archive.jpg, > flowfile_archive.jpg, image-2023-06-26-11-13-19-289.png, > image-2023-06-26-11-15-00-379.png, image-2023-06-26-11-16-21-096.png, > image-2023-06-26-11-16-35-791.png, image-2023-06-26-11-16-48-186.png, > jvm.jpg, nifi1-app.log, nifi2-app.log, nifi3-app.log, nifi_bug.jpg, > provenance_archive.jpg > > > Nifi primary node reports disk full causing all nodes to stop working. > Restarting nifi service does not resolve. > Restarting the VM does not resolve. > The only way to fix is to clean te content_repository dir: > rm -rf ./nifi/content_repository/* > > Unfortunately I have no logs of the issue ongoing. > > UPDATE: > I'm having the problem again. > Every archive size is more than 50% on each node, with 70%+ peak on > coordinator node (see attachments). > I'm also attaching nifi-app.log this time. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11530) Disk full even with nifi.content.repository.archive.max.usage.percentage set to 50%
[ https://issues.apache.org/jira/browse/NIFI-11530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giovanni updated NIFI-11530: Attachment: image-2023-06-26-11-15-00-379.png > Disk full even with nifi.content.repository.archive.max.usage.percentage set > to 50% > --- > > Key: NIFI-11530 > URL: https://issues.apache.org/jira/browse/NIFI-11530 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.20.0 > Environment: Ubuntu 20.04.5 LTS >Reporter: Giovanni >Priority: Major > Attachments: 20230605_disk_usage.jpg, content_archive.jpg, > flowfile_archive.jpg, image-2023-06-26-11-13-19-289.png, > image-2023-06-26-11-15-00-379.png, jvm.jpg, nifi1-app.log, nifi2-app.log, > nifi3-app.log, nifi_bug.jpg, provenance_archive.jpg > > > Nifi primary node reports disk full causing all nodes to stop working. > Restarting nifi service does not resolve. > Restarting the VM does not resolve. > The only way to fix is to clean te content_repository dir: > rm -rf ./nifi/content_repository/* > > Unfortunately I have no logs of the issue ongoing. > > UPDATE: > I'm having the problem again. > Every archive size is more than 50% on each node, with 70%+ peak on > coordinator node (see attachments). > I'm also attaching nifi-app.log this time. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11530) Disk full even with nifi.content.repository.archive.max.usage.percentage set to 50%
[ https://issues.apache.org/jira/browse/NIFI-11530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giovanni updated NIFI-11530: Attachment: image-2023-06-26-11-13-19-289.png > Disk full even with nifi.content.repository.archive.max.usage.percentage set > to 50% > --- > > Key: NIFI-11530 > URL: https://issues.apache.org/jira/browse/NIFI-11530 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.20.0 > Environment: Ubuntu 20.04.5 LTS >Reporter: Giovanni >Priority: Major > Attachments: 20230605_disk_usage.jpg, content_archive.jpg, > flowfile_archive.jpg, image-2023-06-26-11-13-19-289.png, jvm.jpg, > nifi1-app.log, nifi2-app.log, nifi3-app.log, nifi_bug.jpg, > provenance_archive.jpg > > > Nifi primary node reports disk full causing all nodes to stop working. > Restarting nifi service does not resolve. > Restarting the VM does not resolve. > The only way to fix is to clean te content_repository dir: > rm -rf ./nifi/content_repository/* > > Unfortunately I have no logs of the issue ongoing. > > UPDATE: > I'm having the problem again. > Every archive size is more than 50% on each node, with 70%+ peak on > coordinator node (see attachments). > I'm also attaching nifi-app.log this time. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11745) Update QuestDB to 7.2
[ https://issues.apache.org/jira/browse/NIFI-11745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Bence updated NIFI-11745: --- Component/s: Core Framework Fix Version/s: 2.latest Affects Version/s: 2.latest > Update QuestDB to 7.2 > - > > Key: NIFI-11745 > URL: https://issues.apache.org/jira/browse/NIFI-11745 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Affects Versions: 2.latest >Reporter: Simon Bence >Assignee: Simon Bence >Priority: Major > Fix For: 2.latest > > > As the 7.x line of QuestDB does not support Java 8, we could not move on with > upgrading this dependency but as of NiFi 2.x will not provide Java 8 support, > it is adventageous to update to the last stable release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MINIFICPP-2143) CWEL JSON: add System/Security/UserId
[ https://issues.apache.org/jira/browse/MINIFICPP-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Debreceni reassigned MINIFICPP-2143: - Assignee: Adam Debreceni > CWEL JSON: add System/Security/UserId > - > > Key: MINIFICPP-2143 > URL: https://issues.apache.org/jira/browse/MINIFICPP-2143 > Project: Apache NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Marton Szasz >Assignee: Adam Debreceni >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (MINIFICPP-2144) Allow windows service and standalone execution with different MINIFI_HOMEs
[ https://issues.apache.org/jira/browse/MINIFICPP-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737027#comment-17737027 ] Adam Debreceni edited comment on MINIFICPP-2144 at 6/26/23 7:42 AM: turns out that this was caused by the semaphore usage which is removed as of [MINIFICPP-2121|https://issues.apache.org/jira/browse/MINIFICPP-2121] was (Author: adebreceni): turns out that this was caused by the semaphore usage which is removed as of [MINIFICPP-2020|https://issues.apache.org/jira/browse/MINIFICPP-2020] > Allow windows service and standalone execution with different MINIFI_HOMEs > -- > > Key: MINIFICPP-2144 > URL: https://issues.apache.org/jira/browse/MINIFICPP-2144 > Project: Apache NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Adam Debreceni >Assignee: Adam Debreceni >Priority: Major > > A minifi service on windows prevents any other minifi instance from running > even if their MINIFI_HOME is different. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (MINIFICPP-2144) Allow windows service and standalone execution with different MINIFI_HOMEs
[ https://issues.apache.org/jira/browse/MINIFICPP-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Debreceni resolved MINIFICPP-2144. --- Resolution: Fixed fixed in https://issues.apache.org/jira/browse/MINIFICPP-2121 > Allow windows service and standalone execution with different MINIFI_HOMEs > -- > > Key: MINIFICPP-2144 > URL: https://issues.apache.org/jira/browse/MINIFICPP-2144 > Project: Apache NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Adam Debreceni >Assignee: Adam Debreceni >Priority: Major > > A minifi service on windows prevents any other minifi instance from running > even if their MINIFI_HOME is different. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MINIFICPP-2144) Allow windows service and standalone execution with different MINIFI_HOMEs
[ https://issues.apache.org/jira/browse/MINIFICPP-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737027#comment-17737027 ] Adam Debreceni commented on MINIFICPP-2144: --- turns out that this was caused by the semaphore usage which is removed as of [MINIFICPP-2020|https://issues.apache.org/jira/browse/MINIFICPP-2020] > Allow windows service and standalone execution with different MINIFI_HOMEs > -- > > Key: MINIFICPP-2144 > URL: https://issues.apache.org/jira/browse/MINIFICPP-2144 > Project: Apache NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Adam Debreceni >Assignee: Adam Debreceni >Priority: Major > > A minifi service on windows prevents any other minifi instance from running > even if their MINIFI_HOME is different. -- This message was sent by Atlassian Jira (v8.20.10#820010)
