[jira] [Updated] (NIFI-12225) Improve NiFi splash loading animation
[ https://issues.apache.org/jira/browse/NIFI-12225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-12225: -- Description: With NiFi 2.0 just around the corner, I thought it's a great opportunity to differentiate it from from the 1.x line by introducing a fresh splash screen. The PR includes both a GIF and a JSON version. The JSON format would be the preferred choice, but it requires an additional frontend dependency to render. Personally, I don't believe that having just a single animation from that source justifies adding the extra dependency. I'm including it in the PR primarily as an option for potential future use. was:With NiFi 2.0 just around the corner, I thought it's a great opportunity to differentiate it from from the 1.x line by introducing a fresh splash screen. > Improve NiFi splash loading animation > - > > Key: NIFI-12225 > URL: https://issues.apache.org/jira/browse/NIFI-12225 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Nandor Soma Abonyi >Assignee: Nandor Soma Abonyi >Priority: Minor > Fix For: 2.latest > > > With NiFi 2.0 just around the corner, I thought it's a great opportunity to > differentiate it from from the 1.x line by introducing a fresh splash screen. > The PR includes both a GIF and a JSON version. The JSON format would be the > preferred choice, but it requires an additional frontend dependency to > render. Personally, I don't believe that having just a single animation from > that source justifies adding the extra dependency. I'm including it in the PR > primarily as an option for potential future use. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12225) Improve NiFi splash loading animation
Nandor Soma Abonyi created NIFI-12225: - Summary: Improve NiFi splash loading animation Key: NIFI-12225 URL: https://issues.apache.org/jira/browse/NIFI-12225 Project: Apache NiFi Issue Type: Improvement Reporter: Nandor Soma Abonyi Assignee: Nandor Soma Abonyi With NiFi 2.0 just around the corner, I thought it's a great opportunity to differentiate it from from the 1.x line by introducing a fresh splash screen. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12225) Improve NiFi splash loading animation
[ https://issues.apache.org/jira/browse/NIFI-12225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-12225: -- Fix Version/s: 2.latest > Improve NiFi splash loading animation > - > > Key: NIFI-12225 > URL: https://issues.apache.org/jira/browse/NIFI-12225 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Nandor Soma Abonyi >Assignee: Nandor Soma Abonyi >Priority: Minor > Fix For: 2.latest > > > With NiFi 2.0 just around the corner, I thought it's a great opportunity to > differentiate it from from the 1.x line by introducing a fresh splash screen. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12197) Upgrade wrapper Maven from 3.9.4 to 3.9.5
[ https://issues.apache.org/jira/browse/NIFI-12197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-12197: -- Fix Version/s: 1.latest 2.latest > Upgrade wrapper Maven from 3.9.4 to 3.9.5 > - > > Key: NIFI-12197 > URL: https://issues.apache.org/jira/browse/NIFI-12197 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Nandor Soma Abonyi >Assignee: Nandor Soma Abonyi >Priority: Minor > Fix For: 1.latest, 2.latest > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12197) Upgrade wrapper Maven from 3.9.4 to 3.9.5
Nandor Soma Abonyi created NIFI-12197: - Summary: Upgrade wrapper Maven from 3.9.4 to 3.9.5 Key: NIFI-12197 URL: https://issues.apache.org/jira/browse/NIFI-12197 Project: Apache NiFi Issue Type: Improvement Reporter: Nandor Soma Abonyi Assignee: Nandor Soma Abonyi -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12133) Include python in the maven build
[ https://issues.apache.org/jira/browse/NIFI-12133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-12133: -- Fix Version/s: 2.latest > Include python in the maven build > - > > Key: NIFI-12133 > URL: https://issues.apache.org/jira/browse/NIFI-12133 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Nandor Soma Abonyi >Priority: Major > Fix For: 2.latest > > > Include python in the build process to run python IT tests, similarly as the > npm build is part of the maven build. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12133) Include python in the maven build
Nandor Soma Abonyi created NIFI-12133: - Summary: Include python in the maven build Key: NIFI-12133 URL: https://issues.apache.org/jira/browse/NIFI-12133 Project: Apache NiFi Issue Type: Improvement Reporter: Nandor Soma Abonyi Include python in the build process to run python IT tests, similarly as the npm build is part of the maven build. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12114) Create separate test instance for python extensions
[ https://issues.apache.org/jira/browse/NIFI-12114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-12114: -- Fix Version/s: 2.latest > Create separate test instance for python extensions > --- > > Key: NIFI-12114 > URL: https://issues.apache.org/jira/browse/NIFI-12114 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Nandor Soma Abonyi >Assignee: Nandor Soma Abonyi >Priority: Major > Fix For: 2.latest > > > Currently, python is needed for all IT tests, even if they are not using > Python extensions. As a proposal, I created a separate test instance for > Python-related IT tests. This way, the traditional IT tests can run without > python. > As a follow-up, I'd like to move Python tests to a separate module, where we > could download python just like what we do in the web modules with npm and > node. Thoughts? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12114) Create separate test instance for python extensions
Nandor Soma Abonyi created NIFI-12114: - Summary: Create separate test instance for python extensions Key: NIFI-12114 URL: https://issues.apache.org/jira/browse/NIFI-12114 Project: Apache NiFi Issue Type: Improvement Reporter: Nandor Soma Abonyi Assignee: Nandor Soma Abonyi Currently, python is needed for all IT tests, even if they are not using Python extensions. As a proposal, I created a separate test instance for Python-related IT tests. This way, the traditional IT tests can run without python. As a follow-up, I'd like to move Python tests to a separate module, where we could download python just like what we do in the web modules with npm and node. Thoughts? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12095) Increase default Xmx to 1g
[ https://issues.apache.org/jira/browse/NIFI-12095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-12095: -- Fix Version/s: 1.latest 2.latest > Increase default Xmx to 1g > -- > > Key: NIFI-12095 > URL: https://issues.apache.org/jira/browse/NIFI-12095 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Nandor Soma Abonyi >Assignee: Nandor Soma Abonyi >Priority: Minor > Fix For: 1.latest, 2.latest > > Time Spent: 0.5h > Remaining Estimate: 0h > > The default 512m dates back many years, and sometimes, a simple flow can > cause OutOfMemoryError. This should be fine-tuned for production for sure, > but increasing the default to 1g can reduce the inconvenience new users might > experience. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12095) Increase default Xmx to 1g
Nandor Soma Abonyi created NIFI-12095: - Summary: Increase default Xmx to 1g Key: NIFI-12095 URL: https://issues.apache.org/jira/browse/NIFI-12095 Project: Apache NiFi Issue Type: Improvement Reporter: Nandor Soma Abonyi Assignee: Nandor Soma Abonyi The default 512m dates back many years, and sometimes, a simple flow can cause OutOfMemoryError. This should be fine-tuned for production for sure, but increasing the default to 1g can reduce the inconvenience new users might experience. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11852) CLI - connect two process groups
[
https://issues.apache.org/jira/browse/NIFI-11852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandor Soma Abonyi updated NIFI-11852:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> CLI - connect two process groups
>
>
> Key: NIFI-11852
> URL: https://issues.apache.org/jira/browse/NIFI-11852
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Tools and Build
>Reporter: Pierre Villard
>Assignee: Pierre Villard
>Priority: Major
> Fix For: 2.0.0, 1.24.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Add a CLI command to connect two process groups together
> {code:java}
> ./cli.sh nifi pg-connect \
> --source-pg \
> --source-output-port \
> --destination-pg \
> --destination-input-port {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-11852) CLI - connect two process groups
[
https://issues.apache.org/jira/browse/NIFI-11852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandor Soma Abonyi updated NIFI-11852:
--
Fix Version/s: 2.0.0
1.24.0
(was: 1.latest)
(was: 2.latest)
> CLI - connect two process groups
>
>
> Key: NIFI-11852
> URL: https://issues.apache.org/jira/browse/NIFI-11852
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Tools and Build
>Reporter: Pierre Villard
>Assignee: Pierre Villard
>Priority: Major
> Fix For: 2.0.0, 1.24.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Add a CLI command to connect two process groups together
> {code:java}
> ./cli.sh nifi pg-connect \
> --source-pg \
> --source-output-port \
> --destination-pg \
> --destination-input-port {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-12077) CLI - make LB Strategy and Prioritizers configurable when connecting two process groups
[ https://issues.apache.org/jira/browse/NIFI-12077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-12077: -- Summary: CLI - make LB Strategy and Prioritizers configurable when connecting two process groups (was: CLI -LB Strategy and Prioritizers configurable when connecting two process groups) > CLI - make LB Strategy and Prioritizers configurable when connecting two > process groups > --- > > Key: NIFI-12077 > URL: https://issues.apache.org/jira/browse/NIFI-12077 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Reporter: Nandor Soma Abonyi >Priority: Major > > Make it possible to configure the same set of properties that are available > on the UI? Like "Load Balancing Strategy" and "Selected Prioritizers". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12077) CLI -LB Strategy and Prioritizers configurable when connecting two process groups
[ https://issues.apache.org/jira/browse/NIFI-12077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-12077: -- Summary: CLI -LB Strategy and Prioritizers configurable when connecting two process groups (was: CLI - connect two process groups, make LB Strategy and Prioritizers configurable) > CLI -LB Strategy and Prioritizers configurable when connecting two process > groups > - > > Key: NIFI-12077 > URL: https://issues.apache.org/jira/browse/NIFI-12077 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Reporter: Nandor Soma Abonyi >Priority: Major > > Make it possible to configure the same set of properties that are available > on the UI? Like "Load Balancing Strategy" and "Selected Prioritizers". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12077) CLI - connect two process groups, make LB Strategy and Prioritizers configurable
[ https://issues.apache.org/jira/browse/NIFI-12077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-12077: -- Fix Version/s: (was: 1.latest) (was: 2.latest) > CLI - connect two process groups, make LB Strategy and Prioritizers > configurable > > > Key: NIFI-12077 > URL: https://issues.apache.org/jira/browse/NIFI-12077 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Reporter: Nandor Soma Abonyi >Priority: Major > > Make it possible to configure the same set of properties that are available > on the UI? Like "Load Balancing Strategy" and "Selected Prioritizers". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12077) CLI - connect two process groups, make LB Strategy and Prioritizers configurable
[
https://issues.apache.org/jira/browse/NIFI-12077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandor Soma Abonyi updated NIFI-12077:
--
Description: Make it possible to configure the same set of properties that
are available on the UI? Like "Load Balancing Strategy" and "Selected
Prioritizers". (was: Add a CLI command to connect two process groups together
{code:java}
./cli.sh nifi pg-connect \
--source-pg \
--source-output-port \
--destination-pg \
--destination-input-port {code})
> CLI - connect two process groups, make LB Strategy and Prioritizers
> configurable
>
>
> Key: NIFI-12077
> URL: https://issues.apache.org/jira/browse/NIFI-12077
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Tools and Build
>Reporter: Nandor Soma Abonyi
>Priority: Major
> Fix For: 1.latest, 2.latest
>
>
> Make it possible to configure the same set of properties that are available
> on the UI? Like "Load Balancing Strategy" and "Selected Prioritizers".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (NIFI-12077) CLI - connect two process groups, make LB Strategy and Prioritizers configurable
[
https://issues.apache.org/jira/browse/NIFI-12077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandor Soma Abonyi reassigned NIFI-12077:
-
Assignee: Nandor Soma Abonyi (was: Pierre Villard)
> CLI - connect two process groups, make LB Strategy and Prioritizers
> configurable
>
>
> Key: NIFI-12077
> URL: https://issues.apache.org/jira/browse/NIFI-12077
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Tools and Build
>Reporter: Nandor Soma Abonyi
>Assignee: Nandor Soma Abonyi
>Priority: Major
> Fix For: 1.latest, 2.latest
>
>
> Add a CLI command to connect two process groups together
> {code:java}
> ./cli.sh nifi pg-connect \
> --source-pg \
> --source-output-port \
> --destination-pg \
> --destination-input-port {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (NIFI-12077) CLI - connect two process groups, make LB Strategy and Prioritizers configurable
Nandor Soma Abonyi created NIFI-12077:
-
Summary: CLI - connect two process groups, make LB Strategy and
Prioritizers configurable
Key: NIFI-12077
URL: https://issues.apache.org/jira/browse/NIFI-12077
Project: Apache NiFi
Issue Type: Improvement
Components: Tools and Build
Reporter: Nandor Soma Abonyi
Assignee: Pierre Villard
Fix For: 1.latest, 2.latest
Add a CLI command to connect two process groups together
{code:java}
./cli.sh nifi pg-connect \
--source-pg \
--source-output-port \
--destination-pg \
--destination-input-port {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (NIFI-12077) CLI - connect two process groups, make LB Strategy and Prioritizers configurable
[
https://issues.apache.org/jira/browse/NIFI-12077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandor Soma Abonyi reassigned NIFI-12077:
-
Assignee: (was: Nandor Soma Abonyi)
> CLI - connect two process groups, make LB Strategy and Prioritizers
> configurable
>
>
> Key: NIFI-12077
> URL: https://issues.apache.org/jira/browse/NIFI-12077
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Tools and Build
>Reporter: Nandor Soma Abonyi
>Priority: Major
> Fix For: 1.latest, 2.latest
>
>
> Add a CLI command to connect two process groups together
> {code:java}
> ./cli.sh nifi pg-connect \
> --source-pg \
> --source-output-port \
> --destination-pg \
> --destination-input-port {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-11940) Unable to configure SLLContext on GetSplunk
[ https://issues.apache.org/jira/browse/NIFI-11940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761907#comment-17761907 ] Nandor Soma Abonyi edited comment on NIFI-11940 at 9/4/23 11:01 PM: [~mac388], I've created a fix, but I wonder if you could test it before releasing 1.24. Building NiFi from the main branch works for you? Draft PR: [https://github.com/apache/nifi/pull/7668] was (Author: sabonyi): [~mac388], I've created a fix, but I wonder if you could test it before releasing 1.24. Building NiFi from the main branch works for you? > Unable to configure SLLContext on GetSplunk > --- > > Key: NIFI-11940 > URL: https://issues.apache.org/jira/browse/NIFI-11940 > Project: Apache NiFi > Issue Type: Bug > Components: Configuration >Affects Versions: 1.23.0 >Reporter: Miles >Assignee: Nandor Soma Abonyi >Priority: Blocker > > GetSplunk processor does not have SSLContext Parameters available - this > causes PKIX cert path errors when attempting to use GetSplunk with HTTPS > configurations. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11940) Unable to configure SLLContext on GetSplunk
[ https://issues.apache.org/jira/browse/NIFI-11940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-11940: -- Summary: Unable to configure SLLContext on GetSplunk (was: Unable to configure SLLGetSplunk) > Unable to configure SLLContext on GetSplunk > --- > > Key: NIFI-11940 > URL: https://issues.apache.org/jira/browse/NIFI-11940 > Project: Apache NiFi > Issue Type: Bug > Components: Configuration >Affects Versions: 1.23.0 >Reporter: Miles >Assignee: Nandor Soma Abonyi >Priority: Blocker > > GetSplunk processor does not have SSLContext Parameters available - this > causes PKIX cert path errors when attempting to use GetSplunk with HTTPS > configurations. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11940) Unable to configure SLLGetSplunk
[ https://issues.apache.org/jira/browse/NIFI-11940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-11940: -- Summary: Unable to configure SLLGetSplunk (was: GetSplunk) > Unable to configure SLLGetSplunk > > > Key: NIFI-11940 > URL: https://issues.apache.org/jira/browse/NIFI-11940 > Project: Apache NiFi > Issue Type: Bug > Components: Configuration >Affects Versions: 1.23.0 >Reporter: Miles >Assignee: Nandor Soma Abonyi >Priority: Blocker > > GetSplunk processor does not have SSLContext Parameters available - this > causes PKIX cert path errors when attempting to use GetSplunk with HTTPS > configurations. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-11940) GetSplunk
[ https://issues.apache.org/jira/browse/NIFI-11940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi reassigned NIFI-11940: - Assignee: Nandor Soma Abonyi > GetSplunk > - > > Key: NIFI-11940 > URL: https://issues.apache.org/jira/browse/NIFI-11940 > Project: Apache NiFi > Issue Type: Bug > Components: Configuration >Affects Versions: 1.23.0 >Reporter: Miles >Assignee: Nandor Soma Abonyi >Priority: Blocker > > GetSplunk processor does not have SSLContext Parameters available - this > causes PKIX cert path errors when attempting to use GetSplunk with HTTPS > configurations. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-11940) GetSplunk
[ https://issues.apache.org/jira/browse/NIFI-11940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761907#comment-17761907 ] Nandor Soma Abonyi commented on NIFI-11940: --- [~mac388], I've created a fix, but I wonder if you could test it before releasing 1.24. Building NiFi from the main branch works for you? > GetSplunk > - > > Key: NIFI-11940 > URL: https://issues.apache.org/jira/browse/NIFI-11940 > Project: Apache NiFi > Issue Type: Bug > Components: Configuration >Affects Versions: 1.23.0 >Reporter: Miles >Priority: Blocker > > GetSplunk processor does not have SSLContext Parameters available - this > causes PKIX cert path errors when attempting to use GetSplunk with HTTPS > configurations. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12022) Minor refactor to extract verification logic from JMSConnectionFactoryProvider
Nandor Soma Abonyi created NIFI-12022: - Summary: Minor refactor to extract verification logic from JMSConnectionFactoryProvider Key: NIFI-12022 URL: https://issues.apache.org/jira/browse/NIFI-12022 Project: Apache NiFi Issue Type: Improvement Components: Extensions Reporter: Nandor Soma Abonyi Assignee: Nandor Soma Abonyi -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-11999) Update netty.4.version to 4.1.97.Final
[ https://issues.apache.org/jira/browse/NIFI-11999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi resolved NIFI-11999. --- Fix Version/s: 2.0.0 1.24.0 Resolution: Fixed > Update netty.4.version to 4.1.97.Final > -- > > Key: NIFI-11999 > URL: https://issues.apache.org/jira/browse/NIFI-11999 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.23.2 >Reporter: Mike R >Assignee: Mike R >Priority: Major > Fix For: 2.0.0, 1.24.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Update netty.4.version to 4.1.97.Final -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-11998) Update spring.data.redis.version to 2.7.15
[ https://issues.apache.org/jira/browse/NIFI-11998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi resolved NIFI-11998. --- Fix Version/s: 2.0.0 1.24.0 Resolution: Fixed > Update spring.data.redis.version to 2.7.15 > -- > > Key: NIFI-11998 > URL: https://issues.apache.org/jira/browse/NIFI-11998 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.23.2 >Reporter: Mike R >Assignee: Mike R >Priority: Major > Fix For: 2.0.0, 1.24.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Update spring.data.redis.version to 2.7.15 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-11997) Update spring.security.version to 5.8.6
[ https://issues.apache.org/jira/browse/NIFI-11997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi resolved NIFI-11997. --- Fix Version/s: 2.0.0 1.24.0 Resolution: Fixed > Update spring.security.version to 5.8.6 > --- > > Key: NIFI-11997 > URL: https://issues.apache.org/jira/browse/NIFI-11997 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.23.2 >Reporter: Mike R >Assignee: Mike R >Priority: Major > Fix For: 2.0.0, 1.24.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Update spring.security.version to 5.8.6 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11987) PutAzureBlobStorage_v12 using FileResourceService may fail with OutOfMemoryError
[
https://issues.apache.org/jira/browse/NIFI-11987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandor Soma Abonyi updated NIFI-11987:
--
Fix Version/s: 2.0.0
1.24.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> PutAzureBlobStorage_v12 using FileResourceService may fail with
> OutOfMemoryError
>
>
> Key: NIFI-11987
> URL: https://issues.apache.org/jira/browse/NIFI-11987
> Project: Apache NiFi
> Issue Type: Bug
>Reporter: Peter Turcsanyi
>Assignee: Peter Turcsanyi
>Priority: Major
> Fix For: 2.0.0, 1.24.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> NIFI-11758 introduced FileResourceService used by PutAzureBlobStorage_v12 for
> loading the input file directly from disk (skipping content repository).
> In case of direct file access, the Azure client lib uses
> {{java.nio.FileChannel}} with {{MappedByteBuffer}}-s allocated in the native
> memory. The [default buffer size is 4096
> bytes|https://github.com/Azure/azure-sdk-for-java/blob/eedfd0ad9db9ee38a0f12943de647267d0649396/sdk/core/azure-core/src/main/java/com/azure/core/util/FluxUtil.java#L257-L259]
> which is too small for large files. The library loads the first 256 MB (by
> default) of the input file in order to decide single vs multiple upload. It
> means 256 MB / 4K = 65536 chunks in native memory which may exceed
> {{vm.max_map_count}} limit on Linux (e.g. it is 65530 by default on RedHat 8
> and Ubuntu 22.04). The result is OutOfMemoryError:
> {code:java}
> 2023-08-21 16:12:36,751 ERROR
> org.apache.nifi.processors.azure.storage.PutAzureBlobStorage_v12:
> PutAzureBlobStorage_v12[id=f8fe3228-0189-1000--3f4dc44d] Failed to
> create blob on Azure Blob Storage
> reactor.core.Exceptions$ReactiveException: java.io.IOException: Map failed
> at reactor.core.Exceptions.propagate(Exceptions.java:396)
> at
> reactor.core.publisher.BlockingSingleSubscriber.blockingGet(BlockingSingleSubscriber.java:97)
> at reactor.core.publisher.Mono.block(Mono.java:1742)
> at
> com.azure.storage.common.implementation.StorageImplUtils.blockWithOptionalTimeout(StorageImplUtils.java:129)
> at
> com.azure.storage.blob.BlobClient.uploadWithResponse(BlobClient.java:337)
> at
> org.apache.nifi.processors.azure.storage.PutAzureBlobStorage_v12.onTrigger(PutAzureBlobStorage_v12.java:204)
> at
> org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
> at
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1360)
> at
> org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:246)
> at
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:102)
> at org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:750)
> Suppressed: java.lang.Exception: #block terminated with an error
> at
> reactor.core.publisher.BlockingSingleSubscriber.blockingGet(BlockingSingleSubscriber.java:99)
> ... 16 common frames omitted
> Caused by: java.io.IOException: Map failed
> at sun.nio.ch.FileChannelImpl.map(FileChannelImpl.java:938)
> at
> com.azure.core.util.FluxUtil.lambda$toFluxByteBuffer$4(FluxUtil.java:276)
> at
> reactor.core.publisher.FluxGenerate$GenerateSubscription.slowPath(FluxGenerate.java:271)
> at
> reactor.core.publisher.FluxGenerate$GenerateSubscription.request(FluxGenerate.java:213)
> at
> reactor.core.publisher.FluxFilterFuseable$FilterFuseableSubscriber.request(FluxFilterFuseable.java:191)
> at
> reactor.core.publisher.FluxConcatMapNoPrefetch$FluxConcatMapNoPrefetchSubscriber.request(FluxConcatMapNoPrefetch.java:336)
> at
> reactor.core.publisher.FluxSwitchOnFirst$AbstractSwitchOnFirstMain.onSubscribe(FluxSwitchOnFirst.java:499)
> at
> reactor.core.publisher.FluxConcatMapNoPrefetch$FluxConcatMapNoPrefetchSubscriber.onSubscribe(FluxConcatMapNoPrefetch.java:164)
>
[jira] [Updated] (NIFI-11912) Add to StandardOauth2AccessTokenProvider controller service the possibility to choose a Proxy Configuration Service
[ https://issues.apache.org/jira/browse/NIFI-11912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-11912: -- Fix Version/s: 1.latest 2.latest > Add to StandardOauth2AccessTokenProvider controller service the possibility > to choose a Proxy Configuration Service > > > Key: NIFI-11912 > URL: https://issues.apache.org/jira/browse/NIFI-11912 > Project: Apache NiFi > Issue Type: New Feature > Components: Core Framework >Affects Versions: 1.23.0 >Reporter: Andrea Molteni >Assignee: Nandor Soma Abonyi >Priority: Major > Fix For: 1.latest, 2.latest > > Time Spent: 10m > Remaining Estimate: 0h > > Actually the StandardOauth2AccessTokenProvider is not able to use a Proxy > configuration service controller. > As a result connectivity when requesting a Token does not work and the > StandardOauth2AccessTokenProvider returns a timeout. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11912) Add to StandardOauth2AccessTokenProvider controller service the possibility to choose a Proxy Configuration Service
[ https://issues.apache.org/jira/browse/NIFI-11912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-11912: -- Status: Patch Available (was: In Progress) > Add to StandardOauth2AccessTokenProvider controller service the possibility > to choose a Proxy Configuration Service > > > Key: NIFI-11912 > URL: https://issues.apache.org/jira/browse/NIFI-11912 > Project: Apache NiFi > Issue Type: New Feature > Components: Core Framework >Affects Versions: 1.23.0 >Reporter: Andrea Molteni >Assignee: Nandor Soma Abonyi >Priority: Major > Fix For: 1.latest, 2.latest > > Time Spent: 10m > Remaining Estimate: 0h > > Actually the StandardOauth2AccessTokenProvider is not able to use a Proxy > configuration service controller. > As a result connectivity when requesting a Token does not work and the > StandardOauth2AccessTokenProvider returns a timeout. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-11912) Add to StandardOauth2AccessTokenProvider controller service the possibility to choose a Proxy Configuration Service
[ https://issues.apache.org/jira/browse/NIFI-11912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi reassigned NIFI-11912: - Assignee: Nandor Soma Abonyi > Add to StandardOauth2AccessTokenProvider controller service the possibility > to choose a Proxy Configuration Service > > > Key: NIFI-11912 > URL: https://issues.apache.org/jira/browse/NIFI-11912 > Project: Apache NiFi > Issue Type: New Feature > Components: Core Framework >Affects Versions: 1.23.0 >Reporter: Andrea Molteni >Assignee: Nandor Soma Abonyi >Priority: Major > > Actually the StandardOauth2AccessTokenProvider is not able to use a Proxy > configuration service controller. > As a result connectivity when requesting a Token does not work and the > StandardOauth2AccessTokenProvider returns a timeout. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11848) Allocate unused port in TlsCertificateAuthorityTest
[ https://issues.apache.org/jira/browse/NIFI-11848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-11848: -- Labels: toolkit (was: ) > Allocate unused port in TlsCertificateAuthorityTest > --- > > Key: NIFI-11848 > URL: https://issues.apache.org/jira/browse/NIFI-11848 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Nandor Soma Abonyi >Assignee: Nandor Soma Abonyi >Priority: Minor > Labels: toolkit > > To eliminate intermittent failures due to port collision. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11848) Allocate unused port in TlsCertificateAuthorityTest
Nandor Soma Abonyi created NIFI-11848: - Summary: Allocate unused port in TlsCertificateAuthorityTest Key: NIFI-11848 URL: https://issues.apache.org/jira/browse/NIFI-11848 Project: Apache NiFi Issue Type: Improvement Reporter: Nandor Soma Abonyi Assignee: Nandor Soma Abonyi To eliminate intermittent failures due to port collision. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-11818) Update snappy-java to 1.1.10.2
[ https://issues.apache.org/jira/browse/NIFI-11818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi resolved NIFI-11818. --- Fix Version/s: 2.0.0 1.23.0 Resolution: Fixed > Update snappy-java to 1.1.10.2 > -- > > Key: NIFI-11818 > URL: https://issues.apache.org/jira/browse/NIFI-11818 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.22.0 >Reporter: Mike R >Assignee: Mike R >Priority: Major > Fix For: 2.0.0, 1.23.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Update snappy-java to 1.1.10.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11758) Add local file upload option in PutAzure*Storage processors
[ https://issues.apache.org/jira/browse/NIFI-11758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-11758: -- Fix Version/s: 2.0.0 1.23.0 Resolution: Fixed Status: Resolved (was: Patch Available) > Add local file upload option in PutAzure*Storage processors > --- > > Key: NIFI-11758 > URL: https://issues.apache.org/jira/browse/NIFI-11758 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Peter Turcsanyi >Assignee: Peter Turcsanyi >Priority: Major > Fix For: 2.0.0, 1.23.0 > > Time Spent: 2h 40m > Remaining Estimate: 0h > > There are cases when the files to be uploaded to Azure Storage are available > on the local filesystem where NiFi is running. That is, the flow could read > and upload the files directly from the filesystem without adding it in NiFi's > content repo which is an overhead in this case (can be relevant for huge > files). > Add "Data to Upload" property with options "FlowFile's Content" (default, > current behaviour) and "Local File". Using the latter, the user can by-pass > the content repo and upload the file from the local filesystem to Azure > Storage directly. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-11592) JSONTreeReader behaving different between V1.21 and V1.18
[
https://issues.apache.org/jira/browse/NIFI-11592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17742733#comment-17742733
]
Nandor Soma Abonyi commented on NIFI-11592:
---
[~ollyhank] I couldn't reproduce the issue either upstream or on 1.22. On these
versions, it works as expected. Can you verify whether your flow works on 1.22?
Attaching my test flow. [^NIFI-11592.json]Also, please note that schema
inference has limitations and should not be used in production.
> JSONTreeReader behaving different between V1.21 and V1.18
> -
>
> Key: NIFI-11592
> URL: https://issues.apache.org/jira/browse/NIFI-11592
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.21.0
>Reporter: Olly Hancock
>Assignee: Nandor Soma Abonyi
>Priority: Major
> Attachments: NIFI-11592.json
>
>
> When parsing a json array with a json tree reader (in this case using convert
> record), I am presented with this error, this testing was done in Nifi
> Version 1.21.0. However this error never occurs in Version 1.18.0.
> !https://community.cloudera.com/t5/image/serverpage/image-id/37634i431F02226471E286/image-size/medium?v=v2&px=400!
> An example of json that fails in 1.21.0 that works in 1.18.0
>
> {code:java}
> [
> {"a": [ {"b": [{}]}]},
> {"a": [ {"b": []}]}
> ] {code}
>
> Any help would be greatly appreciated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-11592) JSONTreeReader behaving different between V1.21 and V1.18
[
https://issues.apache.org/jira/browse/NIFI-11592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17742733#comment-17742733
]
Nandor Soma Abonyi edited comment on NIFI-11592 at 7/13/23 9:33 AM:
[~ollyhank] I couldn't reproduce the issue either upstream or on 1.22. On these
versions, it works as expected. Can you verify whether your flow works on 1.22?
Attaching my test flow. [^NIFI-11592.json]Also, please note that schema
inference has limitations and should not be used in production.
was (Author: sabonyi):
[~ollyhank] I couldn't reproduce the issue either upstream or on 1.22. On these
versions, it works as expected. Can you verify whether your flow works on 1.22?
Attaching my test flow. [^NIFI-11592.json]Also, please note that schema
inference has limitations and should not be used in production.
> JSONTreeReader behaving different between V1.21 and V1.18
> -
>
> Key: NIFI-11592
> URL: https://issues.apache.org/jira/browse/NIFI-11592
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.21.0
>Reporter: Olly Hancock
>Assignee: Nandor Soma Abonyi
>Priority: Major
> Attachments: NIFI-11592.json
>
>
> When parsing a json array with a json tree reader (in this case using convert
> record), I am presented with this error, this testing was done in Nifi
> Version 1.21.0. However this error never occurs in Version 1.18.0.
> !https://community.cloudera.com/t5/image/serverpage/image-id/37634i431F02226471E286/image-size/medium?v=v2&px=400!
> An example of json that fails in 1.21.0 that works in 1.18.0
>
> {code:java}
> [
> {"a": [ {"b": [{}]}]},
> {"a": [ {"b": []}]}
> ] {code}
>
> Any help would be greatly appreciated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-11592) JSONTreeReader behaving different between V1.21 and V1.18
[
https://issues.apache.org/jira/browse/NIFI-11592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandor Soma Abonyi updated NIFI-11592:
--
Attachment: NIFI-11592.json
> JSONTreeReader behaving different between V1.21 and V1.18
> -
>
> Key: NIFI-11592
> URL: https://issues.apache.org/jira/browse/NIFI-11592
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.21.0
>Reporter: Olly Hancock
>Assignee: Nandor Soma Abonyi
>Priority: Major
> Attachments: NIFI-11592.json
>
>
> When parsing a json array with a json tree reader (in this case using convert
> record), I am presented with this error, this testing was done in Nifi
> Version 1.21.0. However this error never occurs in Version 1.18.0.
> !https://community.cloudera.com/t5/image/serverpage/image-id/37634i431F02226471E286/image-size/medium?v=v2&px=400!
> An example of json that fails in 1.21.0 that works in 1.18.0
>
> {code:java}
> [
> {"a": [ {"b": [{}]}]},
> {"a": [ {"b": []}]}
> ] {code}
>
> Any help would be greatly appreciated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-11592) JSONTreeReader behaving different between V1.21 and V1.18
[
https://issues.apache.org/jira/browse/NIFI-11592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17742688#comment-17742688
]
Nandor Soma Abonyi commented on NIFI-11592:
---
Hi [~ollyhank]! I'm going to investigate this.
> JSONTreeReader behaving different between V1.21 and V1.18
> -
>
> Key: NIFI-11592
> URL: https://issues.apache.org/jira/browse/NIFI-11592
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.21.0
>Reporter: Olly Hancock
>Assignee: Nandor Soma Abonyi
>Priority: Major
>
> When parsing a json array with a json tree reader (in this case using convert
> record), I am presented with this error, this testing was done in Nifi
> Version 1.21.0. However this error never occurs in Version 1.18.0.
> !https://community.cloudera.com/t5/image/serverpage/image-id/37634i431F02226471E286/image-size/medium?v=v2&px=400!
> An example of json that fails in 1.21.0 that works in 1.18.0
>
> {code:java}
> [
> {"a": [ {"b": [{}]}]},
> {"a": [ {"b": []}]}
> ] {code}
>
> Any help would be greatly appreciated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (NIFI-11592) JSONTreeReader behaving different between V1.21 and V1.18
[
https://issues.apache.org/jira/browse/NIFI-11592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandor Soma Abonyi reassigned NIFI-11592:
-
Assignee: Nandor Soma Abonyi
> JSONTreeReader behaving different between V1.21 and V1.18
> -
>
> Key: NIFI-11592
> URL: https://issues.apache.org/jira/browse/NIFI-11592
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.21.0
>Reporter: Olly Hancock
>Assignee: Nandor Soma Abonyi
>Priority: Major
>
> When parsing a json array with a json tree reader (in this case using convert
> record), I am presented with this error, this testing was done in Nifi
> Version 1.21.0. However this error never occurs in Version 1.18.0.
> !https://community.cloudera.com/t5/image/serverpage/image-id/37634i431F02226471E286/image-size/medium?v=v2&px=400!
> An example of json that fails in 1.21.0 that works in 1.18.0
>
> {code:java}
> [
> {"a": [ {"b": [{}]}]},
> {"a": [ {"b": []}]}
> ] {code}
>
> Any help would be greatly appreciated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (NIFI-11796) Upgrade Avro from 1.11.1 to 1.11.2
[ https://issues.apache.org/jira/browse/NIFI-11796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi resolved NIFI-11796. --- Fix Version/s: 2.0.0 1.23.0 (was: 1.latest) (was: 2.latest) Resolution: Fixed > Upgrade Avro from 1.11.1 to 1.11.2 > -- > > Key: NIFI-11796 > URL: https://issues.apache.org/jira/browse/NIFI-11796 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Nándor Soma Abonyi >Assignee: Nandor Soma Abonyi >Priority: Minor > Fix For: 2.0.0, 1.23.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11796) Upgrade Avro from 1.11.1 to 1.11.2
[ https://issues.apache.org/jira/browse/NIFI-11796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-11796: -- Fix Version/s: 1.latest 2.latest > Upgrade Avro from 1.11.1 to 1.11.2 > -- > > Key: NIFI-11796 > URL: https://issues.apache.org/jira/browse/NIFI-11796 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Nándor Soma Abonyi >Assignee: Nandor Soma Abonyi >Priority: Minor > Fix For: 1.latest, 2.latest > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-11796) Upgrade Avro from 1.11.1 to 1.11.2
[ https://issues.apache.org/jira/browse/NIFI-11796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi reassigned NIFI-11796: - Assignee: Nandor Soma Abonyi > Upgrade Avro from 1.11.1 to 1.11.2 > -- > > Key: NIFI-11796 > URL: https://issues.apache.org/jira/browse/NIFI-11796 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Nándor Soma Abonyi >Assignee: Nandor Soma Abonyi >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11750) Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide
[ https://issues.apache.org/jira/browse/NIFI-11750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-11750: -- Description: Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide to reflect the current situation. The main reasons that indicated the change: - homebrew moved to /opt/homebrew from /usr/local/Cellar which changed the config location of dnsmasq. - nifi.sensitive.props.key wasn't part of the guide - it is better to use a separate location to store configs instead of littering the toolkit directory - asciidoc supports formatting xml which is better than an image when we need to copy paste the config was: Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide to reflect the current situation. The main reasons that indicated the change: - homebrew moved to /opt/homebrew from /usr/local/Cellar which changed the config location of dnsmasq. - nifi.sensitive.props.key wasn't part of the guide - it is better to use a separate location to store configs instead of littering the toolkit directory > Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide > > > Key: NIFI-11750 > URL: https://issues.apache.org/jira/browse/NIFI-11750 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation & Website >Reporter: Nandor Soma Abonyi >Assignee: Nandor Soma Abonyi >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide > to reflect the current situation. > The main reasons that indicated the change: > - homebrew moved to /opt/homebrew from /usr/local/Cellar which changed the > config location of dnsmasq. > - nifi.sensitive.props.key wasn't part of the guide > - it is better to use a separate location to store configs instead of > littering the toolkit directory > - asciidoc supports formatting xml which is better than an image when we > need to copy paste the config > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11750) Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide
[ https://issues.apache.org/jira/browse/NIFI-11750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-11750: -- Description: Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide to reflect the current situation. The main reasons that indicated the change: - homebrew moved to /opt/homebrew from /usr/local/Cellar which changed the config location of dnsmasq. - nifi.sensitive.props.key wasn't part of the guide - it is better to use a separate location to store configs instead of littering the toolkit directory was: Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide to reflect the current situation. The main reasons that indicated the change: - homebrew moved to /opt/homebrew from /usr/local/Cellar which changed the config location of dnsmasq. - nifi.sensitive.props.key wasn't part of the guide > Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide > > > Key: NIFI-11750 > URL: https://issues.apache.org/jira/browse/NIFI-11750 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation & Website >Reporter: Nandor Soma Abonyi >Assignee: Nandor Soma Abonyi >Priority: Minor > > Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide > to reflect the current situation. > The main reasons that indicated the change: > - homebrew moved to /opt/homebrew from /usr/local/Cellar which changed the > config location of dnsmasq. > - nifi.sensitive.props.key wasn't part of the guide > - it is better to use a separate location to store configs instead of > littering the toolkit directory > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11750) Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide
Nandor Soma Abonyi created NIFI-11750: - Summary: Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide Key: NIFI-11750 URL: https://issues.apache.org/jira/browse/NIFI-11750 Project: Apache NiFi Issue Type: Improvement Components: Documentation & Website Reporter: Nandor Soma Abonyi Assignee: Nandor Soma Abonyi Update the "Creating and Securing a NiFi Cluster with the TLS Toolkit" guide to reflect the current situation. The main reasons that indicated the change: - homebrew moved to /opt/homebrew from /usr/local/Cellar which changed the config location of dnsmasq. - nifi.sensitive.props.key wasn't part of the guide -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11673) Remove Legacy TLS Versions from Shared Configuration
[
https://issues.apache.org/jira/browse/NIFI-11673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandor Soma Abonyi updated NIFI-11673:
--
Fix Version/s: 2.0.0
(was: 2.latest)
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Remove Legacy TLS Versions from Shared Configuration
>
>
> Key: NIFI-11673
> URL: https://issues.apache.org/jira/browse/NIFI-11673
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
> Fix For: 2.0.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The {{TlsConfiguration}} interface and referencing components include logic
> specific to Java 8 and 11, in addition to referencing legacy version of the
> TLS protocol. Modern Java distributions disallow TLS 1.0 and 1.1 in the
> default {{java.security}} configuration, and with NiFi 2.0 removing support
> for Java 8, version-based protocol selection can be removed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-11736) NAR Maven release process documentation
[ https://issues.apache.org/jira/browse/NIFI-11736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-11736: -- Status: Patch Available (was: Open) > NAR Maven release process documentation > --- > > Key: NIFI-11736 > URL: https://issues.apache.org/jira/browse/NIFI-11736 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation & Website >Reporter: Nandor Soma Abonyi >Assignee: Nandor Soma Abonyi >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > Create documentation that describes the release process of NAR Maven Plugin. > These pages were used as an example: > [https://cwiki.apache.org/confluence/display/NIFIREG/Releasing+NiFi+Registry] > [https://nifi.apache.org/release-guide.html] > > Deprecate NiFi Registry release guide since it is no longer released > separately. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11609) Support Request-Response pattern in MQTT5 Processors
[ https://issues.apache.org/jira/browse/NIFI-11609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-11609: -- Status: Patch Available (was: Open) > Support Request-Response pattern in MQTT5 Processors > > > Key: NIFI-11609 > URL: https://issues.apache.org/jira/browse/NIFI-11609 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: Nandor Soma Abonyi >Assignee: Nandor Soma Abonyi >Priority: Major > Labels: mqtt > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-11449) add autocommit property to PutDatabaseRecord processor
[
https://issues.apache.org/jira/browse/NIFI-11449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17736060#comment-17736060
]
Nandor Soma Abonyi commented on NIFI-11449:
---
Hi [~Abdelrahimk]!
We have a dedicated processor called PutIceberg
([https://github.com/apache/nifi/blob/adb8420b484a971103d4d5e5017cab228c5c56de/nifi-nar-bundles/nifi-iceberg-bundle/nifi-iceberg-processors/src/main/java/org/apache/nifi/processors/iceberg/PutIceberg.java#L79]).
Any chance that you've tried it already?
> add autocommit property to PutDatabaseRecord processor
> --
>
> Key: NIFI-11449
> URL: https://issues.apache.org/jira/browse/NIFI-11449
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
>Affects Versions: 1.21.0
> Environment: Any Nifi Deployment
>Reporter: Abdelrahim Ahmad
>Priority: Blocker
> Labels: Trino, autocommit, database, iceberg, putdatabaserecord
>
> The issue is with the {{PutDatabaseRecord}} processor in Apache NiFi. When
> using the processor with the Trino-JDBC-Driver or Dremio-JDBC-Driver to write
> to an Iceberg catalog, it disables the autocommit feature. This leads to
> errors such as "{*}Catalog only supports writes using autocommit: iceberg{*}".
> the autocommit feature needs to be added in the processor to be
> enabled/disabled.
> enabling auto-commit in the Nifi PutDatabaseRecord processor is important for
> Deltalake, Iceberg, and Hudi as it ensures data consistency and integrity by
> allowing atomic writes to be performed in the underlying database. This will
> allow the process to be widely used with bigger range of databases.
> _Improving this processor will allow Nifi to be the main tool to ingest data
> into these new Technologies. So we don't have to deal with another tool to do
> so._
> +*_{color:#de350b}BUT:{color}_*+
> I have reviewed The {{PutDatabaseRecord}} processor in NiFi. It inserts
> records one by one into the database using a prepared statement, and commits
> the transaction at the end of the loop that processes each record. This
> approach can be inefficient and slow when inserting large volumes of data
> into tables that are optimized for bulk ingestion, such as Delta Lake,
> Iceberg, and Hudi tables.
> These tables use various techniques to optimize the performance of bulk
> ingestion, such as partitioning, clustering, and indexing. Inserting records
> one by one using a prepared statement can bypass these optimizations, leading
> to poor performance and potentially causing issues such as excessive disk
> usage, increased memory consumption, and decreased query performance.
> To avoid these issues, it is recommended to have a new processor, or add
> feature to the current one, to bulk insert method with AutoCommit feature
> when inserting large volumes of data into Delta Lake, Iceberg, and Hudi
> tables.
>
> P.S.: using PutSQL is not a have autoCommit but have the same performance
> problem described above..
> Thanks and best regards :)
> Abdelrahim Ahmad
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (NIFI-11736) NAR Maven release process documentation
Nandor Soma Abonyi created NIFI-11736: - Summary: NAR Maven release process documentation Key: NIFI-11736 URL: https://issues.apache.org/jira/browse/NIFI-11736 Project: Apache NiFi Issue Type: Improvement Components: Documentation & Website Reporter: Nandor Soma Abonyi Assignee: Nandor Soma Abonyi Create documentation that describes the release process of NAR Maven Plugin. These pages were used as an example: [https://cwiki.apache.org/confluence/display/NIFIREG/Releasing+NiFi+Registry] [https://nifi.apache.org/release-guide.html] Deprecate NiFi Registry release guide since it is no longer released separately. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11708) Upgrade snowflake-ingest-sdk to 2.0.1 and snowflake-jdbc to 3.13.33
[ https://issues.apache.org/jira/browse/NIFI-11708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-11708: -- Fix Version/s: 2.0.0 1.23.0 Resolution: Fixed Status: Resolved (was: Patch Available) > Upgrade snowflake-ingest-sdk to 2.0.1 and snowflake-jdbc to 3.13.33 > --- > > Key: NIFI-11708 > URL: https://issues.apache.org/jira/browse/NIFI-11708 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Peter Turcsanyi >Assignee: Peter Turcsanyi >Priority: Major > Fix For: 2.0.0, 1.23.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11718) Update NAR Maven Plugin to 1.5.1
[ https://issues.apache.org/jira/browse/NIFI-11718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-11718: -- Status: Patch Available (was: In Progress) > Update NAR Maven Plugin to 1.5.1 > > > Key: NIFI-11718 > URL: https://issues.apache.org/jira/browse/NIFI-11718 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Nandor Soma Abonyi >Assignee: Nandor Soma Abonyi >Priority: Minor > Fix For: 1.latest, 2.latest > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11718) Update NAR Maven Plugin to 1.5.1
Nandor Soma Abonyi created NIFI-11718: - Summary: Update NAR Maven Plugin to 1.5.1 Key: NIFI-11718 URL: https://issues.apache.org/jira/browse/NIFI-11718 Project: Apache NiFi Issue Type: Improvement Reporter: Nandor Soma Abonyi Assignee: Nandor Soma Abonyi Fix For: 1.latest, 2.latest -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-11688) Release Manager - Release NAR Maven Plugin 1.5.1
[ https://issues.apache.org/jira/browse/NIFI-11688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi resolved NIFI-11688. --- Resolution: Resolved > Release Manager - Release NAR Maven Plugin 1.5.1 > > > Key: NIFI-11688 > URL: https://issues.apache.org/jira/browse/NIFI-11688 > Project: Apache NiFi > Issue Type: Task > Components: Tools and Build >Reporter: Nandor Soma Abonyi >Assignee: Nandor Soma Abonyi >Priority: Major > Fix For: nifi-nar-maven-plugin-1.5.1 > > > Release Manager activities related to releasing NAR Maven Plugin 1.5.1. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11692) Fix scm tag in NiFi NAR Maven Plugin pom.xml
[ https://issues.apache.org/jira/browse/NIFI-11692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-11692: -- Fix Version/s: nifi-nar-maven-plugin-1.5.1 > Fix scm tag in NiFi NAR Maven Plugin pom.xml > > > Key: NIFI-11692 > URL: https://issues.apache.org/jira/browse/NIFI-11692 > Project: Apache NiFi > Issue Type: Task >Reporter: Nandor Soma Abonyi >Assignee: Nandor Soma Abonyi >Priority: Major > Fix For: nifi-nar-maven-plugin-1.5.1 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-11692) Fix scm tag in NiFi NAR Maven Plugin pom.xml
[ https://issues.apache.org/jira/browse/NIFI-11692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi resolved NIFI-11692. --- Resolution: Fixed > Fix scm tag in NiFi NAR Maven Plugin pom.xml > > > Key: NIFI-11692 > URL: https://issues.apache.org/jira/browse/NIFI-11692 > Project: Apache NiFi > Issue Type: Task >Reporter: Nandor Soma Abonyi >Assignee: Nandor Soma Abonyi >Priority: Major > Fix For: nifi-nar-maven-plugin-1.5.1 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11693) Fix scm tag in NiFi pom.xml
[ https://issues.apache.org/jira/browse/NIFI-11693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-11693: -- Description: On main scm tag should be HEAD. Now the release plugin sets back a wrong tag which stuck at the 1.15.0 release. > Fix scm tag in NiFi pom.xml > --- > > Key: NIFI-11693 > URL: https://issues.apache.org/jira/browse/NIFI-11693 > Project: Apache NiFi > Issue Type: Task >Reporter: Nandor Soma Abonyi >Assignee: Nandor Soma Abonyi >Priority: Minor > Fix For: 1.latest, 2.latest > > > On main scm tag should be HEAD. Now the release plugin sets back a wrong tag > which stuck at the 1.15.0 release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11693) Fix scm tag in NiFi pom.xml
Nandor Soma Abonyi created NIFI-11693: - Summary: Fix scm tag in NiFi pom.xml Key: NIFI-11693 URL: https://issues.apache.org/jira/browse/NIFI-11693 Project: Apache NiFi Issue Type: Task Reporter: Nandor Soma Abonyi Assignee: Nandor Soma Abonyi Fix For: 1.latest, 2.latest -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11692) Fix scm tag in NiFi NAR Maven Plugin pom.xml
Nandor Soma Abonyi created NIFI-11692: - Summary: Fix scm tag in NiFi NAR Maven Plugin pom.xml Key: NIFI-11692 URL: https://issues.apache.org/jira/browse/NIFI-11692 Project: Apache NiFi Issue Type: Task Reporter: Nandor Soma Abonyi Assignee: Nandor Soma Abonyi -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11324) NAR Plugin extension docs not correctly resolving overridden versions from system properties
[ https://issues.apache.org/jira/browse/NIFI-11324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-11324: -- Resolution: Fixed Status: Resolved (was: Patch Available) > NAR Plugin extension docs not correctly resolving overridden versions from > system properties > > > Key: NIFI-11324 > URL: https://issues.apache.org/jira/browse/NIFI-11324 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: nifi-nar-maven-plugin-1.3.4, > nifi-nar-maven-plugin-1.4.0, nifi-nar-maven-plugin-1.5.0 >Reporter: Bryan Bende >Assignee: Bryan Bende >Priority: Minor > Fix For: nifi-nar-maven-plugin-1.5.1 > > Time Spent: 0.5h > Remaining Estimate: 0h > > In a NAR project with a property like 1.19.1 > defined, it seems that if you build the NAR and specify > -Dnifi.version=1.20.0, it still shows trying to resolve 1.19.1 artifacts > during generation of the extension documentation, even though the final NAR > correctly has the 1.20.0 jars. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11324) NAR Plugin extension docs not correctly resolving overridden versions from system properties
[ https://issues.apache.org/jira/browse/NIFI-11324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-11324: -- Fix Version/s: nifi-nar-maven-plugin-1.5.1 > NAR Plugin extension docs not correctly resolving overridden versions from > system properties > > > Key: NIFI-11324 > URL: https://issues.apache.org/jira/browse/NIFI-11324 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: nifi-nar-maven-plugin-1.3.4, > nifi-nar-maven-plugin-1.4.0, nifi-nar-maven-plugin-1.5.0 >Reporter: Bryan Bende >Assignee: Bryan Bende >Priority: Minor > Fix For: nifi-nar-maven-plugin-1.5.1 > > Time Spent: 0.5h > Remaining Estimate: 0h > > In a NAR project with a property like 1.19.1 > defined, it seems that if you build the NAR and specify > -Dnifi.version=1.20.0, it still shows trying to resolve 1.19.1 artifacts > during generation of the extension documentation, even though the final NAR > correctly has the 1.20.0 jars. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11688) Release Manager - Release NAR Maven Plugin 1.5.1
Nandor Soma Abonyi created NIFI-11688: - Summary: Release Manager - Release NAR Maven Plugin 1.5.1 Key: NIFI-11688 URL: https://issues.apache.org/jira/browse/NIFI-11688 Project: Apache NiFi Issue Type: Task Components: Tools and Build Reporter: Nandor Soma Abonyi Assignee: Nandor Soma Abonyi Fix For: nifi-nar-maven-plugin-1.5.1 Release Manager activities related to releasing NAR Maven Plugin 1.5.1. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11683) Add Transfer a secret key section to the GPG documentation
[ https://issues.apache.org/jira/browse/NIFI-11683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-11683: -- Status: Patch Available (was: Open) > Add Transfer a secret key section to the GPG documentation > -- > > Key: NIFI-11683 > URL: https://issues.apache.org/jira/browse/NIFI-11683 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation & Website >Reporter: Nandor Soma Abonyi >Assignee: Nandor Soma Abonyi >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11683) Add Transfer a secret key section to the GPG documentation
[ https://issues.apache.org/jira/browse/NIFI-11683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-11683: -- Summary: Add Transfer a secret key section to the GPG documentation (was: Add key Transfer a secret key section to the GPG documentation) > Add Transfer a secret key section to the GPG documentation > -- > > Key: NIFI-11683 > URL: https://issues.apache.org/jira/browse/NIFI-11683 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation & Website >Reporter: Nandor Soma Abonyi >Assignee: Nandor Soma Abonyi >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11683) Add key Transfer a secret key section to the GPG documentation
Nandor Soma Abonyi created NIFI-11683: - Summary: Add key Transfer a secret key section to the GPG documentation Key: NIFI-11683 URL: https://issues.apache.org/jira/browse/NIFI-11683 Project: Apache NiFi Issue Type: Improvement Components: Documentation & Website Reporter: Nandor Soma Abonyi Assignee: Nandor Soma Abonyi -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11662) ConsumeMQTT attributes appended as record fields are null when using AvroRecordSetWriter
[ https://issues.apache.org/jira/browse/NIFI-11662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-11662: -- Description: In ConsumeMQTT when `Add attributes as fields` is true and using AvroRecordSetWriter, the appended field values are null. While they have the correct values when using JsonRecordSetWriter. (was: In ConsumeMQTT when `Add attributes as fields` is true, the appended field values are going to be null when using AvroRecordSetWriter, while they going to have the correct values when using JsonRecordSetWriter.) > ConsumeMQTT attributes appended as record fields are null when using > AvroRecordSetWriter > > > Key: NIFI-11662 > URL: https://issues.apache.org/jira/browse/NIFI-11662 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Affects Versions: 1.22.0 >Reporter: Nandor Soma Abonyi >Priority: Major > Labels: MQTT > > In ConsumeMQTT when `Add attributes as fields` is true and using > AvroRecordSetWriter, the appended field values are null. While they have the > correct values when using JsonRecordSetWriter. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11662) ConsumeMQTT attributes appended as record fields are null when using AvroRecordSetWriter
[ https://issues.apache.org/jira/browse/NIFI-11662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-11662: -- Description: In ConsumeMQTT when `Add attributes as fields` is true, the appended field values are going to be null when using AvroRecordSetWriter, while they going to have the correct values when using JsonRecordSetWriter. (was: In ConsumeMQTT when `Add attributes as fields` is true, the appended field values are going to be null when using AvroRecordSetWriter, while they have the correct values when using JsonRecordSetWriter.) > ConsumeMQTT attributes appended as record fields are null when using > AvroRecordSetWriter > > > Key: NIFI-11662 > URL: https://issues.apache.org/jira/browse/NIFI-11662 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Affects Versions: 1.22.0 >Reporter: Nandor Soma Abonyi >Priority: Major > Labels: MQTT > > In ConsumeMQTT when `Add attributes as fields` is true, the appended field > values are going to be null when using AvroRecordSetWriter, while they going > to have the correct values when using JsonRecordSetWriter. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11662) ConsumeMQTT attributes appended as record fields are null when using AvroRecordSetWriter
[ https://issues.apache.org/jira/browse/NIFI-11662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-11662: -- Description: In ConsumeMQTT when `Add attributes as fields` is true, the appended field values are going to be null when using AvroRecordSetWriter, while they have the correct values when using JsonRecordSetWriter. (was: In ConsumeMQTT when `Add attributes as fields` is true, the field values are going to be null when using AvroRecordSetWriter, while they have the correct values when using JsonRecordSetWriter.) > ConsumeMQTT attributes appended as record fields are null when using > AvroRecordSetWriter > > > Key: NIFI-11662 > URL: https://issues.apache.org/jira/browse/NIFI-11662 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Affects Versions: 1.22.0 >Reporter: Nandor Soma Abonyi >Priority: Major > Labels: MQTT > > In ConsumeMQTT when `Add attributes as fields` is true, the appended field > values are going to be null when using AvroRecordSetWriter, while they have > the correct values when using JsonRecordSetWriter. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11662) ConsumeMQTT attributes appended as record fields are null when using AvroRecordSetWriter
[ https://issues.apache.org/jira/browse/NIFI-11662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-11662: -- Affects Version/s: 1.22.0 > ConsumeMQTT attributes appended as record fields are null when using > AvroRecordSetWriter > > > Key: NIFI-11662 > URL: https://issues.apache.org/jira/browse/NIFI-11662 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Affects Versions: 1.22.0 >Reporter: Nandor Soma Abonyi >Priority: Major > Labels: MQTT > > In ConsumeMQTT when `Add attributes as fields` is true, the field values are > going to be null when using AvroRecordSetWriter, while they have the correct > values when using JsonRecordSetWriter. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11662) ConsumeMQTT attributes appended as record fields are null when using AvroRecordSetWriter
Nandor Soma Abonyi created NIFI-11662: - Summary: ConsumeMQTT attributes appended as record fields are null when using AvroRecordSetWriter Key: NIFI-11662 URL: https://issues.apache.org/jira/browse/NIFI-11662 Project: Apache NiFi Issue Type: Bug Components: Extensions Reporter: Nandor Soma Abonyi In ConsumeMQTT when `Add attributes as fields` is true, the field values are going to be null when using AvroRecordSetWriter, while they have the correct values when using JsonRecordSetWriter. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11656) Remove Deprecated Azure Queue Storage Processors and Services
[ https://issues.apache.org/jira/browse/NIFI-11656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-11656: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Remove Deprecated Azure Queue Storage Processors and Services > - > > Key: NIFI-11656 > URL: https://issues.apache.org/jira/browse/NIFI-11656 > Project: Apache NiFi > Issue Type: Task >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > With the addition of GetAzureQueueStorage_v12 and PutAzureQueueStorage_v12, > the deprecated GetAzureQueueStorage and PutAzureQueueStorage Processors > should be removed for the next major release version. > The removal of the deprecated Azure Queue Storage Processors also obviates > the need for the legacy Credentials Controller Services, so > AzureStorageCredentialsControllerService and related implementations should > be removed along with the legacy azure-storage dependency. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11659) Remove vulnerable org.codehaus.jackson dependencies to partially mitigate CVE-2019-10202
Nandor Soma Abonyi created NIFI-11659: - Summary: Remove vulnerable org.codehaus.jackson dependencies to partially mitigate CVE-2019-10202 Key: NIFI-11659 URL: https://issues.apache.org/jira/browse/NIFI-11659 Project: Apache NiFi Issue Type: Improvement Components: Core Framework, Extensions Reporter: Nandor Soma Abonyi Assignee: Nandor Soma Abonyi Fix For: 1.latest, 2.latest Removing direct org.codehaus.jackson dependencies to mitigate CVE-2019-10202 ([https://devhub.checkmarx.com/cve-details/CVE-2019-10202/?utm_source=jetbrains&utm_medium=referral&utm_campaign=idea]) Unfortunately the latest ranger dependency, still depends on it, so transitively we will still have this vulnerability. Worth to track [https://mvnrepository.com/artifact/org.apache.ranger/ranger-plugins-common] for future upgrades. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11586) Add AzureStorageCredentialsControllerServiceLookup_v12
[
https://issues.apache.org/jira/browse/NIFI-11586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandor Soma Abonyi updated NIFI-11586:
--
Component/s: Extensions
> Add AzureStorageCredentialsControllerServiceLookup_v12
> --
>
> Key: NIFI-11586
> URL: https://issues.apache.org/jira/browse/NIFI-11586
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
>Reporter: Peter Turcsanyi
>Assignee: Peter Turcsanyi
>Priority: Major
> Fix For: 2.0.0, 1.22.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Similar to {{AzureStorageCredentialsControllerServiceLookup}}, add a lookup
> service for the v12 blob processors.
> {{AzureStorageCredentialsControllerServiceLookup_v12}} will provide accessing
> {{AzureStorageCredentialsService_v12}} services dynamically based on a
> FlowFile attribute.
> The v12 blob processors contain a single client reference. In order to
> support multiple credentials (that is multiple clients), the same client
> factory / cache approach need to be implemented as in case of the ADLS
> processors (DataLakeServiceClientFactory).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-11586) Add AzureStorageCredentialsControllerServiceLookup_v12
[
https://issues.apache.org/jira/browse/NIFI-11586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandor Soma Abonyi updated NIFI-11586:
--
Labels: azure (was: )
> Add AzureStorageCredentialsControllerServiceLookup_v12
> --
>
> Key: NIFI-11586
> URL: https://issues.apache.org/jira/browse/NIFI-11586
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
>Reporter: Peter Turcsanyi
>Assignee: Peter Turcsanyi
>Priority: Major
> Labels: azure
> Fix For: 2.0.0, 1.22.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Similar to {{AzureStorageCredentialsControllerServiceLookup}}, add a lookup
> service for the v12 blob processors.
> {{AzureStorageCredentialsControllerServiceLookup_v12}} will provide accessing
> {{AzureStorageCredentialsService_v12}} services dynamically based on a
> FlowFile attribute.
> The v12 blob processors contain a single client reference. In order to
> support multiple credentials (that is multiple clients), the same client
> factory / cache approach need to be implemented as in case of the ADLS
> processors (DataLakeServiceClientFactory).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-11586) Add AzureStorageCredentialsControllerServiceLookup_v12
[
https://issues.apache.org/jira/browse/NIFI-11586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandor Soma Abonyi updated NIFI-11586:
--
Fix Version/s: 2.0.0
1.22.0
> Add AzureStorageCredentialsControllerServiceLookup_v12
> --
>
> Key: NIFI-11586
> URL: https://issues.apache.org/jira/browse/NIFI-11586
> Project: Apache NiFi
> Issue Type: New Feature
>Reporter: Peter Turcsanyi
>Assignee: Peter Turcsanyi
>Priority: Major
> Fix For: 2.0.0, 1.22.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Similar to {{AzureStorageCredentialsControllerServiceLookup}}, add a lookup
> service for the v12 blob processors.
> {{AzureStorageCredentialsControllerServiceLookup_v12}} will provide accessing
> {{AzureStorageCredentialsService_v12}} services dynamically based on a
> FlowFile attribute.
> The v12 blob processors contain a single client reference. In order to
> support multiple credentials (that is multiple clients), the same client
> factory / cache approach need to be implemented as in case of the ADLS
> processors (DataLakeServiceClientFactory).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-11586) Add AzureStorageCredentialsControllerServiceLookup_v12
[
https://issues.apache.org/jira/browse/NIFI-11586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandor Soma Abonyi updated NIFI-11586:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Add AzureStorageCredentialsControllerServiceLookup_v12
> --
>
> Key: NIFI-11586
> URL: https://issues.apache.org/jira/browse/NIFI-11586
> Project: Apache NiFi
> Issue Type: New Feature
>Reporter: Peter Turcsanyi
>Assignee: Peter Turcsanyi
>Priority: Major
> Fix For: 2.0.0, 1.22.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Similar to {{AzureStorageCredentialsControllerServiceLookup}}, add a lookup
> service for the v12 blob processors.
> {{AzureStorageCredentialsControllerServiceLookup_v12}} will provide accessing
> {{AzureStorageCredentialsService_v12}} services dynamically based on a
> FlowFile attribute.
> The v12 blob processors contain a single client reference. In order to
> support multiple credentials (that is multiple clients), the same client
> factory / cache approach need to be implemented as in case of the ADLS
> processors (DataLakeServiceClientFactory).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (NIFI-11609) Support Request-Response pattern in MQTT5 Processors
Nandor Soma Abonyi created NIFI-11609: - Summary: Support Request-Response pattern in MQTT5 Processors Key: NIFI-11609 URL: https://issues.apache.org/jira/browse/NIFI-11609 Project: Apache NiFi Issue Type: Improvement Components: Extensions Reporter: Nandor Soma Abonyi Assignee: Nandor Soma Abonyi -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11585) Add ADLSCredentialsControllerServiceLookup
[
https://issues.apache.org/jira/browse/NIFI-11585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandor Soma Abonyi updated NIFI-11585:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Add ADLSCredentialsControllerServiceLookup
> --
>
> Key: NIFI-11585
> URL: https://issues.apache.org/jira/browse/NIFI-11585
> Project: Apache NiFi
> Issue Type: New Feature
>Reporter: Peter Turcsanyi
>Assignee: Peter Turcsanyi
>Priority: Major
> Fix For: 2.0.0, 1.22.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Similar to {{AzureStorageCredentialsControllerServiceLookup}}, create a new
> lookup service called {{ADLSCredentialsControllerServiceLookup}} for
> retrieving {{ADLSCredentialsService}}-s dynamically based on a FlowFile
> attribute.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-11585) Add ADLSCredentialsControllerServiceLookup
[
https://issues.apache.org/jira/browse/NIFI-11585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandor Soma Abonyi updated NIFI-11585:
--
Fix Version/s: 2.0.0
1.22.0
> Add ADLSCredentialsControllerServiceLookup
> --
>
> Key: NIFI-11585
> URL: https://issues.apache.org/jira/browse/NIFI-11585
> Project: Apache NiFi
> Issue Type: New Feature
>Reporter: Peter Turcsanyi
>Assignee: Peter Turcsanyi
>Priority: Major
> Fix For: 2.0.0, 1.22.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Similar to {{AzureStorageCredentialsControllerServiceLookup}}, create a new
> lookup service called {{ADLSCredentialsControllerServiceLookup}} for
> retrieving {{ADLSCredentialsService}}-s dynamically based on a FlowFile
> attribute.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-11380) Refactor CaptureChangeMySQL with improvements
[ https://issues.apache.org/jira/browse/NIFI-11380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-11380: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Refactor CaptureChangeMySQL with improvements > - > > Key: NIFI-11380 > URL: https://issues.apache.org/jira/browse/NIFI-11380 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Matt Burgess >Assignee: Matt Burgess >Priority: Major > Fix For: 2.0.0, 1.22.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > The CaptureChangeMySQL processor can be improved in many ways: > - Eliminate use of DistributedCacheClient > - MySQLCDCUtils - delete this class. It’s unnecessary. Just put the single > method that exists in the parent class of the writers > - Eliminate mutable member variables. Gather all state together into an > object and store that as a single volatile member variable. > - The outputEvents method is a huge block of switch/case and if/then/else > blocks. Kill all of this. Create an interface that’s capable of handling a > given event type and have multiple implementations. Determine appropriate > impl and call the method. > - Do not keep a bunch of member variables to “rollback local state”. Keep > this in variables. If we fail, no harm, no foul. If we succeed, then update > member variable. > - Remove onStopped method, just annotate stop() method with @OnStopped. No > need for @OnShutdown > - Change name of “hostname” property to "node", and don’t require the port! > Default to 3306. > - Remove unused hasRun member variable -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11380) Refactor CaptureChangeMySQL with improvements
[ https://issues.apache.org/jira/browse/NIFI-11380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-11380: -- Fix Version/s: (was: 2.latest) 2.0.0 1.22.0 (was: 1.latest) > Refactor CaptureChangeMySQL with improvements > - > > Key: NIFI-11380 > URL: https://issues.apache.org/jira/browse/NIFI-11380 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Matt Burgess >Assignee: Matt Burgess >Priority: Major > Fix For: 2.0.0, 1.22.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > The CaptureChangeMySQL processor can be improved in many ways: > - Eliminate use of DistributedCacheClient > - MySQLCDCUtils - delete this class. It’s unnecessary. Just put the single > method that exists in the parent class of the writers > - Eliminate mutable member variables. Gather all state together into an > object and store that as a single volatile member variable. > - The outputEvents method is a huge block of switch/case and if/then/else > blocks. Kill all of this. Create an interface that’s capable of handling a > given event type and have multiple implementations. Determine appropriate > impl and call the method. > - Do not keep a bunch of member variables to “rollback local state”. Keep > this in variables. If we fail, no harm, no foul. If we succeed, then update > member variable. > - Remove onStopped method, just annotate stop() method with @OnStopped. No > need for @OnShutdown > - Change name of “hostname” property to "node", and don’t require the port! > Default to 3306. > - Remove unused hasRun member variable -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11228) Remove deprecated Azure Blob processors
[ https://issues.apache.org/jira/browse/NIFI-11228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-11228: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Remove deprecated Azure Blob processors > --- > > Key: NIFI-11228 > URL: https://issues.apache.org/jira/browse/NIFI-11228 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 2.0.0 >Reporter: Nandor Soma Abonyi >Assignee: David Handermann >Priority: Major > Labels: azure > Fix For: 2.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11524) Documentation and config experience improvement for ExecuteStreamCommand
[
https://issues.apache.org/jira/browse/NIFI-11524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandor Soma Abonyi updated NIFI-11524:
--
Status: Patch Available (was: In Progress)
> Documentation and config experience improvement for ExecuteStreamCommand
>
>
> Key: NIFI-11524
> URL: https://issues.apache.org/jira/browse/NIFI-11524
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
>Reporter: Nandor Soma Abonyi
>Assignee: Nandor Soma Abonyi
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This PR indends to add documentation for the ExecuteSteamCommand processor
> and improves the configuration experience by adding dependency between
> properties.
> I've noticed that the processor adds every Dynamic Property as environment
> variable even when it is a command argument. I didn't change this behavior
> because it might introduce a breaking change, but I'd change this behavior in
> a separate 2.0 only PR. Simply adding another regex check there would
> introduce the 4. regex check which is quite ugly so it would be a good
> opportunity for refactor. Another option would be to add validation for
> environment variables to ensure they don't contain {{{}.{}}}character,
> because most shells don't support it. But I'm not sure about that because
> there are commands that can utilize such env variables even though they are
> not common.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-11524) Documentation and config experience improvement for ExecuteStreamCommand
[
https://issues.apache.org/jira/browse/NIFI-11524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandor Soma Abonyi updated NIFI-11524:
--
Description:
This PR indends to add documentation for the ExecuteSteamCommand processor and
improves the configuration experience by adding dependency between properties.
I've noticed that the processor adds every Dynamic Property as environment
variable even when it is a command argument. I didn't change this behavior
because it might introduce a breaking change, but I'd change this behavior in a
separate 2.0 only PR. Simply adding another regex check there would introduce
the 4. regex check which is quite ugly so it would be a good opportunity for
refactor. Another option would be to add validation for environment variables
to ensure they don't contain {{{}.{}}}character, because most shells don't
support it. But I'm not sure about that because there are commands that can
utilize such env variables even though they are not common.
> Documentation and config experience improvement for ExecuteStreamCommand
>
>
> Key: NIFI-11524
> URL: https://issues.apache.org/jira/browse/NIFI-11524
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
>Reporter: Nandor Soma Abonyi
>Assignee: Nandor Soma Abonyi
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This PR indends to add documentation for the ExecuteSteamCommand processor
> and improves the configuration experience by adding dependency between
> properties.
> I've noticed that the processor adds every Dynamic Property as environment
> variable even when it is a command argument. I didn't change this behavior
> because it might introduce a breaking change, but I'd change this behavior in
> a separate 2.0 only PR. Simply adding another regex check there would
> introduce the 4. regex check which is quite ugly so it would be a good
> opportunity for refactor. Another option would be to add validation for
> environment variables to ensure they don't contain {{{}.{}}}character,
> because most shells don't support it. But I'm not sure about that because
> there are commands that can utilize such env variables even though they are
> not common.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-11524) Documentation and config experience improvement for ExecuteStreamCommand
[
https://issues.apache.org/jira/browse/NIFI-11524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandor Soma Abonyi updated NIFI-11524:
--
Fix Version/s: 1.latest
2.latest
> Documentation and config experience improvement for ExecuteStreamCommand
>
>
> Key: NIFI-11524
> URL: https://issues.apache.org/jira/browse/NIFI-11524
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
>Reporter: Nandor Soma Abonyi
>Assignee: Nandor Soma Abonyi
>Priority: Major
> Fix For: 1.latest, 2.latest
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This PR indends to add documentation for the ExecuteSteamCommand processor
> and improves the configuration experience by adding dependency between
> properties.
> I've noticed that the processor adds every Dynamic Property as environment
> variable even when it is a command argument. I didn't change this behavior
> because it might introduce a breaking change, but I'd change this behavior in
> a separate 2.0 only PR. Simply adding another regex check there would
> introduce the 4. regex check which is quite ugly so it would be a good
> opportunity for refactor. Another option would be to add validation for
> environment variables to ensure they don't contain {{{}.{}}}character,
> because most shells don't support it. But I'm not sure about that because
> there are commands that can utilize such env variables even though they are
> not common.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (NIFI-11524) Documentation and config experience improvement for ExecuteStreamCommand
Nandor Soma Abonyi created NIFI-11524: - Summary: Documentation and config experience improvement for ExecuteStreamCommand Key: NIFI-11524 URL: https://issues.apache.org/jira/browse/NIFI-11524 Project: Apache NiFi Issue Type: Improvement Components: Extensions Reporter: Nandor Soma Abonyi Assignee: Nandor Soma Abonyi -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11390) Renaming versioned process group is not detected as a change
Nandor Soma Abonyi created NIFI-11390: - Summary: Renaming versioned process group is not detected as a change Key: NIFI-11390 URL: https://issues.apache.org/jira/browse/NIFI-11390 Project: Apache NiFi Issue Type: Bug Components: Core Framework, NiFi Registry Affects Versions: 1.21.0 Reporter: Nandor Soma Abonyi Renaming a versioned process group is not detected as a change. If we modify something in the process group, for example, we move a processor, there will be one “Position changed” local change. However, if we commit after that, the name of the process group will also be changed. There are two options that I can think of: * Treat renaming as a separate local change so it is possible to commit it alone. * Treat the name of the PG local, but don’t update the name “silently” when there are other changes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-8710) StandardProvenanceReporter - receive() incorrectly overiding details parameter
[ https://issues.apache.org/jira/browse/NIFI-8710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-8710: - Resolution: Resolved Status: Resolved (was: Patch Available) > StandardProvenanceReporter - receive() incorrectly overiding details parameter > -- > > Key: NIFI-8710 > URL: https://issues.apache.org/jira/browse/NIFI-8710 > Project: Apache NiFi > Issue Type: Bug >Reporter: Nissim Shiman >Assignee: Matt Burgess >Priority: Major > Fix For: 2.0.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > The ProvenanceReporter interface has receive() with details as the third > parameter [1]: > void receive(FlowFile flowFile, String transitUri, String details, long > transmissionMillis); > StandardProvenanceReporter.java implements this with > sourceSystemFlowFileIdentifier as the third parameter [2]: > public void receive(final FlowFile flowFile, final String transitUri, final > String sourceSystemFlowFileIdentifier, final long transmissionMillis) > This implementation in StandardProvenanceReporter should be modified to > reflect the interface. > > [1] > [https://github.com/apache/nifi/blob/main/nifi-api/src/main/java/org/apache/nifi/provenance/ProvenanceReporter.java#L100] > [2] > [https://github.com/apache/nifi/blob/main/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-components/src/main/java/org/apache/nifi/controller/repository/StandardProvenanceReporter.java#L159] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-8710) StandardProvenanceReporter - receive() incorrectly overiding details parameter
[ https://issues.apache.org/jira/browse/NIFI-8710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-8710: - Fix Version/s: 2.0.0 (was: 2.latest) > StandardProvenanceReporter - receive() incorrectly overiding details parameter > -- > > Key: NIFI-8710 > URL: https://issues.apache.org/jira/browse/NIFI-8710 > Project: Apache NiFi > Issue Type: Bug >Reporter: Nissim Shiman >Assignee: Matt Burgess >Priority: Major > Fix For: 2.0.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > The ProvenanceReporter interface has receive() with details as the third > parameter [1]: > void receive(FlowFile flowFile, String transitUri, String details, long > transmissionMillis); > StandardProvenanceReporter.java implements this with > sourceSystemFlowFileIdentifier as the third parameter [2]: > public void receive(final FlowFile flowFile, final String transitUri, final > String sourceSystemFlowFileIdentifier, final long transmissionMillis) > This implementation in StandardProvenanceReporter should be modified to > reflect the interface. > > [1] > [https://github.com/apache/nifi/blob/main/nifi-api/src/main/java/org/apache/nifi/provenance/ProvenanceReporter.java#L100] > [2] > [https://github.com/apache/nifi/blob/main/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-components/src/main/java/org/apache/nifi/controller/repository/StandardProvenanceReporter.java#L159] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11350) Fix silent attribute override in ConsumeJMS
Nandor Soma Abonyi created NIFI-11350: - Summary: Fix silent attribute override in ConsumeJMS Key: NIFI-11350 URL: https://issues.apache.org/jira/browse/NIFI-11350 Project: Apache NiFi Issue Type: Bug Affects Versions: 1.20.0 Reporter: Nandor Soma Abonyi Assignee: Nandor Soma Abonyi JMS headers and properties are added to flowFile attributes in a way that, in case of collision, the header attribute will be overridden. To fix that, we need to prefix them. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11345) TestPutIcebergWithHiveCatalog Runs Longer than 60 Seconds
[
https://issues.apache.org/jira/browse/NIFI-11345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandor Soma Abonyi updated NIFI-11345:
--
Fix Version/s: 2.0.0
1.21.0
(was: 1.latest)
(was: 2.latest)
Resolution: Resolved
Status: Resolved (was: Patch Available)
> TestPutIcebergWithHiveCatalog Runs Longer than 60 Seconds
> -
>
> Key: NIFI-11345
> URL: https://issues.apache.org/jira/browse/NIFI-11345
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.20.0
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Minor
> Fix For: 2.0.0, 1.21.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The {{TestPutIcebergWithHiveCatalog}} runs multiple parameterized test
> methods that exercise three supported formats: Avro, ORC, and Parquet. Each
> test run is expensive, taking around 5 seconds, resulting in the entire class
> taking over 60 seconds to complete under optimal circumstances. Instead of
> running each method with all three formats, each method should be limited to
> one format to reduce the overall runtime.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-11266) PutGoogleDrive, ListGoogleDrive, FetchGoogleDrive can't access a SharedDrive
[ https://issues.apache.org/jira/browse/NIFI-11266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-11266: -- Resolution: Resolved Status: Resolved (was: Patch Available) > PutGoogleDrive, ListGoogleDrive, FetchGoogleDrive can't access a SharedDrive > > > Key: NIFI-11266 > URL: https://issues.apache.org/jira/browse/NIFI-11266 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Baptiste Moisson >Assignee: Zsihovszki Krisztina >Priority: Major > Fix For: 2.0.0, 1.21.0 > > Time Spent: 50m > Remaining Estimate: 0h > > It seems that Google Drive Put, Fetch and List processor are not able to > perform action on SharedDrive. > Regarding the Google Drive API > ([https://developers.google.com/drive/api/v3/reference/files/list?apix_params=%7B%22includeTeamDriveItems%22%3Afalse%2C%22supportsTeamDrives%22%3Afalse%7D)] > , it seems that options like corpora, driveId , includeItemsFromAllDrives, > supportsAllDrives should be use to perform an SharedDrive access. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11266) PutGoogleDrive, ListGoogleDrive, FetchGoogleDrive can't access a SharedDrive
[ https://issues.apache.org/jira/browse/NIFI-11266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-11266: -- Fix Version/s: 2.0.0 1.21.0 (was: 1.latest) (was: 2.latest) > PutGoogleDrive, ListGoogleDrive, FetchGoogleDrive can't access a SharedDrive > > > Key: NIFI-11266 > URL: https://issues.apache.org/jira/browse/NIFI-11266 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Baptiste Moisson >Assignee: Zsihovszki Krisztina >Priority: Major > Fix For: 2.0.0, 1.21.0 > > Time Spent: 50m > Remaining Estimate: 0h > > It seems that Google Drive Put, Fetch and List processor are not able to > perform action on SharedDrive. > Regarding the Google Drive API > ([https://developers.google.com/drive/api/v3/reference/files/list?apix_params=%7B%22includeTeamDriveItems%22%3Afalse%2C%22supportsTeamDrives%22%3Afalse%7D)] > , it seems that options like corpora, driveId , includeItemsFromAllDrives, > supportsAllDrives should be use to perform an SharedDrive access. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11270) Refactoring of the overly Paho-specific MQTT interface
[ https://issues.apache.org/jira/browse/NIFI-11270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-11270: -- Description: ConsumeMQTT processor implements the MqttClient interface, which follows the signature of the Paho library's MqttClient interface. There are two issues with that. It mixes two types of behavior because the client itself can act as a publisher and subscriber parallelly. However, in NiFi, these two roles are separated into different processors. So it doesn't make sense to implement the subscribe interface in PublishMQTT, and it also doesn't make sense to implement deliveryComplete in ConsumeMQTT. The other issue is that these interfaces cannot be used with the HiveMQ client except messageArrived(). Because of the above, we need to move the existing implementation into the Paho adapter (because it is still required for logging) and create a new interface for handling incoming messages. > Refactoring of the overly Paho-specific MQTT interface > -- > > Key: NIFI-11270 > URL: https://issues.apache.org/jira/browse/NIFI-11270 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: Nandor Soma Abonyi >Assignee: Nandor Soma Abonyi >Priority: Minor > Labels: mqtt > Fix For: 1.latest, 2.latest > > Time Spent: 50m > Remaining Estimate: 0h > > ConsumeMQTT processor implements the MqttClient interface, which follows the > signature of the Paho library's MqttClient interface. There are two issues > with that. It mixes two types of behavior because the client itself can act > as a publisher and subscriber parallelly. However, in NiFi, these two roles > are separated into different processors. So it doesn't make sense to > implement the subscribe interface in PublishMQTT, and it also doesn't make > sense to implement deliveryComplete in ConsumeMQTT. > The other issue is that these interfaces cannot be used with the HiveMQ > client except messageArrived(). Because of the above, we need to move the > existing implementation into the Paho adapter (because it is still required > for logging) and create a new interface for handling incoming messages. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11263) Add case-insensitive and order independent field mapping to PutIceberg record converter
[ https://issues.apache.org/jira/browse/NIFI-11263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi updated NIFI-11263: -- Fix Version/s: 1.21.0 > Add case-insensitive and order independent field mapping to PutIceberg record > converter > --- > > Key: NIFI-11263 > URL: https://issues.apache.org/jira/browse/NIFI-11263 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Mark Bathori >Assignee: Mark Bathori >Priority: Major > Fix For: 2.0.0, 1.21.0 > > Time Spent: 40m > Remaining Estimate: 0h > > The schema matching is currently case-sensitive, and the processor expects > the same field ordering in the incoming records and in the target Iceberg > schema. To make it less strict the field name matching should be > case-insensitive and ordering independent. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-11263) Add case-insensitive and order independent field mapping to PutIceberg record converter
[ https://issues.apache.org/jira/browse/NIFI-11263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Soma Abonyi resolved NIFI-11263. --- Fix Version/s: 2.0.0 Resolution: Resolved > Add case-insensitive and order independent field mapping to PutIceberg record > converter > --- > > Key: NIFI-11263 > URL: https://issues.apache.org/jira/browse/NIFI-11263 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Mark Bathori >Assignee: Mark Bathori >Priority: Major > Fix For: 2.0.0 > > Time Spent: 40m > Remaining Estimate: 0h > > The schema matching is currently case-sensitive, and the processor expects > the same field ordering in the incoming records and in the target Iceberg > schema. To make it less strict the field name matching should be > case-insensitive and ordering independent. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-11285) Unable to build module created by maven archetype plugin
[
https://issues.apache.org/jira/browse/NIFI-11285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17700174#comment-17700174
]
Nandor Soma Abonyi commented on NIFI-11285:
---
To test the plugin in case of services:
{code:java}
mvn archetype:generate -DarchetypeGroupId=org.apache.nifi
-DarchetypeArtifactId=nifi-service-bundle-archetype
-DarchetypeVersion=2.0.0-SNAPSHOT -DnifiVersion=2.0.0-SNAPSHOT
-DartifactBaseName=nifi-mytest-services -DgroupId=org.apache.nifi
-DartifactId=nifi-mytest-bundle -Dversion=2.0.0-SNAPSHOT
-Dpackage=org.apache.nifi.mytest {code}
In case of processors:
{code:java}
mvn archetype:generate -DarchetypeGroupId=org.apache.nifi
-DarchetypeArtifactId=nifi-processor-bundle-archetype
-DarchetypeVersion=2.0.0-SNAPSHOT -DnifiVersion=2.0.0-SNAPSHOT
-DartifactBaseName=nifi-mytest-processors -DgroupId=org.apache.nifi
-DartifactId=nifi-mytestproc-bundle -Dversion=2.0.0-SNAPSHOT
-Dpackage=org.apache.nifi.mytest{code}
> Unable to build module created by maven archetype plugin
>
>
> Key: NIFI-11285
> URL: https://issues.apache.org/jira/browse/NIFI-11285
> Project: Apache NiFi
> Issue Type: Bug
>Reporter: Nandor Soma Abonyi
>Assignee: Nandor Soma Abonyi
>Priority: Major
> Fix For: 1.latest, 2.latest
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Modules created by the archetype plugin use dependencies that are not
> imported. Also, they have check-style issues.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
