[jira] [Commented] (NIFI-13289) Add tooltip to NewCanvas item
[ https://issues.apache.org/jira/browse/NIFI-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850523#comment-17850523 ] ASF subversion and git services commented on NIFI-13289: Commit e3cf0a67bc9781ecd14dc49ed0c019ab328fce5c in nifi's branch refs/heads/main from Shane [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=e3cf0a67bc ] NIFI-13289 add tooltips to NewCanvasItem (#8870) This closes #8870 > Add tooltip to NewCanvas item > - > > Key: NIFI-13289 > URL: https://issues.apache.org/jira/browse/NIFI-13289 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Shane O'Neill >Priority: Major > Attachments: Screenshot 2024-05-23 at 2.36.55 PM.png > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Old NiFi UI had tooltips for the new canvas items in the top bar. These are > currently missing in the new UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13289) Add tooltip to NewCanvas item
[ https://issues.apache.org/jira/browse/NIFI-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Fellows updated NIFI-13289: --- Fix Version/s: 2.0.0-M4 Resolution: Fixed Status: Resolved (was: Patch Available) > Add tooltip to NewCanvas item > - > > Key: NIFI-13289 > URL: https://issues.apache.org/jira/browse/NIFI-13289 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Shane O'Neill >Priority: Major > Fix For: 2.0.0-M4 > > Attachments: Screenshot 2024-05-23 at 2.36.55 PM.png > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Old NiFi UI had tooltips for the new canvas items in the top bar. These are > currently missing in the new UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13289) Add tooltip to NewCanvas item
[ https://issues.apache.org/jira/browse/NIFI-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Fellows updated NIFI-13289: --- Status: Patch Available (was: Open) > Add tooltip to NewCanvas item > - > > Key: NIFI-13289 > URL: https://issues.apache.org/jira/browse/NIFI-13289 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Shane O'Neill >Priority: Major > Attachments: Screenshot 2024-05-23 at 2.36.55 PM.png > > Time Spent: 1h > Remaining Estimate: 0h > > Old NiFi UI had tooltips for the new canvas items in the top bar. These are > currently missing in the new UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13265) Remove the instantiation of Object arrays for arguments in ComponentLog log and org.slf4j.Logger statements
[ https://issues.apache.org/jira/browse/NIFI-13265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Stieglitz updated NIFI-13265: Priority: Major (was: Minor) > Remove the instantiation of Object arrays for arguments in ComponentLog log > and org.slf4j.Logger statements > --- > > Key: NIFI-13265 > URL: https://issues.apache.org/jira/browse/NIFI-13265 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Daniel Stieglitz >Assignee: Daniel Stieglitz >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > There are still classes after the changes in NIFI-12075 and NIFI-12076 which > instantiate an Object array for ComponentLog log statements. This ticket aims > to remove those instantiations. In addition similar changes should be made to > org.slf4j.Logger statements. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13265) Remove the instantiation of Object arrays for arguments in ComponentLog log and org.slf4j.Logger statements
[ https://issues.apache.org/jira/browse/NIFI-13265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Stieglitz updated NIFI-13265: Status: Patch Available (was: In Progress) > Remove the instantiation of Object arrays for arguments in ComponentLog log > and org.slf4j.Logger statements > --- > > Key: NIFI-13265 > URL: https://issues.apache.org/jira/browse/NIFI-13265 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Daniel Stieglitz >Assignee: Daniel Stieglitz >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > There are still classes after the changes in NIFI-12075 and NIFI-12076 which > instantiate an Object array for ComponentLog log statements. This ticket aims > to remove those instantiations. In addition similar changes should be made to > org.slf4j.Logger statements. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13299) Prevent negative numbers in concurrent tasks
[ https://issues.apache.org/jira/browse/NIFI-13299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Fellows updated NIFI-13299: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Prevent negative numbers in concurrent tasks > > > Key: NIFI-13299 > URL: https://issues.apache.org/jira/browse/NIFI-13299 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > For inputs like concurrent tasks we know that negative values are not > allowed. We should prevent them before the user can submit the form. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13299) Prevent negative numbers in concurrent tasks
[ https://issues.apache.org/jira/browse/NIFI-13299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850494#comment-17850494 ] ASF subversion and git services commented on NIFI-13299: Commit 2cd462482567e6be13cbee71b80d942933f0b68f in nifi's branch refs/heads/main from Matt Gilman [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=2cd4624825 ] NIFI-13299: (#8894) - Adding min validators where appropriate. This closes #8894 > Prevent negative numbers in concurrent tasks > > > Key: NIFI-13299 > URL: https://issues.apache.org/jira/browse/NIFI-13299 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > For inputs like concurrent tasks we know that negative values are not > allowed. We should prevent them before the user can submit the form. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-11171) Reorganize Standard Components for 2.0.0
[
https://issues.apache.org/jira/browse/NIFI-11171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann resolved NIFI-11171.
-
Fix Version/s: 2.0.0-M3
Resolution: Fixed
Marking as completed based on changes implemented up to 2.0.0-M3. Any further
changes could be considered under other issues.
> Reorganize Standard Components for 2.0.0
>
>
> Key: NIFI-11171
> URL: https://issues.apache.org/jira/browse/NIFI-11171
> Project: Apache NiFi
> Issue Type: Epic
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
> Fix For: 2.0.0-M3
>
>
> The {{nifi-standard-processors}} and {{nifi-standard-services}} modules
> include a large number of Processors and Controller Services supporting an
> array of capabilities. Some of these capabilities require specialized
> libraries that apply to a limited number of components.
> Moving Processors and Controller Services changes class names and bundle
> coordinates which will break existing flow configurations. For this reason,
> the selection of components for reorganization should be limited and focused.
> Components with less frequent updates or usage and components with large
> dependencies trees should be considered.
> The following items should be considered as described in the [NiFi 2.0
> Release
> Goals|https://cwiki.apache.org/confluence/display/NIFI/NiFi+2.0+Release+Goals]:
> * SFTP Processors
> * Jolt Transform Processors
> * Jetty HTTP Processors
> * JSON Processors
> * Netty-based Processors
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (NIFI-13308) Upgrade Spring Framework to 6.1.8 along with Spring Boot 3.2.6, AWS 2.25.60, Netty 4.1.110 and others
[ https://issues.apache.org/jira/browse/NIFI-13308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann resolved NIFI-13308. - Fix Version/s: 2.0.0-M4 Resolution: Fixed > Upgrade Spring Framework to 6.1.8 along with Spring Boot 3.2.6, AWS 2.25.60, > Netty 4.1.110 and others > - > > Key: NIFI-13308 > URL: https://issues.apache.org/jira/browse/NIFI-13308 > Project: Apache NiFi > Issue Type: Task >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > Fix For: 2.0.0-M4 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13308) Upgrade Spring Framework to 6.1.8 along with Spring Boot 3.2.6, AWS 2.25.60, Netty 4.1.110 and others
[ https://issues.apache.org/jira/browse/NIFI-13308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13308: Summary: Upgrade Spring Framework to 6.1.8 along with Spring Boot 3.2.6, AWS 2.25.60, Netty 4.1.110 and others (was: Bump aws, spring, jersey, netty versions to latest) > Upgrade Spring Framework to 6.1.8 along with Spring Boot 3.2.6, AWS 2.25.60, > Netty 4.1.110 and others > - > > Key: NIFI-13308 > URL: https://issues.apache.org/jira/browse/NIFI-13308 > Project: Apache NiFi > Issue Type: Task >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13308) Bump aws, spring, jersey, netty versions to latest
[ https://issues.apache.org/jira/browse/NIFI-13308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850476#comment-17850476 ] ASF subversion and git services commented on NIFI-13308: Commit 89e8434bf03398ac06dbe4be84c72236a4bd902e in nifi's branch refs/heads/main from Joe Witt [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=89e8434bf0 ] NIFI-13308 Upgraded Spring Framework from 6.1.7 to 6.1.8 - Upgraded Spring Boot from 3.2.5 to 3.2.6 - Upgraded Slack bolt-socket-mode from 1.39.2 to 1.39.3 - Upgraded maven-artifact from 3.9.6 to 3.9.7 - Upgraded mariadb-java-client from 3.3.3 to 3.4.0 - Upgraded software.amazon.awssdk from 2.25.55 to 2.25.60 - Upgraded com.amazonaws from 1.12.725 to 1.12.730 - Upgraded Jersey from 3.1.6 to 3.1.7 - Upgraded Netty from 4.1.109.Final to 4.1.110.Final - Upgraded box-java-sdk from 4.9.0 to 4.9.1 This closes #8887 Signed-off-by: David Handermann > Bump aws, spring, jersey, netty versions to latest > -- > > Key: NIFI-13308 > URL: https://issues.apache.org/jira/browse/NIFI-13308 > Project: Apache NiFi > Issue Type: Task >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12343) PutElasticsearchJson exception with JSON strings over 20 MB
[
https://issues.apache.org/jira/browse/NIFI-12343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850474#comment-17850474
]
ASF subversion and git services commented on NIFI-12343:
Commit cbe5f7db9d678518b9846af1150c9b0e55afae1a in nifi's branch
refs/heads/main from Chris Sampson
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=cbe5f7db9d ]
NIFI-12343 Added Max JSON Field String Length for Elasticsearch
This closes #8881
Signed-off-by: David Handermann
> PutElasticsearchJson exception with JSON strings over 20 MB
> ---
>
> Key: NIFI-12343
> URL: https://issues.apache.org/jira/browse/NIFI-12343
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.23.2, 2.0.0-M2
>Reporter: Gregory M. Foreman
>Assignee: Chris Sampson
>Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
>
> PutElasticsearchJson throws an exception when reading JSON documents that
> contain string fields over 20 MB:
> {code:java}
> PutElasticsearchJson[id=] No FlowFiles successfully parsed for sending to
> Elasticsearch
> PutElasticsearchJson[id=] Could not read FlowFile content valid JSON.:
> com.fasterxml.jackson.core.exc.StreamConstraintsException: String length
> (20050553) exceeds the maximum length (2000)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-12343) PutElasticsearchJson exception with JSON strings over 20 MB
[
https://issues.apache.org/jira/browse/NIFI-12343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-12343:
Fix Version/s: 2.0.0-M4
Resolution: Fixed
Status: Resolved (was: Patch Available)
> PutElasticsearchJson exception with JSON strings over 20 MB
> ---
>
> Key: NIFI-12343
> URL: https://issues.apache.org/jira/browse/NIFI-12343
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.23.2, 2.0.0-M2
>Reporter: Gregory M. Foreman
>Assignee: Chris Sampson
>Priority: Major
> Fix For: 2.0.0-M4
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
>
> PutElasticsearchJson throws an exception when reading JSON documents that
> contain string fields over 20 MB:
> {code:java}
> PutElasticsearchJson[id=] No FlowFiles successfully parsed for sending to
> Elasticsearch
> PutElasticsearchJson[id=] Could not read FlowFile content valid JSON.:
> com.fasterxml.jackson.core.exc.StreamConstraintsException: String length
> (20050553) exceeds the maximum length (2000)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-13284) Consider filtering current-canvas-route
[ https://issues.apache.org/jira/browse/NIFI-13284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850460#comment-17850460 ] ASF subversion and git services commented on NIFI-13284: Commit 0660616864df27a238363036cc2a20414c39fb3b in nifi's branch refs/heads/main from Matt Gilman [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=0660616864 ] NIFI-13284: (#8891) - Only saving canvas routes that are not edit or history. This closes #8891 > Consider filtering current-canvas-route > --- > > Key: NIFI-13284 > URL: https://issues.apache.org/jira/browse/NIFI-13284 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Currently, the canvas tracks the current route so the user can be returned to > where they were when returning to the canvas. We should consider filtering > out any `edit` routes so that the user is returned to the place in the canvas > rather then in an Edit dialog. > Since dialogs are only and must be closed prior to using most navigation > controls this won't happen regularly. However a user routes through a Go To > command it will. By filtering out `edit` routes, it may be less confusing. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13284) Consider filtering current-canvas-route
[ https://issues.apache.org/jira/browse/NIFI-13284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Fellows updated NIFI-13284: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Consider filtering current-canvas-route > --- > > Key: NIFI-13284 > URL: https://issues.apache.org/jira/browse/NIFI-13284 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Currently, the canvas tracks the current route so the user can be returned to > where they were when returning to the canvas. We should consider filtering > out any `edit` routes so that the user is returned to the place in the canvas > rather then in an Edit dialog. > Since dialogs are only and must be closed prior to using most navigation > controls this won't happen regularly. However a user routes through a Go To > command it will. By filtering out `edit` routes, it may be less confusing. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13269) Parameter reference list is randomly ordered or not ordered
[ https://issues.apache.org/jira/browse/NIFI-13269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13269: --- Fix Version/s: 2.0.0-M4 Resolution: Fixed Status: Resolved (was: Patch Available) > Parameter reference list is randomly ordered or not ordered > --- > > Key: NIFI-13269 > URL: https://issues.apache.org/jira/browse/NIFI-13269 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Julien G. >Assignee: Rob Fellows >Priority: Major > Fix For: 2.0.0-M4 > > Attachments: Screenshot 2024-05-22 at 3.49.48 PM.png, > image-2024-05-21-11-04-26-571.png, image-2024-05-22-22-12-46-877.png, > legacy.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > When referencing a parameter in a Controller Service, a list of the availabe > parameter is displayed. > In the new UI, the list is randomly ordered or not ordered at all. > !image-2024-05-21-11-04-26-571.png|thumbnail! > It makes it hard to find a parameter. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13269) Parameter reference list is randomly ordered or not ordered
[ https://issues.apache.org/jira/browse/NIFI-13269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850455#comment-17850455 ] ASF subversion and git services commented on NIFI-13269: Commit dbc786095ce229af8d75199c587c84863bbeeef6 in nifi's branch refs/heads/main from Rob Fellows [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=dbc786095c ] [NIFI-13269] - Order parameter reference list alphabetically (#8885) * [NIFI-13269] - Order parameter reference list alphabetically * ran prettier:format to address minor code style issue * update nfpr and nfel to sort combo entries the same as the combo entries in the property table (case insensitive) This closes #8885 > Parameter reference list is randomly ordered or not ordered > --- > > Key: NIFI-13269 > URL: https://issues.apache.org/jira/browse/NIFI-13269 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Julien G. >Assignee: Rob Fellows >Priority: Major > Attachments: Screenshot 2024-05-22 at 3.49.48 PM.png, > image-2024-05-21-11-04-26-571.png, image-2024-05-22-22-12-46-877.png, > legacy.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > When referencing a parameter in a Controller Service, a list of the availabe > parameter is displayed. > In the new UI, the list is randomly ordered or not ordered at all. > !image-2024-05-21-11-04-26-571.png|thumbnail! > It makes it hard to find a parameter. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12400) Remaining items to migrate UI to currently supported/active framework
[ https://issues.apache.org/jira/browse/NIFI-12400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-12400: --- Description: The purpose of this Jira is to track all remaining items following the initial commit [1] for NIFI-11481. The description will be kept up to date with remaining features, tasks, and improvements. As each items is worked, a new sub task Jira will be created and referenced in this description. * Support Parameters in Properties with Allowable Values (NIFI-12401) * Summary (NIFI-12437) ** Remaining work not addressed in initial Jira: *** input ports (NIFI-12504) *** output ports (NIFI-12504) *** remote process groups (NIFI-12504) *** process groups (NIFI-12504) *** connections (NIFI-12504) *** System Diagnostics (NIFI-12505) *** support for cluster-specific ui elements (NIFI-12537) *** Add pagination (NIFI-12552) *** Support Processor Details dialog *** Support Connection Details dialog * Counters (NIFI-12415) ** Counter table has extra unnecessary can modify check (NIFI-12948) * Bulletin Board (NIFI-12560) * Provenance (NIFI-12445) ** Event Listing (NIFI-12445) ** Search (NIFI-12445) ** Event Dialog (NIFI-12445) ** Lineage (NIFI-12485) ** Replay from context menu (NIFI-12445) ** Clustering (NIFI-12807) * Configure Reporting Task (NIFI-12563) * Flow Analysis Rules (NIFI-12588) * Registry Clients (NIFI-12486) * Import from Registry (NIFI-12734) * Parameter Providers (NIFI-12622) ** Fetch parameters from provider, map to parameter context (dialog) - (NIFI-12665) * Cluster ** Node table (Disconnect/Connect/Load Balance/Etc) (NIFI-13053) ** Status History - node specific values (NIFI-12848) * Flow Configuration History (NIFI-12754) ** ActionEntity.action should be optional (NIFI-12948) * Node Status History (NIFI-12553) * Status history for components from canvas context menu (NIFI-12553) * Users (NIFI-12543) ** Don't show users or groups in create/edit dialog is there are none (NIFI-12948) * Policies (NIFI-12548) ** Overridden policy Empty or Copy (NIFI-12679) ** Select Empty by default (NIFI-12948) * Help (NIFI-12795) * About (NIFI-13094) * Show Upstream/Downstream * Align (NIFI-13162) * Replay last event (NIFI-12445) * List Queue (NIFI-12589) ** Clustering (NIFI-12807) * Empty [all] Queue (NIFI-12604) * View Content (NIFI-12589 and NIFI-12445) * View State (NIFI-12611) ** Clustering (NIFI-13005) * Change Component Version (NIFI-13034) * Consider PG permissions in Toolbox (NIFI-12683) * PG Version (NIFI-12963 & NIFI-12995) ** Start (NIFI-12963) ** Commit (NIFI-12963) ** Force Commit (NIFI-12963) ** Show changes (NIFI-12995) ** Revert changes (NIFI-12995) ** Change Flow version (NIFI-12995) ** Stop (NIFI-12963) * Configure PG (NIFI-12417) * Configure Label (NIFI-13081) * Process Group Services (NIFI-12425) ** Listing (NIFI-12425) ** Create (NIFI-12425) ** Configure (NIFI-12425) ** Delete (NIFI-12425) ** Enable (NIFI-12529) ** Disable (NIFI-12529) ** Improve layout and breadcrumbs ** Disable and Configure * Configure Processor ** Service Link (NIFI-12425) ** Create inline Service (NIFI-12425) ** Parameter Link (NIFI-12502) ** Convert to Parameter (NIFI-12502) ** Fix issue with Property Editor width (NIFI-12547) ** Status Bar ** Stop and Configure ** Open Custom UI (NIFI-12958) ** Property History (NIFI-13047) ** Unable to re-add any removed Property (NIFI-12743) ** Shift-Enter new line when editing Property (NIFI-12743) * Property Verification (NIFI-13247) * Terminate Threads (context menu) (NIFI-13068) * Enable/Disable (context menu/operate panel) (NIFI-13078) * More Details (Processor, Controller Service, Reporting Task) (NIFI-13062) * Download Flow (NIFI-13029) * Create RPG (NIFI-12758) * Configure RPG (NIFI-12774) * RPG Remote Ports (NIFI-12778) * RPG Go To (NIFI-12759) * RPG Refresh (NIFI-12761) * Color (context menu/operate panel) (NIFI-13226) * Move to Front (NIFI-13044) * Copy/Paste (context menu/operate panel) (NIFI-13059) * Add/Update Info Icons in dialogs throughout the application (NIFI-13092) * Set viewport earlier when loading a Process Group (NIFI-12737) * Canvas global menu item should navigate user back to where they were on the canvas (NIFI-12737) * Better theme support (NIFI-12655) * Set up development/production environments files * Run unit tests are part of standard build (NIFI-12941) * Update all API calls to consider disconnect node confirmation (NIFI-13001) * Update API calls to use uiOnly flag (NIFI-12950) * Use polling interval from API * Load FlowConfiguration in guard (NIFI-12948) * Routing error handling (NIFI-13104) * General API response error handling ** Management CS (NIFI-12663) ** Canvas CS (NIFI-12684) ** Remainder of Settings (NIFI-12723) ** Counters (NIFI-12723) ** Bulletins (NIFI-12723) ** Flow Designer (NIFI-13100) ** Parameter Cont
[jira] [Created] (NIFI-13314) Update guides for new UI
Matt Gilman created NIFI-13314: -- Summary: Update guides for new UI Key: NIFI-13314 URL: https://issues.apache.org/jira/browse/NIFI-13314 Project: Apache NiFi Issue Type: Task Components: Documentation Website Reporter: Matt Gilman The new NiFi UI leverages the same general UX as the old UI. However, there are some differences that have evolved as the new UI was built. This Jira is tracking needed changes to the documentation and guides. While is a ton of details in these guides, we should prioritize updating areas where the UX has changed substantially from the old UI. * Managing Remote Ports * Process Group Configuration * Process Group Controller Services * Color Processor/Label * Flow Configuration History Sub-tasks can be added to this Jira for landing each of these updates. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12400) Remaining items to migrate UI to currently supported/active framework
[ https://issues.apache.org/jira/browse/NIFI-12400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-12400: --- Description: The purpose of this Jira is to track all remaining items following the initial commit [1] for NIFI-11481. The description will be kept up to date with remaining features, tasks, and improvements. As each items is worked, a new sub task Jira will be created and referenced in this description. * Support Parameters in Properties with Allowable Values (NIFI-12401) * Summary (NIFI-12437) ** Remaining work not addressed in initial Jira: *** input ports (NIFI-12504) *** output ports (NIFI-12504) *** remote process groups (NIFI-12504) *** process groups (NIFI-12504) *** connections (NIFI-12504) *** System Diagnostics (NIFI-12505) *** support for cluster-specific ui elements (NIFI-12537) *** Add pagination (NIFI-12552) *** Support Processor Details dialog *** Support Connection Details dialog * Counters (NIFI-12415) ** Counter table has extra unnecessary can modify check (NIFI-12948) * Bulletin Board (NIFI-12560) * Provenance (NIFI-12445) ** Event Listing (NIFI-12445) ** Search (NIFI-12445) ** Event Dialog (NIFI-12445) ** Lineage (NIFI-12485) ** Replay from context menu (NIFI-12445) ** Clustering (NIFI-12807) * Configure Reporting Task (NIFI-12563) * Flow Analysis Rules (NIFI-12588) * Registry Clients (NIFI-12486) * Import from Registry (NIFI-12734) * Parameter Providers (NIFI-12622) ** Fetch parameters from provider, map to parameter context (dialog) - (NIFI-12665) * Cluster ** Node table (Disconnect/Connect/Load Balance/Etc) (NIFI-13053) ** Status History - node specific values (NIFI-12848) * Flow Configuration History (NIFI-12754) ** ActionEntity.action should be optional (NIFI-12948) * Node Status History (NIFI-12553) * Status history for components from canvas context menu (NIFI-12553) * Users (NIFI-12543) ** Don't show users or groups in create/edit dialog is there are none (NIFI-12948) * Policies (NIFI-12548) ** Overridden policy Empty or Copy (NIFI-12679) ** Select Empty by default (NIFI-12948) * Help (NIFI-12795) * About (NIFI-13094) * Show Upstream/Downstream * Align (NIFI-13162) * Replay last event (NIFI-12445) * List Queue (NIFI-12589) ** Clustering (NIFI-12807) * Empty [all] Queue (NIFI-12604) * View Content (NIFI-12589 and NIFI-12445) * View State (NIFI-12611) ** Clustering (NIFI-13005) * Change Component Version (NIFI-13034) * Consider PG permissions in Toolbox (NIFI-12683) * PG Version (NIFI-12963 & NIFI-12995) ** Start (NIFI-12963) ** Commit (NIFI-12963) ** Force Commit (NIFI-12963) ** Show changes (NIFI-12995) ** Revert changes (NIFI-12995) ** Change Flow version (NIFI-12995) ** Stop (NIFI-12963) * Configure PG (NIFI-12417) * Configure Label (NIFI-13081) * Process Group Services (NIFI-12425) ** Listing (NIFI-12425) ** Create (NIFI-12425) ** Configure (NIFI-12425) ** Delete (NIFI-12425) ** Enable (NIFI-12529) ** Disable (NIFI-12529) ** Improve layout and breadcrumbs ** Disable and Configure * Configure Processor ** Service Link (NIFI-12425) ** Create inline Service (NIFI-12425) ** Parameter Link (NIFI-12502) ** Convert to Parameter (NIFI-12502) ** Fix issue with Property Editor width (NIFI-12547) ** Status Bar ** Stop and Configure ** Open Custom UI (NIFI-12958) ** Property History (NIFI-13047) ** Unable to re-add any removed Property (NIFI-12743) ** Shift-Enter new line when editing Property (NIFI-12743) * Property Verification (NIFI-13247) * Terminate Threads (context menu) (NIFI-13068) * Enable/Disable (context menu/operate panel) (NIFI-13078) * More Details (Processor, Controller Service, Reporting Task) (NIFI-13062) * Download Flow (NIFI-13029) * Create RPG (NIFI-12758) * Configure RPG (NIFI-12774) * RPG Remote Ports (NIFI-12778) * RPG Go To (NIFI-12759) * RPG Refresh (NIFI-12761) * Color (context menu/operate panel) (NIFI-13226) * Move to Front (NIFI-13044) * Copy/Paste (context menu/operate panel) (NIFI-13059) * Add/Update Info Icons in dialogs throughout the application (NIFI-13092) * Set viewport earlier when loading a Process Group (NIFI-12737) * Canvas global menu item should navigate user back to where they were on the canvas (NIFI-12737) * Better theme support (NIFI-12655) * Set up development/production environments files * Run unit tests are part of standard build (NIFI-12941) * Update all API calls to consider disconnect node confirmation (NIFI-13001) * Update API calls to use uiOnly flag (NIFI-12950) * Use polling interval from API * Load FlowConfiguration in guard (NIFI-12948) * Routing error handling (NIFI-13104) * General API response error handling ** Management CS (NIFI-12663) ** Canvas CS (NIFI-12684) ** Remainder of Settings (NIFI-12723) ** Counters (NIFI-12723) ** Bulletins (NIFI-12723) ** Flow Designer (NIFI-13100) ** Parameter Cont
[jira] [Created] (NIFI-13313) Replace old UI
Matt Gilman created NIFI-13313: -- Summary: Replace old UI Key: NIFI-13313 URL: https://issues.apache.org/jira/browse/NIFI-13313 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Matt Gilman Assignee: Matt Gilman With the new UI functionally ready and other UIs (documentations, data viewers, etc) no longer depending on the old UI it can now be removed. This Jira is tracking removal of that maven module and any downstream changes. These include updating of LICENSE/NOTICEs that no longer bundle removed dependencies and updating the Jetty Server to only deploy the new UI. The new UI should use "/nifi" context. Existing functionality around authentication where the back end redirects the user to the UI should be verified. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13307) Refactor KeyStoreUtils References using nifi-security-ssl
[
https://issues.apache.org/jira/browse/NIFI-13307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-13307:
Summary: Refactor KeyStoreUtils References using nifi-security-ssl (was:
Refactor TLS Loading using nifi-security-ssl)
> Refactor KeyStoreUtils References using nifi-security-ssl
> -
>
> Key: NIFI-13307
> URL: https://issues.apache.org/jira/browse/NIFI-13307
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The {{KeyStoreUtils}} class in {{nifi-security-utils}} contains a large
> number of similar methods for loading keystores and other TLS components. The
> {{nifi-security-ssl}} module contains a streamlined set of builder classes,
> without external dependencies. References to {{KeyStoreUtils}} should be
> refactored to use the newer builder classes to remove unnecessary
> dependencies on {{nifi-security-utils}} and associated transitive
> dependencies.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-13307) Refactor TLS Loading using nifi-security-ssl
[
https://issues.apache.org/jira/browse/NIFI-13307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-13307:
Status: Patch Available (was: Open)
> Refactor TLS Loading using nifi-security-ssl
>
>
> Key: NIFI-13307
> URL: https://issues.apache.org/jira/browse/NIFI-13307
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The {{KeyStoreUtils}} class in {{nifi-security-utils}} contains a large
> number of similar methods for loading keystores and other TLS components. The
> {{nifi-security-ssl}} module contains a streamlined set of builder classes,
> without external dependencies. References to {{KeyStoreUtils}} should be
> refactored to use the newer builder classes to remove unnecessary
> dependencies on {{nifi-security-utils}} and associated transitive
> dependencies.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-13301) Create NiFi Processor Marketplace App Powered by NiFi Registry
[
https://issues.apache.org/jira/browse/NIFI-13301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850446#comment-17850446
]
David Handermann commented on NIFI-13301:
-
One general point worth highlighting is that using NiFi Registry as the
supporting storage service for something like this is probably not ideal.
Although NiFi Registry has a number of configurable features, it does not
support clustered deployment for high availability, which would be a vital part
of such a marketplace. As noted in the approach 2, work on alternative Registry
Clients for Flow Definitions, such as GitHub, highlights options for hosting
that do not require running NiFi Registry. Options for hosting component
bundles could include services that provide Maven-style package services.
> Create NiFi Processor Marketplace App Powered by NiFi Registry
> --
>
> Key: NIFI-13301
> URL: https://issues.apache.org/jira/browse/NIFI-13301
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions, NiFi Registry
> Environment: Linux: Ubuntu 20.04 or 22.04
>Reporter: James Guzman (Medel)
>Assignee: James Guzman (Medel)
>Priority: Minor
>
> *Objective:* Improve/enable sharing/reuse of at least two features of Apache
> NiFi, so the community can have an easier time contributing their flows
> and/or custom processors into a NiFi Marketplace:
> * {*}Pre-Designed Flows{*}: (Approach 1) stored in a NiFi Registry or
> accessible location. (Approach 2) NiFi Registry can also substituted by
> NiFi's git registry client having the location of the NiFi Marketplace.
> Thus, we just have a git location and NiFi uses that to find/store flows.
> * *Components/Processors* built in *Java/Python* that anyone is free to use
> * *End to End Full Stack Applications Powered By NiFi or MiNiFi CPP?* The
> frontend could be various ones from PyQT, ReactJS, H2O.ai Wave, 3D Slicer,
> OHIF Viewer, etc: (Maybe this one can be subscription based where users get
> access if they invest in the monthly or yearly subscription?)
> {*}Project Ownership{*}: There will be a clear line that the NiFi Marketplace
> is not owned by the Apache NiFi PMC, rather it will be managed and owned by a
> vendor in close alignment with NiFi, which we will announce at a later time.
>
> {*}Motivation (NiFi){*}: Some people in the community have shown interest in
> having a NiFi Processor Marketplace where they can contribute their category
> of processors. In particular, I saw some people interested in contributing
> their NiFi python processors. This NiFi Processor marketplace could be also
> applied toward the community interested in contributing custom NiFi java
> processors.
> * {*}Extra MiNiFi C+{+}{+}{*}: We could even add a section for MiNiFi C+
> custom processors. There is a part of the MiNiFi build process that brings in
> NiFi through building the JNI extension. So, that is a way to integrate NiFi
> Registry there too.
> I have briefly talked with [~bbende] and [~joewitt] asking them questions on
> ways to bring custom python processors into production. One of the routes was
> through leveraging NiFi Registry in connection with Apache NiFi to streamline
> integration. For my use case, I would leverage the NiFi Processor Marketplace
> to start contributing my AI/DL "Medical Imaging" Pipeline of custom NiFi
> Python Processors where I focused on my master thesis AI/DL for stroke
> diagnosis.
> *High Level Details of NiFi Processor Marketplace App:* For a full stack NiFi
> Processor Marketplace App, there are frameworks we can leverage for the UI
> from ReactJS (this mainly is used for frontend), H2O.ai Wave (this can be
> used for full stack, but probably would mainly be used for the frontend
> portion) and other options. in the case that we want to make something more
> custom to display each category of processors. This full stack application
> could interact wth the NiFi Registry, which is the central location for
> storage and management of shared resources across one or more instances of
> NiFi and/or MiNiFi (C++). What are some hosting options for Apache projects?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-13301) Create NiFi Processor Marketplace App Powered by NiFi Registry
[
https://issues.apache.org/jira/browse/NIFI-13301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850436#comment-17850436
]
James Guzman (Medel) commented on NIFI-13301:
-
You're welcome. [~joewitt] .
I am happy to help out with this effort in the open source. We can observe some
projects that have done well with community engagement in the open source for
their marketplace apps.
> Create NiFi Processor Marketplace App Powered by NiFi Registry
> --
>
> Key: NIFI-13301
> URL: https://issues.apache.org/jira/browse/NIFI-13301
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions, NiFi Registry
> Environment: Linux: Ubuntu 20.04 or 22.04
>Reporter: James Guzman (Medel)
>Assignee: James Guzman (Medel)
>Priority: Minor
>
> *Objective:* Improve/enable sharing/reuse of at least two features of Apache
> NiFi, so the community can have an easier time contributing their flows
> and/or custom processors into a NiFi Marketplace:
> * {*}Pre-Designed Flows{*}: (Approach 1) stored in a NiFi Registry or
> accessible location. (Approach 2) NiFi Registry can also substituted by
> NiFi's git registry client having the location of the NiFi Marketplace.
> Thus, we just have a git location and NiFi uses that to find/store flows.
> * *Components/Processors* built in *Java/Python* that anyone is free to use
> * *End to End Full Stack Applications Powered By NiFi or MiNiFi CPP?* The
> frontend could be various ones from PyQT, ReactJS, H2O.ai Wave, 3D Slicer,
> OHIF Viewer, etc: (Maybe this one can be subscription based where users get
> access if they invest in the monthly or yearly subscription?)
> {*}Project Ownership{*}: There will be a clear line that the NiFi Marketplace
> is not owned by the Apache NiFi PMC, rather it will be managed and owned by a
> vendor in close alignment with NiFi, which we will announce at a later time.
>
> {*}Motivation (NiFi){*}: Some people in the community have shown interest in
> having a NiFi Processor Marketplace where they can contribute their category
> of processors. In particular, I saw some people interested in contributing
> their NiFi python processors. This NiFi Processor marketplace could be also
> applied toward the community interested in contributing custom NiFi java
> processors.
> * {*}Extra MiNiFi C+{+}{+}{*}: We could even add a section for MiNiFi C+
> custom processors. There is a part of the MiNiFi build process that brings in
> NiFi through building the JNI extension. So, that is a way to integrate NiFi
> Registry there too.
> I have briefly talked with [~bbende] and [~joewitt] asking them questions on
> ways to bring custom python processors into production. One of the routes was
> through leveraging NiFi Registry in connection with Apache NiFi to streamline
> integration. For my use case, I would leverage the NiFi Processor Marketplace
> to start contributing my AI/DL "Medical Imaging" Pipeline of custom NiFi
> Python Processors where I focused on my master thesis AI/DL for stroke
> diagnosis.
> *High Level Details of NiFi Processor Marketplace App:* For a full stack NiFi
> Processor Marketplace App, there are frameworks we can leverage for the UI
> from ReactJS (this mainly is used for frontend), H2O.ai Wave (this can be
> used for full stack, but probably would mainly be used for the frontend
> portion) and other options. in the case that we want to make something more
> custom to display each category of processors. This full stack application
> could interact wth the NiFi Registry, which is the central location for
> storage and management of shared resources across one or more instances of
> NiFi and/or MiNiFi (C++). What are some hosting options for Apache projects?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-13301) Create NiFi Processor Marketplace App Powered by NiFi Registry
[
https://issues.apache.org/jira/browse/NIFI-13301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850435#comment-17850435
]
Joe Witt commented on NIFI-13301:
-
i'd just say someone has to host/maintain/support this thing. Does not have to
be a vendor but I suspect that is the model we can leverage. Other projects
have figured this out we can learn from.. Thanks for capturing James!
> Create NiFi Processor Marketplace App Powered by NiFi Registry
> --
>
> Key: NIFI-13301
> URL: https://issues.apache.org/jira/browse/NIFI-13301
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions, NiFi Registry
> Environment: Linux: Ubuntu 20.04 or 22.04
>Reporter: James Guzman (Medel)
>Assignee: James Guzman (Medel)
>Priority: Minor
>
> *Objective:* Improve/enable sharing/reuse of at least two features of Apache
> NiFi, so the community can have an easier time contributing their flows
> and/or custom processors into a NiFi Marketplace:
> * {*}Pre-Designed Flows{*}: (Approach 1) stored in a NiFi Registry or
> accessible location. (Approach 2) NiFi Registry can also substituted by
> NiFi's git registry client having the location of the NiFi Marketplace.
> Thus, we just have a git location and NiFi uses that to find/store flows.
> * *Components/Processors* built in *Java/Python* that anyone is free to use
> * *End to End Full Stack Applications Powered By NiFi or MiNiFi CPP?* The
> frontend could be various ones from PyQT, ReactJS, H2O.ai Wave, 3D Slicer,
> OHIF Viewer, etc: (Maybe this one can be subscription based where users get
> access if they invest in the monthly or yearly subscription?)
> {*}Project Ownership{*}: There will be a clear line that the NiFi Marketplace
> is not owned by the Apache NiFi PMC, rather it will be managed and owned by a
> vendor in close alignment with NiFi, which we will announce at a later time.
>
> {*}Motivation (NiFi){*}: Some people in the community have shown interest in
> having a NiFi Processor Marketplace where they can contribute their category
> of processors. In particular, I saw some people interested in contributing
> their NiFi python processors. This NiFi Processor marketplace could be also
> applied toward the community interested in contributing custom NiFi java
> processors.
> * {*}Extra MiNiFi C+{+}{+}{*}: We could even add a section for MiNiFi C+
> custom processors. There is a part of the MiNiFi build process that brings in
> NiFi through building the JNI extension. So, that is a way to integrate NiFi
> Registry there too.
> I have briefly talked with [~bbende] and [~joewitt] asking them questions on
> ways to bring custom python processors into production. One of the routes was
> through leveraging NiFi Registry in connection with Apache NiFi to streamline
> integration. For my use case, I would leverage the NiFi Processor Marketplace
> to start contributing my AI/DL "Medical Imaging" Pipeline of custom NiFi
> Python Processors where I focused on my master thesis AI/DL for stroke
> diagnosis.
> *High Level Details of NiFi Processor Marketplace App:* For a full stack NiFi
> Processor Marketplace App, there are frameworks we can leverage for the UI
> from ReactJS (this mainly is used for frontend), H2O.ai Wave (this can be
> used for full stack, but probably would mainly be used for the frontend
> portion) and other options. in the case that we want to make something more
> custom to display each category of processors. This full stack application
> could interact wth the NiFi Registry, which is the central location for
> storage and management of shared resources across one or more instances of
> NiFi and/or MiNiFi (C++). What are some hosting options for Apache projects?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-13301) Create NiFi Processor Marketplace App Powered by NiFi Registry
[
https://issues.apache.org/jira/browse/NIFI-13301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Guzman (Medel) updated NIFI-13301:
Description:
*Objective:* Improve/enable sharing/reuse of at least two features of Apache
NiFi, so the community can have an easier time contributing their flows and/or
custom processors into a NiFi Marketplace:
* {*}Pre-Designed Flows{*}: (Approach 1) stored in a NiFi Registry or
accessible location. (Approach 2) NiFi Registry can also substituted by NiFi's
git registry client having the location of the NiFi Marketplace. Thus, we just
have a git location and NiFi uses that to find/store flows.
* *Components/Processors* built in *Java/Python* that anyone is free to use
* *End to End Full Stack Applications Powered By NiFi or MiNiFi CPP?* The
frontend could be various ones from PyQT, ReactJS, H2O.ai Wave, 3D Slicer, OHIF
Viewer, etc: (Maybe this one can be subscription based where users get access
if they invest in the monthly or yearly subscription?)
{*}Project Ownership{*}: There will be a clear line that the NiFi Marketplace
is not owned by the Apache NiFi PMC, rather it will be managed and owned by a
vendor in close alignment with NiFi, which we will announce at a later time.
{*}Motivation (NiFi){*}: Some people in the community have shown interest in
having a NiFi Processor Marketplace where they can contribute their category of
processors. In particular, I saw some people interested in contributing their
NiFi python processors. This NiFi Processor marketplace could be also applied
toward the community interested in contributing custom NiFi java processors.
* {*}Extra MiNiFi C+{+}{+}{*}: We could even add a section for MiNiFi C+
custom processors. There is a part of the MiNiFi build process that brings in
NiFi through building the JNI extension. So, that is a way to integrate NiFi
Registry there too.
I have briefly talked with [~bbende] and [~joewitt] asking them questions on
ways to bring custom python processors into production. One of the routes was
through leveraging NiFi Registry in connection with Apache NiFi to streamline
integration. For my use case, I would leverage the NiFi Processor Marketplace
to start contributing my AI/DL "Medical Imaging" Pipeline of custom NiFi Python
Processors where I focused on my master thesis AI/DL for stroke diagnosis.
*High Level Details of NiFi Processor Marketplace App:* For a full stack NiFi
Processor Marketplace App, there are frameworks we can leverage for the UI from
ReactJS (this mainly is used for frontend), H2O.ai Wave (this can be used for
full stack, but probably would mainly be used for the frontend portion) and
other options. in the case that we want to make something more custom to
display each category of processors. This full stack application could interact
wth the NiFi Registry, which is the central location for storage and management
of shared resources across one or more instances of NiFi and/or MiNiFi (C++).
What are some hosting options for Apache projects?
was:
{*}Description (NiFi){*}: Some people in the community have shown interest in
having a NiFi Processor Marketplace where they can contribute their category of
processors. In particular, I saw some people interested in contributing their
NiFi python processors. This NiFi Processor marketplace could be also applied
toward the community interested in contributing custom NiFi java processors.
* {*}Extra MiNiFi C++{*}: We could even add a section for MiNiFi C++ custom
processors. There is a part of the MiNiFi build process that brings in NiFi
through building the JNI extension. So, that is a way to integrate NiFi
Registry there too.
I have briefly talked with [~bbende] and [~joewitt] asking them questions on
ways to bring custom python processors into production. One of the routes was
through leveraging NiFi Registry in connection with Apache NiFi to streamline
integration. For my use case, I would leverage the NiFi Processor Marketplace
to start contributing my AI/DL "Medical Imaging" Pipeline of custom NiFi Python
Processors where I focused on my master thesis AI/DL for stroke diagnosis.
*High Level Details of NiFi Processor Marketplace App:* For a full stack NiFi
Processor Marketplace App, there are frameworks we can leverage for the UI from
ReactJS (this mainly is used for frontend), H2O.ai Wave (this can be used for
full stack, but probably would mainly be used for the frontend portion) and
other options. in the case that we want to make something more custom to
display each category of processors. This full stack application could interact
wth the NiFi Registry, which is the central location for storage and management
of shared resources across one or more instances of NiFi and/or MiNiFi (C++).
What are some hosting options for Apache projects?
> Create NiFi Processor Marketpl
[jira] [Commented] (NIFI-13265) Remove the instantiation of Object arrays for arguments in ComponentLog log and org.slf4j.Logger statements
[ https://issues.apache.org/jira/browse/NIFI-13265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850433#comment-17850433 ] David Handermann commented on NIFI-13265: - [~dstiegli1], for warning cases like that one from PutS3Object, the purpose appears to be including the message, but not the stack trace. In most cases, the full exception should be included in order to log the stack trace, but for certain selected instances, the stack trace is not necessary because the message itself contains enough information for troubleshooting. > Remove the instantiation of Object arrays for arguments in ComponentLog log > and org.slf4j.Logger statements > --- > > Key: NIFI-13265 > URL: https://issues.apache.org/jira/browse/NIFI-13265 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Daniel Stieglitz >Assignee: Daniel Stieglitz >Priority: Minor > > There are still classes after the changes in NIFI-12075 and NIFI-12076 which > instantiate an Object array for ComponentLog log statements. This ticket aims > to remove those instantiations. In addition similar changes should be made to > org.slf4j.Logger statements. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13265) Remove the instantiation of Object arrays for arguments in ComponentLog log and org.slf4j.Logger statements
[
https://issues.apache.org/jira/browse/NIFI-13265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850430#comment-17850430
]
Daniel Stieglitz commented on NIFI-13265:
-
[~exceptionfactory] Thanks for clarifying. How about for something like this in
PutS3Object lines 925-929
{code:java}
getLogger().warn("AccessDenied checking S3 Multipart Upload list for {}: {} " +
"** The configured user does not have the
s3:ListBucketMultipartUploads permission " +
"for this bucket, S3 ageoff cannot occur without
this permission. Next ageoff check " +
"time is being advanced by interval to prevent
checking on every upload **",
new Object[]{bucket, e.getMessage()});
{code}
should i completely remove the parameter for the exception as
{code:java}
getLogger().warn("AccessDenied checking S3 Multipart Upload list for {}: " +
"** The configured user does not have the
s3:ListBucketMultipartUploads permission " +
"for this bucket, S3 ageoff cannot occur without
this permission. Next ageoff check " +
"time is being advanced by interval to prevent
checking on every upload **", bucket, e);
{code}
> Remove the instantiation of Object arrays for arguments in ComponentLog log
> and org.slf4j.Logger statements
> ---
>
> Key: NIFI-13265
> URL: https://issues.apache.org/jira/browse/NIFI-13265
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: Daniel Stieglitz
>Assignee: Daniel Stieglitz
>Priority: Minor
>
> There are still classes after the changes in NIFI-12075 and NIFI-12076 which
> instantiate an Object array for ComponentLog log statements. This ticket aims
> to remove those instantiations. In addition similar changes should be made to
> org.slf4j.Logger statements.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-13299) Prevent negative numbers in concurrent tasks
[ https://issues.apache.org/jira/browse/NIFI-13299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13299: --- Status: Patch Available (was: In Progress) > Prevent negative numbers in concurrent tasks > > > Key: NIFI-13299 > URL: https://issues.apache.org/jira/browse/NIFI-13299 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > For inputs like concurrent tasks we know that negative values are not > allowed. We should prevent them before the user can submit the form. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13312) Restructure as an nx monorepo
[ https://issues.apache.org/jira/browse/NIFI-13312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Fellows updated NIFI-13312: --- Status: Patch Available (was: In Progress) > Restructure as an nx monorepo > - > > Key: NIFI-13312 > URL: https://issues.apache.org/jira/browse/NIFI-13312 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Rob Fellows >Assignee: Rob Fellows >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > In preparation for maintaining various ui "apps" in this repo (nifi proper, > documentation, custom ui, ...) we should move to a nx monorepo structure > where nifi is the default project. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13312) Restructure as an nx monorepo
Rob Fellows created NIFI-13312: -- Summary: Restructure as an nx monorepo Key: NIFI-13312 URL: https://issues.apache.org/jira/browse/NIFI-13312 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Rob Fellows Assignee: Rob Fellows In preparation for maintaining various ui "apps" in this repo (nifi proper, documentation, custom ui, ...) we should move to a nx monorepo structure where nifi is the default project. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13304) ExcelReader - ability to split into flowfile per sheet
[ https://issues.apache.org/jira/browse/NIFI-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850403#comment-17850403 ] Daniel Stieglitz commented on NIFI-13304: - [~iiojj2] I believe I understand you now. I was thinking, would a new processor (e.g. SplitExcelSpreadsheet or SplitExcel) which will split up the original worksheet work for your use case? In other words for N sheets, this new processor would create N new worksheets where each worksheet has a single sheet. > ExcelReader - ability to split into flowfile per sheet > -- > > Key: NIFI-13304 > URL: https://issues.apache.org/jira/browse/NIFI-13304 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Philipp Korniets >Priority: Major > > Currently ConvertExcelToCSV processor, if processing excel with multiple > required sheets in it, produces flowfile per sheet. > New ExcelReader produces one flowfile with all data in it > > There should be a way to configure output to be sheet-per-flowfile > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13311) Turn DB adapters into controller services
Rajmund Takacs created NIFI-13311: - Summary: Turn DB adapters into controller services Key: NIFI-13311 URL: https://issues.apache.org/jira/browse/NIFI-13311 Project: Apache NiFi Issue Type: Improvement Components: Extensions Affects Versions: 2.0.0-M3, 2.0.0-M2, 2.0.0-M1 Reporter: Rajmund Takacs Assignee: Rajmund Takacs Most of the SQL processors have a property now, where the user is supposed to select a dialect their database understands. The list of supported dialects is currently hard-coded into the standard processors, and therefore there is no way to add a new one as an end-user, without forking NiFi. On the other hand, the user is allowed to supply their own DBCP controller service, by just dropping in the nar. So having a fixed list of supported SQL dialects is a serious limitation, since the user can have an unsupported database, and while they can create the necessary DBCP, they cannot add support for the dialect. We could resolve this problem by turning these fixed lists into controller services, so letting users fully interfacing NiFi with their own database. With NiFi 2.x, there is a property migration framework, that could be utilized in order to avoid breaking existing flows after upgrade. For 1.x line, we could probably introduce an option to pick the controller service too, by having an option in these fixed lists like 'Use Controller Service'. This could also be the default option, educating existing users. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-13299) Prevent negative numbers in concurrent tasks
[ https://issues.apache.org/jira/browse/NIFI-13299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman reassigned NIFI-13299: -- Assignee: Matt Gilman > Prevent negative numbers in concurrent tasks > > > Key: NIFI-13299 > URL: https://issues.apache.org/jira/browse/NIFI-13299 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > > For inputs like concurrent tasks we know that negative values are not > allowed. We should prevent them before the user can submit the form. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13284) Consider filtering current-canvas-route
[ https://issues.apache.org/jira/browse/NIFI-13284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13284: --- Status: Patch Available (was: In Progress) > Consider filtering current-canvas-route > --- > > Key: NIFI-13284 > URL: https://issues.apache.org/jira/browse/NIFI-13284 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Currently, the canvas tracks the current route so the user can be returned to > where they were when returning to the canvas. We should consider filtering > out any `edit` routes so that the user is returned to the place in the canvas > rather then in an Edit dialog. > Since dialogs are only and must be closed prior to using most navigation > controls this won't happen regularly. However a user routes through a Go To > command it will. By filtering out `edit` routes, it may be less confusing. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13310) Fix duplicate rat plugin declaration in jolt transform module
Joe Witt created NIFI-13310: --- Summary: Fix duplicate rat plugin declaration in jolt transform module Key: NIFI-13310 URL: https://issues.apache.org/jira/browse/NIFI-13310 Project: Apache NiFi Issue Type: Task Reporter: Joe Witt Assignee: Joe Witt [WARNING] [WARNING] Some problems were encountered while building the effective model for org.apache.nifi:nifi-jolt-transform-json-ui:war:2.0.0-SNAPSHOT [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin org.apache.rat:apache-rat-plugin @ line 209, column 21 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13303) Remove text indicating property verification is disabled
[ https://issues.apache.org/jira/browse/NIFI-13303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13303: --- Fix Version/s: 2.0.0-M4 Resolution: Fixed Status: Resolved (was: Patch Available) > Remove text indicating property verification is disabled > > > Key: NIFI-13303 > URL: https://issues.apache.org/jira/browse/NIFI-13303 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Rob Fellows >Assignee: Rob Fellows >Priority: Major > Fix For: 2.0.0-M4 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The text "Property verification is disabled" is extraneous. Don't display it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13303) Remove text indicating property verification is disabled
[ https://issues.apache.org/jira/browse/NIFI-13303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850363#comment-17850363 ] ASF subversion and git services commented on NIFI-13303: Commit 82cd1e5ef0f98a4e21c1cfbf6cffd58e848fc7e9 in nifi's branch refs/heads/main from Rob Fellows [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=82cd1e5ef0 ] [NIFI-13303] - Remove text indicating property verification is disabled. (#8884) This closes #8884 > Remove text indicating property verification is disabled > > > Key: NIFI-13303 > URL: https://issues.apache.org/jira/browse/NIFI-13303 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Rob Fellows >Assignee: Rob Fellows >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > The text "Property verification is disabled" is extraneous. Don't display it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (NIFI-13231) Update GitHubFlowRegistryClient to generate App Installation Token
[ https://issues.apache.org/jira/browse/NIFI-13231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850286#comment-17850286 ] Vansh Chaudhary edited comment on NIFI-13231 at 5/29/24 11:40 AM: -- Hi [~exceptionfactory] , I've added the authentication with Private key. can you check and review , I've added method to generate Token since JWTTokenProvider didn't process PKCS#1 keys. [https://github.com/apache/nifi/compare/main...maybevanshh:nifi:main] was (Author: JIRAUSER305277): Hi [~exceptionfactory] , I've added the authentication with Private key. can you check and review before i raise the pr request? https://github.com/apache/nifi/compare/main...maybevanshh:nifi:main > Update GitHubFlowRegistryClient to generate App Installation Token > -- > > Key: NIFI-13231 > URL: https://issues.apache.org/jira/browse/NIFI-13231 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M3 >Reporter: Brian Ghigiarelli >Assignee: Vansh Chaudhary >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The new GitHubFlowRegistryClient accepts two types of authentication: > # Personal Access Token > # App Installation Token > The App Installation Token requires the user to input the token as a > property, then uses that to communicate with GitHub. However, this token is > short-lived and would require frequent updates (~hourly). > Instead of directly providing the token, the GitHubFlowRegistryClient should > accept as properties: > # App ID > # Private Key (PEM text format) > and use these values to generate a short-lived token, following the guide at > https://docs.github.com/en/apps/creating-github-apps/authenticating-with-a-github-app/generating-a-json-web-token-jwt-for-a-github-app#generating-a-json-web-token-jwt -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MINIFICPP-2390) Save build type and build dir in python bootstrap state
Gábor Gyimesi created MINIFICPP-2390: Summary: Save build type and build dir in python bootstrap state Key: MINIFICPP-2390 URL: https://issues.apache.org/jira/browse/MINIFICPP-2390 Project: Apache NiFi MiNiFi C++ Issue Type: Improvement Reporter: Gábor Gyimesi Assignee: Gábor Gyimesi -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13309) MiNiFi flow update fails to lookup compatible bundles
Ferenc Erdei created NIFI-13309:
---
Summary: MiNiFi flow update fails to lookup compatible bundles
Key: NIFI-13309
URL: https://issues.apache.org/jira/browse/NIFI-13309
Project: Apache NiFi
Issue Type: Bug
Components: MiNiFi
Affects Versions: 2.0.0-M3, 2.0.0-M2, 2.0.0-M1
Reporter: Ferenc Erdei
Assignee: Ferenc Erdei
Fix For: 2.0.0-M4
h3. Issue
Publishing a MiNiFi flow that was designed with not the same manifest version
as the current MiNiFi runtime use causes flow update failure.
Steps to reproduce:
* Design a Flow with the previous NiFi version
* Publish that flow through C2 Server
h3. Expected behaviour
The flow should be loaded with the compatible bundles.
h3. Actual behaviour
Exceptions in logs:
{noformat}
2024-05-29 11:43:43,872 INFO [pool-15-thread-1]
o.a.n.f.s.StandardVersionedComponentSynchronizer Added
GhostProcessor[id=f4d7586c-d575-4255-bbe1-c0f7b129a7ea] to
StandardProcessGroup[identifier=7072239a-c047-4d5e-8e68-cd2cbc651343,name=root]
2024-05-29 11:43:43,872 ERROR [pool-15-thread-1]
o.a.nifi.controller.ExtensionBuilder Could not create Processor of type
org.apache.nifi.processors.standard.GenerateFlowFile for ID
d7c7463f-beaf-4122-b7af-581a41740512 due to:
org.apache.nifi.processors.standard.GenerateFlowFile; creating "Ghost"
implementation{noformat}
And Flow is reverted to the previous flow.
h3. Root cause
We have a condition in
[https://github.com/apache/nifi/blob/main/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/serialization/VersionedFlowSynchronizer.java#L170]
for the existing flow, but we should have a null check for the proposed, and
map the compatible bundles even if the old flow was empty.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-13231) Update GitHubFlowRegistryClient to generate App Installation Token
[ https://issues.apache.org/jira/browse/NIFI-13231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850286#comment-17850286 ] Vansh Chaudhary commented on NIFI-13231: Hi [~exceptionfactory] , I've added the authentication with Private key. can you check and review before i raise the pr request? https://github.com/apache/nifi/compare/main...maybevanshh:nifi:main > Update GitHubFlowRegistryClient to generate App Installation Token > -- > > Key: NIFI-13231 > URL: https://issues.apache.org/jira/browse/NIFI-13231 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M3 >Reporter: Brian Ghigiarelli >Assignee: Vansh Chaudhary >Priority: Major > > The new GitHubFlowRegistryClient accepts two types of authentication: > # Personal Access Token > # App Installation Token > The App Installation Token requires the user to input the token as a > property, then uses that to communicate with GitHub. However, this token is > short-lived and would require frequent updates (~hourly). > Instead of directly providing the token, the GitHubFlowRegistryClient should > accept as properties: > # App ID > # Private Key (PEM text format) > and use these values to generate a short-lived token, following the guide at > https://docs.github.com/en/apps/creating-github-apps/authenticating-with-a-github-app/generating-a-json-web-token-jwt-for-a-github-app#generating-a-json-web-token-jwt -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13285) Fit on Enter PG
[ https://issues.apache.org/jira/browse/NIFI-13285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Fellows updated NIFI-13285: --- Fix Version/s: 2.0.0-M4 Resolution: Fixed Status: Resolved (was: Patch Available) > Fit on Enter PG > --- > > Key: NIFI-13285 > URL: https://issues.apache.org/jira/browse/NIFI-13285 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > Fix For: 2.0.0-M4 > > Time Spent: 0.5h > Remaining Estimate: 0h > > When navigating into a PG where there is no saved viewport position we should > consider executing a fit action so that flow is shown centered on the canvas. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13285) Fit on Enter PG
[ https://issues.apache.org/jira/browse/NIFI-13285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850217#comment-17850217 ] ASF subversion and git services commented on NIFI-13285: Commit ffa5e8473d568cc31fc3cf9261b81a316c2bb64d in nifi's branch refs/heads/main from Matt Gilman [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=ffa5e8473d ] NIFI-13285: If there is no transform to restore for the current viewport, executing a zoom fit (#8874) * NIFI-13285: - If there is no transform to restore for the current viewport, executing a zoom fit. * NIFI-13285: - Adjusting the canvas position styles and zoom fit calculations. This closes #8874 > Fit on Enter PG > --- > > Key: NIFI-13285 > URL: https://issues.apache.org/jira/browse/NIFI-13285 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > When navigating into a PG where there is no saved viewport position we should > consider executing a fit action so that flow is shown centered on the canvas. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (NIFI-13308) Bump aws, spring, jersey, netty versions to latest
[ https://issues.apache.org/jira/browse/NIFI-13308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850166#comment-17850166 ] Joe Witt edited comment on NIFI-13308 at 5/28/24 8:32 PM: -- com.slack.api/bot-socket-mode 1.39.2 1.39.3 org.apache.maven/maven-artifact 3.9.6 3.9.7 org.mariadb.jdbc mariadb-java-client 3.3.3 3.4.0 org.springframework.boot spring-boot-* 3.2.5 3.2.6 software.amazon.awssdk * 2.25.55 2.25.60 org.springframework spring* 6.1.7 6.1.8 org.glassfish.jersey.* * 3.1.6 3.1.7 io.netty netty-* 4.1.109.Final 4.1.110.Final com.box box-java-sdk 4.9.0 4.9.1 com.amazonaws aws* 1.12.725 1.12.730 was (Author: joewitt): com.slack.api/bot-socket-mode 1.39.2 1.39.3 org.apache.maven/maven-artifact 3.9.6 3.9.7 org.mariadb.jdbc mariadb-java-client 3.3.3 3.4.0 org.springframework.boot spring-boot-* 3.2.5 3.2.6 software.amazon.awssdk * 2.25.55 2.25.60 org.springframework spring* 6.1.7 6.1.8 org.glassfish.jersey.* * 3.1.6 3.1.7 io.netty netty-* 4.1.109.Final 4.1.110.Final com.nimbusds numbus-jose-jwt 9.37.3 9.39.1 com.nimbusds oauth2-oidc-sdk 11.10.1 11.12 com.box box-java-sdk 4.9.0 4.9.1 com.amazonaws aws* 1.12.725 1.12.730 > Bump aws, spring, jersey, netty versions to latest > -- > > Key: NIFI-13308 > URL: https://issues.apache.org/jira/browse/NIFI-13308 > Project: Apache NiFi > Issue Type: Task >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (NIFI-13308) Bump aws, spring, jersey, netty versions to latest
[ https://issues.apache.org/jira/browse/NIFI-13308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850166#comment-17850166 ] Joe Witt edited comment on NIFI-13308 at 5/28/24 8:31 PM: -- com.slack.api/bot-socket-mode 1.39.2 1.39.3 org.apache.maven/maven-artifact 3.9.6 3.9.7 org.mariadb.jdbc mariadb-java-client 3.3.3 3.4.0 org.springframework.boot spring-boot-* 3.2.5 3.2.6 software.amazon.awssdk * 2.25.55 2.25.60 org.springframework spring* 6.1.7 6.1.8 org.glassfish.jersey.* * 3.1.6 3.1.7 io.netty netty-* 4.1.109.Final 4.1.110.Final com.nimbusds numbus-jose-jwt 9.37.3 9.39.1 com.nimbusds oauth2-oidc-sdk 11.10.1 11.12 com.box box-java-sdk 4.9.0 4.9.1 com.amazonaws aws* 1.12.725 1.12.730 was (Author: joewitt): com.slack.api/bot-socket-mode 1.39.2 1.39.3 org.apache.maven/maven-artifact 3.9.6 3.9.7 org.mariadb.jdbc mariadb-java-client 3.3.3 3.4.0 org.springframework.boot spring-boot-* 3.2.5 3.2.6 software.amazon.awssdk * 2.25.55 2.25.60 org.springframework spring* 6.1.7 6.1.8 org.glassfish.jersey.* * 3.1.6 3.1.7 net.snowflake snowflake-jdbc 3.14.5 3.16.1 (??) io.netty netty-* 4.1.109.Final 4.1.110.Final com.nimbusds numbus-jose-jwt 9.37.3 9.39.1 com.nimbusds oauth2-oidc-sdk 11.10.1 11.12 com.box box-java-sdk 4.9.0 4.9.1 com.amazonaws aws* 1.12.725 1.12.730 > Bump aws, spring, jersey, netty versions to latest > -- > > Key: NIFI-13308 > URL: https://issues.apache.org/jira/browse/NIFI-13308 > Project: Apache NiFi > Issue Type: Task >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (NIFI-13308) Bump aws, spring, jersey, netty versions to latest
[ https://issues.apache.org/jira/browse/NIFI-13308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850166#comment-17850166 ] Joe Witt edited comment on NIFI-13308 at 5/28/24 8:29 PM: -- com.slack.api/bot-socket-mode 1.39.2 1.39.3 org.apache.maven/maven-artifact 3.9.6 3.9.7 org.mariadb.jdbc mariadb-java-client 3.3.3 3.4.0 org.springframework.boot spring-boot-* 3.2.5 3.2.6 software.amazon.awssdk * 2.25.55 2.25.60 org.springframework spring* 6.1.7 6.1.8 org.glassfish.jersey.* * 3.1.6 3.1.7 net.snowflake snowflake-jdbc 3.14.5 3.16.1 (??) io.netty netty-* 4.1.109.Final 4.1.110.Final com.nimbusds numbus-jose-jwt 9.37.3 9.39.1 com.nimbusds oauth2-oidc-sdk 11.10.1 11.12 com.box box-java-sdk 4.9.0 4.9.1 com.amazonaws aws* 1.12.725 1.12.730 was (Author: joewitt): com.slack.api/bot-socket-mode 1.39.2 1.39.3 org.apache.maven/maven-artifact 3.9.6 3.9.7 org.mariadb.jdbc mariadb-java-client 3.3.3 3.4.0 org.springframework.boot spring-boot-* 3.2.5 3.2.6 software.amazon.awssdk * 2.25.55 2.25.60 org.springframework spring* 6.1.7 6.1.8 org.glassfish.jersey.* * 3.1.6 3.1.7 org.apache.maven.plugin-tools maven-plugin-annotations 3.12.0 3.13.0 net.snowflake snowflake-jdbc 3.14.5 3.16.1 (??) io.netty netty-* 4.1.109.Final 4.1.110.Final com.nimbusds numbus-jose-jwt 9.37.3 9.39.1 com.nimbusds oauth2-oidc-sdk 11.10.1 11.12 com.box box-java-sdk 4.9.0 4.9.1 com.amazonaws aws* 1.12.725 1.12.730 > Bump aws, spring, jersey, netty versions to latest > -- > > Key: NIFI-13308 > URL: https://issues.apache.org/jira/browse/NIFI-13308 > Project: Apache NiFi > Issue Type: Task >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (NIFI-13308) Bump aws, spring, jersey, netty versions to latest
[ https://issues.apache.org/jira/browse/NIFI-13308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850166#comment-17850166 ] Joe Witt edited comment on NIFI-13308 at 5/28/24 8:27 PM: -- com.slack.api/bot-socket-mode 1.39.2 1.39.3 org.apache.maven/maven-artifact 3.9.6 3.9.7 org.mariadb.jdbc mariadb-java-client 3.3.3 3.4.0 org.springframework.boot spring-boot-* 3.2.5 3.2.6 software.amazon.awssdk * 2.25.55 2.25.60 org.springframework spring* 6.1.7 6.1.8 org.glassfish.jersey.* * 3.1.6 3.1.7 org.apache.maven.plugin-tools maven-plugin-annotations 3.12.0 3.13.0 net.snowflake snowflake-jdbc 3.14.5 3.16.1 (??) io.netty netty-* 4.1.109.Final 4.1.110.Final com.nimbusds numbus-jose-jwt 9.37.3 9.39.1 com.nimbusds oauth2-oidc-sdk 11.10.1 11.12 com.box box-java-sdk 4.9.0 4.9.1 com.amazonaws aws* 1.12.725 1.12.730 was (Author: joewitt): com.slack.api/bot-socket-mode 1.39.2 org.apache.maven/maven-artifact 3.9.6 3.9.7 org.mariadb.jdbc mariadb-java-client 3.3.3 3.4.0 org.springframework.boot spring-boot-* 3.2.5 3.2.6 software.amazon.awssdk * 2.25.55 2.25.60 org.springframework spring* 6.1.7 6.1.8 org.glassfish.jersey.* * 3.1.6 3.1.7 org.apache.maven.plugin-tools maven-plugin-annotations 3.12.0 3.13.0 net.snowflake snowflake-jdbc 3.14.5 3.16.1 (??) io.netty netty-* 4.1.109.Final 4.1.110.Final com.nimbusds numbus-jose-jwt 9.37.3 9.39.1 com.nimbusds oauth2-oidc-sdk 11.10.1 11.12 com.box box-java-sdk 4.9.0 4.9.1 com.amazonaws aws* 1.12.725 1.12.730 > Bump aws, spring, jersey, netty versions to latest > -- > > Key: NIFI-13308 > URL: https://issues.apache.org/jira/browse/NIFI-13308 > Project: Apache NiFi > Issue Type: Task >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13308) Bump aws, spring, jersey, netty versions to latest
[ https://issues.apache.org/jira/browse/NIFI-13308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850166#comment-17850166 ] Joe Witt commented on NIFI-13308: - com.slack.api/bot-socket-mode 1.39.2 org.apache.maven/maven-artifact 3.9.6 3.9.7 org.mariadb.jdbc mariadb-java-client 3.3.3 3.4.0 org.springframework.boot spring-boot-* 3.2.5 3.2.6 software.amazon.awssdk * 2.25.55 2.25.60 org.springframework spring* 6.1.7 6.1.8 org.glassfish.jersey.* * 3.1.6 3.1.7 org.apache.maven.plugin-tools maven-plugin-annotations 3.12.0 3.13.0 net.snowflake snowflake-jdbc 3.14.5 3.16.1 (??) io.netty netty-* 4.1.109.Final 4.1.110.Final com.nimbusds numbus-jose-jwt 9.37.3 9.39.1 com.nimbusds oauth2-oidc-sdk 11.10.1 11.12 com.box box-java-sdk 4.9.0 4.9.1 com.amazonaws aws* 1.12.725 1.12.730 > Bump aws, spring, jersey, netty versions to latest > -- > > Key: NIFI-13308 > URL: https://issues.apache.org/jira/browse/NIFI-13308 > Project: Apache NiFi > Issue Type: Task >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13308) Bump aws, spring, jersey, netty versions to latest
Joe Witt created NIFI-13308: --- Summary: Bump aws, spring, jersey, netty versions to latest Key: NIFI-13308 URL: https://issues.apache.org/jira/browse/NIFI-13308 Project: Apache NiFi Issue Type: Task Reporter: Joe Witt Assignee: Joe Witt -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-13284) Consider filtering current-canvas-route
[ https://issues.apache.org/jira/browse/NIFI-13284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman reassigned NIFI-13284: -- Assignee: Matt Gilman > Consider filtering current-canvas-route > --- > > Key: NIFI-13284 > URL: https://issues.apache.org/jira/browse/NIFI-13284 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > > Currently, the canvas tracks the current route so the user can be returned to > where they were when returning to the canvas. We should consider filtering > out any `edit` routes so that the user is returned to the place in the canvas > rather then in an Edit dialog. > Since dialogs are only and must be closed prior to using most navigation > controls this won't happen regularly. However a user routes through a Go To > command it will. By filtering out `edit` routes, it may be less confusing. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12967) Improve navigation to/from Canvas
[ https://issues.apache.org/jira/browse/NIFI-12967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Aslan updated NIFI-12967: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Improve navigation to/from Canvas > - > > Key: NIFI-12967 > URL: https://issues.apache.org/jira/browse/NIFI-12967 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > Time Spent: 1h 40m > Remaining Estimate: 0h > > When leaving the Canvas (ie listing queue, viewing documentation, etc) the UI > should offer a more intuitive means to navigate back to where they were > before. Currently they must use the Global menu or click on the logo in the > header. However, these options are not necessarily obvious at first. The > browser back button also works but the UI should probably offer some in the > application. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12967) Improve navigation to/from Canvas
[ https://issues.apache.org/jira/browse/NIFI-12967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850160#comment-17850160 ] ASF subversion and git services commented on NIFI-12967: Commit f0e1cdcb22f1fdeef804a005813edc0c09929d87 in nifi's branch refs/heads/main from Matt Gilman [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=f0e1cdcb22 ] NIFI-12967: Introducing Back action (#8859) * NIFI-12967: - Adding support for navigating back to the users previous location in certain circumstances like going to a Controller Service, managing access policies, going to parameters, viewing documentation, opening advanced UIs, and viewing data provenance. - Cleaning unnecessary instances of postUpdateNavigation. * NIFI-12967: - Updating the implementation to leverage router events and router state to simplify needed changes. * NIFI-12967: - Conditionally resetting or popping back navigation history because on routing context. * NIFI-12967: - Adding support for navigating back from queue listing and provenance. * NIFI-12967: - Conditionally applying the back navigation following a component update. * NIFI-12967: - Adding back from CS service listing. * NIFI-12967: - Adding back from Go To CS. - Restoring some space in the context menu. * NIFI-12967: - Prevent duplicate entries in the back navigation stack. * NIFI-12967: - Not executing pop through navigation extras because it can result in multiple pops if the user uses their back/forward browser buttons. Instead, always popping until we encounter a back navigation that is still within a route boundary. > Improve navigation to/from Canvas > - > > Key: NIFI-12967 > URL: https://issues.apache.org/jira/browse/NIFI-12967 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > Time Spent: 1h 40m > Remaining Estimate: 0h > > When leaving the Canvas (ie listing queue, viewing documentation, etc) the UI > should offer a more intuitive means to navigate back to where they were > before. Currently they must use the Global menu or click on the logo in the > header. However, these options are not necessarily obvious at first. The > browser back button also works but the UI should probably offer some in the > application. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (NIFI-13304) ExcelReader - ability to split into flowfile per sheet
[ https://issues.apache.org/jira/browse/NIFI-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850141#comment-17850141 ] Philipp Korniets edited comment on NIFI-13304 at 5/28/24 7:02 PM: -- This assumes I should know which columns belong to which sheet. was (Author: iiojj2): This assumes I should know which columns belong to which file. > ExcelReader - ability to split into flowfile per sheet > -- > > Key: NIFI-13304 > URL: https://issues.apache.org/jira/browse/NIFI-13304 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Philipp Korniets >Priority: Major > > Currently ConvertExcelToCSV processor, if processing excel with multiple > required sheets in it, produces flowfile per sheet. > New ExcelReader produces one flowfile with all data in it > > There should be a way to configure output to be sheet-per-flowfile > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (NIFI-13304) ExcelReader - ability to split into flowfile per sheet
[ https://issues.apache.org/jira/browse/NIFI-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850141#comment-17850141 ] Philipp Korniets edited comment on NIFI-13304 at 5/28/24 7:02 PM: -- This assumes I should know which columns belong to which file. was (Author: iiojj2): I don't think this will work > ExcelReader - ability to split into flowfile per sheet > -- > > Key: NIFI-13304 > URL: https://issues.apache.org/jira/browse/NIFI-13304 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Philipp Korniets >Priority: Major > > Currently ConvertExcelToCSV processor, if processing excel with multiple > required sheets in it, produces flowfile per sheet. > New ExcelReader produces one flowfile with all data in it > > There should be a way to configure output to be sheet-per-flowfile > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13304) ExcelReader - ability to split into flowfile per sheet
[ https://issues.apache.org/jira/browse/NIFI-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850141#comment-17850141 ] Philipp Korniets commented on NIFI-13304: - I don't think this will work > ExcelReader - ability to split into flowfile per sheet > -- > > Key: NIFI-13304 > URL: https://issues.apache.org/jira/browse/NIFI-13304 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Philipp Korniets >Priority: Major > > Currently ConvertExcelToCSV processor, if processing excel with multiple > required sheets in it, produces flowfile per sheet. > New ExcelReader produces one flowfile with all data in it > > There should be a way to configure output to be sheet-per-flowfile > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13305) Upgrade HBase to 2.6.0
[ https://issues.apache.org/jira/browse/NIFI-13305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Witt updated NIFI-13305: Fix Version/s: 2.0.0-M4 Resolution: Fixed Status: Resolved (was: Patch Available) > Upgrade HBase to 2.6.0 > -- > > Key: NIFI-13305 > URL: https://issues.apache.org/jira/browse/NIFI-13305 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Fix For: 2.0.0-M4 > > Time Spent: 40m > Remaining Estimate: 0h > > HBase [2.6.0|https://issues.apache.org/jira/projects/HBASE/versions/12350930] > includes a number of bug fixes, improvements, and transitive dependency > upgrades that should be incorporate in client service components. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13305) Upgrade HBase to 2.6.0
[ https://issues.apache.org/jira/browse/NIFI-13305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850137#comment-17850137 ] ASF subversion and git services commented on NIFI-13305: Commit 68630b64c1b98a1237b0ce3a56ff73b93e92e1e9 in nifi's branch refs/heads/main from David Handermann [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=68630b64c1 ] NIFI-13305 Upgraded HBase from 2.5.8 to 2.6.0 This closes 8886 - Removed unnecessary transitive dependency overrides Signed-off-by: Joseph Witt > Upgrade HBase to 2.6.0 > -- > > Key: NIFI-13305 > URL: https://issues.apache.org/jira/browse/NIFI-13305 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > HBase [2.6.0|https://issues.apache.org/jira/projects/HBASE/versions/12350930] > includes a number of bug fixes, improvements, and transitive dependency > upgrades that should be incorporate in client service components. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13304) ExcelReader - ability to split into flowfile per sheet
[
https://issues.apache.org/jira/browse/NIFI-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850136#comment-17850136
]
Daniel Stieglitz commented on NIFI-13304:
-
{quote}
Thinking about it - if there are two different sets of columns in two sheets -
we can't really use QueryRecord or Partition.
{quote}
I am not sure why not. Couldn't you have a schema which encompasses both and
then have two queries to extract each of the data into separate flow files?
> ExcelReader - ability to split into flowfile per sheet
> --
>
> Key: NIFI-13304
> URL: https://issues.apache.org/jira/browse/NIFI-13304
> Project: Apache NiFi
> Issue Type: New Feature
>Reporter: Philipp Korniets
>Priority: Major
>
> Currently ConvertExcelToCSV processor, if processing excel with multiple
> required sheets in it, produces flowfile per sheet.
> New ExcelReader produces one flowfile with all data in it
>
> There should be a way to configure output to be sheet-per-flowfile
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-13304) ExcelReader - ability to split into flowfile per sheet
[ https://issues.apache.org/jira/browse/NIFI-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850123#comment-17850123 ] Philipp Korniets edited comment on NIFI-13304 at 5/28/24 6:15 PM: -- Thinking about it - if there are two different sets of columns in two sheets - we can't really use QueryRecord or Partition. Trick with sheet name - duplicating flowfiles - not a nice solution. Looks more like a hack.. The workaround is update attribute + retry But simple and easy ConvertExcelToCSV is much better was (Author: iiojj2): Thinking about it - if there are two different sets of columns in two she - we can't really use QueryRecord or Partition. Trick with sheet name - duplicating flowfiles - not a nice solution. Looks more like a hack.. The workaround is update attribute + retry But simple and easy ConvertExcelToCSV is much better > ExcelReader - ability to split into flowfile per sheet > -- > > Key: NIFI-13304 > URL: https://issues.apache.org/jira/browse/NIFI-13304 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Philipp Korniets >Priority: Major > > Currently ConvertExcelToCSV processor, if processing excel with multiple > required sheets in it, produces flowfile per sheet. > New ExcelReader produces one flowfile with all data in it > > There should be a way to configure output to be sheet-per-flowfile > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (NIFI-13304) ExcelReader - ability to split into flowfile per sheet
[ https://issues.apache.org/jira/browse/NIFI-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850123#comment-17850123 ] Philipp Korniets edited comment on NIFI-13304 at 5/28/24 6:14 PM: -- Thinking about it - if there are two different sets of columns in two she - we can't really use QueryRecord or Partition. Trick with sheet name - duplicating flowfiles - not a nice solution. Looks more like a hack.. The workaround is update attribute + retry But simple and easy ConvertExcelToCSV is much better was (Author: iiojj2): Thinking about it - if there are two different sets of columns in two she - we can't really use QueryRecord or Partition. Trick with sheet name - duplicating flowfiles - not a nice solution. Looks more like a hack.. > ExcelReader - ability to split into flowfile per sheet > -- > > Key: NIFI-13304 > URL: https://issues.apache.org/jira/browse/NIFI-13304 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Philipp Korniets >Priority: Major > > Currently ConvertExcelToCSV processor, if processing excel with multiple > required sheets in it, produces flowfile per sheet. > New ExcelReader produces one flowfile with all data in it > > There should be a way to configure output to be sheet-per-flowfile > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13304) ExcelReader - ability to split into flowfile per sheet
[ https://issues.apache.org/jira/browse/NIFI-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850123#comment-17850123 ] Philipp Korniets commented on NIFI-13304: - Thinking about it - if there are two different sets of columns in two she - we can't really use QueryRecord or Partition. Trick with sheet name - duplicating flowfiles - not a nice solution. Looks more like a hack.. > ExcelReader - ability to split into flowfile per sheet > -- > > Key: NIFI-13304 > URL: https://issues.apache.org/jira/browse/NIFI-13304 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Philipp Korniets >Priority: Major > > Currently ConvertExcelToCSV processor, if processing excel with multiple > required sheets in it, produces flowfile per sheet. > New ExcelReader produces one flowfile with all data in it > > There should be a way to configure output to be sheet-per-flowfile > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13304) ExcelReader - ability to split into flowfile per sheet
[ https://issues.apache.org/jira/browse/NIFI-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850119#comment-17850119 ] Daniel Stieglitz commented on NIFI-13304: - [~iiojj2] What was the issue with using the sheet name trick you mentioned and then using QueryRecord to create the desired flow files? > ExcelReader - ability to split into flowfile per sheet > -- > > Key: NIFI-13304 > URL: https://issues.apache.org/jira/browse/NIFI-13304 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Philipp Korniets >Priority: Major > > Currently ConvertExcelToCSV processor, if processing excel with multiple > required sheets in it, produces flowfile per sheet. > New ExcelReader produces one flowfile with all data in it > > There should be a way to configure output to be sheet-per-flowfile > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13304) ExcelReader - ability to split into flowfile per sheet
[ https://issues.apache.org/jira/browse/NIFI-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850118#comment-17850118 ] Philipp Korniets commented on NIFI-13304: - [~dstiegli1] we need a way to split data from one file into multiple flowfiles easily. Currently it's impossible with excelReader > ExcelReader - ability to split into flowfile per sheet > -- > > Key: NIFI-13304 > URL: https://issues.apache.org/jira/browse/NIFI-13304 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Philipp Korniets >Priority: Major > > Currently ConvertExcelToCSV processor, if processing excel with multiple > required sheets in it, produces flowfile per sheet. > New ExcelReader produces one flowfile with all data in it > > There should be a way to configure output to be sheet-per-flowfile > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11858) Improve column name normalization in PutDatabaseRecord processor
[
https://issues.apache.org/jira/browse/NIFI-11858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Burgess updated NIFI-11858:
Status: Patch Available (was: Open)
> Improve column name normalization in PutDatabaseRecord processor
>
>
> Key: NIFI-11858
> URL: https://issues.apache.org/jira/browse/NIFI-11858
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: RAVINARAYAN SINGH
>Assignee: RAVINARAYAN SINGH
>Priority: Minor
> Time Spent: 4h 20m
> Remaining Estimate: 0h
>
> *Current Behavior:*
> The current behavior of the PutDatabaseRecord processor when
> `column_translation` is set to true involves removing underscores ("_") from
> column names and replacing them with an empty string. This results in column
> names like "Pic_1_11" and "Pic_11_1" being considered the same, which may not
> be desired, especially in databases that allow underscores as valid
> characters in column names.
> *Proposed Improvements:*
> To address this issue and provide users with more control over the
> normalization process, we propose the following improvements:
> 1. Allow users to specify their own regex expression: Instead of hard-coding
> the normalization behavior, we can enhance the function by allowing users to
> pass a custom regex expression as the `column_translation` parameter. This
> way, advanced users can define their specific normalization rules based on
> their database requirements.
> 2. Predefined normalization options: To simplify the process for users who
> don't want to create their own regex expressions, we can provide some
> well-defined translation options, such as:
> a. REMOVE_UNDERSCORE: This option will remove all underscores from the
> column names.
> b. REMOVE_ALL_SPECIAL_CHAR: This option will remove all special characters
> (non-alphanumeric and non-space characters) from the column names.
> c. REMOVE_SPACE: This option will remove all spaces from the column names.
> *Expected Behavior:*
> With these improvements, users will have more flexibility and control over
> the normalization process when using the PutDatabaseRecord processor. They
> can either choose predefined normalization options or specify their custom
> regex expression to suit their specific database requirements.
> *Note:*
> This improvement will enhance the usability and compatibility of the
> PutDatabaseRecord processor with various database systems that have different
> rules for column name normalization.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-13304) ExcelReader - ability to split into flowfile per sheet
[ https://issues.apache.org/jira/browse/NIFI-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850117#comment-17850117 ] Daniel Stieglitz commented on NIFI-13304: - [~iiojj2] Just trying to clarify whether you have a path forward or not (in other words is this ticket still necessary)? > ExcelReader - ability to split into flowfile per sheet > -- > > Key: NIFI-13304 > URL: https://issues.apache.org/jira/browse/NIFI-13304 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Philipp Korniets >Priority: Major > > Currently ConvertExcelToCSV processor, if processing excel with multiple > required sheets in it, produces flowfile per sheet. > New ExcelReader produces one flowfile with all data in it > > There should be a way to configure output to be sheet-per-flowfile > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (NIFI-13304) ExcelReader - ability to split into flowfile per sheet
[ https://issues.apache.org/jira/browse/NIFI-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850113#comment-17850113 ] Philipp Korniets edited comment on NIFI-13304 at 5/28/24 5:16 PM: -- Column with sheet name will do a trick, which can be used in partition record or QueryRecord Example- sheet with data and sheet with dictionary which we want to join (enrich): we use ConvertExcelToCSV (which generates 2 flowfiles) then use joinEnrichment of two sheet with the step of setting groupid and enrichment.role was (Author: iiojj2): Column with sheet name will do a trick, which will can be used in partition record or QueryRecord Example- sheet with data and sheet with dictionary which we want to join (enrich): we use ConvertExcelToCSV (which generates 2 flowfiles) then use joinEnrichment of two sheet with the step of setting groupid and enrichment.role > ExcelReader - ability to split into flowfile per sheet > -- > > Key: NIFI-13304 > URL: https://issues.apache.org/jira/browse/NIFI-13304 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Philipp Korniets >Priority: Major > > Currently ConvertExcelToCSV processor, if processing excel with multiple > required sheets in it, produces flowfile per sheet. > New ExcelReader produces one flowfile with all data in it > > There should be a way to configure output to be sheet-per-flowfile > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (NIFI-13304) ExcelReader - ability to split into flowfile per sheet
[ https://issues.apache.org/jira/browse/NIFI-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850110#comment-17850110 ] Philipp Korniets edited comment on NIFI-13304 at 5/28/24 5:16 PM: -- I think an approach to treat excel as a single sheet data source is erroneous. So a record reader which treats it this way will create complexity where it's not needed was (Author: iiojj2): I think an approach to treat excel as a single sheet data source is erroneous. So a record reader which treats it this way will create complexity where it's not need. > ExcelReader - ability to split into flowfile per sheet > -- > > Key: NIFI-13304 > URL: https://issues.apache.org/jira/browse/NIFI-13304 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Philipp Korniets >Priority: Major > > Currently ConvertExcelToCSV processor, if processing excel with multiple > required sheets in it, produces flowfile per sheet. > New ExcelReader produces one flowfile with all data in it > > There should be a way to configure output to be sheet-per-flowfile > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (NIFI-13304) ExcelReader - ability to split into flowfile per sheet
[ https://issues.apache.org/jira/browse/NIFI-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850113#comment-17850113 ] Philipp Korniets edited comment on NIFI-13304 at 5/28/24 5:11 PM: -- Column with sheet name will do a trick, which will can be used in partition record or QueryRecord Example- sheet with data and sheet with dictionary which we want to join (enrich): we use ConvertExcelToCSV (which generates 2 flowfiles) then use joinEnrichment of two sheet with the step of setting groupid and enrichment.role was (Author: iiojj2): Column with sheet name will do a trick, which will can be used in partition record or QueryRecord > ExcelReader - ability to split into flowfile per sheet > -- > > Key: NIFI-13304 > URL: https://issues.apache.org/jira/browse/NIFI-13304 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Philipp Korniets >Priority: Major > > Currently ConvertExcelToCSV processor, if processing excel with multiple > required sheets in it, produces flowfile per sheet. > New ExcelReader produces one flowfile with all data in it > > There should be a way to configure output to be sheet-per-flowfile > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (NIFI-13304) ExcelReader - ability to split into flowfile per sheet
[ https://issues.apache.org/jira/browse/NIFI-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850110#comment-17850110 ] Philipp Korniets edited comment on NIFI-13304 at 5/28/24 5:06 PM: -- I think an approach to treat excel as a single sheet data source is erroneous. So a record reader which treats it this way will create complexity where it's not need. was (Author: iiojj2): I think an approach to treat excel as a single sheet data source is erroneous. So a record reader which treats it this way will create complexity where it's not needed. I'm coming from a lot of experience with excel consumption in financial industry. > ExcelReader - ability to split into flowfile per sheet > -- > > Key: NIFI-13304 > URL: https://issues.apache.org/jira/browse/NIFI-13304 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Philipp Korniets >Priority: Major > > Currently ConvertExcelToCSV processor, if processing excel with multiple > required sheets in it, produces flowfile per sheet. > New ExcelReader produces one flowfile with all data in it > > There should be a way to configure output to be sheet-per-flowfile > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13304) ExcelReader - ability to split into flowfile per sheet
[ https://issues.apache.org/jira/browse/NIFI-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850113#comment-17850113 ] Philipp Korniets commented on NIFI-13304: - ColumnName with sheet name will do a trick, which will can be used in partition record or QueryRecord > ExcelReader - ability to split into flowfile per sheet > -- > > Key: NIFI-13304 > URL: https://issues.apache.org/jira/browse/NIFI-13304 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Philipp Korniets >Priority: Major > > Currently ConvertExcelToCSV processor, if processing excel with multiple > required sheets in it, produces flowfile per sheet. > New ExcelReader produces one flowfile with all data in it > > There should be a way to configure output to be sheet-per-flowfile > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (NIFI-13304) ExcelReader - ability to split into flowfile per sheet
[ https://issues.apache.org/jira/browse/NIFI-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850113#comment-17850113 ] Philipp Korniets edited comment on NIFI-13304 at 5/28/24 5:02 PM: -- Column with sheet name will do a trick, which will can be used in partition record or QueryRecord was (Author: iiojj2): ColumnName with sheet name will do a trick, which will can be used in partition record or QueryRecord > ExcelReader - ability to split into flowfile per sheet > -- > > Key: NIFI-13304 > URL: https://issues.apache.org/jira/browse/NIFI-13304 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Philipp Korniets >Priority: Major > > Currently ConvertExcelToCSV processor, if processing excel with multiple > required sheets in it, produces flowfile per sheet. > New ExcelReader produces one flowfile with all data in it > > There should be a way to configure output to be sheet-per-flowfile > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13304) ExcelReader - ability to split into flowfile per sheet
[ https://issues.apache.org/jira/browse/NIFI-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850110#comment-17850110 ] Philipp Korniets commented on NIFI-13304: - I think an approach to treat excel as a single sheet data source is erroneous. So a record reader which treats it this way will create complexity where it's not needed. I'm coming from a lot of experience with excel consumption in financial industry. > ExcelReader - ability to split into flowfile per sheet > -- > > Key: NIFI-13304 > URL: https://issues.apache.org/jira/browse/NIFI-13304 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Philipp Korniets >Priority: Major > > Currently ConvertExcelToCSV processor, if processing excel with multiple > required sheets in it, produces flowfile per sheet. > New ExcelReader produces one flowfile with all data in it > > There should be a way to configure output to be sheet-per-flowfile > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13304) ExcelReader - ability to split into flowfile per sheet
[ https://issues.apache.org/jira/browse/NIFI-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850107#comment-17850107 ] David Handermann commented on NIFI-13304: - [~dstiegli1] As you noted, ExcelReader itself does not create FlowFiles, so it is not capable of splitting based on sheet in the current design. The QueryRecord Processor could be used to effectively split input spreadsheets if each sheet had a distinguishable column that could be referenced in a SQL query. That isn't a completely dynamic solution either, but it would work for spreadsheets of expected formats. > ExcelReader - ability to split into flowfile per sheet > -- > > Key: NIFI-13304 > URL: https://issues.apache.org/jira/browse/NIFI-13304 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Philipp Korniets >Priority: Major > > Currently ConvertExcelToCSV processor, if processing excel with multiple > required sheets in it, produces flowfile per sheet. > New ExcelReader produces one flowfile with all data in it > > There should be a way to configure output to be sheet-per-flowfile > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (NIFI-13304) ExcelReader - ability to split into flowfile per sheet
[ https://issues.apache.org/jira/browse/NIFI-13304 ] Philipp Korniets deleted comment on NIFI-13304: - was (Author: iiojj2): May be we need a separate processor for that? > ExcelReader - ability to split into flowfile per sheet > -- > > Key: NIFI-13304 > URL: https://issues.apache.org/jira/browse/NIFI-13304 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Philipp Korniets >Priority: Major > > Currently ConvertExcelToCSV processor, if processing excel with multiple > required sheets in it, produces flowfile per sheet. > New ExcelReader produces one flowfile with all data in it > > There should be a way to configure output to be sheet-per-flowfile > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13304) ExcelReader - ability to split into flowfile per sheet
[ https://issues.apache.org/jira/browse/NIFI-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850106#comment-17850106 ] Philipp Korniets commented on NIFI-13304: - May be we need a separate processor for that? > ExcelReader - ability to split into flowfile per sheet > -- > > Key: NIFI-13304 > URL: https://issues.apache.org/jira/browse/NIFI-13304 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Philipp Korniets >Priority: Major > > Currently ConvertExcelToCSV processor, if processing excel with multiple > required sheets in it, produces flowfile per sheet. > New ExcelReader produces one flowfile with all data in it > > There should be a way to configure output to be sheet-per-flowfile > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (NIFI-13304) ExcelReader - ability to split into flowfile per sheet
[ https://issues.apache.org/jira/browse/NIFI-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850095#comment-17850095 ] Philipp Korniets edited comment on NIFI-13304 at 5/28/24 4:39 PM: -- Interesting question. The other option is to duplicate flowfiles and pass each individual sheet as a separate attribute. But this solution is messy.. current convertExcelToCSV works really well with that. And it's is really useful. And in our nifi society we got this question asked few times already. was (Author: iiojj2): Interesting question. The other option is to duplicate flowfiles and pass each individual sheet as a separate attribute. But this solution is messy.. current convertExcelToCSV works really well with that. And it's is really useful. > ExcelReader - ability to split into flowfile per sheet > -- > > Key: NIFI-13304 > URL: https://issues.apache.org/jira/browse/NIFI-13304 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Philipp Korniets >Priority: Major > > Currently ConvertExcelToCSV processor, if processing excel with multiple > required sheets in it, produces flowfile per sheet. > New ExcelReader produces one flowfile with all data in it > > There should be a way to configure output to be sheet-per-flowfile > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13290) Dialog close on route navigation causes extra selection route to fire and browser history to be removed
[ https://issues.apache.org/jira/browse/NIFI-13290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850098#comment-17850098 ] ASF subversion and git services commented on NIFI-13290: Commit 94b6e424b3b46f0151c93795b245bef1df3ddc6a in nifi's branch refs/heads/main from Matt Gilman [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=94b6e424b3 ] NIFI-13290: (#8871) - Manually closing dialogs with proper result in Navigation lifecycle to ensure back/forward browser button works correctly. This change also handles any scenario when a user routes away from a dialog via a link or go to action so we were able to remove the dialog close action form those places. > Dialog close on route navigation causes extra selection route to fire and > browser history to be removed > --- > > Key: NIFI-13290 > URL: https://issues.apache.org/jira/browse/NIFI-13290 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan >Assignee: Matt Gilman >Priority: Major > Attachments: Kapture 2024-05-22 at 17.24.17.gif, example2.gif > > Time Spent: 20m > Remaining Estimate: 0h > > https://github.com/apache/nifi/pull/8859#discussion_r1612046025 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13290) Dialog close on route navigation causes extra selection route to fire and browser history to be removed
[ https://issues.apache.org/jira/browse/NIFI-13290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Aslan updated NIFI-13290: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Dialog close on route navigation causes extra selection route to fire and > browser history to be removed > --- > > Key: NIFI-13290 > URL: https://issues.apache.org/jira/browse/NIFI-13290 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan >Assignee: Matt Gilman >Priority: Major > Attachments: Kapture 2024-05-22 at 17.24.17.gif, example2.gif > > Time Spent: 20m > Remaining Estimate: 0h > > https://github.com/apache/nifi/pull/8859#discussion_r1612046025 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (NIFI-13304) ExcelReader - ability to split into flowfile per sheet
[ https://issues.apache.org/jira/browse/NIFI-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850095#comment-17850095 ] Philipp Korniets edited comment on NIFI-13304 at 5/28/24 4:34 PM: -- Interesting question. The other option is to duplicate flowfiles and pass each individual sheet as a separate attribute. But this solution is messy.. current convertExcelToCSV works really well with that. And it's is really useful. was (Author: iiojj2): Interesting question. The other option is to duplicate flowfiles and pass each individual sheet as a separate attribute. But this solution is messy.. > ExcelReader - ability to split into flowfile per sheet > -- > > Key: NIFI-13304 > URL: https://issues.apache.org/jira/browse/NIFI-13304 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Philipp Korniets >Priority: Major > > Currently ConvertExcelToCSV processor, if processing excel with multiple > required sheets in it, produces flowfile per sheet. > New ExcelReader produces one flowfile with all data in it > > There should be a way to configure output to be sheet-per-flowfile > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13304) ExcelReader - ability to split into flowfile per sheet
[ https://issues.apache.org/jira/browse/NIFI-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850095#comment-17850095 ] Philipp Korniets commented on NIFI-13304: - Interesting question. The other option is to duplicate flowfiles and pass each individual sheet as a separate attribute. But this solution is messy.. > ExcelReader - ability to split into flowfile per sheet > -- > > Key: NIFI-13304 > URL: https://issues.apache.org/jira/browse/NIFI-13304 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Philipp Korniets >Priority: Major > > Currently ConvertExcelToCSV processor, if processing excel with multiple > required sheets in it, produces flowfile per sheet. > New ExcelReader produces one flowfile with all data in it > > There should be a way to configure output to be sheet-per-flowfile > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13304) ExcelReader - ability to split into flowfile per sheet
[ https://issues.apache.org/jira/browse/NIFI-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850085#comment-17850085 ] Daniel Stieglitz commented on NIFI-13304: - [~exceptionfactory] Is this request even possible? The ExcelReader is controller service which is meant to work in the record framework. It identifies what the records are. It does not create actual flow files. > ExcelReader - ability to split into flowfile per sheet > -- > > Key: NIFI-13304 > URL: https://issues.apache.org/jira/browse/NIFI-13304 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Philipp Korniets >Priority: Major > > Currently ConvertExcelToCSV processor, if processing excel with multiple > required sheets in it, produces flowfile per sheet. > New ExcelReader produces one flowfile with all data in it > > There should be a way to configure output to be sheet-per-flowfile > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13307) Refactor TLS Loading using nifi-security-ssl
David Handermann created NIFI-13307:
---
Summary: Refactor TLS Loading using nifi-security-ssl
Key: NIFI-13307
URL: https://issues.apache.org/jira/browse/NIFI-13307
Project: Apache NiFi
Issue Type: Improvement
Reporter: David Handermann
Assignee: David Handermann
The {{KeyStoreUtils}} class in {{nifi-security-utils}} contains a large number
of similar methods for loading keystores and other TLS components. The
{{nifi-security-ssl}} module contains a streamlined set of builder classes,
without external dependencies. References to {{KeyStoreUtils}} should be
refactored to use the newer builder classes to remove unnecessary dependencies
on {{nifi-security-utils}} and associated transitive dependencies.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (NIFI-13306) Site to Site protocol cannot handle target cluster swap during transaction completion
Michael created NIFI-13306:
--
Summary: Site to Site protocol cannot handle target cluster swap
during transaction completion
Key: NIFI-13306
URL: https://issues.apache.org/jira/browse/NIFI-13306
Project: Apache NiFi
Issue Type: Bug
Reporter: Michael
Attachments: nifi-cutover.jpg
When sending data from MINIFI using SXS, and the target NIFI cluster is
replaced (e.g. a blue green deployment). The transaction can get stuck in a
condition that will cause it to continue to retry (and fail) to close the
transaction, blocking the process group and not allowing other traffic to flow.
MINIFI does seem to recover in other parts of the transaction flow.
Sample log entry:
_2024-05-22 12:59:51,626 ERROR [Timer-Driven Process Thread-5]
o.a.nifi.remote.{*}StandardRemoteGroupPort{*} RemoteGroupPort[name=From Minifi
FL,targets=https://<>/nifi/] failed to communicate with remote NiFi instance
due to java.io.IOException: Failed to complete transaction with
Peer[url=https://<>/nifi-api] due to java.io.IOException:
[Url=https://<>/nifi-api, TransferDirection=SEND, State=TRANSACTION_CONFIRMED]
Failed to receive a response from Peer[url=https://<>/nifi-api] when expecting
a TransactionFinished Indicator. It is unknown whether or not the peer
successfully received/processed the data. java.io.IOException: Unexpected
response code: 404 errCode:Abort errMessage:Transaction was not found._
Sample blue/green flow attached.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-13305) Upgrade HBase to 2.6.0
[ https://issues.apache.org/jira/browse/NIFI-13305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13305: Status: Patch Available (was: Open) > Upgrade HBase to 2.6.0 > -- > > Key: NIFI-13305 > URL: https://issues.apache.org/jira/browse/NIFI-13305 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > HBase [2.6.0|https://issues.apache.org/jira/projects/HBASE/versions/12350930] > includes a number of bug fixes, improvements, and transitive dependency > upgrades that should be incorporate in client service components. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13305) Upgrade HBase to 2.6.0
David Handermann created NIFI-13305: --- Summary: Upgrade HBase to 2.6.0 Key: NIFI-13305 URL: https://issues.apache.org/jira/browse/NIFI-13305 Project: Apache NiFi Issue Type: Improvement Components: Extensions Reporter: David Handermann Assignee: David Handermann HBase [2.6.0|https://issues.apache.org/jira/projects/HBASE/versions/12350930] includes a number of bug fixes, improvements, and transitive dependency upgrades that should be incorporate in client service components. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13304) ExcelReader - ability to split into flowfile per sheet
[ https://issues.apache.org/jira/browse/NIFI-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Korniets updated NIFI-13304: Description: Currently ConvertExcelToCSV processor, if processing excel with multiple required sheets in it, produces flowfile per sheet. New ExcelReader produces one flowfile with all data in it There should be a way to configure output to be sheet-per-flowfile was: Currently ConvertExcelToCSV processor, if processing excel with multiple sheets in it, produces flowfile per sheet. New ExcelReader produces one flowfile with all data in it There should be a way to configure output to be sheet-per-flowfile > ExcelReader - ability to split into flowfile per sheet > -- > > Key: NIFI-13304 > URL: https://issues.apache.org/jira/browse/NIFI-13304 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Philipp Korniets >Priority: Major > > Currently ConvertExcelToCSV processor, if processing excel with multiple > required sheets in it, produces flowfile per sheet. > New ExcelReader produces one flowfile with all data in it > > There should be a way to configure output to be sheet-per-flowfile > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13304) ExcelReader - ability to split into flowfile per sheet
[ https://issues.apache.org/jira/browse/NIFI-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850056#comment-17850056 ] Philipp Korniets commented on NIFI-13304: - [~dstiggy] can you please take a look? > ExcelReader - ability to split into flowfile per sheet > -- > > Key: NIFI-13304 > URL: https://issues.apache.org/jira/browse/NIFI-13304 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Philipp Korniets >Priority: Major > > Currently ConvertExcelToCSV processor, if processing excel with multiple > sheets in it, produces flowfile per sheet. > New ExcelReader produces one flowfile with all data in it > > There should be a way to configure output to be sheet-per-flowfile > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13304) ExcelReader - ability to split into flowfile per sheet
[ https://issues.apache.org/jira/browse/NIFI-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Korniets updated NIFI-13304: Description: Currently ConvertExcelToCSV processor, if processing excel with multiple sheets in it, produces flowfile per sheet. New ExcelReader produces one flowfile with all data in it There should be a way to configure output to be sheet-per-flowfile was: Currently ConvertExcelToCSV processor if processing excel with multiple sheets in it produces flowfile per sheet. New ExcelReader produces one flowfile with all data in it There should be a way to configure output to be sheet-per-flowfile > ExcelReader - ability to split into flowfile per sheet > -- > > Key: NIFI-13304 > URL: https://issues.apache.org/jira/browse/NIFI-13304 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Philipp Korniets >Priority: Major > > Currently ConvertExcelToCSV processor, if processing excel with multiple > sheets in it, produces flowfile per sheet. > New ExcelReader produces one flowfile with all data in it > > There should be a way to configure output to be sheet-per-flowfile > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13304) ExcelReader - ability to split into flowfile per sheet
[ https://issues.apache.org/jira/browse/NIFI-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Korniets updated NIFI-13304: Summary: ExcelReader - ability to split into flowfile per sheet (was: ExcelReader - ability to split into individual sheets) > ExcelReader - ability to split into flowfile per sheet > -- > > Key: NIFI-13304 > URL: https://issues.apache.org/jira/browse/NIFI-13304 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Philipp Korniets >Priority: Major > > Currently ConvertExcelToCSV processor if processing excel with multiple > sheets in it produces flowfile per sheet. > New ExcelReader produces one flowfile with all data in it > > There should be a way to configure output to be sheet-per-flowfile > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13304) ExcelReader - ability to split into individual sheets
Philipp Korniets created NIFI-13304: --- Summary: ExcelReader - ability to split into individual sheets Key: NIFI-13304 URL: https://issues.apache.org/jira/browse/NIFI-13304 Project: Apache NiFi Issue Type: New Feature Reporter: Philipp Korniets Currently ConvertExcelToCSV processor if processing excel with multiple sheets in it produces flowfile per sheet. New ExcelReader produces one flowfile with all data in it There should be a way to configure output to be sheet-per-flowfile -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13298) Remove unused instantiated java.util.HashSet from RouteAttribute
[ https://issues.apache.org/jira/browse/NIFI-13298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13298: Fix Version/s: 1.27.0 2.0.0-M4 Resolution: Fixed Status: Resolved (was: Patch Available) > Remove unused instantiated java.util.HashSet from RouteAttribute > > > Key: NIFI-13298 > URL: https://issues.apache.org/jira/browse/NIFI-13298 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Daniel Stieglitz >Assignee: Daniel Stieglitz >Priority: Minor > Fix For: 1.27.0, 2.0.0-M4 > > Time Spent: 20m > Remaining Estimate: 0h > > In RouteOnAttribute on line 352 a set is instantiated > final Set clones = new HashSet<>(); > and on line 358 its populated > clones.add(cloneFlowFile); > Yet after that nothing is done with it (per Intellij it is updated but > never queried). > This should removed as it is not serving any purpose. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13298) Remove unused instantiated java.util.HashSet from RouteAttribute
[ https://issues.apache.org/jira/browse/NIFI-13298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850049#comment-17850049 ] ASF subversion and git services commented on NIFI-13298: Commit 8734e2ec491273942217a785feea637261f36681 in nifi's branch refs/heads/support/nifi-1.x from dan-s1 [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=8734e2ec49 ] NIFI-13298 Removed unused instantiated java.util.HashSet from RouteAttribute This closes #8883 Signed-off-by: David Handermann (cherry picked from commit a1a7c3c5a5779477d4b20027a57a22390095303a) > Remove unused instantiated java.util.HashSet from RouteAttribute > > > Key: NIFI-13298 > URL: https://issues.apache.org/jira/browse/NIFI-13298 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Daniel Stieglitz >Assignee: Daniel Stieglitz >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > In RouteOnAttribute on line 352 a set is instantiated > final Set clones = new HashSet<>(); > and on line 358 its populated > clones.add(cloneFlowFile); > Yet after that nothing is done with it (per Intellij it is updated but > never queried). > This should removed as it is not serving any purpose. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13298) Remove unused instantiated java.util.HashSet from RouteAttribute
[ https://issues.apache.org/jira/browse/NIFI-13298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850048#comment-17850048 ] ASF subversion and git services commented on NIFI-13298: Commit a1a7c3c5a5779477d4b20027a57a22390095303a in nifi's branch refs/heads/main from dan-s1 [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=a1a7c3c5a5 ] NIFI-13298 Removed unused instantiated java.util.HashSet from RouteAttribute This closes #8883 Signed-off-by: David Handermann > Remove unused instantiated java.util.HashSet from RouteAttribute > > > Key: NIFI-13298 > URL: https://issues.apache.org/jira/browse/NIFI-13298 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Daniel Stieglitz >Assignee: Daniel Stieglitz >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > In RouteOnAttribute on line 352 a set is instantiated > final Set clones = new HashSet<>(); > and on line 358 its populated > clones.add(cloneFlowFile); > Yet after that nothing is done with it (per Intellij it is updated but > never queried). > This should removed as it is not serving any purpose. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13269) Parameter reference list is randomly ordered or not ordered
[ https://issues.apache.org/jira/browse/NIFI-13269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Fellows updated NIFI-13269: --- Status: Patch Available (was: In Progress) > Parameter reference list is randomly ordered or not ordered > --- > > Key: NIFI-13269 > URL: https://issues.apache.org/jira/browse/NIFI-13269 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Julien G. >Assignee: Rob Fellows >Priority: Major > Attachments: Screenshot 2024-05-22 at 3.49.48 PM.png, > image-2024-05-21-11-04-26-571.png, image-2024-05-22-22-12-46-877.png, > legacy.png > > Time Spent: 10m > Remaining Estimate: 0h > > When referencing a parameter in a Controller Service, a list of the availabe > parameter is displayed. > In the new UI, the list is randomly ordered or not ordered at all. > !image-2024-05-21-11-04-26-571.png|thumbnail! > It makes it hard to find a parameter. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (NIFI-13265) Remove the instantiation of Object arrays for arguments in ComponentLog log and org.slf4j.Logger statements
[
https://issues.apache.org/jira/browse/NIFI-13265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850046#comment-17850046
]
David Handermann edited comment on NIFI-13265 at 5/28/24 2:30 PM:
--
Thanks for highlighting those examples [~dstiegli1]. The {{due to...}} syntax
is an artifact of legacy behavior that did not properly handle {{Throwable}}
arguments. When making the changes, {{due to}} should be removed completely,
as follows based on the example you provided:
{noformat}
getLogger().error("Routing to failure since failed to retrieve content from {}
for {}", filenameValue, originalFlowFile, e);{noformat}
was (Author: exceptionfactory):
Thanks for highlighting those examples [~dstiegli1]. The {{due to...}} syntax
is an artifact of legacy behavior that did not properly handle {{Throwable}}
examples. When making the changes, {{due to}} should be removed completely, as
follows based on the example you provided:
{noformat}
getLogger().error("Routing to failure since failed to retrieve content from {}
for {}", filenameValue, originalFlowFile, e);{noformat}
> Remove the instantiation of Object arrays for arguments in ComponentLog log
> and org.slf4j.Logger statements
> ---
>
> Key: NIFI-13265
> URL: https://issues.apache.org/jira/browse/NIFI-13265
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: Daniel Stieglitz
>Assignee: Daniel Stieglitz
>Priority: Minor
>
> There are still classes after the changes in NIFI-12075 and NIFI-12076 which
> instantiate an Object array for ComponentLog log statements. This ticket aims
> to remove those instantiations. In addition similar changes should be made to
> org.slf4j.Logger statements.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-13265) Remove the instantiation of Object arrays for arguments in ComponentLog log and org.slf4j.Logger statements
[
https://issues.apache.org/jira/browse/NIFI-13265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850046#comment-17850046
]
David Handermann commented on NIFI-13265:
-
Thanks for highlighting those examples [~dstiegli1]. The {{due to...}} syntax
is an artifact of legacy behavior that did not properly handle {{Throwable}}
examples. When making the changes, {{due to}} should be removed completely, as
follows based on the example you provided:
{noformat}
getLogger().error("Routing to failure since failed to retrieve content from {}
for {}", filenameValue, originalFlowFile, e);{noformat}
> Remove the instantiation of Object arrays for arguments in ComponentLog log
> and org.slf4j.Logger statements
> ---
>
> Key: NIFI-13265
> URL: https://issues.apache.org/jira/browse/NIFI-13265
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: Daniel Stieglitz
>Assignee: Daniel Stieglitz
>Priority: Minor
>
> There are still classes after the changes in NIFI-12075 and NIFI-12076 which
> instantiate an Object array for ComponentLog log statements. This ticket aims
> to remove those instantiations. In addition similar changes should be made to
> org.slf4j.Logger statements.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (NIFI-13269) Parameter reference list is randomly ordered or not ordered
[ https://issues.apache.org/jira/browse/NIFI-13269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Fellows reassigned NIFI-13269: -- Assignee: Rob Fellows > Parameter reference list is randomly ordered or not ordered > --- > > Key: NIFI-13269 > URL: https://issues.apache.org/jira/browse/NIFI-13269 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Julien G. >Assignee: Rob Fellows >Priority: Major > Attachments: Screenshot 2024-05-22 at 3.49.48 PM.png, > image-2024-05-21-11-04-26-571.png, image-2024-05-22-22-12-46-877.png, > legacy.png > > > When referencing a parameter in a Controller Service, a list of the availabe > parameter is displayed. > In the new UI, the list is randomly ordered or not ordered at all. > !image-2024-05-21-11-04-26-571.png|thumbnail! > It makes it hard to find a parameter. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13300) Bump Apache parent and move to Maven 3.9.7 and latest maven wrapper 3.3.2
[ https://issues.apache.org/jira/browse/NIFI-13300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850038#comment-17850038 ] ASF subversion and git services commented on NIFI-13300: Commit 2598068b31f9bb4c1b29f0d3562f2e41303391df in nifi's branch refs/heads/main from Joe Witt [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=2598068b31 ] NIFI-13300 Upgraded Maven from 3.9.6 to 3.9.7 - Upgraded Apache Parent from 31 to 32 - Upgraded Maven Wrapper from 3.2.0 to 3.3.2 This closes #8880 Signed-off-by: David Handermann > Bump Apache parent and move to Maven 3.9.7 and latest maven wrapper 3.3.2 > - > > Key: NIFI-13300 > URL: https://issues.apache.org/jira/browse/NIFI-13300 > Project: Apache NiFi > Issue Type: Task >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Maven fixed the file/locking issue and recommends we move to 3.9.7 as per > https://issues.apache.org/jira/browse/MNG-7868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849476#comment-17849476 > Also the apache parent pom has bumped to version 32. -- This message was sent by Atlassian Jira (v8.20.10#820010)
