[jira] [Updated] (NIFI-13208) Increase member visibility in AbstractHadoopConnectionPool
[ https://issues.apache.org/jira/browse/NIFI-13208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lehel Boér updated NIFI-13208: -- Status: Patch Available (was: In Progress) > Increase member visibility in AbstractHadoopConnectionPool > -- > > Key: NIFI-13208 > URL: https://issues.apache.org/jira/browse/NIFI-13208 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Lehel Boér >Assignee: Lehel Boér >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > HADOOP_CONFIGURATION_RESOURCES access modifier should be changed to public in > order to used in any inherited class. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] NIFI-13208: Increase member visibility of HadoopDBCPConnectionPool [nifi]
Lehel44 opened a new pull request, #8805: URL: https://github.com/apache/nifi/pull/8805 # 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 21 ### UI Contributions - [ ] NiFi is modernizing its UI. Any contributions that update the [current UI](https://github.com/apache/nifi/tree/main/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-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] [Created] (NIFI-13208) Increase member visibility in AbstractHadoopConnectionPool
Lehel Boér created NIFI-13208: - Summary: Increase member visibility in AbstractHadoopConnectionPool Key: NIFI-13208 URL: https://issues.apache.org/jira/browse/NIFI-13208 Project: Apache NiFi Issue Type: Improvement Reporter: Lehel Boér Assignee: Lehel Boér HADOOP_CONFIGURATION_RESOURCES access modifier should be changed to public in order to used in any inherited class. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13207) Page header padding/spacing
[ https://issues.apache.org/jira/browse/NIFI-13207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Aslan updated NIFI-13207: --- Status: Patch Available (was: In Progress) > Page header padding/spacing > --- > > Key: NIFI-13207 > URL: https://issues.apache.org/jira/browse/NIFI-13207 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan >Assignee: Scott Aslan >Priority: Major > Attachments: Screenshot 2024-05-09 at 8.04.12 PM.png, Screenshot > 2024-05-09 at 8.04.20 PM.png, Screenshot 2024-05-09 at 8.04.30 PM.png, > Screenshot 2024-05-09 at 8.04.40 PM.png, Screenshot 2024-05-09 at 8.04.50 > PM.png, Screenshot 2024-05-09 at 8.05.02 PM.png, Screenshot 2024-05-09 at > 8.05.10 PM.png, Screenshot 2024-05-09 at 8.05.26 PM.png, Screenshot > 2024-05-09 at 8.05.33 PM.png > > Time Spent: 10m > Remaining Estimate: 0h > > The various page header titles have various spacing padding: -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] [NIFI-13207] page headers and refresh containers are consistently pos… [nifi]
scottyaslan opened a new pull request, #8804: URL: https://github.com/apache/nifi/pull/8804 …itioned between pages  -- 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-12983: Qdrant vector store support [nifi]
Anush008 commented on PR #8590: URL: https://github.com/apache/nifi/pull/8590#issuecomment-2103654246 > I'm curious what the role of langchain there is. Does that get used as the official qdrant python API? Langchain provides a common abstraction over several vector databases. Currently, all the NiFi vector database extensions use it. -- 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]
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}
*UPDATE (May 9, 2024)* -
[ca3d6df|https://github.com/apache/nifi-minifi-cpp/pull/1775/commits/ca3d6df318162e2ee9d3e76e173d9f83e17d3010]:
{*}Enabled MiNiFi C++ extensions GPS and COAP{*}. I added conan recipe for
libcoap keeping the windows cmake patches for minifi. Since the original
libcoap conan recipe's conanfile.py on conan-center-index was tailored for
CMake building libcoap versions > 4.3.0, I modified the recipe, so we can build
libcoap 4.2.1, which didnt have CMake support yet and thus, I updated that
conanfile.py to run 'autogen.sh' to create the configure script, I passed the
configure args to the configure script and then I used conan's Autotools() to
run the configure script and then ran the generated make file to build libcoap
4.2.1. I updated BundledLibCoAP to account for the
[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]
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}
*UPDATE (May 9, 2024)* -
[ca3d6df|https://github.com/apache/nifi-minifi-cpp/pull/1775/commits/ca3d6df318162e2ee9d3e76e173d9f83e17d3010]:
{*}Enabled MiNiFi C++ extensions GPS and COAP{*}. I added conan recipe for
libcoap keeping the windows cmake patches for minifi. Since the original
libcoap conan recipe's conanfile.py on conan-center-index was tailored for
CMake building libcoap versions > 4.3.0, I modified the recipe, so we can build
libcoap 4.2.1, which didnt have CMake support yet and thus, I updated that
conanfile.py to run 'autogen.sh' to create the configure script, I passed the
configure args to the configure script and then I used conan's Autotools() to
run the configure script and then ran the generated make file to build libcoap
4.2.1. I updated BundledLibCoAP to account for the
[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]
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}*{color:#172b4d}(UPDATE (May 8, 2024) -{color}*{color}
*{color:#172b4d}{color}[93fe5d1|https://github.com/apache/nifi-minifi-cpp/pull/1775/commits/93fe5d1a712834b422d5c8e45829a3641852ca7a]:*
{color:#172b4d}*Enabled NANOFI* lib and binary executable, {*}Enabled MiNiFi
C++ extensions SYSTEMD, PROCFS, LIBARCHIVE and XY_UTILS (LZMA){*}. I added
conan recipe for liblzma (xy_utils) and libarchive keeping the patches for
minifi. One area I found an issue with was integrating openssl conan package
with libarchive conan package and libarchive complained about not being able to
find openssl::openssl target. I did try to solve the issue by updating the
libarchive conan recipe, but wasn't able to solve that openssl integration
issue. I think the problem comes from libarchive CMakeLists.txt
[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]
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}*{color:#172b4d}(UPDATE (May 8, 2024) -{color}
[93fe5d1|https://github.com/apache/nifi-minifi-cpp/pull/1775/commits/93fe5d1a712834b422d5c8e45829a3641852ca7a]:*
{color:#172b4d}*Enabled NANOFI* lib and binary executable, {*}Enabled MiNiFi
C++ extensions SYSTEMD, PROCFS, LIBARCHIVE and XY_UTILS (LZMA){*}. I added
conan recipe for liblzma (xy_utils) and libarchive keeping the patches for
minifi. One area I found an issue with was integrating openssl conan package
with libarchive conan package and libarchive complained about not being able to
find openssl::openssl target. I did try to solve the issue by updating the
libarchive conan recipe, but wasn't able to solve that openssl integration
issue. I think the problem comes from libarchive CMakeLists.txt and its
integration with conan
[PR] NIFI-13172 deprecated nifi kafka connect components [nifi]
joewitt opened a new pull request, #8803: URL: https://github.com/apache/nifi/pull/8803 # Summary [NIFI-13172](https://issues.apache.org/jira/browse/NIFI-13172) # 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-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-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] [Updated] (NIFI-13172) Deprecate nifi-externals/kafka-connect component in 1.x
[ https://issues.apache.org/jira/browse/NIFI-13172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Witt updated NIFI-13172: Status: Patch Available (was: Open) > Deprecate nifi-externals/kafka-connect component in 1.x > --- > > Key: NIFI-13172 > URL: https://issues.apache.org/jira/browse/NIFI-13172 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > See NIFI-13171 description for context. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13207) Page header padding/spacing
Scott Aslan created NIFI-13207: -- Summary: Page header padding/spacing Key: NIFI-13207 URL: https://issues.apache.org/jira/browse/NIFI-13207 Project: Apache NiFi Issue Type: Sub-task Reporter: Scott Aslan Assignee: Scott Aslan Attachments: Screenshot 2024-05-09 at 8.04.12 PM.png, Screenshot 2024-05-09 at 8.04.20 PM.png, Screenshot 2024-05-09 at 8.04.30 PM.png, Screenshot 2024-05-09 at 8.04.40 PM.png, Screenshot 2024-05-09 at 8.04.50 PM.png, Screenshot 2024-05-09 at 8.05.02 PM.png, Screenshot 2024-05-09 at 8.05.10 PM.png, Screenshot 2024-05-09 at 8.05.26 PM.png, Screenshot 2024-05-09 at 8.05.33 PM.png The various page header titles have various spacing padding: -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13153) [BUG] processors with long names cause overflow issues in dialogs
[ https://issues.apache.org/jira/browse/NIFI-13153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Aslan updated NIFI-13153: --- Status: Patch Available (was: In Progress) > [BUG] processors with long names cause overflow issues in dialogs > - > > Key: NIFI-13153 > URL: https://issues.apache.org/jira/browse/NIFI-13153 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan >Assignee: Scott Aslan >Priority: Major > Attachments: Screenshot 2024-05-06 at 1.46.25 PM.png, Screenshot > 2024-05-06 at 1.46.38 PM.png > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] [NIFI-13153] use ellipsis for long component names in dialogs [nifi]
scottyaslan opened a new pull request, #8802: URL: https://github.com/apache/nifi/pull/8802 https://github.com/apache/nifi/assets/6797571/c3836be4-864f-4305-8177-6a06087c735f;> https://github.com/apache/nifi/assets/6797571/0fbd2cf4-e280-44f6-8612-309f96d034e1;> https://github.com/apache/nifi/assets/6797571/b6964915-549c-40f4-ab6c-2a4b11a67923;> https://github.com/apache/nifi/assets/6797571/474d7109-034e-4919-b4b0-7e4f9d8ece70;> -- 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-13153) [BUG] processors with long names cause overflow issues in dialogs
[ https://issues.apache.org/jira/browse/NIFI-13153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Aslan reassigned NIFI-13153: -- Assignee: Scott Aslan > [BUG] processors with long names cause overflow issues in dialogs > - > > Key: NIFI-13153 > URL: https://issues.apache.org/jira/browse/NIFI-13153 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan >Assignee: Scott Aslan >Priority: Major > Attachments: Screenshot 2024-05-06 at 1.46.25 PM.png, Screenshot > 2024-05-06 at 1.46.38 PM.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (NIFI-13171) Remove nifi-external and kafka connect standalone component from the codebase
[ https://issues.apache.org/jira/browse/NIFI-13171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844472#comment-17844472 ] Joe Witt edited comment on NIFI-13171 at 5/9/24 11:53 PM: -- 0. pending any feedback on discuss thread initiated 1. create PR to remove this module. 2. Deprecate on the 1.x line 3. Update wiki migration guide for 2.x indicating this component is gone. was (Author: joewitt): 0. pending any feedback on discuss thread initiated 1. create PR to remove this module. 2. Update wiki migration guide for 2.x indicating this component is gone. > Remove nifi-external and kafka connect standalone component from the codebase > - > > Key: NIFI-13171 > URL: https://issues.apache.org/jira/browse/NIFI-13171 > Project: Apache NiFi > Issue Type: Task >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The nifi-external/kafka-connect component usage is unknown. We see very > little apache community engagement in/around this component. And it sees > very little if any maintainenance. In the past year there appears to be a > single change other than dependency updates around the component but not > within (ie it isn't updated for latest Kafka 3 or even Kafka 2). > Any remaining usage of it can continue from the 1.x release of it but we > should discontinue support for it in the NiFi 2.x line unless there is a > significant shift in both interest/usage and maintenance. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] NIFI-13206: Update to delete bucket encryption after creating s3 buck… [nifi]
markap14 opened a new pull request, #8801: URL: https://github.com/apache/nifi/pull/8801 …ets for integration tests; some code cleanup that IDE was flagging while looking into the failures # 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 21 ### UI Contributions - [ ] NiFi is modernizing its UI. Any contributions that update the [current UI](https://github.com/apache/nifi/tree/main/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-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] [Updated] (NIFI-13206) S3 Integration tests failing due to server-side encrypt enabled by default
[
https://issues.apache.org/jira/browse/NIFI-13206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Payne updated NIFI-13206:
--
Status: Patch Available (was: Open)
> S3 Integration tests failing due to server-side encrypt enabled by default
> --
>
> Key: NIFI-13206
> URL: https://issues.apache.org/jira/browse/NIFI-13206
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Major
> Fix For: 2.0.0-M3
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The 3.0 version of Localstack enabled S3 server-side encryption by default.
> This is causing integration tests now to fail with errors such as:
> {code:java}
> org.opentest4j.AssertionFailedError: Attribute s3.sseAlgorithm should not
> exist on FlowFile, but exists with value AES256 ==>
> Expected :false
> Actual :true {code}
> This is happening in both Fetch and Put S3 integration tests. They tests work
> as-is if we change the docker image of Localstack to 2.3.2
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (NIFI-13206) S3 Integration tests failing due to server-side encrypt enabled by default
Mark Payne created NIFI-13206:
-
Summary: S3 Integration tests failing due to server-side encrypt
enabled by default
Key: NIFI-13206
URL: https://issues.apache.org/jira/browse/NIFI-13206
Project: Apache NiFi
Issue Type: Improvement
Components: Extensions
Reporter: Mark Payne
Assignee: Mark Payne
Fix For: 2.0.0-M3
The 3.0 version of Localstack enabled S3 server-side encryption by default.
This is causing integration tests now to fail with errors such as:
{code:java}
org.opentest4j.AssertionFailedError: Attribute s3.sseAlgorithm should not exist
on FlowFile, but exists with value AES256 ==>
Expected :false
Actual :true {code}
This is happening in both Fetch and Put S3 integration tests. They tests work
as-is if we change the docker image of Localstack to 2.3.2
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-13171) Remove nifi-external and kafka connect standalone component from the codebase
[ https://issues.apache.org/jira/browse/NIFI-13171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844472#comment-17844472 ] Joe Witt edited comment on NIFI-13171 at 5/9/24 11:41 PM: -- 0. pending any feedback on discuss thread initiated 1. create PR to remove this module. 2. Update wiki migration guide for 2.x indicating this component is gone. was (Author: joewitt): 0. pending any feedback on discuss thread initiated 1. create PR to remove this module. 2. create PR for child task to deprecate on the 1.x line. 3. Update wiki migration guide for 2.x indicating this component is gone. > Remove nifi-external and kafka connect standalone component from the codebase > - > > Key: NIFI-13171 > URL: https://issues.apache.org/jira/browse/NIFI-13171 > Project: Apache NiFi > Issue Type: Task >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The nifi-external/kafka-connect component usage is unknown. We see very > little apache community engagement in/around this component. And it sees > very little if any maintainenance. In the past year there appears to be a > single change other than dependency updates around the component but not > within (ie it isn't updated for latest Kafka 3 or even Kafka 2). > Any remaining usage of it can continue from the 1.x release of it but we > should discontinue support for it in the NiFi 2.x line unless there is a > significant shift in both interest/usage and maintenance. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13200) Framework should not allow removal of 'filename' or 'path' attributes
[ https://issues.apache.org/jira/browse/NIFI-13200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845158#comment-17845158 ] Mark Payne commented on NIFI-13200: --- Yup good catch, [~mosermw] > Framework should not allow removal of 'filename' or 'path' attributes > - > > Key: NIFI-13200 > URL: https://issues.apache.org/jira/browse/NIFI-13200 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Major > Fix For: 2.0.0-M3 > > Time Spent: 20m > Remaining Estimate: 0h > > Currently, the framework prevents processors from removing the 'uuid' > attribute. However, it does allow any other attribute to be removed. However, > there are many processors that assume that the 'filename' and 'path' > attributes exist, and they are intended always to exist - they are even > assigned values when the FlowFile is created. We should ensure that these > attributes cannot be removed. > Otherwise, configuring UpdateAttribute to remove these attributes can cause > follow-on processors to fail with unexpected NullPointerExceptions -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13171) Remove nifi-external and kafka connect standalone component from the codebase
[ https://issues.apache.org/jira/browse/NIFI-13171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Witt updated NIFI-13171: Status: Patch Available (was: Open) > Remove nifi-external and kafka connect standalone component from the codebase > - > > Key: NIFI-13171 > URL: https://issues.apache.org/jira/browse/NIFI-13171 > Project: Apache NiFi > Issue Type: Task >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The nifi-external/kafka-connect component usage is unknown. We see very > little apache community engagement in/around this component. And it sees > very little if any maintainenance. In the past year there appears to be a > single change other than dependency updates around the component but not > within (ie it isn't updated for latest Kafka 3 or even Kafka 2). > Any remaining usage of it can continue from the 1.x release of it but we > should discontinue support for it in the NiFi 2.x line unless there is a > significant shift in both interest/usage and maintenance. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] NIFI-13171 removed nifi-external module containing nifi kafka connect… [nifi]
joewitt opened a new pull request, #8800: URL: https://github.com/apache/nifi/pull/8800 … standalone component # Summary [NIFI-13171](https://issues.apache.org/jira/browse/NIFI-13171) # 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-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-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
Re: [PR] [NIFI-13177] ensure consistent typography rendering [nifi]
scottyaslan commented on PR #8786: URL: https://github.com/apache/nifi/pull/8786#issuecomment-2103595719 @rfellows thanks for the updates and the PR. These are great! -- 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-13200) Framework should not allow removal of 'filename' or 'path' attributes
[ https://issues.apache.org/jira/browse/NIFI-13200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Witt updated NIFI-13200: Fix Version/s: 2.0.0-M3 Resolution: Fixed Status: Resolved (was: Patch Available) > Framework should not allow removal of 'filename' or 'path' attributes > - > > Key: NIFI-13200 > URL: https://issues.apache.org/jira/browse/NIFI-13200 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Major > Fix For: 2.0.0-M3 > > Time Spent: 20m > Remaining Estimate: 0h > > Currently, the framework prevents processors from removing the 'uuid' > attribute. However, it does allow any other attribute to be removed. However, > there are many processors that assume that the 'filename' and 'path' > attributes exist, and they are intended always to exist - they are even > assigned values when the FlowFile is created. We should ensure that these > attributes cannot be removed. > Otherwise, configuring UpdateAttribute to remove these attributes can cause > follow-on processors to fail with unexpected NullPointerExceptions -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13200) Framework should not allow removal of 'filename' or 'path' attributes
[ https://issues.apache.org/jira/browse/NIFI-13200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845155#comment-17845155 ] ASF subversion and git services commented on NIFI-13200: Commit 9cf5f947e8dda4b57cf1eb4c429a8c1159af341a in nifi's branch refs/heads/main from Mark Payne [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=9cf5f947e8 ] NIFI-13200: Do not allow 'filename' or 'path' attribute to removed from FlowFile This closes #8791 Signed-off-by: Joseph Witt > Framework should not allow removal of 'filename' or 'path' attributes > - > > Key: NIFI-13200 > URL: https://issues.apache.org/jira/browse/NIFI-13200 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Currently, the framework prevents processors from removing the 'uuid' > attribute. However, it does allow any other attribute to be removed. However, > there are many processors that assume that the 'filename' and 'path' > attributes exist, and they are intended always to exist - they are even > assigned values when the FlowFile is created. We should ensure that these > attributes cannot be removed. > Otherwise, configuring UpdateAttribute to remove these attributes can cause > follow-on processors to fail with unexpected NullPointerExceptions -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-13200: Do not allow 'filename' or 'path' attribute to removed fr… [nifi]
asfgit closed pull request #8791: NIFI-13200: Do not allow 'filename' or 'path' attribute to removed fr… URL: https://github.com/apache/nifi/pull/8791 -- 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-13200) Framework should not allow removal of 'filename' or 'path' attributes
[ https://issues.apache.org/jira/browse/NIFI-13200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845154#comment-17845154 ] Joe Witt commented on NIFI-13200: - [~mosermw]Oops - good catch on that. I linked em and resolved that. Merging this one now. > Framework should not allow removal of 'filename' or 'path' attributes > - > > Key: NIFI-13200 > URL: https://issues.apache.org/jira/browse/NIFI-13200 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Currently, the framework prevents processors from removing the 'uuid' > attribute. However, it does allow any other attribute to be removed. However, > there are many processors that assume that the 'filename' and 'path' > attributes exist, and they are intended always to exist - they are even > assigned values when the FlowFile is created. We should ensure that these > attributes cannot be removed. > Otherwise, configuring UpdateAttribute to remove these attributes can cause > follow-on processors to fail with unexpected NullPointerExceptions -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-4298) NiFi allows users to remove critical Attributes that are needed by processors.
[
https://issues.apache.org/jira/browse/NIFI-4298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Witt resolved NIFI-4298.
Fix Version/s: 2.0.0-M3
Resolution: Fixed
> NiFi allows users to remove critical Attributes that are needed by processors.
> --
>
> Key: NIFI-4298
> URL: https://issues.apache.org/jira/browse/NIFI-4298
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 1.2.0
>Reporter: Matthew Clarke
>Priority: Major
> Fix For: 2.0.0-M3
>
>
> The UpdateAttribute processor provides users with the ability to provide a
> "Delete Attributes Expression".
> While FlowFile properties entryDate, lineageDate, fileSize, and uuid are
> protected and can not be removed, FlowFile attributes path and filename can
> be removed.
> Removal of these attributes has adverse affects on many other processors.
> Any processor that will write a FlowFile out requires the filename attribute.
> In addition, I have found that the MergeContent processor (configured to use
> FlowFileStreams as the merge strategy). also, for whatever reason, requires
> that the path attribute exists on the FlowFile.
> If this attribute is missing, a NPE is thrown and the session is rolled back.
> 2017-08-14 19:27:00,156 ERROR [Timer-Driven Process Thread-7]
> o.a.n.processors.standard.MergeContent
> MergeContent[id=d7213e1f-0c03-1715-93cc-b1be9228ec36] Failed to process
> bundle of 1 files due to java.lang.NullPointerException; rolling back
> sessions: {}
> A stack trace is not produced even if DEBUG is enabled for this processor.
> NiFi needs to prevent users from being able to remove attributes which may be
> "required" by other processors.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-13202) Remove Accumulo Components
[ https://issues.apache.org/jira/browse/NIFI-13202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Witt updated NIFI-13202: Resolution: Fixed Status: Resolved (was: Patch Available) > Remove Accumulo Components > -- > > Key: NIFI-13202 > URL: https://issues.apache.org/jira/browse/NIFI-13202 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Fix For: 2.0.0-M3 > > Time Spent: 20m > Remaining Estimate: 0h > > Apache Accumulo Processors and Services should be removed from the main > branch given the lack of maintenance and updates over multiple years. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-13202 Remove Accumulo Processors and Services [nifi]
asfgit closed pull request #8794: NIFI-13202 Remove Accumulo Processors and Services URL: https://github.com/apache/nifi/pull/8794 -- 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-13202) Remove Accumulo Components
[ https://issues.apache.org/jira/browse/NIFI-13202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845153#comment-17845153 ] ASF subversion and git services commented on NIFI-13202: Commit 72b45f311488a40e518e97a039dd7ecc5378a3f3 in nifi's branch refs/heads/main from David Handermann [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=72b45f3114 ] NIFI-13202 Removed Accumulo Processors and Services This closes #8794. Signed-off-by: Joseph Witt > Remove Accumulo Components > -- > > Key: NIFI-13202 > URL: https://issues.apache.org/jira/browse/NIFI-13202 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Fix For: 2.0.0-M3 > > Time Spent: 10m > Remaining Estimate: 0h > > Apache Accumulo Processors and Services should be removed from the main > branch given the lack of maintenance and updates over multiple years. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13201) Deprecate Accumulo Components for Removal
[ https://issues.apache.org/jira/browse/NIFI-13201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Witt updated NIFI-13201: Fix Version/s: 1.27.0 > Deprecate Accumulo Components for Removal > - > > Key: NIFI-13201 > URL: https://issues.apache.org/jira/browse/NIFI-13201 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Fix For: 1.27.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The Processors and Services for Apache Accumulo have not received any > improvements or notable changes for several years. These components should be > deprecated for removal to reduce dependency maintenance and avoid including > outdated transitive dependencies. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13201) Deprecate Accumulo Components for Removal
[ https://issues.apache.org/jira/browse/NIFI-13201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Witt updated NIFI-13201: Resolution: Fixed Status: Resolved (was: Patch Available) thanks david - merged > Deprecate Accumulo Components for Removal > - > > Key: NIFI-13201 > URL: https://issues.apache.org/jira/browse/NIFI-13201 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > The Processors and Services for Apache Accumulo have not received any > improvements or notable changes for several years. These components should be > deprecated for removal to reduce dependency maintenance and avoid including > outdated transitive dependencies. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13201) Deprecate Accumulo Components for Removal
[ https://issues.apache.org/jira/browse/NIFI-13201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845150#comment-17845150 ] ASF subversion and git services commented on NIFI-13201: Commit 99603eb6b8a1aacf1b30f6091a36bcbc66ec0798 in nifi's branch refs/heads/support/nifi-1.x from David Handermann [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=99603eb6b8 ] NIFI-13201 Deprecated Accumulo Components for Removal This closes #8793 Signed-off-by: Joseph Witt > Deprecate Accumulo Components for Removal > - > > Key: NIFI-13201 > URL: https://issues.apache.org/jira/browse/NIFI-13201 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > The Processors and Services for Apache Accumulo have not received any > improvements or notable changes for several years. These components should be > deprecated for removal to reduce dependency maintenance and avoid including > outdated transitive dependencies. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-13201 Deprecate Accumulo Components for Removal [nifi]
joewitt closed pull request #8793: NIFI-13201 Deprecate Accumulo Components for Removal URL: https://github.com/apache/nifi/pull/8793 -- 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-13205 removed legacy integration test and binary test artifacts … [nifi]
joewitt opened a new pull request, #8799: URL: https://github.com/apache/nifi/pull/8799 …for persistent provenance repo # Summary [NIFI-13205](https://issues.apache.org/jira/browse/NIFI-13205) # 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-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-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] [Updated] (NIFI-13193) Update maven plugins to latest and require minimum of Apache Maven 3.9.6
[
https://issues.apache.org/jira/browse/NIFI-13193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Witt updated NIFI-13193:
Status: Patch Available (was: Open)
> Update maven plugins to latest and require minimum of Apache Maven 3.9.6
>
>
> Key: NIFI-13193
> URL: https://issues.apache.org/jira/browse/NIFI-13193
> Project: Apache NiFi
> Issue Type: Task
>Reporter: Joe Witt
>Assignee: Joe Witt
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Apache Maven 3.8.5 is more than two years old already and many plugin updates
> suggest they require at least that. Bumping versions found during plugin
> update scanning and bumping to that minimum maven version.
> {noformat}
> Update Maven Plugins
> org.codehaus.mojo:exec-maven-plugin 3.1.0 -> 3.2.0
> maven-clean-plugin . 3.3.1 -> 3.3.2
> com.github.eirslett:frontend-maven-plugin 1.14.2 -> 1.15.0
> com.coderplus.maven.plugins:copy-rename-maven-plugin . 1.0 -> 1.0.1
> org.codehaus.mojo:license-maven-plugin . 2.2.0 -> 2.4.0
> org.asciidoctor:asciidoctor-maven-plugin ... 2.2.4 -> 2.2.6 (or 3.0.0
> if we want to require maven 3.8.5)
> com.googlecode.maven-download-plugin:download-maven-plugin 1.7.1 -> 1.9.0
> com.github.spotbugs:spotbugs-maven-plugin .. 4.7.3.5 -> 4.8.5.0
> maven-jar-plugin ... 3.3.0 -> 3.4.1
> org.codehaus.mojo:jaxb2-maven-plugin ... 3.1.0 -> 3.2.0
> org.patrodyne.jvnet:hisrc-higherjaxb40-maven-plugin 2.1.1 -> 2.2.0 (require
> maven 3.8.4)
> org.jacoco:jacoco-maven-plugin ... 0.8.11 -> 0.8.12
> io.swagger.core.v3:swagger-maven-plugin-jakarta .. 2.2.20 -> 2.2.21
> io.swagger.codegen.v3:swagger-codegen-maven-plugin 3.0.52 -> 3.0.55
> {noformat}
> Not worth doing now as it causes some failure and we need to run that down.
> io.fabric8:docker-maven-plugin ... 0.43.4 -> 0.44.0
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] NIFI-13196: Added new isAutoTerminated(Relationship) method to Proces… [nifi]
joewitt commented on PR #8790: URL: https://github.com/apache/nifi/pull/8790#issuecomment-2103577089 Thanks. This makes sense and I'm a +1. Will merge tomorrow pending any further inputs. The change is specific, well documented, and the two JIRAs filed are good examples of how it can be applied well. -- 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-13203) Include s3.url attribute in FetchS3Object and PutS3Object
[ https://issues.apache.org/jira/browse/NIFI-13203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Witt updated NIFI-13203: Resolution: Fixed Status: Resolved (was: Patch Available) > Include s3.url attribute in FetchS3Object and PutS3Object > - > > Key: NIFI-13203 > URL: https://issues.apache.org/jira/browse/NIFI-13203 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Major > Fix For: 2.0.0-M3 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The FetchS3Object and PutS3Object add several s3-related attributes, such as > s3.bucket, s3.key, etc. and then at the end of the onTrigger, they emit a > provenance event with the S3 URL. However, there is no attribute for the S3 > url. This would be handy to have available when building flows. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13203) Include s3.url attribute in FetchS3Object and PutS3Object
[ https://issues.apache.org/jira/browse/NIFI-13203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845148#comment-17845148 ] ASF subversion and git services commented on NIFI-13203: Commit db7e073368eeec2a17da73f74415d64d81e55458 in nifi's branch refs/heads/main from Mark Payne [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=db7e073368 ] NIFI-13203: Include s3.url attribute in FetchS3Object, PutS3Object This closes #8795 Signed-off-by: Joseph Witt > Include s3.url attribute in FetchS3Object and PutS3Object > - > > Key: NIFI-13203 > URL: https://issues.apache.org/jira/browse/NIFI-13203 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Major > Fix For: 2.0.0-M3 > > Time Spent: 10m > Remaining Estimate: 0h > > The FetchS3Object and PutS3Object add several s3-related attributes, such as > s3.bucket, s3.key, etc. and then at the end of the onTrigger, they emit a > provenance event with the S3 URL. However, there is no attribute for the S3 > url. This would be handy to have available when building flows. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-13203: Include s3.url attribute in FetchS3Object, PutS3Object [nifi]
joewitt commented on PR #8795: URL: https://github.com/apache/nifi/pull/8795#issuecomment-2103572372 Thanks mark. the failure was unrelated and I put a JIRA/PR to address that. this looks good merged to main -- 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-13203: Include s3.url attribute in FetchS3Object, PutS3Object [nifi]
asfgit closed pull request #8795: NIFI-13203: Include s3.url attribute in FetchS3Object, PutS3Object URL: https://github.com/apache/nifi/pull/8795 -- 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-13205) Remove StartupAgainstOldLuceneIndexIT
[ https://issues.apache.org/jira/browse/NIFI-13205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Witt updated NIFI-13205: Status: Patch Available (was: Open) > Remove StartupAgainstOldLuceneIndexIT > - > > Key: NIFI-13205 > URL: https://issues.apache.org/jira/browse/NIFI-13205 > Project: Apache NiFi > Issue Type: Task >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > > The test post Lucene 9 update is failing on Github CI due to how long it runs > and it was not even detecting the old index using the backward codecs so > isn't that useful at this stage. It should be removed along with, ideally, > the binary index files included in the repo. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13205) Remove StartupAgainstOldLuceneIndexIT
[
https://issues.apache.org/jira/browse/NIFI-13205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845146#comment-17845146
]
Joe Witt commented on NIFI-13205:
-
{noformat}
Error: Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.041 s
<<< FAILURE! -- in org.apache.nifi.provenance.StartupAgainstOldLuceneIndexIT
Error: org.apache.nifi.provenance.StartupAgainstOldLuceneIndexIT.testStartup
-- Time elapsed: 5.023 s <<< ERROR!
java.util.concurrent.TimeoutException: testStartup() timed out after 5 seconds
at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
Suppressed: java.lang.InterruptedException: sleep interrupted
at java.base/java.lang.Thread.sleep0(Native Method)
at java.base/java.lang.Thread.sleep(Thread.java:509)
at
org.apache.nifi.provenance.StartupAgainstOldLuceneIndexIT.testStartup(StartupAgainstOldLuceneIndexIT.java:96)
at
org.apache.nifi.provenance.StartupAgainstOldLuceneIndexIT.testStartup(StartupAgainstOldLuceneIndexIT.java:53)
at java.base/java.lang.reflect.Method.invoke(Method.java:580)
... 2 more
{noformat}
> Remove StartupAgainstOldLuceneIndexIT
> -
>
> Key: NIFI-13205
> URL: https://issues.apache.org/jira/browse/NIFI-13205
> Project: Apache NiFi
> Issue Type: Task
>Reporter: Joe Witt
>Assignee: Joe Witt
>Priority: Major
>
> The test post Lucene 9 update is failing on Github CI due to how long it runs
> and it was not even detecting the old index using the backward codecs so
> isn't that useful at this stage. It should be removed along with, ideally,
> the binary index files included in the repo.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (NIFI-13113) upgrade Iceberg from 1.5.0 to 1.5.2
[ https://issues.apache.org/jira/browse/NIFI-13113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Witt resolved NIFI-13113. - Fix Version/s: 2.0.0-M3 Assignee: Joe Witt Resolution: Fixed thanks sean. merged > upgrade Iceberg from 1.5.0 to 1.5.2 > --- > > Key: NIFI-13113 > URL: https://issues.apache.org/jira/browse/NIFI-13113 > Project: Apache NiFi > Issue Type: Task >Reporter: Sean Sullivan >Assignee: Joe Witt >Priority: Minor > Fix For: 2.0.0-M3 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > > Iceberg 1.5.2 > > [https://iceberg.apache.org/releases/] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13204) Enable/Disable All Controller Services
[ https://issues.apache.org/jira/browse/NIFI-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13204: --- Status: Patch Available (was: Open) > Enable/Disable All Controller Services > -- > > Key: NIFI-13204 > URL: https://issues.apache.org/jira/browse/NIFI-13204 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13113) upgrade Iceberg from 1.5.0 to 1.5.2
[ https://issues.apache.org/jira/browse/NIFI-13113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845144#comment-17845144 ] ASF subversion and git services commented on NIFI-13113: Commit 7584a5c6f560eecb0c758c5d222a4824c0eea0dc in nifi's branch refs/heads/main from sullis [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=7584a5c6f5 ] NIFI-13113: upgrade Iceberg from 1.5.0 to 1.5.2 This closes #8796 Signed-off-by: Joseph Witt > upgrade Iceberg from 1.5.0 to 1.5.2 > --- > > Key: NIFI-13113 > URL: https://issues.apache.org/jira/browse/NIFI-13113 > Project: Apache NiFi > Issue Type: Task >Reporter: Sean Sullivan >Priority: Minor > Time Spent: 1h 10m > Remaining Estimate: 0h > > > Iceberg 1.5.2 > > [https://iceberg.apache.org/releases/] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] NIFI-13204: Adding the Enable/Disable All Controller Service context menu items [nifi]
mcgilman opened a new pull request, #8798: URL: https://github.com/apache/nifi/pull/8798 NIFI-13204: - Adding the Enable/Disable All Controller Service context menu items. -- 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-13113: upgrade Iceberg from 1.5.0 to 1.5.2 [nifi]
asfgit closed pull request #8796: NIFI-13113: upgrade Iceberg from 1.5.0 to 1.5.2 URL: https://github.com/apache/nifi/pull/8796 -- 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-13205) Remove StartupAgainstOldLuceneIndexIT
Joe Witt created NIFI-13205: --- Summary: Remove StartupAgainstOldLuceneIndexIT Key: NIFI-13205 URL: https://issues.apache.org/jira/browse/NIFI-13205 Project: Apache NiFi Issue Type: Task Reporter: Joe Witt Assignee: Joe Witt The test post Lucene 9 update is failing on Github CI due to how long it runs and it was not even detecting the old index using the backward codecs so isn't that useful at this stage. It should be removed along with, ideally, the binary index files included in the repo. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13204) Enable/Disable All Controller Services
Matt Gilman created NIFI-13204: -- Summary: Enable/Disable All Controller Services Key: NIFI-13204 URL: https://issues.apache.org/jira/browse/NIFI-13204 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Matt Gilman Assignee: Matt Gilman -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13060) UI - property table property column ellipsis
[ https://issues.apache.org/jira/browse/NIFI-13060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13060: --- Fix Version/s: 2.0.0-M3 Resolution: Fixed Status: Resolved (was: Patch Available) > UI - property table property column ellipsis > > > Key: NIFI-13060 > URL: https://issues.apache.org/jira/browse/NIFI-13060 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan >Assignee: Matt Gilman >Priority: Major > Fix For: 2.0.0-M3 > > Attachments: Screenshot 2024-04-16 at 3.49.44 PM.png > > Time Spent: 20m > Remaining Estimate: 0h > > It can happen that a really long property name is displayed in a property > table. When this happens the ellipsis is not properly applied to the text. > !Screenshot 2024-04-16 at 3.49.44 PM.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13060) UI - property table property column ellipsis
[ https://issues.apache.org/jira/browse/NIFI-13060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845141#comment-17845141 ] ASF subversion and git services commented on NIFI-13060: Commit 8b2e770ebd3c7fde6d34249b6e943f19f3d86717 in nifi's branch refs/heads/main from Matt Gilman [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=8b2e770ebd ] NIFI-13060: Using ellipsis and normal line height in the property table (#8792) * NIFI-13060: - Using ellipsis and normal line height in the property table. * NIFI-13060: - Setting title attribute. This closes #8792 > UI - property table property column ellipsis > > > Key: NIFI-13060 > URL: https://issues.apache.org/jira/browse/NIFI-13060 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan >Assignee: Matt Gilman >Priority: Major > Attachments: Screenshot 2024-04-16 at 3.49.44 PM.png > > Time Spent: 20m > Remaining Estimate: 0h > > It can happen that a really long property name is displayed in a property > table. When this happens the ellipsis is not properly applied to the text. > !Screenshot 2024-04-16 at 3.49.44 PM.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-13060: Using ellipsis and normal line height in the property table [nifi]
mcgilman merged PR #8792: URL: https://github.com/apache/nifi/pull/8792 -- 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-13193 ensure plugin versions are latest and that our minumum sup… [nifi]
joewitt opened a new pull request, #8797: URL: https://github.com/apache/nifi/pull/8797 …port maven version now aligns to the maven wrapper which is 3.9.6 # Summary [NIFI-13193](https://issues.apache.org/jira/browse/NIFI-13193) # 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-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-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] [Updated] (NIFI-12400) Remaining items to migrate UI to currently supported/active framework
[ https://issues.apache.org/jira/browse/NIFI-12400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-12400: --- Description: The purpose of this Jira is to track all remaining items following the initial commit [1] for NIFI-11481. The description will be kept up to date with remaining features, tasks, and improvements. As each items is worked, a new sub task Jira will be created and referenced in this description. * Support Parameters in Properties with Allowable Values (NIFI-12401) * Summary (NIFI-12437) ** Remaining work not addressed in initial Jira: *** input ports (NIFI-12504) *** output ports (NIFI-12504) *** remote process groups (NIFI-12504) *** process groups (NIFI-12504) *** connections (NIFI-12504) *** System Diagnostics (NIFI-12505) *** support for cluster-specific ui elements (NIFI-12537) *** Add pagination (NIFI-12552) *** Support Processor Details dialog *** Support Connection Details dialog * Counters (NIFI-12415) ** Counter table has extra unnecessary can modify check (NIFI-12948) * Bulletin Board (NIFI-12560) * Provenance (NIFI-12445) ** Event Listing (NIFI-12445) ** Search (NIFI-12445) ** Event Dialog (NIFI-12445) ** Lineage (NIFI-12485) ** Replay from context menu (NIFI-12445) ** Clustering (NIFI-12807) * Configure Reporting Task (NIFI-12563) * Flow Analysis Rules (NIFI-12588) * Registry Clients (NIFI-12486) * Import from Registry (NIFI-12734) * Parameter Providers (NIFI-12622) ** Fetch parameters from provider, map to parameter context (dialog) - (NIFI-12665) * Cluster ** Node table (Disconnect/Connect/Load Balance/Etc) (NIFI-13053) ** Status History - node specific values (NIFI-12848) * Flow Configuration History (NIFI-12754) ** ActionEntity.action should be optional (NIFI-12948) * Node Status History (NIFI-12553) * Status history for components from canvas context menu (NIFI-12553) * Users (NIFI-12543) ** Don't show users or groups in create/edit dialog is there are none (NIFI-12948) * Policies (NIFI-12548) ** Overridden policy Empty or Copy (NIFI-12679) ** Select Empty by default (NIFI-12948) * Help (NIFI-12795) * About (NIFI-13094) * Show Upstream/Downstream * Align (NIFI-13162) * Replay last event (NIFI-12445) * List Queue (NIFI-12589) ** Clustering (NIFI-12807) * Empty [all] Queue (NIFI-12604) * View Content (NIFI-12589 and NIFI-12445) * View State (NIFI-12611) ** Clustering (NIFI-13005) * Change Component Version (NIFI-13034) * Consider PG permissions in Toolbox (NIFI-12683) * PG Version (NIFI-12963 & NIFI-12995) ** Start (NIFI-12963) ** Commit (NIFI-12963) ** Force Commit (NIFI-12963) ** Show changes (NIFI-12995) ** Revert changes (NIFI-12995) ** Change Flow version (NIFI-12995) ** Stop (NIFI-12963) * Configure PG (NIFI-12417) * Configure Label (NIFI-13081) * Process Group Services (NIFI-12425) ** Listing (NIFI-12425) ** Create (NIFI-12425) ** Configure (NIFI-12425) ** Delete (NIFI-12425) ** Enable (NIFI-12529) ** Disable (NIFI-12529) ** Improve layout and breadcrumbs ** Disable and Configure * Configure Processor ** Service Link (NIFI-12425) ** Create inline Service (NIFI-12425) ** Parameter Link (NIFI-12502) ** Convert to Parameter (NIFI-12502) ** Fix issue with Property Editor width (NIFI-12547) ** Status Bar ** Stop and Configure ** Open Custom UI (NIFI-12958) ** Property History (NIFI-13047) ** Unable to re-add any removed Property (NIFI-12743) ** Shift-Enter new line when editing Property (NIFI-12743) * Property Verification * Terminate Threads (context menu) (NIFI-13068) * Enable/Disable (context menu/operate panel) (NIFI-13078) * More Details (Processor, Controller Service, Reporting Task) (NIFI-13062) * Download Flow (NIFI-13029) * Create RPG (NIFI-12758) * Configure RPG (NIFI-12774) * RPG Remote Ports (NIFI-12778) * RPG Go To (NIFI-12759) * RPG Refresh (NIFI-12761) * Color (context menu/operate panel) * Move to Front (NIFI-13044) * Copy/Paste (context menu/operate panel) (NIFI-13059) * Add/Update Info Icons in dialogs throughout the application (NIFI-13092) * Set viewport earlier when loading a Process Group (NIFI-12737) * Canvas global menu item should navigate user back to where they were on the canvas (NIFI-12737) * Better theme support (NIFI-12655) * Set up development/production environments files * Run unit tests are part of standard build (NIFI-12941) * Update all API calls to consider disconnect node confirmation (NIFI-13001) * Update API calls to use uiOnly flag (NIFI-12950) * Use polling interval from API * Load FlowConfiguration in guard (NIFI-12948) * Routing error handling (NIFI-13104) * General API response error handling ** Management CS (NIFI-12663) ** Canvas CS (NIFI-12684) ** Remainder of Settings (NIFI-12723) ** Counters (NIFI-12723) ** Bulletins (NIFI-12723) ** Flow Designer (NIFI-13100) ** Parameter Contexts (NIFI-12937) ** Convert to
[jira] [Updated] (NIFI-13195) Cluster Request Replicator not handling header removal with HTTP/2
[
https://issues.apache.org/jira/browse/NIFI-13195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Gilman updated NIFI-13195:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Cluster Request Replicator not handling header removal with HTTP/2
> --
>
> Key: NIFI-13195
> URL: https://issues.apache.org/jira/browse/NIFI-13195
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
> Fix For: 2.0.0-M3
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The {{ThreadPoolRequestReplicator}} performs HTTP request replication between
> cluster nodes and includes several methods for removing headers that should
> not be passed in forwarded requests. When receiving requests over HTTP/1.1,
> header names can be capitalized, but over HTTP/2, header names are lowercase.
> The removal logic should be updated to handle header removal without
> depending on the protocol format of the header names.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-13195) Cluster Request Replicator not handling header removal with HTTP/2
[
https://issues.apache.org/jira/browse/NIFI-13195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845136#comment-17845136
]
ASF subversion and git services commented on NIFI-13195:
Commit e005d5f8c176b6d907d5b45dd3a3b7200e42 in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=e005d5f8c1 ]
NIFI-13195 Corrected Replicated Request Header Removal for HTTP/2 (#8789)
- Added findHeaderName method to look for header names regardless of casing
This closes #8789
> Cluster Request Replicator not handling header removal with HTTP/2
> --
>
> Key: NIFI-13195
> URL: https://issues.apache.org/jira/browse/NIFI-13195
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
> Fix For: 2.0.0-M3
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The {{ThreadPoolRequestReplicator}} performs HTTP request replication between
> cluster nodes and includes several methods for removing headers that should
> not be passed in forwarded requests. When receiving requests over HTTP/1.1,
> header names can be capitalized, but over HTTP/2, header names are lowercase.
> The removal logic should be updated to handle header removal without
> depending on the protocol format of the header names.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] NIFI-13195 Correct Replicated Request Header Removal for HTTP/2 [nifi]
mcgilman merged PR #8789: URL: https://github.com/apache/nifi/pull/8789 -- 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-13193) Update maven plugins to latest and require minimum of Apache Maven 3.8.0
[
https://issues.apache.org/jira/browse/NIFI-13193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Witt updated NIFI-13193:
Description:
Apache Maven 3.8.5 is more than two years old already and many plugin updates
suggest they require at least that. Bumping versions found during plugin
update scanning and bumping to that minimum maven version.
{noformat}
Update Maven Plugins
org.codehaus.mojo:exec-maven-plugin 3.1.0 -> 3.2.0
maven-clean-plugin . 3.3.1 -> 3.3.2
com.github.eirslett:frontend-maven-plugin 1.14.2 -> 1.15.0
com.coderplus.maven.plugins:copy-rename-maven-plugin . 1.0 -> 1.0.1
org.codehaus.mojo:license-maven-plugin . 2.2.0 -> 2.4.0
org.asciidoctor:asciidoctor-maven-plugin ... 2.2.4 -> 2.2.6 (or 3.0.0
if we want to require maven 3.8.5)
com.googlecode.maven-download-plugin:download-maven-plugin 1.7.1 -> 1.9.0
com.github.spotbugs:spotbugs-maven-plugin .. 4.7.3.5 -> 4.8.5.0
maven-jar-plugin ... 3.3.0 -> 3.4.1
org.codehaus.mojo:jaxb2-maven-plugin ... 3.1.0 -> 3.2.0
org.patrodyne.jvnet:hisrc-higherjaxb40-maven-plugin 2.1.1 -> 2.2.0 (require
maven 3.8.4)
org.jacoco:jacoco-maven-plugin ... 0.8.11 -> 0.8.12
io.swagger.core.v3:swagger-maven-plugin-jakarta .. 2.2.20 -> 2.2.21
io.swagger.codegen.v3:swagger-codegen-maven-plugin 3.0.52 -> 3.0.55
{noformat}
Not worth doing now as it causes some failure and we need to run that down.
io.fabric8:docker-maven-plugin ... 0.43.4 -> 0.44.0
was:
Apache Maven 3.8.5 is more than two years old already and many plugin updates
suggest they require at least that. Bumping versions found during plugin
update scanning and bumping to that minimum maven version.
{noformat}
Update Maven Plugins
org.codehaus.mojo:exec-maven-plugin 3.1.0 -> 3.2.0
maven-clean-plugin . 3.3.1 -> 3.3.2
com.github.eirslett:frontend-maven-plugin 1.14.2 -> 1.15.0
com.coderplus.maven.plugins:copy-rename-maven-plugin . 1.0 -> 1.0.1
org.codehaus.mojo:license-maven-plugin . 2.2.0 -> 2.4.0
org.asciidoctor:asciidoctor-maven-plugin ... 2.2.4 -> 2.2.6 (or 3.0.0
if we want to require maven 3.8.5)
com.googlecode.maven-download-plugin:download-maven-plugin 1.7.1 -> 1.9.0
com.github.spotbugs:spotbugs-maven-plugin .. 4.7.3.5 -> 4.8.5.0
maven-jar-plugin ... 3.3.0 -> 3.4.1
org.codehaus.mojo:jaxb2-maven-plugin ... 3.1.0 -> 3.2.0
org.patrodyne.jvnet:hisrc-higherjaxb40-maven-plugin 2.1.1 -> 2.2.0 (require
maven 3.8.4)
org.jacoco:jacoco-maven-plugin ... 0.8.11 -> 0.8.12
io.swagger.core.v3:swagger-maven-plugin-jakarta .. 2.2.20 -> 2.2.21
io.swagger.codegen.v3:swagger-codegen-maven-plugin 3.0.52 -> 3.0.55
io.fabric8:docker-maven-plugin ... 0.43.4 -> 0.44.0
{noformat}
> Update maven plugins to latest and require minimum of Apache Maven 3.8.0
>
>
> Key: NIFI-13193
> URL: https://issues.apache.org/jira/browse/NIFI-13193
> Project: Apache NiFi
> Issue Type: Task
>Reporter: Joe Witt
>Assignee: Joe Witt
>Priority: Major
>
> Apache Maven 3.8.5 is more than two years old already and many plugin updates
> suggest they require at least that. Bumping versions found during plugin
> update scanning and bumping to that minimum maven version.
> {noformat}
> Update Maven Plugins
> org.codehaus.mojo:exec-maven-plugin 3.1.0 -> 3.2.0
> maven-clean-plugin . 3.3.1 -> 3.3.2
> com.github.eirslett:frontend-maven-plugin 1.14.2 -> 1.15.0
> com.coderplus.maven.plugins:copy-rename-maven-plugin . 1.0 -> 1.0.1
> org.codehaus.mojo:license-maven-plugin . 2.2.0 -> 2.4.0
> org.asciidoctor:asciidoctor-maven-plugin ... 2.2.4 -> 2.2.6 (or 3.0.0
> if we want to require maven 3.8.5)
> com.googlecode.maven-download-plugin:download-maven-plugin 1.7.1 -> 1.9.0
> com.github.spotbugs:spotbugs-maven-plugin .. 4.7.3.5 -> 4.8.5.0
> maven-jar-plugin ... 3.3.0 -> 3.4.1
> org.codehaus.mojo:jaxb2-maven-plugin ... 3.1.0 -> 3.2.0
> org.patrodyne.jvnet:hisrc-higherjaxb40-maven-plugin 2.1.1 -> 2.2.0 (require
> maven 3.8.4)
> org.jacoco:jacoco-maven-plugin ... 0.8.11 -> 0.8.12
> io.swagger.core.v3:swagger-maven-plugin-jakarta .. 2.2.20 -> 2.2.21
> io.swagger.codegen.v3:swagger-codegen-maven-plugin 3.0.52 -> 3.0.55
> {noformat}
> Not worth doing now as it causes some failure and we need to run that down.
> io.fabric8:docker-maven-plugin ... 0.43.4 -> 0.44.0
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-13193) Update maven plugins to latest and require minimum of Apache Maven 3.9.6
[
https://issues.apache.org/jira/browse/NIFI-13193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Witt updated NIFI-13193:
Summary: Update maven plugins to latest and require minimum of Apache Maven
3.9.6 (was: Update maven plugins to latest and require minimum of Apache Maven
3.8.0)
> Update maven plugins to latest and require minimum of Apache Maven 3.9.6
>
>
> Key: NIFI-13193
> URL: https://issues.apache.org/jira/browse/NIFI-13193
> Project: Apache NiFi
> Issue Type: Task
>Reporter: Joe Witt
>Assignee: Joe Witt
>Priority: Major
>
> Apache Maven 3.8.5 is more than two years old already and many plugin updates
> suggest they require at least that. Bumping versions found during plugin
> update scanning and bumping to that minimum maven version.
> {noformat}
> Update Maven Plugins
> org.codehaus.mojo:exec-maven-plugin 3.1.0 -> 3.2.0
> maven-clean-plugin . 3.3.1 -> 3.3.2
> com.github.eirslett:frontend-maven-plugin 1.14.2 -> 1.15.0
> com.coderplus.maven.plugins:copy-rename-maven-plugin . 1.0 -> 1.0.1
> org.codehaus.mojo:license-maven-plugin . 2.2.0 -> 2.4.0
> org.asciidoctor:asciidoctor-maven-plugin ... 2.2.4 -> 2.2.6 (or 3.0.0
> if we want to require maven 3.8.5)
> com.googlecode.maven-download-plugin:download-maven-plugin 1.7.1 -> 1.9.0
> com.github.spotbugs:spotbugs-maven-plugin .. 4.7.3.5 -> 4.8.5.0
> maven-jar-plugin ... 3.3.0 -> 3.4.1
> org.codehaus.mojo:jaxb2-maven-plugin ... 3.1.0 -> 3.2.0
> org.patrodyne.jvnet:hisrc-higherjaxb40-maven-plugin 2.1.1 -> 2.2.0 (require
> maven 3.8.4)
> org.jacoco:jacoco-maven-plugin ... 0.8.11 -> 0.8.12
> io.swagger.core.v3:swagger-maven-plugin-jakarta .. 2.2.20 -> 2.2.21
> io.swagger.codegen.v3:swagger-codegen-maven-plugin 3.0.52 -> 3.0.55
> {noformat}
> Not worth doing now as it causes some failure and we need to run that down.
> io.fabric8:docker-maven-plugin ... 0.43.4 -> 0.44.0
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] NIFI-13113: upgrade Iceberg from 1.5.0 to 1.5.1 [nifi]
sullis commented on PR #8712: URL: https://github.com/apache/nifi/pull/8712#issuecomment-2103452444 new PR: https://github.com/apache/nifi/pull/8796 -- 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-13113: upgrade Iceberg from 1.5.0 to 1.5.2 [nifi]
sullis opened a new pull request, #8796: URL: https://github.com/apache/nifi/pull/8796 # 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 21 ### UI Contributions - [ ] NiFi is modernizing its UI. Any contributions that update the [current UI](https://github.com/apache/nifi/tree/main/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-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-13200) Framework should not allow removal of 'filename' or 'path' attributes
[ https://issues.apache.org/jira/browse/NIFI-13200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845132#comment-17845132 ] Michael W Moser commented on NIFI-13200: [~markap14] Would this also resolve NIFI-4298? > Framework should not allow removal of 'filename' or 'path' attributes > - > > Key: NIFI-13200 > URL: https://issues.apache.org/jira/browse/NIFI-13200 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Currently, the framework prevents processors from removing the 'uuid' > attribute. However, it does allow any other attribute to be removed. However, > there are many processors that assume that the 'filename' and 'path' > attributes exist, and they are intended always to exist - they are even > assigned values when the FlowFile is created. We should ensure that these > attributes cannot be removed. > Otherwise, configuring UpdateAttribute to remove these attributes can cause > follow-on processors to fail with unexpected NullPointerExceptions -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13113) upgrade Iceberg from 1.5.0 to 1.5.2
[ https://issues.apache.org/jira/browse/NIFI-13113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Sullivan updated NIFI-13113: - Summary: upgrade Iceberg from 1.5.0 to 1.5.2 (was: upgrade Iceberg from 1.5.0 to 1.5.1 ) > upgrade Iceberg from 1.5.0 to 1.5.2 > --- > > Key: NIFI-13113 > URL: https://issues.apache.org/jira/browse/NIFI-13113 > Project: Apache NiFi > Issue Type: Task >Reporter: Sean Sullivan >Priority: Minor > Time Spent: 50m > Remaining Estimate: 0h > > > Iceberg 1.5.2 > > [https://iceberg.apache.org/releases/] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13113) upgrade Iceberg from 1.5.0 to 1.5.1
[ https://issues.apache.org/jira/browse/NIFI-13113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Sullivan updated NIFI-13113: - Description: Iceberg 1.5.2 [https://iceberg.apache.org/releases/] was: Iceberg 1.5.1 [https://github.com/apache/iceberg/releases/tag/apache-iceberg-1.5.1] [https://iceberg.apache.org/releases/] > upgrade Iceberg from 1.5.0 to 1.5.1 > > > Key: NIFI-13113 > URL: https://issues.apache.org/jira/browse/NIFI-13113 > Project: Apache NiFi > Issue Type: Task >Reporter: Sean Sullivan >Priority: Minor > Time Spent: 50m > Remaining Estimate: 0h > > > Iceberg 1.5.2 > > [https://iceberg.apache.org/releases/] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13203) Include s3.url attribute in FetchS3Object and PutS3Object
[ https://issues.apache.org/jira/browse/NIFI-13203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-13203: -- Fix Version/s: 2.0.0-M3 Assignee: Mark Payne Status: Patch Available (was: Open) > Include s3.url attribute in FetchS3Object and PutS3Object > - > > Key: NIFI-13203 > URL: https://issues.apache.org/jira/browse/NIFI-13203 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Major > Fix For: 2.0.0-M3 > > Time Spent: 10m > Remaining Estimate: 0h > > The FetchS3Object and PutS3Object add several s3-related attributes, such as > s3.bucket, s3.key, etc. and then at the end of the onTrigger, they emit a > provenance event with the S3 URL. However, there is no attribute for the S3 > url. This would be handy to have available when building flows. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] NIFI-13203: Include s3.url attribute in FetchS3Object, PutS3Object [nifi]
markap14 opened a new pull request, #8795: URL: https://github.com/apache/nifi/pull/8795 # 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 21 ### UI Contributions - [ ] NiFi is modernizing its UI. Any contributions that update the [current UI](https://github.com/apache/nifi/tree/main/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-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] [Created] (NIFI-13203) Include s3.url attribute in FetchS3Object and PutS3Object
Mark Payne created NIFI-13203: - Summary: Include s3.url attribute in FetchS3Object and PutS3Object Key: NIFI-13203 URL: https://issues.apache.org/jira/browse/NIFI-13203 Project: Apache NiFi Issue Type: Improvement Components: Extensions Reporter: Mark Payne The FetchS3Object and PutS3Object add several s3-related attributes, such as s3.bucket, s3.key, etc. and then at the end of the onTrigger, they emit a provenance event with the S3 URL. However, there is no attribute for the S3 url. This would be handy to have available when building flows. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13202) Remove Accumulo Components
[ https://issues.apache.org/jira/browse/NIFI-13202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13202: Status: Patch Available (was: Open) > Remove Accumulo Components > -- > > Key: NIFI-13202 > URL: https://issues.apache.org/jira/browse/NIFI-13202 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Fix For: 2.0.0-M3 > > Time Spent: 10m > Remaining Estimate: 0h > > Apache Accumulo Processors and Services should be removed from the main > branch given the lack of maintenance and updates over multiple years. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] NIFI-13202 Remove Accumulo Processors and Services [nifi]
exceptionfactory opened a new pull request, #8794: URL: https://github.com/apache/nifi/pull/8794 # Summary [NIFI-13202](https://issues.apache.org/jira/browse/NIFI-13202) Removes Apache Accumulo Processors PutAccumuloRecord and ScanAccumulo, along with the AccumuloService and associated Maven modules. # 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 21 ### UI Contributions - [ ] NiFi is modernizing its UI. Any contributions that update the [current UI](https://github.com/apache/nifi/tree/main/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-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] [Updated] (NIFI-13201) Deprecate Accumulo Components for Removal
[ https://issues.apache.org/jira/browse/NIFI-13201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13201: Status: Patch Available (was: Open) > Deprecate Accumulo Components for Removal > - > > Key: NIFI-13201 > URL: https://issues.apache.org/jira/browse/NIFI-13201 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > The Processors and Services for Apache Accumulo have not received any > improvements or notable changes for several years. These components should be > deprecated for removal to reduce dependency maintenance and avoid including > outdated transitive dependencies. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] NIFI-13201 Deprecate Accumulo Components for Removal [nifi]
exceptionfactory opened a new pull request, #8793: URL: https://github.com/apache/nifi/pull/8793 # Summary [NIFI-13201](https://issues.apache.org/jira/browse/NIFI-13201) Deprecates Apache Accumulo Processors PutAccumuloRecord and ScanAccumulo, along with AccumuloService, for subsequent removal. The Accumulo components have not received any maintenance other than minor version updates for several years. # 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 21 ### UI Contributions - [ ] NiFi is modernizing its UI. Any contributions that update the [current UI](https://github.com/apache/nifi/tree/main/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-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-13191) Deprecate InvokeAWSGatewayApi Processor
[ https://issues.apache.org/jira/browse/NIFI-13191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845126#comment-17845126 ] Otto Fowler commented on NIFI-13191: I don't see or haven't seen any user issues with this since introduction, so I'm not sure anyone is using it beyond the initial users I wrote it for, and I doubt they are still using it as I think that product is no longer in production. It was still working in the 1x last I tried it, so there are options for anyone silently using it. Deprecation is the correct move. > Deprecate InvokeAWSGatewayApi Processor > --- > > Key: NIFI-13191 > URL: https://issues.apache.org/jira/browse/NIFI-13191 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Gresock >Assignee: Joe Gresock >Priority: Minor > Fix For: 1.27.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Similar to the other AWS client library upgrade issues, this targets the > InvokeAWSGatewayApi processor. > Note: After discussing with [~exceptionfactory] and [~otto], we agree that > this processor can be deprecated, and removed in NiFi 2.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13060) UI - property table property column ellipsis
[ https://issues.apache.org/jira/browse/NIFI-13060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13060: --- Status: Patch Available (was: Open) > UI - property table property column ellipsis > > > Key: NIFI-13060 > URL: https://issues.apache.org/jira/browse/NIFI-13060 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan >Assignee: Matt Gilman >Priority: Major > Attachments: Screenshot 2024-04-16 at 3.49.44 PM.png > > Time Spent: 10m > Remaining Estimate: 0h > > It can happen that a really long property name is displayed in a property > table. When this happens the ellipsis is not properly applied to the text. > !Screenshot 2024-04-16 at 3.49.44 PM.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] NIFI-13060: Using ellipsis and normal line height in the property table [nifi]
mcgilman opened a new pull request, #8792: URL: https://github.com/apache/nifi/pull/8792 NIFI-13060: - Using ellipsis and normal line height in the property table. -- 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-13060) UI - property table property column ellipsis
[ https://issues.apache.org/jira/browse/NIFI-13060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman reassigned NIFI-13060: -- Assignee: Matt Gilman > UI - property table property column ellipsis > > > Key: NIFI-13060 > URL: https://issues.apache.org/jira/browse/NIFI-13060 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan >Assignee: Matt Gilman >Priority: Major > Attachments: Screenshot 2024-04-16 at 3.49.44 PM.png > > > It can happen that a really long property name is displayed in a property > table. When this happens the ellipsis is not properly applied to the text. > !Screenshot 2024-04-16 at 3.49.44 PM.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13202) Remove Accumulo Components
David Handermann created NIFI-13202: --- Summary: Remove Accumulo Components Key: NIFI-13202 URL: https://issues.apache.org/jira/browse/NIFI-13202 Project: Apache NiFi Issue Type: Improvement Components: Extensions Reporter: David Handermann Assignee: David Handermann Fix For: 2.0.0-M3 Apache Accumulo Processors and Services should be removed from the main branch given the lack of maintenance and updates over multiple years. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13201) Deprecate Accumulo Components for Removal
David Handermann created NIFI-13201: --- Summary: Deprecate Accumulo Components for Removal Key: NIFI-13201 URL: https://issues.apache.org/jira/browse/NIFI-13201 Project: Apache NiFi Issue Type: Improvement Components: Extensions Reporter: David Handermann Assignee: David Handermann The Processors and Services for Apache Accumulo have not received any improvements or notable changes for several years. These components should be deprecated for removal to reduce dependency maintenance and avoid including outdated transitive dependencies. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] NIFI-13200: Do not allow 'filename' or 'path' attribute to removed fr… [nifi]
markap14 opened a new pull request, #8791: URL: https://github.com/apache/nifi/pull/8791 …om FlowFile # 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 21 ### UI Contributions - [ ] NiFi is modernizing its UI. Any contributions that update the [current UI](https://github.com/apache/nifi/tree/main/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-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] [Updated] (NIFI-13200) Framework should not allow removal of 'filename' or 'path' attributes
[ https://issues.apache.org/jira/browse/NIFI-13200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-13200: -- Status: Patch Available (was: Open) > Framework should not allow removal of 'filename' or 'path' attributes > - > > Key: NIFI-13200 > URL: https://issues.apache.org/jira/browse/NIFI-13200 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Currently, the framework prevents processors from removing the 'uuid' > attribute. However, it does allow any other attribute to be removed. However, > there are many processors that assume that the 'filename' and 'path' > attributes exist, and they are intended always to exist - they are even > assigned values when the FlowFile is created. We should ensure that these > attributes cannot be removed. > Otherwise, configuring UpdateAttribute to remove these attributes can cause > follow-on processors to fail with unexpected NullPointerExceptions -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13200) Framework should not allow removal of 'filename' or 'path' attributes
Mark Payne created NIFI-13200: - Summary: Framework should not allow removal of 'filename' or 'path' attributes Key: NIFI-13200 URL: https://issues.apache.org/jira/browse/NIFI-13200 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Reporter: Mark Payne Assignee: Mark Payne Currently, the framework prevents processors from removing the 'uuid' attribute. However, it does allow any other attribute to be removed. However, there are many processors that assume that the 'filename' and 'path' attributes exist, and they are intended always to exist - they are even assigned values when the FlowFile is created. We should ensure that these attributes cannot be removed. Otherwise, configuring UpdateAttribute to remove these attributes can cause follow-on processors to fail with unexpected NullPointerExceptions -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13199) Update ValidateRecord to avoid writing to FlowFiles that will be auto-terminated
Mark Payne created NIFI-13199: - Summary: Update ValidateRecord to avoid writing to FlowFiles that will be auto-terminated Key: NIFI-13199 URL: https://issues.apache.org/jira/browse/NIFI-13199 Project: Apache NiFi Issue Type: Improvement Components: Extensions Reporter: Mark Payne NIFI-13196 introduces the ability to check if a relationship is auto-terminated. In the case of ValidateRecord, the processor is commonly used to filter out invalid records. Before writing records to an 'invalid' FlowFile we should first check if the relationship is auto-terminated and not spend the resources to create the data if it will be auto-terminated. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-13196: Added new isAutoTerminated(Relationship) method to Proces… [nifi]
markap14 commented on PR #8790: URL: https://github.com/apache/nifi/pull/8790#issuecomment-2103367968 @joewitt just created a Jira for RouteText, for example. https://issues.apache.org/jira/browse/NIFI-13198 Will take some thinking through which processors can make use of this, but for several Route types processors, especially those with an 'unmatched' type of relationship it will make sense. -- 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-13198) Update RouteText not to write to FlowFiles for auto-terminated relationships
Mark Payne created NIFI-13198: - Summary: Update RouteText not to write to FlowFiles for auto-terminated relationships Key: NIFI-13198 URL: https://issues.apache.org/jira/browse/NIFI-13198 Project: Apache NiFi Issue Type: Improvement Components: Extensions Reporter: Mark Payne NIFI-13196 introduces the ability to check if a relationship is auto-terminated. In the case of RouteText, the processor is commonly used to filter out unwanted lines of text. For anything that is auto-terminated, though, we still write out the data. We should instead check if the Relationship that we're writing to is auto-terminated and if so, don't bother creating the flowfile or writing to it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-13194) Remove InvokeAWSGatewayApi processor from NiFi 2
[ https://issues.apache.org/jira/browse/NIFI-13194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann resolved NIFI-13194. - Fix Version/s: 2.0.0-M3 Resolution: Fixed > Remove InvokeAWSGatewayApi processor from NiFi 2 > > > Key: NIFI-13194 > URL: https://issues.apache.org/jira/browse/NIFI-13194 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Gresock >Assignee: Joe Gresock >Priority: Major > Fix For: 2.0.0-M3 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Based on the discussion in NIFI-13191. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13194) Remove InvokeAWSGatewayApi processor from NiFi 2
[ https://issues.apache.org/jira/browse/NIFI-13194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845119#comment-17845119 ] ASF subversion and git services commented on NIFI-13194: Commit 1592b98298403c5ae50844bd75e0b9497669cecb in nifi's branch refs/heads/main from Joe Gresock [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=1592b98298 ] NIFI-13194 Removed InvokeAWSGatewayApi Processor This closes #8787 Signed-off-by: David Handermann > Remove InvokeAWSGatewayApi processor from NiFi 2 > > > Key: NIFI-13194 > URL: https://issues.apache.org/jira/browse/NIFI-13194 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Gresock >Assignee: Joe Gresock >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > Based on the discussion in NIFI-13191. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-13194: Removing InvokeAWSGatewayApi processor [nifi]
exceptionfactory closed pull request #8787: NIFI-13194: Removing InvokeAWSGatewayApi processor URL: https://github.com/apache/nifi/pull/8787 -- 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-13196: Added new isAutoTerminated(Relationship) method to Proces… [nifi]
markap14 commented on PR #8790: URL: https://github.com/apache/nifi/pull/8790#issuecomment-2103356772 @joewitt yes correct, I was sure that we had this method already, then I found that it exists on Connectable but was not surfaced in the ProcessContext. I am almost sure that we have processors that could take advantage of it already, and will do a scan through, creating any Jiras as necessary. -- 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-13196: Added new isAutoTerminated(Relationship) method to Proces… [nifi]
joewitt commented on PR #8790: URL: https://github.com/apache/nifi/pull/8790#issuecomment-2103353122 @markap14 one has to wonder how on earth we did not have this mechanism long ago. So if I'm writing a processor, such as a custom processor or otherwise, I can now ask "Hey if I make this potentially expensive output is it going to get thrown away anyway so I can just bypass doing so?" Very nice! Once this lands makes sense to have follow-on JIRA(s) to take advantage of it. -- 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-13191: Deprecating InvokeAWSGatewayApi processor [nifi]
exceptionfactory commented on PR #8788: URL: https://github.com/apache/nifi/pull/8788#issuecomment-2103349159 Merged in https://github.com/apache/nifi/commit/d2993b246384bc2109bfa1525ce1267f842e90f2 -- 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-13191) Deprecate InvokeAWSGatewayApi Processor
[ https://issues.apache.org/jira/browse/NIFI-13191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845115#comment-17845115 ] ASF subversion and git services commented on NIFI-13191: Commit d2993b246384bc2109bfa1525ce1267f842e90f2 in nifi's branch refs/heads/support/nifi-1.x from Joe Gresock [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=d2993b2463 ] NIFI-13191 Deprecated InvokeAWSGatewayApi This closes #8788 Signed-off-by: David Handermann > Deprecate InvokeAWSGatewayApi Processor > --- > > Key: NIFI-13191 > URL: https://issues.apache.org/jira/browse/NIFI-13191 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Gresock >Assignee: Joe Gresock >Priority: Minor > > Similar to the other AWS client library upgrade issues, this targets the > InvokeAWSGatewayApi processor. > Note: After discussing with [~exceptionfactory] and [~otto], we agree that > this processor can be deprecated, and removed in NiFi 2.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-13191) Deprecate InvokeAWSGatewayApi Processor
[ https://issues.apache.org/jira/browse/NIFI-13191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann resolved NIFI-13191. - Fix Version/s: 1.27.0 Resolution: Fixed > Deprecate InvokeAWSGatewayApi Processor > --- > > Key: NIFI-13191 > URL: https://issues.apache.org/jira/browse/NIFI-13191 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Gresock >Assignee: Joe Gresock >Priority: Minor > Fix For: 1.27.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Similar to the other AWS client library upgrade issues, this targets the > InvokeAWSGatewayApi processor. > Note: After discussing with [~exceptionfactory] and [~otto], we agree that > this processor can be deprecated, and removed in NiFi 2.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-13191: Deprecating InvokeAWSGatewayApi processor [nifi]
exceptionfactory closed pull request #8788: NIFI-13191: Deprecating InvokeAWSGatewayApi processor URL: https://github.com/apache/nifi/pull/8788 -- 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-12857) Refactor QueuePrioritizer using updated Java APIs
[ https://issues.apache.org/jira/browse/NIFI-12857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12857: Priority: Minor (was: Major) > Refactor QueuePrioritizer using updated Java APIs > - > > Key: NIFI-12857 > URL: https://issues.apache.org/jira/browse/NIFI-12857 > Project: Apache NiFi > Issue Type: Improvement >Reporter: endzeit >Assignee: endzeit >Priority: Minor > Fix For: 2.0.0-M3 > > Time Spent: 50m > Remaining Estimate: 0h > > The QueuePrioritizer is not covered by a dedicated test. Additionally, it > contains some boilerplate that can be reduced by using updated Java APIs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-12857) Refactor QueuePrioritizer using updated Java APIs
[ https://issues.apache.org/jira/browse/NIFI-12857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann resolved NIFI-12857. - Fix Version/s: 2.0.0-M3 Resolution: Fixed > Refactor QueuePrioritizer using updated Java APIs > - > > Key: NIFI-12857 > URL: https://issues.apache.org/jira/browse/NIFI-12857 > Project: Apache NiFi > Issue Type: Improvement >Reporter: endzeit >Assignee: endzeit >Priority: Major > Fix For: 2.0.0-M3 > > Time Spent: 50m > Remaining Estimate: 0h > > The QueuePrioritizer is not covered by a dedicated test. Additionally, it > contains some boilerplate that can be reduced by using updated Java APIs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12857) Refactor QueuePrioritizer using updated Java APIs
[ https://issues.apache.org/jira/browse/NIFI-12857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845114#comment-17845114 ] ASF subversion and git services commented on NIFI-12857: Commit 53207a20a0d2692437368ffaee594ae6e796a647 in nifi's branch refs/heads/main from EndzeitBegins [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=53207a20a0 ] NIFI-12857 Simplified implementation of QueuePrioritizer and added tests This closes #8466 Signed-off-by: David Handermann > Refactor QueuePrioritizer using updated Java APIs > - > > Key: NIFI-12857 > URL: https://issues.apache.org/jira/browse/NIFI-12857 > Project: Apache NiFi > Issue Type: Task >Reporter: endzeit >Assignee: endzeit >Priority: Major > Time Spent: 50m > Remaining Estimate: 0h > > The QueuePrioritizer is not covered by a dedicated test. Additionally, it > contains some boilerplate that can be reduced by using updated Java APIs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12857) Refactor QueuePrioritizer using updated Java APIs
[ https://issues.apache.org/jira/browse/NIFI-12857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12857: Issue Type: Improvement (was: Task) > Refactor QueuePrioritizer using updated Java APIs > - > > Key: NIFI-12857 > URL: https://issues.apache.org/jira/browse/NIFI-12857 > Project: Apache NiFi > Issue Type: Improvement >Reporter: endzeit >Assignee: endzeit >Priority: Major > Time Spent: 50m > Remaining Estimate: 0h > > The QueuePrioritizer is not covered by a dedicated test. Additionally, it > contains some boilerplate that can be reduced by using updated Java APIs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
