[jira] [Updated] (MINIFICPP-2346) Speed up MiNiFi Build with Conan package manager (C++)
[
https://issues.apache.org/jira/browse/MINIFICPP-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Guzman (Medel) updated MINIFICPP-2346:
Attachment: minifi_cpp_conan_build_2d1b884.log
> Speed up MiNiFi Build with Conan package manager (C++)
> --
>
> Key: MINIFICPP-2346
> URL: https://issues.apache.org/jira/browse/MINIFICPP-2346
> Project: Apache NiFi MiNiFi C++
> Issue Type: Improvement
>Affects Versions: 0.15.0
> Environment: Ubuntu 22.04
>Reporter: James Guzman (Medel)
>Assignee: James Guzman (Medel)
>Priority: Minor
> Labels: build, conan, ubuntu
> Attachments: minifi_cpp_conan_build_2d1b884.log
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> *NOTE:* I noticed you guys recently switched from 0.15 to 0.99, so at certain
> point, I will pull in lastest updates from MiNiFi C++ main branch on parent
> level and rebase or merge into my PR.
> *Description of Issue:* Building MiNiFi C++ with just CMake is really slow.
> During the the build process, it clones all the external dependencies and
> then builds those external dependencies while its building MiNiFi CPP.
> Sometimes the MiNiFi CPP build fails too when external lib dependencies fail
> to download or fail to build. It would be faster to build MiNiFi C++ with the
> external dependencies already preinstalled.
>
> *Potential Solution:* Integrate *conan version 2* into MiNiFi C++ project to
> enable support for using *conan install* to install all or most of MiNiFi's
> external dependencies, using *conan install --build=missing* to build them as
> prebuilt binary conan packages, upload them to conancenter with {*}conan
> upload{*}, and then run cmake generate to generate the appropriate build
> files for the OS, then run make to build MiNiFi CPP. Also conan has really
> good support for cross platform compatibility for Linux and Windows. At this
> point because we already have most of MiNiFi CPP's external lib dependencies
> installed with conan, our CMake build will just focus on building the MiNiFi
> CPP code, enabling faster builds. Also I will need to account for backward
> compatibility support with the previous way of installing MiNiFi CPP external
> lib dependencies using CMake FetchContent_Declare(...) approach until
> conanfile.py approach covers installing all these dependencies. A valid
> verification of the MiNiFi C++ build would be to run GTESTs and if all the
> expected test cases pass, then it may be fair to conclude we would be ready
> to deprecate the slow CMake FetchContent_Declare(...) approach.
>
> *Steps to Perform MiNiFi C++ Build Enhancement (Plan to Integrate into
> script(s)):*
> # Install conan version 2 into MiNiFi C++ dev environment (my preference is
> using docker container)
> # Create a conanfile.py file at root of MiNiFi C++ project where we run
> "conan install" or "conan install --build=missing" to install MiNiFi C++
> external lib dependencies first. Then we run CMake to build MiNiFi C++.
> # Find all MiNiFi C++ find_package(...) CMake function calls and check if
> there is already supported conan packages on the conancenter, so we can
> install those packages.
> # Find all FetchContent_Declare(...) CMake function calls and check if there
> is already supported conan packages on the conancenter, so we can install
> those packages.
> # At this point we will have used conan version 2 C++ package manager to
> install almost all MiNiFi C++'s external dependencies.
> ## With Conan, we will have installed these MiNiFi external lib dependencies
> as prebuilt binary conan packages.
> ## Or we will have instructed conan to first build each C++ external lib
> dependency, upload each lib to conancenter.
> # Thus, conan manages installing MiNiFi C++'s external lib dependencies, so
> we can then run CMake to build MiNiFi faster.
>
> Here is my draft PR for this Jira Ticket for your reference:
> [https://github.com/apache/nifi-minifi-cpp/pull/1775]
> * I have added *abseil* external lib dependency to conanfile.py and
> integrated it into Abseil.cmake with conditional statement that checks if
> USE_CONAN_PACKAGER minifi cpp option is true else checks if
> USE_CMAKE_FETCH_CONTENT option is true for backward compatibility, so we can
> began the process of integrating in conan version 2.
>
> Here are the commands that I run:
>
> {code:java}
> cd $HOME/src/pipeline/nifi-minifi-cpp
> # NOTE: I also plan to add smoother integration of conan commands into MiNiFI
> CPP too
> # For instance, I know you guys have your bootstrap scripts too
> # You also have your github actions workflow scripts too
> conan install . --output-folder=build
> -pr=$HOME/src/nifi-minifi-cpp/etc/build/conan/profiles/release-linux
> #
[jira] [Updated] (NIFI-13144) Improve dependency-update detection configuration and bump various detected dependency versions
[
https://issues.apache.org/jira/browse/NIFI-13144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Witt updated NIFI-13144:
Status: Patch Available (was: Open)
> Improve dependency-update detection configuration and bump various detected
> dependency versions
> ---
>
> Key: NIFI-13144
> URL: https://issues.apache.org/jira/browse/NIFI-13144
> Project: Apache NiFi
> Issue Type: Task
>Reporter: Joe Witt
>Assignee: Joe Witt
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {noformat}
> com.puppycrawl.tools:checkstyle ... 10.15.0 -> 10.16.0
> software.amazon.awssdk:xray ... 2.25.40 -> 2.25.45
> com.amazonaws:aws-java-sdk-keyspaces 1.12.710 -> 1.12.715
> com.azure:azure-sdk-bom 1.2.21 -> 1.2.23
> com.google.cloud:libraries-bom ... 26.37.0 -> 26.38.0
> net.bytebuddy:byte-buddy .. 1.14.12 -> 1.14.14
> org.checkerframework:checker-qual ... 3.37.0 -> 3.43.0
> org.eclipse.jdt:ecj . 3.33.0 -> 3.37.0
> com.microsoft.azure:msal4j .. 1.14.3 -> 1.15.0
> com.google.guava:guava .. 33.1.0-jre -> 33.2.0-jre
> com.ibm.icu:icu4j ... 74.2 -> 75.1
> org.opensaml:opensaml-* 4.3.1 -> 4.3.2
> org.apache.sshd:sshd-* ... 2.12.0 -> 2.12.1
> com.nimbusds:oauth2-oidc-sdk ... 9.43.3 -> 9.43.4
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-13139) PythonNarIT tests failing, missing StandardPythonBridge
[ https://issues.apache.org/jira/browse/NIFI-13139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Witt updated NIFI-13139: Status: Patch Available (was: Open) > PythonNarIT tests failing, missing StandardPythonBridge > --- > > Key: NIFI-13139 > URL: https://issues.apache.org/jira/browse/NIFI-13139 > Project: Apache NiFi > Issue Type: Bug >Reporter: Tamas Palfy >Assignee: Joe Witt >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The issue seems to be due to > nifi-system-tests/nifi-system-test-suite/target/pythonic-instance/lib not > prepared to have the nifi-py4j-nar-2.0.0-SNAPSHOT.nar. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] NIFI-13139 ensure nifi-py4j-nar is included in test assembly [nifi]
joewitt opened a new pull request, #8747: URL: https://github.com/apache/nifi/pull/8747 # Summary [NIFI-13139](https://issues.apache.org/jira/browse/NIFI-13139) # 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 21 ### UI Contributions - [ ] NiFi is modernizing its UI. Any contributions that update the [current UI](https://github.com/apache/nifi/tree/main/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui) also need to be implemented in the [new UI](https://github.com/apache/nifi/tree/main/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi). ### 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] [Commented] (NIFI-13139) PythonNarIT tests failing, missing StandardPythonBridge
[ https://issues.apache.org/jira/browse/NIFI-13139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843521#comment-17843521 ] Joe Witt commented on NIFI-13139: - the assembly for the test suite was not pulling in the nifi-py4j-nar. The PR resolves that > PythonNarIT tests failing, missing StandardPythonBridge > --- > > Key: NIFI-13139 > URL: https://issues.apache.org/jira/browse/NIFI-13139 > Project: Apache NiFi > Issue Type: Bug >Reporter: Tamas Palfy >Assignee: Joe Witt >Priority: Major > > The issue seems to be due to > nifi-system-tests/nifi-system-test-suite/target/pythonic-instance/lib not > prepared to have the nifi-py4j-nar-2.0.0-SNAPSHOT.nar. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-13139) PythonNarIT tests failing, missing StandardPythonBridge
[ https://issues.apache.org/jira/browse/NIFI-13139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Witt reassigned NIFI-13139: --- Assignee: Joe Witt > PythonNarIT tests failing, missing StandardPythonBridge > --- > > Key: NIFI-13139 > URL: https://issues.apache.org/jira/browse/NIFI-13139 > Project: Apache NiFi > Issue Type: Bug >Reporter: Tamas Palfy >Assignee: Joe Witt >Priority: Major > > The issue seems to be due to > nifi-system-tests/nifi-system-test-suite/target/pythonic-instance/lib not > prepared to have the nifi-py4j-nar-2.0.0-SNAPSHOT.nar. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12973 Add Process Group scope to Flow Analysis rules [nifi]
joewitt commented on PR #8682: URL: https://github.com/apache/nifi/pull/8682#issuecomment-2094552799 @pvillard31 disregard. I'll have a pull request up for for NIFI-13139 that should address that problem. I think you can ignore that for this PR about flow analysis -- 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-2346) Speed up MiNiFi Build with Conan package manager (C++)
[
https://issues.apache.org/jira/browse/MINIFICPP-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Guzman (Medel) updated MINIFICPP-2346:
Description:
*NOTE:* I noticed you guys recently switched from 0.15 to 0.99, so at certain
point, I will pull in lastest updates from MiNiFi C++ main branch on parent
level and rebase or merge into my PR.
*Description of Issue:* Building MiNiFi C++ with just CMake is really slow.
During the the build process, it clones all the external dependencies and then
builds those external dependencies while its building MiNiFi CPP. Sometimes the
MiNiFi CPP build fails too when external lib dependencies fail to download or
fail to build. It would be faster to build MiNiFi C++ with the external
dependencies already preinstalled.
*Potential Solution:* Integrate *conan version 2* into MiNiFi C++ project to
enable support for using *conan install* to install all or most of MiNiFi's
external dependencies, using *conan install --build=missing* to build them as
prebuilt binary conan packages, upload them to conancenter with {*}conan
upload{*}, and then run cmake generate to generate the appropriate build files
for the OS, then run make to build MiNiFi CPP. Also conan has really good
support for cross platform compatibility for Linux and Windows. At this point
because we already have most of MiNiFi CPP's external lib dependencies
installed with conan, our CMake build will just focus on building the MiNiFi
CPP code, enabling faster builds. Also I will need to account for backward
compatibility support with the previous way of installing MiNiFi CPP external
lib dependencies using CMake FetchContent_Declare(...) approach until
conanfile.py approach covers installing all these dependencies. A valid
verification of the MiNiFi C++ build would be to run GTESTs and if all the
expected test cases pass, then it may be fair to conclude we would be ready to
deprecate the slow CMake FetchContent_Declare(...) approach.
*Steps to Perform MiNiFi C++ Build Enhancement (Plan to Integrate into
script(s)):*
# Install conan version 2 into MiNiFi C++ dev environment (my preference is
using docker container)
# Create a conanfile.py file at root of MiNiFi C++ project where we run "conan
install" or "conan install --build=missing" to install MiNiFi C++ external lib
dependencies first. Then we run CMake to build MiNiFi C++.
# Find all MiNiFi C++ find_package(...) CMake function calls and check if
there is already supported conan packages on the conancenter, so we can install
those packages.
# Find all FetchContent_Declare(...) CMake function calls and check if there
is already supported conan packages on the conancenter, so we can install those
packages.
# At this point we will have used conan version 2 C++ package manager to
install almost all MiNiFi C++'s external dependencies.
## With Conan, we will have installed these MiNiFi external lib dependencies
as prebuilt binary conan packages.
## Or we will have instructed conan to first build each C++ external lib
dependency, upload each lib to conancenter.
# Thus, conan manages installing MiNiFi C++'s external lib dependencies, so we
can then run CMake to build MiNiFi faster.
Here is my draft PR for this Jira Ticket for your reference:
[https://github.com/apache/nifi-minifi-cpp/pull/1775]
* I have added *abseil* external lib dependency to conanfile.py and integrated
it into Abseil.cmake with conditional statement that checks if
USE_CONAN_PACKAGER minifi cpp option is true else checks if
USE_CMAKE_FETCH_CONTENT option is true for backward compatibility, so we can
began the process of integrating in conan version 2.
Here are the commands that I run:
{code:java}
cd $HOME/src/pipeline/nifi-minifi-cpp
# NOTE: I also plan to add smoother integration of conan commands into MiNiFI
CPP too
# For instance, I know you guys have your bootstrap scripts too
# You also have your github actions workflow scripts too
conan install . --output-folder=build
-pr=$HOME/src/nifi-minifi-cpp/etc/build/conan/profiles/release-linux
# install conan packages and build C++ for minifi using Conan & CMake, we run
this way, so conan's tc.cache_variables
# are like passing -D{minifi_option} upon running cmake generate, then make
to build MiNiFi C++
conan build . --output-folder=build
-pr=/home/bizon/src/jam-repo/main/etc/build/conan/profiles/release-linux{code}
{color:#0747a6}{*}UPDATE (May 4, 2024) -
[2d1b884|https://github.com/apache/nifi-minifi-cpp/pull/1775/commits/2d1b8842c6809380f981f9857543805efbfd00cc]{*}:{color}
Updated MiNiFi CPP code with Conan & CMake to build libMiNiFi *core-minifi*
and MiNiFi Main's *minifiexe* and {*}minifi-{*}{*}standard-processors{*}
extension with minimal set of external libraries needed. If you look at our
conanfile.py, you'll see {*}minifi_core_external_libraries{*}, which is a tuple
[jira] [Updated] (MINIFICPP-2346) Speed up MiNiFi Build with Conan package manager (C++)
[
https://issues.apache.org/jira/browse/MINIFICPP-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Guzman (Medel) updated MINIFICPP-2346:
Description:
*NOTE:* I noticed you guys recently switched from 0.15 to 0.99, so at certain
point, I will pull in lastest updates from MiNiFi C++ main branch on parent
level and rebase or merge into my PR.
*Description of Issue:* Building MiNiFi C++ with just CMake is really slow.
During the the build process, it clones all the external dependencies and then
builds those external dependencies while its building MiNiFi CPP. Sometimes the
MiNiFi CPP build fails too when external lib dependencies fail to download or
fail to build. It would be faster to build MiNiFi C++ with the external
dependencies already preinstalled.
*Potential Solution:* Integrate *conan version 2* into MiNiFi C++ project to
enable support for using *conan install* to install all or most of MiNiFi's
external dependencies, using *conan install --build=missing* to build them as
prebuilt binary conan packages, upload them to conancenter with {*}conan
upload{*}, and then run cmake generate to generate the appropriate build files
for the OS, then run make to build MiNiFi CPP. Also conan has really good
support for cross platform compatibility for Linux and Windows. At this point
because we already have most of MiNiFi CPP's external lib dependencies
installed with conan, our CMake build will just focus on building the MiNiFi
CPP code, enabling faster builds. Also I will need to account for backward
compatibility support with the previous way of installing MiNiFi CPP external
lib dependencies using CMake FetchContent_Declare(...) approach until
conanfile.py approach covers installing all these dependencies. A valid
verification of the MiNiFi C++ build would be to run GTESTs and if all the
expected test cases pass, then it may be fair to conclude we would be ready to
deprecate the slow CMake FetchContent_Declare(...) approach.
*Steps to Perform MiNiFi C++ Build Enhancement (Plan to Integrate into
script(s)):*
# Install conan version 2 into MiNiFi C++ dev environment (my preference is
using docker container)
# Create a conanfile.py file at root of MiNiFi C++ project where we run "conan
install" or "conan install --build=missing" to install MiNiFi C++ external lib
dependencies first. Then we run CMake to build MiNiFi C++.
# Find all MiNiFi C++ find_package(...) CMake function calls and check if
there is already supported conan packages on the conancenter, so we can install
those packages.
# Find all FetchContent_Declare(...) CMake function calls and check if there
is already supported conan packages on the conancenter, so we can install those
packages.
# At this point we will have used conan version 2 C++ package manager to
install almost all MiNiFi C++'s external dependencies.
## With Conan, we will have installed these MiNiFi external lib dependencies
as prebuilt binary conan packages.
## Or we will have instructed conan to first build each C++ external lib
dependency, upload each lib to conancenter.
# Thus, conan manages installing MiNiFi C++'s external lib dependencies, so we
can then run CMake to build MiNiFi faster.
Here is my draft PR for this Jira Ticket for your reference:
[https://github.com/apache/nifi-minifi-cpp/pull/1775]
* I have added *abseil* external lib dependency to conanfile.py and integrated
it into Abseil.cmake with conditional statement that checks if
USE_CONAN_PACKAGER minifi cpp option is true else checks if
USE_CMAKE_FETCH_CONTENT option is true for backward compatibility, so we can
began the process of integrating in conan version 2.
Here are the commands that I run:
{code:java}
cd $HOME/src/pipeline/nifi-minifi-cpp
# NOTE: I also plan to add smoother integration of conan commands into MiNiFI
CPP too
# For instance, I know you guys have your bootstrap scripts too
# You also have your github actions workflow scripts too
conan install . --output-folder=build
-pr=$HOME/src/nifi-minifi-cpp/etc/build/conan/profiles/release-linux
# install conan packages and build C++ for minifi using Conan & CMake, we run
this way, so conan's tc.cache_variables
# are like passing -D{minifi_option} upon running cmake generate, then make
to build MiNiFi C++
conan build . --output-folder=build
-pr=/home/bizon/src/jam-repo/main/etc/build/conan/profiles/release-linux{code}
{color:#0747a6}{*}UPDATE (May 4, 2024){*}:{color} Updated MiNiFi CPP code with
Conan & CMake to build libMiNiFi *core-minifi* and MiNiFi Main's *minifiexe*
and {*}minifi-{*}{*}standard-processors{*} extension with minimal set of
external libraries needed. If you look at our conanfile.py, you'll see
{*}minifi_core_external_libraries{*}, which is a tuple of the minimal external
libraries needed to build these two essential building blocks of MiNFi CPP.
Next when you
[jira] [Updated] (MINIFICPP-2346) Speed up MiNiFi Build with Conan package manager (C++)
[
https://issues.apache.org/jira/browse/MINIFICPP-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Guzman (Medel) updated MINIFICPP-2346:
Description:
*NOTE:* I noticed you guys recently switched from 0.15 to 0.99, so at certain
point, I will pull in lastest updates from MiNiFi C++ main branch on parent
level and rebase or merge into my PR.
*Description of Issue:* Building MiNiFi C++ with just CMake is really slow.
During the the build process, it clones all the external dependencies and then
builds those external dependencies while its building MiNiFi CPP. Sometimes the
MiNiFi CPP build fails too when external lib dependencies fail to download or
fail to build. It would be faster to build MiNiFi C++ with the external
dependencies already preinstalled.
*Potential Solution:* Integrate *conan version 2* into MiNiFi C++ project to
enable support for using *conan install* to install all or most of MiNiFi's
external dependencies, using *conan install --build=missing* to build them as
prebuilt binary conan packages, upload them to conancenter with {*}conan
upload{*}, and then run cmake generate to generate the appropriate build files
for the OS, then run make to build MiNiFi CPP. Also conan has really good
support for cross platform compatibility for Linux and Windows. At this point
because we already have most of MiNiFi CPP's external lib dependencies
installed with conan, our CMake build will just focus on building the MiNiFi
CPP code, enabling faster builds. Also I will need to account for backward
compatibility support with the previous way of installing MiNiFi CPP external
lib dependencies using CMake FetchContent_Declare(...) approach until
conanfile.py approach covers installing all these dependencies. A valid
verification of the MiNiFi C++ build would be to run GTESTs and if all the
expected test cases pass, then it may be fair to conclude we would be ready to
deprecate the slow CMake FetchContent_Declare(...) approach.
*Steps to Perform MiNiFi C++ Build Enhancement (Plan to Integrate into
script(s)):*
# Install conan version 2 into MiNiFi C++ dev environment (my preference is
using docker container)
# Create a conanfile.py file at root of MiNiFi C++ project where we run "conan
install" or "conan install --build=missing" to install MiNiFi C++ external lib
dependencies first. Then we run CMake to build MiNiFi C++.
# Find all MiNiFi C++ find_package(...) CMake function calls and check if
there is already supported conan packages on the conancenter, so we can install
those packages.
# Find all FetchContent_Declare(...) CMake function calls and check if there
is already supported conan packages on the conancenter, so we can install those
packages.
# At this point we will have used conan version 2 C++ package manager to
install almost all MiNiFi C++'s external dependencies.
## With Conan, we will have installed these MiNiFi external lib dependencies
as prebuilt binary conan packages.
## Or we will have instructed conan to first build each C++ external lib
dependency, upload each lib to conancenter.
# Thus, conan manages installing MiNiFi C++'s external lib dependencies, so we
can then run CMake to build MiNiFi faster.
Here is my draft PR for this Jira Ticket for your reference:
[https://github.com/apache/nifi-minifi-cpp/pull/1775]
* I have added *abseil* external lib dependency to conanfile.py and integrated
it into Abseil.cmake with conditional statement that checks if
USE_CONAN_PACKAGER minifi cpp option is true else checks if
USE_CMAKE_FETCH_CONTENT option is true for backward compatibility, so we can
began the process of integrating in conan version 2.
Here are the commands that I run:
{code:java}
cd $HOME/src/pipeline/nifi-minifi-cpp
# NOTE: I also plan to add smoother integration of conan commands into MiNiFI
CPP too
# For instance, I know you guys have your bootstrap scripts too
# You also have your github actions workflow scripts too
conan install . --output-folder=build
-pr=$HOME/src/nifi-minifi-cpp/etc/build/conan/profiles/release-linux
# install conan packages and build C++ for minifi using Conan & CMake, we run
this way, so conan's tc.cache_variables
# are like passing -D{minifi_option} upon running cmake generate, then make
to build MiNiFi C++
conan build . --output-folder=build
-pr=/home/bizon/src/jam-repo/main/etc/build/conan/profiles/release-linux{code}
{color:#0747a6}{*}UPDATE (May 4, 2024){*}:{color} Updated MiNiFi CPP code with
Conan & CMake to build libMiNiFi *core-minifi* and MiNiFi Main's *minifiexe*
and {*}minifi-{*}{*}standard-processors{*} extension with minimal set of
external libraries needed. If you look at our conanfile.py, you'll see
{*}minifi_core_external_libraries{*}, which is a list of the minimal external
libraries needed to build these two essential building blocks of MiNFi CPP.
Next when you
[jira] [Commented] (NIFI-13139) PythonNarIT tests failing, missing StandardPythonBridge
[
https://issues.apache.org/jira/browse/NIFI-13139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843514#comment-17843514
]
Joe Witt commented on NIFI-13139:
-
while PythonNarIT is running it will just hang. If you look at
pythonic-instance logs it shows
{noformat}
... 85 common frames omitted
Caused by: org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'flowController': FactoryBean threw exception on object
creation
at
org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:188)
at
org.springframework.beans.factory.support.FactoryBeanRegistrySupport.getObjectFromFactoryBean(FactoryBeanRegistrySupport.java:124)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getObjectForBeanInstance(AbstractBeanFactory.java:1850)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.getObjectForBeanInstance(AbstractAutowireCapableBeanFactory.java:1276)
at
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:336)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:200)
at
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:313)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:200)
at
org.springframework.beans.factory.config.DependencyDescriptor.resolveCandidate(DependencyDescriptor.java:254)
at
org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1443)
at
org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1353)
at
org.springframework.beans.factory.support.ConstructorResolver.resolveAutowiredArgument(ConstructorResolver.java:904)
at
org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:782)
... 108 common frames omitted
Caused by: java.lang.RuntimeException: Python Bridge initialization failed
at
org.apache.nifi.controller.FlowController.createPythonBridge(FlowController.java:945)
at
org.apache.nifi.controller.FlowController.(FlowController.java:573)
at
org.apache.nifi.controller.FlowController.createStandaloneInstance(FlowController.java:411)
at
org.apache.nifi.spring.FlowControllerFactoryBean.getObject(FlowControllerFactoryBean.java:83)
at
org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:182)
... 120 common frames omitted
Caused by: java.lang.IllegalStateException: The specified implementation class
'org.apache.nifi.py4j.StandardPythonBridge' is not known to this nifi.
at
org.apache.nifi.nar.NarThreadContextClassLoader.createInstance(NarThreadContextClassLoader.java:222)
at
org.apache.nifi.nar.NarThreadContextClassLoader.createInstance(NarThreadContextClassLoader.java:198)
at
org.apache.nifi.controller.FlowController.createPythonBridge(FlowController.java:928)
... 124 common frames omitted
2024-05-04 15:08:05,139 INFO [Thread-0] org.apache.nifi.NiFi Application Server
shutdown started
{noformat}
> PythonNarIT tests failing, missing StandardPythonBridge
> ---
>
> Key: NIFI-13139
> URL: https://issues.apache.org/jira/browse/NIFI-13139
> Project: Apache NiFi
> Issue Type: Bug
>Reporter: Tamas Palfy
>Priority: Major
>
> The issue seems to be due to
> nifi-system-tests/nifi-system-test-suite/target/pythonic-instance/lib not
> prepared to have the nifi-py4j-nar-2.0.0-SNAPSHOT.nar.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (NIFI-11960) Update maven-resources-plugin in py4j to 3.3.1
[ https://issues.apache.org/jira/browse/NIFI-11960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Witt resolved NIFI-11960. - Resolution: Duplicate this is already 3.3.1 on main > Update maven-resources-plugin in py4j to 3.3.1 > -- > > Key: NIFI-11960 > URL: https://issues.apache.org/jira/browse/NIFI-11960 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.23.0, 1.23.1 >Reporter: Mike R >Priority: Minor > Time Spent: 0.5h > Remaining Estimate: 0h > > Update maven-resources-plugin in py4j -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12411: Update PublishAMQP to read AMQP headers value from FlowFile attributes and `amq$headers` string [nifi]
joewitt commented on PR #8105: URL: https://github.com/apache/nifi/pull/8105#issuecomment-2094426305 @umarhussain15 Can you please rebase and consider the feedback shared from @exceptionfactory ? Thanks -- 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
Re: [PR] NIFI-12973 Add Process Group scope to Flow Analysis rules [nifi]
joewitt commented on PR #8682: URL: https://github.com/apache/nifi/pull/8682#issuecomment-2094422608 @pvillard31 What command are you running to have the Python tests fail? Consistent with what we run on github CI I use ` mvn verify -Pintegration-tests,integration-tests-ci,skip-unit-tests -pl -:minifi-assembly -pl -:nifi-assembly -pl -:nifi-toolkit-assembly -pl -:nifi-registry-assembly -pl -:nifi-registry-toolkit-assembly -pl -:nifi-runtime-manifest -pl -:nifi-runtime-manifest-test -pl -:nifi-stateless-assembly -pl -:nifi-stateless-system-test-suite -pl -:nifi-system-test-suite -pl -:nifi-nar-provider-assembly -pl -:nifi-py4j-integration-tests -pl -:nifi-docs -pl -:nifi-maven-archetypes -pl -:nifi-processor-bundle-archetype -pl -:nifi-service-bundle-archetype` But notably that skips py4j-integration-tests. I'll run that locally and see what fun comes out -- 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
Re: [PR] NIFI-13137 - Switch to Zulu for MacOS Java 8 action [nifi]
joewitt commented on PR #8739: URL: https://github.com/apache/nifi/pull/8739#issuecomment-2094417081 +1 merged to support/nifi-1.x -- 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
Re: [PR] NIFI-13137 - Switch to Zulu for MacOS Java 8 action [nifi]
joewitt closed pull request #8739: NIFI-13137 - Switch to Zulu for MacOS Java 8 action URL: https://github.com/apache/nifi/pull/8739 -- 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-13137) Switch to Zulu for MacOS Java 8 action
[ https://issues.apache.org/jira/browse/NIFI-13137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843511#comment-17843511 ] ASF subversion and git services commented on NIFI-13137: Commit 5adc0d8cb834206e09138d1310c303bdfa985df0 in nifi's branch refs/heads/support/nifi-1.x from Pierre Villard [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=5adc0d8cb8 ] NIFI-13137 - Switch to Zulu for MacOS Java 8 action This closes #8739. Signed-off-by: Joseph Witt > Switch to Zulu for MacOS Java 8 action > -- > > Key: NIFI-13137 > URL: https://issues.apache.org/jira/browse/NIFI-13137 > Project: Apache NiFi > Issue Type: Task > Components: Tools and Build >Affects Versions: 1.26.0 >Reporter: Pierre Villard >Assignee: Pierre Villard >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Temurin Java 8 is not available for macOS 14 on AArch64. The most > straightforward solution would be switching to some other JDK, such as Azul. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13137) Switch to Zulu for MacOS Java 8 action
[ https://issues.apache.org/jira/browse/NIFI-13137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Witt updated NIFI-13137: Fix Version/s: 1.27.0 Resolution: Fixed Status: Resolved (was: Patch Available) > Switch to Zulu for MacOS Java 8 action > -- > > Key: NIFI-13137 > URL: https://issues.apache.org/jira/browse/NIFI-13137 > Project: Apache NiFi > Issue Type: Task > Components: Tools and Build >Affects Versions: 1.26.0 >Reporter: Pierre Villard >Assignee: Pierre Villard >Priority: Major > Fix For: 1.27.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Temurin Java 8 is not available for macOS 14 on AArch64. The most > straightforward solution would be switching to some other JDK, such as Azul. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-13144 improved depependency update config and various dependencies [nifi]
joewitt commented on PR #8746: URL: https://github.com/apache/nifi/pull/8746#issuecomment-2094410808 Locally verified: - full clean build w contrib and new ui - all integration tests run in the Github CI suite - The full suite of system tests - Dependency-check results validated The JIRA outlines details of things left unchanged which deserve attention in follow-on JIRAs/tickets. It also explains how others can more easily maintain/review dependencies over 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
[PR] NIFI-13144 improved depependency update config and various dependencies [nifi]
joewitt opened a new pull request, #8746: URL: https://github.com/apache/nifi/pull/8746 com.puppycrawl.tools:checkstyle 10.15.0 -> 10.16.0 software.amazon.awssdk:xray 2.25.40 -> 2.25.45 com.amazonaws:aws-java-sdk-keyspaces 1.12.710 -> 1.12.715 com.azure:azure-sdk-bom 1.2.21 -> 1.2.23 com.google.cloud:libraries-bom 26.37.0 -> 26.38.0 net.bytebuddy:byte-buddy 1.14.12 -> 1.14.14 org.checkerframework:checker-qual 3.37.0 -> 3.43.0 org.eclipse.jdt:ecj 3.33.0 -> 3.37.0 com.microsoft.azure:msal4j 1.14.3 -> 1.15.0 com.google.guava:guava 33.1.0-jre -> 33.2.0-jre com.ibm.icu:icu4j 74.2 -> 75.1 org.opensaml:opensaml-* 4.3.1 -> 4.3.2 org.apache.sshd:sshd-* 2.12.0 -> 2.12.1 com.nimbusds:oauth2-oidc-sdk 9.43.3 -> 9.43.4 excel-streaming-reader 4.2.1 -> 4.3.1 amqp-client 5.20.0 5.21.0 json-schema-validator 1.3.2 1.4.0 Saxon-HE 12.3 12.4 lucene 8.11.2 8.11.3 commons-compiler 3.1.10 3.1.12 dropbox.client.version 5.4.4 5.4.6 subethasmtp 7.0.1 7.0.2 docker-java-api 3.3.4 3.3.6 google-api-services-drive v3-rev20230520-2.0.0 v3-rev20240327-2.0.0 protobuf-java 3.25.1 3.25.3 hazelcast 5.3.5 5.3.7 jackson-datatype-protobuf 0.9.14 0.9.15 kusto-* 5.0.3 5.0.5 mysql-connector-j 8.3.0 8.4.0 docker-compose-junit-jupiter 2.0.0 2.3.0 bolt-socket-mode 1.37.0 1.39.0 wire-schema-jvm 4.9.3 4.9.9 mysql-binlog-connector-java 0.29.0 0.29.2 jjwt 0.12.3 0.12.5 reactor-core 3.4.34 3.4.37 reactor-test 3.5.14 3.5.16 jakarta.activation-api 2.0.1 (and 2.1.2) to 2.1.3 jakarta.mail-api 2.0.1 (and 2.1.2) to 2.1.3 datafaker 2.0.2 to 2.2.2 jna and jna-platform 5.13.0 5.14.0 activemq-* 6.1.1 6.1.2 camel-salesforce 3.14.9 3.14.10 commons-csv 1.10.0 1.11.0 hbase.version 2.5.5-hadoop3 2.5.8-hadoop3 httpasyncclient 4.1.4 4.1.5 httpcore-nio 4.4.12 4.4.16 iotdb 1.3.0 1.3.1 mina-core 2.1.6 2.1.8 gremlin-* 3.7.1 3.7.2 clojure 1.11.2 1.11.3 angus-mail 2.0.2 2.0.3 jgit* 6.8.0.202311291450-r 6.9.0.202403050737-r javaassist 3.29.2-GA 3.30.2-GA jline 3.25.1 3.26.1 mariadb-java-client 3.3.0 3.3.3 mongodb-driver-sync 4.11.1 4.11.2 neo4j-java-driver 4.4.12 4.4.16 postgresql 4.7.2 4.7.3 spring-data-redis 2.7.15 2.7.18 spring-integration-mail 6.2.1 6.2.4 spring-vault-core 3.1.0 3.1.1 xmlunit-core 2.9.1 2.10.0 xmlunit-matchers 2.9.1 2.10.0 amazon-kinesis-client 2.5.7 2.5.8 reactor-netty-http 1.0.39 1.0.44 ant 1.10.13 1.10.14 hamcrest-core and hamcrest-all 1.3 moved to just hamcrest 2.2 # Summary [NIFI-13144](https://issues.apache.org/jira/browse/NIFI-13144) # 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 21 ### UI Contributions - [ ] NiFi is modernizing its UI. Any contributions that update the [current UI](https://github.com/apache/nifi/tree/main/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui) also need to be implemented in the [new UI](https://github.com/apache/nifi/tree/main/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi). ### 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] [Commented] (NIFI-13144) Improve dependency-update detection configuration and bump various detected dependency versions
[
https://issues.apache.org/jira/browse/NIFI-13144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843510#comment-17843510
]
Joe Witt commented on NIFI-13144:
-
full clean build with contrib check and new ui all good.
full run of integration-tests consistent with CI runs all good.
full run of integration system tests all good.
results of dependency-check consistent with previous runs. Main issues are
with hadoop related components and/or threetenbp which is medium and disputed.
Another finding is a test lib not used in the resulting build.
Putting up PR shortly.
> Improve dependency-update detection configuration and bump various detected
> dependency versions
> ---
>
> Key: NIFI-13144
> URL: https://issues.apache.org/jira/browse/NIFI-13144
> Project: Apache NiFi
> Issue Type: Task
>Reporter: Joe Witt
>Assignee: Joe Witt
>Priority: Major
>
> {noformat}
> com.puppycrawl.tools:checkstyle ... 10.15.0 -> 10.16.0
> software.amazon.awssdk:xray ... 2.25.40 -> 2.25.45
> com.amazonaws:aws-java-sdk-keyspaces 1.12.710 -> 1.12.715
> com.azure:azure-sdk-bom 1.2.21 -> 1.2.23
> com.google.cloud:libraries-bom ... 26.37.0 -> 26.38.0
> net.bytebuddy:byte-buddy .. 1.14.12 -> 1.14.14
> org.checkerframework:checker-qual ... 3.37.0 -> 3.43.0
> org.eclipse.jdt:ecj . 3.33.0 -> 3.37.0
> com.microsoft.azure:msal4j .. 1.14.3 -> 1.15.0
> com.google.guava:guava .. 33.1.0-jre -> 33.2.0-jre
> com.ibm.icu:icu4j ... 74.2 -> 75.1
> org.opensaml:opensaml-* 4.3.1 -> 4.3.2
> org.apache.sshd:sshd-* ... 2.12.0 -> 2.12.1
> com.nimbusds:oauth2-oidc-sdk ... 9.43.3 -> 9.43.4
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] NIFI-12231 FetchSmb supports Move and Delete Completion Strategies [nifi]
turcsanyip commented on PR #8617: URL: https://github.com/apache/nifi/pull/8617#issuecomment-2094368629 @exceptionfactory I managed to fix the tests by changing the logic in FetchSmb. There were 2 overlapping sessions to the SMB server: one for reading the file and the other for executing the completions strategy (move or delete) in `commitAsync()`. I moved the commit out of the TWR block of the first session, so the "read" session gets closed before the "move/delete" session starts. Parallel sessions should not cause issues as the file handles are closed properly and it worked in my environments (ran flows connecting to Windows share and Samba share, ran integrations tests on Mac and Linux). Not sure what the docker environment is doing in Github CI but this change fixed it. I re-ran the integrations tests 3 times and all were green. -- 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] [Comment Edited] (NIFI-13144) Improve dependency-update detection configuration and bump various detected dependency versions
[
https://issues.apache.org/jira/browse/NIFI-13144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843492#comment-17843492
]
Joe Witt edited comment on NIFI-13144 at 5/4/24 7:21 PM:
-
Requires more effort as version change results in compile or test failures
{noformat}
questdb 7.3.7 7.3.10 (there is a 7.4.2)
{noformat}
Needs follow up as major change or has bitten in the past on version change:
{noformat}
org.jetbrains: annotations 13.0 to 24.1.0
springframework-security-kerberos 1.0 to 2.0
elasticsearch 7.13.4 to 7.17.21 (although major release 8.x already available)
lucene 8.11.3 to 9.10.0
okhttp-digest 2.7 to 3.1.0
oauth2-oidc-sdk 9.43.4 to 11.10.1
protobuf 3.25.3 to 4.26.1
couchbase core/clien 1.7x and 2.7x to 2.6x and 3.6x
camel-salesforce 3.14.10 to 3.22.1 (and 4.5 is out!)
de.siegmar fastcsv 2.2.2 to 3.1.0
reactor-core and test from 3.4x to 3.6.5
unboundid-ldapsdk 6x to 7x but only in test scope
hazelcast 5.3.7 to 5.4.0
dropbox-core-sdk 5.x to 7x
{noformat}
was (Author: joewitt):
Requires more effort as version change results in compile or test failures
{noformat}
questdb 7.3.7 7.3.10 (there is a 7.4.2)
{noformat}
Needs follow up as major change or has bitten in the past on version change:
{noformat}
org.jetbrains: annotations 13.0 to 24.1.0
springframework-security-kerberos 1.0 to 2.0
elasticsearch 7.13.4 to 7.17.21 (although major release 8.x already available)
lucene 8.11.3 to 9.10.0
okhttp-digest 2.7 to 3.1.0
oauth2-oidc-sdk 9.43.4 to 11.10.1
protobuf 3.25.3 to 4.26.1
couchbase core/clien 1.7x and 2.7x to 2.6x and 3.6x
camel-salesforce 3.14.10 to 3.22.1
de.siegmar fastcsv 2.2.2 to 3.1.0
reactor-core and test from 3.4x to 3.6.5
unboundid-ldapsdk 6x to 7x but only in test scope
hazelcast 5.3.7 to 5.4.0
dropbox-core-sdk 5.x to 7x
{noformat}
> Improve dependency-update detection configuration and bump various detected
> dependency versions
> ---
>
> Key: NIFI-13144
> URL: https://issues.apache.org/jira/browse/NIFI-13144
> Project: Apache NiFi
> Issue Type: Task
>Reporter: Joe Witt
>Assignee: Joe Witt
>Priority: Major
>
> {noformat}
> com.puppycrawl.tools:checkstyle ... 10.15.0 -> 10.16.0
> software.amazon.awssdk:xray ... 2.25.40 -> 2.25.45
> com.amazonaws:aws-java-sdk-keyspaces 1.12.710 -> 1.12.715
> com.azure:azure-sdk-bom 1.2.21 -> 1.2.23
> com.google.cloud:libraries-bom ... 26.37.0 -> 26.38.0
> net.bytebuddy:byte-buddy .. 1.14.12 -> 1.14.14
> org.checkerframework:checker-qual ... 3.37.0 -> 3.43.0
> org.eclipse.jdt:ecj . 3.33.0 -> 3.37.0
> com.microsoft.azure:msal4j .. 1.14.3 -> 1.15.0
> com.google.guava:guava .. 33.1.0-jre -> 33.2.0-jre
> com.ibm.icu:icu4j ... 74.2 -> 75.1
> org.opensaml:opensaml-* 4.3.1 -> 4.3.2
> org.apache.sshd:sshd-* ... 2.12.0 -> 2.12.1
> com.nimbusds:oauth2-oidc-sdk ... 9.43.3 -> 9.43.4
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-13144) Improve dependency-update detection configuration and bump various detected dependency versions
[
https://issues.apache.org/jira/browse/NIFI-13144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843499#comment-17843499
]
Joe Witt commented on NIFI-13144:
-
Changed and full clean build w/contrib is legit (haven't run full CI suite yet)
{noformat}
com.puppycrawl.tools:checkstyle 10.15.0 -> 10.16.0
software.amazon.awssdk:xray 2.25.40 -> 2.25.45
com.amazonaws:aws-java-sdk-keyspaces 1.12.710 -> 1.12.715
com.azure:azure-sdk-bom 1.2.21 -> 1.2.23
com.google.cloud:libraries-bom 26.37.0 -> 26.38.0
net.bytebuddy:byte-buddy 1.14.12 -> 1.14.14
org.checkerframework:checker-qual 3.37.0 -> 3.43.0
org.eclipse.jdt:ecj 3.33.0 -> 3.37.0
com.microsoft.azure:msal4j 1.14.3 -> 1.15.0
com.google.guava:guava 33.1.0-jre -> 33.2.0-jre
com.ibm.icu:icu4j 74.2 -> 75.1
org.opensaml:opensaml-* 4.3.1 -> 4.3.2
org.apache.sshd:sshd-* 2.12.0 -> 2.12.1
com.nimbusds:oauth2-oidc-sdk 9.43.3 -> 9.43.4
excel-streaming-reader 4.2.1 -> 4.3.1
amqp-client 5.20.0 5.21.0
json-schema-validator 1.3.2 1.4.0
Saxon-HE 12.3 12.4
lucene 8.11.2 8.11.3
commons-compiler 3.1.10 3.1.12
dropbox.client.version 5.4.4 5.4.6
subethasmtp 7.0.1 7.0.2
docker-java-api 3.3.4 3.3.6
google-api-services-drive v3-rev20230520-2.0.0 v3-rev20240327-2.0.0
protobuf-java 3.25.1 3.25.3
hazelcast 5.3.5 5.3.7
jackson-datatype-protobuf 0.9.14 0.9.15
kusto-* 5.0.3 5.0.5
mysql-connector-j 8.3.0 8.4.0
docker-compose-junit-jupiter 2.0.0 2.3.0
bolt-socket-mode 1.37.0 1.39.0
wire-schema-jvm 4.9.3 4.9.9
mysql-binlog-connector-java 0.29.0 0.29.2
jjwt 0.12.3 0.12.5
reactor-core 3.4.34 3.4.37
reactor-test 3.5.14 3.5.16
jakarta.activation-api 2.0.1 (and 2.1.2) to 2.1.3 **need to verify this
builds/tests pass
jakarta.mail-api 2.0.1 (and 2.1.2) to 2.1.3
datafaker 2.0.2 to 2.2.2
jna and jna-platform 5.13.0 5.14.0
activemq-* 6.1.1 6.1.2
camel-salesforce 3.14.9 3.14.10
commons-csv 1.10.0 1.11.0
hbase.version 2.5.5-hadoop3 2.5.8-hadoop3
httpasyncclient 4.1.4 4.1.5
httpcore-nio 4.4.12 4.4.16
iotdb 1.3.0 1.3.1
mina-core 2.1.6 2.1.8
gremlin-* 3.7.1 3.7.2
clojure 1.11.2 1.11.3
angus-mail 2.0.2 2.0.3
jgit* 6.8.0.202311291450-r 6.9.0.202403050737-r
javaassist 3.29.2-GA 3.30.2-GA
jline 3.25.1 3.26.1
mariadb-java-client 3.3.0 3.3.3
mongodb-driver-sync 4.11.1 4.11.2
neo4j-java-driver 4.4.12 4.4.16
postgresql 4.7.2 4.7.3
spring-data-redis 2.7.15 2.7.18
spring-integration-mail 6.2.1 6.2.4
spring-vault-core 3.1.0 3.1.1
xmlunit-core 2.9.1 2.10.0
xmlunit-matchers 2.9.1 2.10.0
amazon-kinesis-client 2.5.7 2.5.8
reactor-netty-http 1.0.39 1.0.44
ant 1.10.13 1.10.14
hamcrest-core and hamcrest-all 1.3 moved to just hamcrest 2.2
{noformat}
> Improve dependency-update detection configuration and bump various detected
> dependency versions
> ---
>
> Key: NIFI-13144
> URL: https://issues.apache.org/jira/browse/NIFI-13144
> Project: Apache NiFi
> Issue Type: Task
>Reporter: Joe Witt
>Assignee: Joe Witt
>Priority: Major
>
> {noformat}
> com.puppycrawl.tools:checkstyle ... 10.15.0 -> 10.16.0
> software.amazon.awssdk:xray ... 2.25.40 -> 2.25.45
> com.amazonaws:aws-java-sdk-keyspaces 1.12.710 -> 1.12.715
> com.azure:azure-sdk-bom 1.2.21 -> 1.2.23
> com.google.cloud:libraries-bom ... 26.37.0 -> 26.38.0
> net.bytebuddy:byte-buddy .. 1.14.12 -> 1.14.14
> org.checkerframework:checker-qual ... 3.37.0 -> 3.43.0
> org.eclipse.jdt:ecj . 3.33.0 -> 3.37.0
> com.microsoft.azure:msal4j .. 1.14.3 -> 1.15.0
> com.google.guava:guava .. 33.1.0-jre -> 33.2.0-jre
> com.ibm.icu:icu4j ... 74.2 -> 75.1
> org.opensaml:opensaml-* 4.3.1 -> 4.3.2
> org.apache.sshd:sshd-* ... 2.12.0 -> 2.12.1
> com.nimbusds:oauth2-oidc-sdk ... 9.43.3 -> 9.43.4
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-13144) Improve dependency-update detection configuration and bump various detected dependency versions
[
https://issues.apache.org/jira/browse/NIFI-13144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843492#comment-17843492
]
Joe Witt commented on NIFI-13144:
-
Requires more effort as version change results in compile or test failures
{noformat}
questdb 7.3.7 7.3.10 (there is a 7.4.2)
{noformat}
Needs follow up as major change or has bitten in the past on version change:
{noformat}
org.jetbrains: annotations 13.0 to 24.1.0
springframework-security-kerberos 1.0 to 2.0
elasticsearch 7.13.4 to 7.17.21 (although major release 8.x already available)
lucene 8.11.3 to 9.10.0
okhttp-digest 2.7 to 3.1.0
oauth2-oidc-sdk 9.43.4 to 11.10.1
protobuf 3.25.3 to 4.26.1
couchbase core/clien 1.7x and 2.7x to 2.6x and 3.6x
camel-salesforce 3.14.10 to 3.22.1
de.siegmar fastcsv 2.2.2 to 3.1.0
reactor-core and test from 3.4x to 3.6.5
unboundid-ldapsdk 6x to 7x but only in test scope
hazelcast 5.3.7 to 5.4.0
dropbox-core-sdk 5.x to 7x
{noformat}
> Improve dependency-update detection configuration and bump various detected
> dependency versions
> ---
>
> Key: NIFI-13144
> URL: https://issues.apache.org/jira/browse/NIFI-13144
> Project: Apache NiFi
> Issue Type: Task
>Reporter: Joe Witt
>Assignee: Joe Witt
>Priority: Major
>
> {noformat}
> com.puppycrawl.tools:checkstyle ... 10.15.0 -> 10.16.0
> software.amazon.awssdk:xray ... 2.25.40 -> 2.25.45
> com.amazonaws:aws-java-sdk-keyspaces 1.12.710 -> 1.12.715
> com.azure:azure-sdk-bom 1.2.21 -> 1.2.23
> com.google.cloud:libraries-bom ... 26.37.0 -> 26.38.0
> net.bytebuddy:byte-buddy .. 1.14.12 -> 1.14.14
> org.checkerframework:checker-qual ... 3.37.0 -> 3.43.0
> org.eclipse.jdt:ecj . 3.33.0 -> 3.37.0
> com.microsoft.azure:msal4j .. 1.14.3 -> 1.15.0
> com.google.guava:guava .. 33.1.0-jre -> 33.2.0-jre
> com.ibm.icu:icu4j ... 74.2 -> 75.1
> org.opensaml:opensaml-* 4.3.1 -> 4.3.2
> org.apache.sshd:sshd-* ... 2.12.0 -> 2.12.1
> com.nimbusds:oauth2-oidc-sdk ... 9.43.3 -> 9.43.4
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-13144) Improve dependency-update detection configuration and bump various detected dependency versions
[
https://issues.apache.org/jira/browse/NIFI-13144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843480#comment-17843480
]
Joe Witt commented on NIFI-13144:
-
With the improved dependency tracking setup with maven also found the following
{noformat}
excel-streaming-reader 4.2.1 -> 4.3.1
amqp-client 5.20.0 5.21.0
json-schema-validator 1.3.2 1.4.0
Saxon-HE 12.3 12.4
lucene 8.11.2 8.11.3
commons-compiler 3.1.10 3.1.12
dropbox.client.version 5.4.4 5.4.6
subethasmtp 7.0.1 7.0.2
docker-java-api 3.3.4 3.3.6
google-api-services-drive v3-rev20230520-2.0.0 v3-rev20240327-2.0.0
protobuf-java 3.25.1 3.25.3
hazelcast 5.3.5 5.3.7
jackson-datatype-protobuf 0.9.14 0.9.15
kusto-* 5.0.3 5.0.5
mysql-connector-j 8.3.0 8.5.0
docker-compose-junit-jupiter 2.0.0 2.3.0
bolt-socket-mode 1.37.0 1.39.0
wire-schema-jvm 4.9.3 4.9.9
mysql-binlog-connector-java 0.29.0 0.29.2
jjwt 0.12.3 0.12.5
reactor-core 3.4.34 3.4.37
reactor-test 3.5.14 3.5.16
jakarta.activation-api 2.0.1 (and 2.1.2) to 2.1.3 **need to verify this
builds/tests pass
jakarta.mail-api 2.0.1 (and 2.1.2) to 2.1.3
datafaker 2.0.2 to 2.2.2
jna and jna-platform 5.13.0 5.14.0
activemq-* 6.1.1 6.1.2
camel-salesforce 3.14.9 3.14.10
commons-csv 1.10.0 1.11.0
hbase.version 2.5.5-hadoop3 2.5.8-hadoop3
httpasyncclient 4.1.4 4.1.5
httpcore-nio 4.4.12 4.4.16
iotdb 1.3.0 1.3.1
mina-core 2.1.6 2.1.8
gremlin-* 3.7.1 3.7.2
clojure 1.11.2 1.11.3
angus-mail 2.0.2 2.0.3
jgit* 6.8.0.202311291450-r 6.9.0.202403050737-r
javaassist 3.29.2-GA 3.30.2-GA
jline 3.25.1 3.26.1
mariadb-java-client 3.3.0 3.3.3
mongodb-driver-sync 4.11.1 4.11.2
neo4j-java-driver 4.4.12 4.4.16
postgresql 4.7.2 4.7.3
questdb 7.3.7 7.3.10
spring-data-redis 2.7.15 2.7.18
spring-integration-mail 6.2.1 6.2.4
spring-vault-core 3.1.0 3.1.1
xmlunit-core 2.9.1 2.10.0
xmlunit-matchers 2.9.1 2.10.0
amazon-kinesis-client 2.5.7 2.5.8
{noformat}
> Improve dependency-update detection configuration and bump various detected
> dependency versions
> ---
>
> Key: NIFI-13144
> URL: https://issues.apache.org/jira/browse/NIFI-13144
> Project: Apache NiFi
> Issue Type: Task
>Reporter: Joe Witt
>Assignee: Joe Witt
>Priority: Major
>
> {noformat}
> com.puppycrawl.tools:checkstyle ... 10.15.0 -> 10.16.0
> software.amazon.awssdk:xray ... 2.25.40 -> 2.25.45
> com.amazonaws:aws-java-sdk-keyspaces 1.12.710 -> 1.12.715
> com.azure:azure-sdk-bom 1.2.21 -> 1.2.23
> com.google.cloud:libraries-bom ... 26.37.0 -> 26.38.0
> net.bytebuddy:byte-buddy .. 1.14.12 -> 1.14.14
> org.checkerframework:checker-qual ... 3.37.0 -> 3.43.0
> org.eclipse.jdt:ecj . 3.33.0 -> 3.37.0
> com.microsoft.azure:msal4j .. 1.14.3 -> 1.15.0
> com.google.guava:guava .. 33.1.0-jre -> 33.2.0-jre
> com.ibm.icu:icu4j ... 74.2 -> 75.1
> org.opensaml:opensaml-* 4.3.1 -> 4.3.2
> org.apache.sshd:sshd-* ... 2.12.0 -> 2.12.1
> com.nimbusds:oauth2-oidc-sdk ... 9.43.3 -> 9.43.4
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-13144) Improve dependency-update detection configuration and bump various detected dependency versions
[
https://issues.apache.org/jira/browse/NIFI-13144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843476#comment-17843476
]
Joe Witt commented on NIFI-13144:
-
This command run at the root of NiFi now produces a very helpful report.
{noformat}
mvn -T 1.0C versions:dependency-updates-aggregate-report -DonlyUpgradable=true
{noformat}
> Improve dependency-update detection configuration and bump various detected
> dependency versions
> ---
>
> Key: NIFI-13144
> URL: https://issues.apache.org/jira/browse/NIFI-13144
> Project: Apache NiFi
> Issue Type: Task
>Reporter: Joe Witt
>Assignee: Joe Witt
>Priority: Major
>
> {noformat}
> com.puppycrawl.tools:checkstyle ... 10.15.0 -> 10.16.0
> software.amazon.awssdk:xray ... 2.25.40 -> 2.25.45
> com.amazonaws:aws-java-sdk-keyspaces 1.12.710 -> 1.12.715
> com.azure:azure-sdk-bom 1.2.21 -> 1.2.23
> com.google.cloud:libraries-bom ... 26.37.0 -> 26.38.0
> net.bytebuddy:byte-buddy .. 1.14.12 -> 1.14.14
> org.checkerframework:checker-qual ... 3.37.0 -> 3.43.0
> org.eclipse.jdt:ecj . 3.33.0 -> 3.37.0
> com.microsoft.azure:msal4j .. 1.14.3 -> 1.15.0
> com.google.guava:guava .. 33.1.0-jre -> 33.2.0-jre
> com.ibm.icu:icu4j ... 74.2 -> 75.1
> org.opensaml:opensaml-* 4.3.1 -> 4.3.2
> org.apache.sshd:sshd-* ... 2.12.0 -> 2.12.1
> com.nimbusds:oauth2-oidc-sdk ... 9.43.3 -> 9.43.4
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-13144) Improve dependency-update detection configuration and bump various detected dependency versions
[
https://issues.apache.org/jira/browse/NIFI-13144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843474#comment-17843474
]
Joe Witt commented on NIFI-13144:
-
The couchbase components seem very out of date. We should consider
deprecation/removal.
> Improve dependency-update detection configuration and bump various detected
> dependency versions
> ---
>
> Key: NIFI-13144
> URL: https://issues.apache.org/jira/browse/NIFI-13144
> Project: Apache NiFi
> Issue Type: Task
>Reporter: Joe Witt
>Assignee: Joe Witt
>Priority: Major
>
> {noformat}
> com.puppycrawl.tools:checkstyle ... 10.15.0 -> 10.16.0
> software.amazon.awssdk:xray ... 2.25.40 -> 2.25.45
> com.amazonaws:aws-java-sdk-keyspaces 1.12.710 -> 1.12.715
> com.azure:azure-sdk-bom 1.2.21 -> 1.2.23
> com.google.cloud:libraries-bom ... 26.37.0 -> 26.38.0
> net.bytebuddy:byte-buddy .. 1.14.12 -> 1.14.14
> org.checkerframework:checker-qual ... 3.37.0 -> 3.43.0
> org.eclipse.jdt:ecj . 3.33.0 -> 3.37.0
> com.microsoft.azure:msal4j .. 1.14.3 -> 1.15.0
> com.google.guava:guava .. 33.1.0-jre -> 33.2.0-jre
> com.ibm.icu:icu4j ... 74.2 -> 75.1
> org.opensaml:opensaml-* 4.3.1 -> 4.3.2
> org.apache.sshd:sshd-* ... 2.12.0 -> 2.12.1
> com.nimbusds:oauth2-oidc-sdk ... 9.43.3 -> 9.43.4
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-13143) [BUG] EL/Parameter tooltip missing styles
[ https://issues.apache.org/jira/browse/NIFI-13143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Aslan updated NIFI-13143: --- Status: Patch Available (was: In Progress) > [BUG] EL/Parameter tooltip missing styles > - > > Key: NIFI-13143 > URL: https://issues.apache.org/jira/browse/NIFI-13143 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan >Assignee: Scott Aslan >Priority: Major > Attachments: Screenshot 2024-05-03 at 7.18.24 PM.png, Screenshot > 2024-05-03 at 7.18.33 PM.png > > > The section header is missing the darker bold font. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13143) [BUG] EL/Parameter tooltip missing styles
[ https://issues.apache.org/jira/browse/NIFI-13143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843470#comment-17843470 ] Scott Aslan commented on NIFI-13143: Solved in https://github.com/apache/nifi/pull/8745 > [BUG] EL/Parameter tooltip missing styles > - > > Key: NIFI-13143 > URL: https://issues.apache.org/jira/browse/NIFI-13143 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan >Assignee: Scott Aslan >Priority: Major > Attachments: Screenshot 2024-05-03 at 7.18.24 PM.png, Screenshot > 2024-05-03 at 7.18.33 PM.png > > > The section header is missing the darker bold font. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-13143) [BUG] EL/Parameter tooltip missing styles
[ https://issues.apache.org/jira/browse/NIFI-13143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Aslan reassigned NIFI-13143: -- Assignee: Scott Aslan > [BUG] EL/Parameter tooltip missing styles > - > > Key: NIFI-13143 > URL: https://issues.apache.org/jira/browse/NIFI-13143 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan >Assignee: Scott Aslan >Priority: Major > Attachments: Screenshot 2024-05-03 at 7.18.24 PM.png, Screenshot > 2024-05-03 at 7.18.33 PM.png > > > The section header is missing the darker bold font. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-8134 allow unescapeJson Record Path function to recursively convert Maps to Records [nifi]
joewitt commented on PR #7745: URL: https://github.com/apache/nifi/pull/7745#issuecomment-2094286612 Thanks for rebasing @ChrisSamo632 ! -- 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
Re: [PR] NIFI-12255 refactor PutElasticsearchRecord and PutElasticsearchJson relationships to be more consistent with other processors [nifi]
joewitt commented on PR #7940: URL: https://github.com/apache/nifi/pull/7940#issuecomment-2094285531 @ChrisSamo632 Thanks for rebasing and also leveraging migrate properties! -- 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-13144) Improve dependency-update detection configuration and bump various detected dependency versions
[
https://issues.apache.org/jira/browse/NIFI-13144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843467#comment-17843467
]
Joe Witt commented on NIFI-13144:
-
The above items are updated and appear safe to do as well as the full clean
build with contrib plus integration tests and system tests work.
There are a range of other dependency bumps that will require specific action
and potentially code changes as they are major and/or confirmed to break the
build. Will list these out as well here though perhaps it makes more sense to
have an EPIC for them or specific JIRAs.
> Improve dependency-update detection configuration and bump various detected
> dependency versions
> ---
>
> Key: NIFI-13144
> URL: https://issues.apache.org/jira/browse/NIFI-13144
> Project: Apache NiFi
> Issue Type: Task
>Reporter: Joe Witt
>Assignee: Joe Witt
>Priority: Major
>
> {noformat}
> com.puppycrawl.tools:checkstyle ... 10.15.0 -> 10.16.0
> software.amazon.awssdk:xray ... 2.25.40 -> 2.25.45
> com.amazonaws:aws-java-sdk-keyspaces 1.12.710 -> 1.12.715
> com.azure:azure-sdk-bom 1.2.21 -> 1.2.23
> com.google.cloud:libraries-bom ... 26.37.0 -> 26.38.0
> net.bytebuddy:byte-buddy .. 1.14.12 -> 1.14.14
> org.checkerframework:checker-qual ... 3.37.0 -> 3.43.0
> org.eclipse.jdt:ecj . 3.33.0 -> 3.37.0
> com.microsoft.azure:msal4j .. 1.14.3 -> 1.15.0
> com.google.guava:guava .. 33.1.0-jre -> 33.2.0-jre
> com.ibm.icu:icu4j ... 74.2 -> 75.1
> org.opensaml:opensaml-* 4.3.1 -> 4.3.2
> org.apache.sshd:sshd-* ... 2.12.0 -> 2.12.1
> com.nimbusds:oauth2-oidc-sdk ... 9.43.3 -> 9.43.4
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-13144) Improve dependency-update detection configuration and bump various detected dependency versions
[ https://issues.apache.org/jira/browse/NIFI-13144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Witt updated NIFI-13144: Summary: Improve dependency-update detection configuration and bump various detected dependency versions (was: Update various dependencies (cloud providers, etc..)) > Improve dependency-update detection configuration and bump various detected > dependency versions > --- > > Key: NIFI-13144 > URL: https://issues.apache.org/jira/browse/NIFI-13144 > Project: Apache NiFi > Issue Type: Task >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > > com.puppycrawl.tools:checkstyle ... 10.15.0 -> 10.16.0 > software.amazon.awssdk:xray ... 2.25.40 -> 2.25.45 > com.amazonaws:aws-java-sdk-keyspaces 1.12.710 -> 1.12.715 > com.azure:azure-core 1.46.0 -> 1.49.0 > com.google.api:api-common ... 2.18.0 -> 2.31.0 > io.grpc:grpc-all 1.58.0 -> 1.63.0 > [INFO] com.azure:azure-core-http-okhttp .. 1.11.18 -> > 1.11.21 > [INFO] com.azure:azure-security-keyvault-keys 4.8.0 -> > 4.8.3 > [INFO] com.azure:azure-security-keyvault-secrets . 4.8.0 -> > 4.8.2 > [INFO] com.google.cloud:google-cloud-kms ... 2.31.0 -> > 2.45.0 > [INFO] net.bytebuddy:byte-buddy .. 1.14.12 -> > 1.14.14 > [INFO] org.checkerframework:checker-qual ... 3.37.0 -> > 3.43.0 > [INFO] org.eclipse.jdt:ecj . 3.33.0 -> > 3.37.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13144) Improve dependency-update detection configuration and bump various detected dependency versions
[
https://issues.apache.org/jira/browse/NIFI-13144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Witt updated NIFI-13144:
Description:
{noformat}
com.puppycrawl.tools:checkstyle ... 10.15.0 -> 10.16.0
software.amazon.awssdk:xray ... 2.25.40 -> 2.25.45
com.amazonaws:aws-java-sdk-keyspaces 1.12.710 -> 1.12.715
com.azure:azure-sdk-bom 1.2.21 -> 1.2.23
com.google.cloud:libraries-bom ... 26.37.0 -> 26.38.0
net.bytebuddy:byte-buddy .. 1.14.12 -> 1.14.14
org.checkerframework:checker-qual ... 3.37.0 -> 3.43.0
org.eclipse.jdt:ecj . 3.33.0 -> 3.37.0
com.microsoft.azure:msal4j .. 1.14.3 -> 1.15.0
com.google.guava:guava .. 33.1.0-jre -> 33.2.0-jre
com.ibm.icu:icu4j ... 74.2 -> 75.1
org.opensaml:opensaml-* 4.3.1 -> 4.3.2
org.apache.sshd:sshd-* ... 2.12.0 -> 2.12.1
com.nimbusds:oauth2-oidc-sdk ... 9.43.3 -> 9.43.4
{noformat}
was:
com.puppycrawl.tools:checkstyle ... 10.15.0 -> 10.16.0
software.amazon.awssdk:xray ... 2.25.40 -> 2.25.45
com.amazonaws:aws-java-sdk-keyspaces 1.12.710 -> 1.12.715
com.azure:azure-core 1.46.0 -> 1.49.0
com.google.api:api-common ... 2.18.0 -> 2.31.0
io.grpc:grpc-all 1.58.0 -> 1.63.0
[INFO] com.azure:azure-core-http-okhttp .. 1.11.18 -> 1.11.21
[INFO] com.azure:azure-security-keyvault-keys 4.8.0 -> 4.8.3
[INFO] com.azure:azure-security-keyvault-secrets . 4.8.0 -> 4.8.2
[INFO] com.google.cloud:google-cloud-kms ... 2.31.0 -> 2.45.0
[INFO] net.bytebuddy:byte-buddy .. 1.14.12 -> 1.14.14
[INFO] org.checkerframework:checker-qual ... 3.37.0 -> 3.43.0
[INFO] org.eclipse.jdt:ecj . 3.33.0 -> 3.37.0
> Improve dependency-update detection configuration and bump various detected
> dependency versions
> ---
>
> Key: NIFI-13144
> URL: https://issues.apache.org/jira/browse/NIFI-13144
> Project: Apache NiFi
> Issue Type: Task
>Reporter: Joe Witt
>Assignee: Joe Witt
>Priority: Major
>
> {noformat}
> com.puppycrawl.tools:checkstyle ... 10.15.0 -> 10.16.0
> software.amazon.awssdk:xray ... 2.25.40 -> 2.25.45
> com.amazonaws:aws-java-sdk-keyspaces 1.12.710 -> 1.12.715
> com.azure:azure-sdk-bom 1.2.21 -> 1.2.23
> com.google.cloud:libraries-bom ... 26.37.0 -> 26.38.0
> net.bytebuddy:byte-buddy .. 1.14.12 -> 1.14.14
> org.checkerframework:checker-qual ... 3.37.0 -> 3.43.0
> org.eclipse.jdt:ecj . 3.33.0 -> 3.37.0
> com.microsoft.azure:msal4j .. 1.14.3 -> 1.15.0
> com.google.guava:guava .. 33.1.0-jre -> 33.2.0-jre
> com.ibm.icu:icu4j ... 74.2 -> 75.1
> org.opensaml:opensaml-* 4.3.1 -> 4.3.2
> org.apache.sshd:sshd-* ... 2.12.0 -> 2.12.1
> com.nimbusds:oauth2-oidc-sdk ... 9.43.3 -> 9.43.4
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-12802) Update to minimum node LTS version needed to support new UI
[ https://issues.apache.org/jira/browse/NIFI-12802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843446#comment-17843446 ] ASF subversion and git services commented on NIFI-12802: Commit d5bfec7d7f35c42cc768a1ea002755d16a428c35 in nifi's branch refs/heads/main from Rob Fellows [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=d5bfec7d7f ] [NIFI-12802] - Update to use node 22 (#8744) This closes #8744 > Update to minimum node LTS version needed to support new UI > --- > > Key: NIFI-12802 > URL: https://issues.apache.org/jira/browse/NIFI-12802 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan >Assignee: Rob Fellows >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > https://github.com/apache/nifi/pull/8410/files#r1491162482 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [NIFI-12802] - Update to use node 22 [nifi]
scottyaslan merged PR #8744: URL: https://github.com/apache/nifi/pull/8744 -- 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-13143) [BUG] EL/Parameter tooltip missing styles
[ https://issues.apache.org/jira/browse/NIFI-13143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman reassigned NIFI-13143: -- Assignee: (was: Matt Gilman) > [BUG] EL/Parameter tooltip missing styles > - > > Key: NIFI-13143 > URL: https://issues.apache.org/jira/browse/NIFI-13143 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan >Priority: Major > Attachments: Screenshot 2024-05-03 at 7.18.24 PM.png, Screenshot > 2024-05-03 at 7.18.33 PM.png > > > The section header is missing the darker bold font. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-13141) Some canvas actions reset when polling occurs
[ https://issues.apache.org/jira/browse/NIFI-13141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman reassigned NIFI-13141: -- Assignee: Matt Gilman > Some canvas actions reset when polling occurs > - > > Key: NIFI-13141 > URL: https://issues.apache.org/jira/browse/NIFI-13141 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > > If polling occurs while the user is moving a bend point, moving a connection > label, or resizing a label and the canvas polls the positions will be reset. > If the user is performing one of these actions we should consider not > applying these values which would reset the positions. We may however need to > honor the existing behavior if the component revision has changed by another > user. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-13143) [BUG] EL/Parameter tooltip missing styles
[ https://issues.apache.org/jira/browse/NIFI-13143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman reassigned NIFI-13143: -- Assignee: Matt Gilman > [BUG] EL/Parameter tooltip missing styles > - > > Key: NIFI-13143 > URL: https://issues.apache.org/jira/browse/NIFI-13143 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan >Assignee: Matt Gilman >Priority: Major > Attachments: Screenshot 2024-05-03 at 7.18.24 PM.png, Screenshot > 2024-05-03 at 7.18.33 PM.png > > > The section header is missing the darker bold font. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12255 refactor PutElasticsearchRecord and PutElasticsearchJson relationships to be more consistent with other processors [nifi]
ChrisSamo632 commented on PR #7940: URL: https://github.com/apache/nifi/pull/7940#issuecomment-2094061873 Rebased against latest `main` to refactor changed into new `nifi-extension-bundles` module -- 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
Re: [PR] NIFI-8134 allow unescapeJson Record Path function to recursively convert Maps to Records [nifi]
ChrisSamo632 commented on PR #7745: URL: https://github.com/apache/nifi/pull/7745#issuecomment-2094055528 Rebased against latest `main` to refactor changes into new `nifi-extension-bundles` module -- 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
