[jira] [Commented] (NIFI-12682) [MiNiFi] agentInfo.agentManifestHash is changing between MiNiFi restarts
[ https://issues.apache.org/jira/browse/NIFI-12682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17812177#comment-17812177 ] ASF subversion and git services commented on NIFI-12682: Commit 79b3083546593268761300e33a670dc7f92d7747 in nifi's branch refs/heads/support/nifi-1.x from Ferenc Erdei [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=79b3083546 ] NIFI-12682 Fix MiNiFi agent manifest hash swaps Signed-off-by: Ferenc Kis This closes #8309. > [MiNiFi] agentInfo.agentManifestHash is changing between MiNiFi restarts > > > Key: NIFI-12682 > URL: https://issues.apache.org/jira/browse/NIFI-12682 > Project: Apache NiFi > Issue Type: Bug > Components: MiNiFi >Affects Versions: 2.0.0-M1, 1.24.0, 2.0.0-M2 >Reporter: Ferenc Erdei >Assignee: Ferenc Erdei >Priority: Minor > Labels: minifi-java > Fix For: 2.0.0, 1.26.0 > > Time Spent: 20m > Remaining Estimate: 0h > > In the C2 Heartbeat request payload the agentInfo.agentManifestHash can be > used by the C2 server to determine whether agent configuration changed > between heartbeats and if the C2 server needs to send a DESCRIBE_MANIFEST > request. > Issue: the hash is changing between restart therefore an unnecessary command > might be sent to the agent. > Possible root cause: > Probably linkedhashmap or linkedset is missing somewhere in the flow of the > supported operations. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-12682) [MiNiFi] agentInfo.agentManifestHash is changing between MiNiFi restarts
[ https://issues.apache.org/jira/browse/NIFI-12682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ferenc Kis resolved NIFI-12682. --- Fix Version/s: 2.0.0 Resolution: Fixed > [MiNiFi] agentInfo.agentManifestHash is changing between MiNiFi restarts > > > Key: NIFI-12682 > URL: https://issues.apache.org/jira/browse/NIFI-12682 > Project: Apache NiFi > Issue Type: Bug > Components: MiNiFi >Affects Versions: 2.0.0-M1, 1.24.0, 2.0.0-M2 >Reporter: Ferenc Erdei >Assignee: Ferenc Erdei >Priority: Minor > Labels: minifi-java > Fix For: 2.0.0, 1.26.0 > > Time Spent: 20m > Remaining Estimate: 0h > > In the C2 Heartbeat request payload the agentInfo.agentManifestHash can be > used by the C2 server to determine whether agent configuration changed > between heartbeats and if the C2 server needs to send a DESCRIBE_MANIFEST > request. > Issue: the hash is changing between restart therefore an unnecessary command > might be sent to the agent. > Possible root cause: > Probably linkedhashmap or linkedset is missing somewhere in the flow of the > supported operations. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12682) [MiNiFi] agentInfo.agentManifestHash is changing between MiNiFi restarts
[ https://issues.apache.org/jira/browse/NIFI-12682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17812173#comment-17812173 ] ASF subversion and git services commented on NIFI-12682: Commit 13271d198f8d09e5634a0923c1920ded41a84222 in nifi's branch refs/heads/main from Ferenc Erdei [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=13271d198f ] NIFI-12682 Fix MiNiFi agent manifest hash swaps Signed-off-by: Ferenc Kis This closes #8309. > [MiNiFi] agentInfo.agentManifestHash is changing between MiNiFi restarts > > > Key: NIFI-12682 > URL: https://issues.apache.org/jira/browse/NIFI-12682 > Project: Apache NiFi > Issue Type: Bug > Components: MiNiFi >Affects Versions: 2.0.0-M1, 1.24.0, 2.0.0-M2 >Reporter: Ferenc Erdei >Assignee: Ferenc Erdei >Priority: Minor > Labels: minifi-java > Fix For: 1.26.0 > > Time Spent: 20m > Remaining Estimate: 0h > > In the C2 Heartbeat request payload the agentInfo.agentManifestHash can be > used by the C2 server to determine whether agent configuration changed > between heartbeats and if the C2 server needs to send a DESCRIBE_MANIFEST > request. > Issue: the hash is changing between restart therefore an unnecessary command > might be sent to the agent. > Possible root cause: > Probably linkedhashmap or linkedset is missing somewhere in the flow of the > supported operations. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12682 Fix MiNiFi agent manifest hash swaps [nifi]
briansolo1985 closed pull request #8309: NIFI-12682 Fix MiNiFi agent manifest hash swaps URL: https://github.com/apache/nifi/pull/8309 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [NIFI-12655] theme NiFi following Material Design spec and leveraging Angular Material themes [nifi]
scottyaslan commented on PR #8294: URL: https://github.com/apache/nifi/pull/8294#issuecomment-1915986287 > Create Process Group dialog isn't right. Its inlined, the form elements should be on separate lines: https://private-user-images.githubusercontent.com/713866/300623646-89d83559-a08c-4308-9329-44843b0fe492.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MDY1NzEwOTgsIm5iZiI6MTcwNjU3MDc5OCwicGF0aCI6Ii83MTM4NjYvMzAwNjIzNjQ2LTg5ZDgzNTU5LWEwOGMtNDMwOC05MzI5LTQ0ODQzYjBmZTQ5Mi5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwMTI5JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDEyOVQyMzI2MzhaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1mYjVhMGMwYzczODFjYTE3ZmQzOTA1ZTEyNGQxNWQwMjE5Yzc1NWI2MTFhN2U0NjYwNTMzNTAwNjY2YmFjOTg4JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.yZ6Uc5r7P9-IUj7T-tAesoGch9BEnbTjTKCWm7Jbej8;> This is fixed in my latest commit. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [NIFI-12655] theme NiFi following Material Design spec and leveraging Angular Material themes [nifi]
scottyaslan commented on code in PR #8294:
URL: https://github.com/apache/nifi/pull/8294#discussion_r1470525304
##
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi/src/styles.scss:
##
@@ -122,341 +169,332 @@ $appFontPath: '~roboto-fontface/fonts';
@tailwind components;
@tailwind utilities;
-$nifi-primary-palette: (
-50: #eef1f3,
-100: #d5dde1,
-200: #b9c7cd,
-300: #9cb0b9,
-400: #879faa,
-500: #728e9b,
-600: #6a8693,
-700: #5f7b89,
-800: #55717f,
-900: #425f6d,
-A100: #c7ecff,
-A200: #94daff,
-A400: #61c9ff,
-A700: #47c0ff,
-contrast: (
-50: #00,
-100: #00,
-200: #00,
-300: #00,
-400: #00,
-500: #00,
-600: #ff,
-700: #ff,
-800: #ff,
-900: #ff,
-A100: #00,
-A200: #00,
-A400: #00,
-A700: #00
-)
-);
-
-$nifi-accent-palette: (
-50: #fcfcfd,
-100: #f7f8f9,
-200: #f1f4f5,
-300: #ebeff1,
-400: #e7ebee,
-500: #e3e8eb,
-600: #e0e5e9,
-700: #dce2e5,
-800: #d8dee2,
-900: #d0d8dd,
-A100: #ff,
-A200: #ff,
-A400: #ff,
-A700: #ff,
-contrast: (
-50: #00,
-100: #00,
-200: #00,
-300: #00,
-400: #00,
-500: #00,
-600: #00,
-700: #00,
-800: #00,
-900: #00,
-A100: #00,
-A200: #00,
-A400: #00,
-A700: #00
-)
-);
-
-// Define the palettes for your theme using the Material Design palettes
available in palette.scss
-// (imported above). For each palette, you can optionally specify a default,
lighter, and darker
-// hue. Available color palettes: https://material.io/design/color/
-$nifi-primary: mat.define-palette($nifi-primary-palette);
-$nifi-accent: mat.define-palette($nifi-accent-palette);
-
-//#728e9b
-//#aabbc3
-//#e3e8eb
-
-// The warn palette is optional (defaults to red).
-$nifi-warn: mat.define-palette(mat.$red-palette);
-
-// Create the theme object. A theme consists of configurations for individual
-// theming systems such as "color" or "typography".
-$nifi-theme: mat.define-light-theme(
-(
-color: (
-primary: $nifi-primary,
-accent: $nifi-accent,
-warn: $nifi-warn
-),
-//typography: mat.define-typography-config(),
-density: -3
-)
-);
-
-// Include theme styles for core and each component used in your app.
-// Alternatively, you can import and @include the theme mixins for each
component
-// that you are using.
-@include mat.all-component-themes($nifi-theme);
-
-/* You can add global styles to this file, and also import other style files */
-
-html,
-body {
-height: 100%;
-}
-
-body {
-margin: 0;
-//font-family: Roboto, 'Helvetica Neue', sans-serif;
-}
-
-a {
-font-size: 13px;
-cursor: pointer;
-color: #004849;
-font-weight: normal;
-display: inline-block;
-font-family: Roboto;
-text-decoration: underline;
-text-decoration-color: #ccdadb;
-text-underline-offset: 3px;
-}
+//General status styles. TODO - Reconsider this... separating canvas/style
styles from html styles...
+@mixin theme($material-theme, $canvas-theme) {
+// Get the color config from the theme.
+$color-config: mat.get-color-config($material-theme);
+$canvas-color-config: mat.get-color-config($canvas-theme);
+
+// Get the color palette from the color-config.
+$primary-palette: map.get($color-config, 'primary');
+$accent-palette: map.get($color-config, 'accent');
+$warn-palette: map.get($color-config, 'warn');
+$canvas-primary-palette: map.get($canvas-color-config, 'primary');
+
+// Get hues from palette
+$primary-palette-50: mat.get-color-from-palette($primary-palette, 50);
+$primary-palette-200: mat.get-color-from-palette($primary-palette, 200);
+$primary-palette-500: mat.get-color-from-palette($primary-palette, 500);
+$primary-palette-A100: mat.get-color-from-palette($primary-palette,
'A100');
+$primary-palette-A200: mat.get-color-from-palette($primary-palette,
'A200');
+$primary-palette-A400: mat.get-color-from-palette($primary-palette,
'A400');
+$canvas-primary-palette-50:
mat.get-color-from-palette($canvas-primary-palette, 50);
+$canvas-primary-palette-200:
mat.get-color-from-palette($canvas-primary-palette, 200);
+$canvas-primary-palette-400:
mat.get-color-from-palette($canvas-primary-palette, 400);
+$canvas-primary-palette-900:
mat.get-color-from-palette($canvas-primary-palette, 900);
+$accent-palette-200: mat.get-color-from-palette($accent-palette, 200);
+$accent-palette-400: mat.get-color-from-palette($accent-palette, 400);
+$accent-palette-A200: mat.get-color-from-palette($accent-palette,
[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) * Counters (NIFI-12415) * 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) * Configure Reporting Task (NIFI-12563) * Flow Analysis Rules (NIFI-12588) * Registry Clients (NIFI-12486) * Import from Registry * Parameter Providers (NIFI-12622) ** Fetch parameters from provider, map to parameter context (dialog) - (NIFI-12665) * Cluster * Flow Configuration History * Node Status History (NIFI-12553) * Status history for components from canvas context menu (NIFI-12553) * Users (NIFI-12543) * Policies (NIFI-12548) ** Overridden policy Empty or Copy * Help * About * Show Upstream/Downstream * Align * List Queue (NIFI-12589) * Empty [all] Queue (NIFI-12604) * View Content (NIFI-12589 and NIFI-12445) * View State (NIFI-12611) * Change Component Version * Consider PG permissions in Toolbox (NIFI-12683) * PG Version ** Start ** Commit ** Force Commit ** Show changes ** Revert changes ** Change Flow version ** Stop * Configure PG (NIFI-12417) * 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 * 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) ** Stop and Configure ** Open Custom UI ** Property History ** Unable to re-add any removed Property * Property Verification * More Details (Processor, Controller Service, Reporting Task) * Download Flow * Create RPG * Configure RPG * RPG Remote Ports * RPG Go To * Color * Move to Front * Copy/Paste * Add/Update Info Icons in dialogs throughout the application * Better theme support (NIFI-12655) * Run unit tests are part of standard build * Update all API calls to consider disconnect node confirmation * Update API calls to use uiOnly flag * Use polling interval from API * Routing error handling * General API response error handling ** Management CS (NIFI-12663) ** Canvas CS (NIFI-12684) * Introduce header in new pages to unify with canvas and offer better navigation. (NIFI-12597) * Prompt user to save Parameter Context when Edit form is dirty * Start/Stop processors, process groups, ... (NIFI-12568) * Dialog vertical resizing on smaller screens do not allow users to access all fields (NIFI-12603) * Flow Analysis report menu [1] [https://github.com/apache/nifi/pull/8053] was: 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) * Counters (NIFI-12415) * 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) * Configure Reporting Task (NIFI-12563) * Flow Analysis Rules (NIFI-12588) * Registry Clients (NIFI-12486) * Import from Registry * Parameter Providers (NIFI-12622) ** Fetch parameters from provider, map to parameter context (dialog) - (NIFI-12665) * Cluster * Flow Configuration History * Node Status History (NIFI-12553) * Status history for components from canvas
[jira] [Created] (NIFI-12684) Canvas Controller Services - General API error response handling
Matt Gilman created NIFI-12684: -- Summary: Canvas Controller Services - General API error response handling Key: NIFI-12684 URL: https://issues.apache.org/jira/browse/NIFI-12684 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Matt Gilman Assignee: Matt Gilman -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12684) Canvas Controller Services - General API error response handling
[ https://issues.apache.org/jira/browse/NIFI-12684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-12684: --- Description: Update the Canvas Controller Services page to show API error responses. > Canvas Controller Services - General API error response handling > > > Key: NIFI-12684 > URL: https://issues.apache.org/jira/browse/NIFI-12684 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > > Update the Canvas Controller Services page to show API error responses. -- 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) * Counters (NIFI-12415) * 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) * Configure Reporting Task (NIFI-12563) * Flow Analysis Rules (NIFI-12588) * Registry Clients (NIFI-12486) * Import from Registry * Parameter Providers (NIFI-12622) ** Fetch parameters from provider, map to parameter context (dialog) - (NIFI-12665) * Cluster * Flow Configuration History * Node Status History (NIFI-12553) * Status history for components from canvas context menu (NIFI-12553) * Users (NIFI-12543) * Policies (NIFI-12548) ** Overridden policy Empty or Copy * Help * About * Show Upstream/Downstream * Align * List Queue (NIFI-12589) * Empty [all] Queue (NIFI-12604) * View Content (NIFI-12589 and NIFI-12445) * View State (NIFI-12611) * Change Component Version * Consider PG permissions in Toolbox (NIFI-12683) * PG Version ** Start ** Commit ** Force Commit ** Show changes ** Revert changes ** Change Flow version ** Stop * Configure PG (NIFI-12417) * 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 * 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) ** Stop and Configure ** Open Custom UI ** Property History ** Unable to re-add any removed Property * Property Verification * More Details (Processor, Controller Service, Reporting Task) * Download Flow * Create RPG * Configure RPG * RPG Remote Ports * RPG Go To * Color * Move to Front * Copy/Paste * Add/Update Info Icons in dialogs throughout the application * Better theme support (NIFI-12655) * Run unit tests are part of standard build * Update all API calls to consider disconnect node confirmation * Update API calls to use uiOnly flag * Use polling interval from API * Routing error handling * General API response error handling ** Management CS (NIFI-12663) ** Canvas CS * Introduce header in new pages to unify with canvas and offer better navigation. (NIFI-12597) * Prompt user to save Parameter Context when Edit form is dirty * Start/Stop processors, process groups, ... (NIFI-12568) * Dialog vertical resizing on smaller screens do not allow users to access all fields (NIFI-12603) * Flow Analysis report menu [1] [https://github.com/apache/nifi/pull/8053] was: 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) * Counters (NIFI-12415) * 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) * Configure Reporting Task (NIFI-12563) * Flow Analysis Rules (NIFI-12588) * Registry Clients (NIFI-12486) * Import from Registry * Parameter Providers (NIFI-12622) ** Fetch parameters from provider, map to parameter context (dialog) - (NIFI-12665) * Cluster * Flow Configuration History * Node Status History (NIFI-12553) * Status history for components from canvas context menu
[jira] [Updated] (NIFI-12683) Consider PG permissions in Toolbox
[ https://issues.apache.org/jira/browse/NIFI-12683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-12683: --- Status: Patch Available (was: In Progress) > Consider PG permissions in Toolbox > -- > > Key: NIFI-12683 > URL: https://issues.apache.org/jira/browse/NIFI-12683 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Update the new canvas items in the Toolbox to consider the permissions in the > current Process Group. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] NIFI-12683: Considering current PG permissions in the new canvas item toolbox [nifi]
mcgilman opened a new pull request, #8311: URL: https://github.com/apache/nifi/pull/8311 NIFI-12683: - Considering current PG permissions in the new canvas item toolbox. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (NIFI-12400) Remaining items to migrate UI to currently supported/active framework
[ https://issues.apache.org/jira/browse/NIFI-12400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-12400: --- Description: The purpose of this Jira is to track all remaining items following the initial commit [1] for NIFI-11481. The description will be kept up to date with remaining features, tasks, and improvements. As each items is worked, a new sub task Jira will be created and referenced in this description. * Support Parameters in Properties with Allowable Values (NIFI-12401) * Summary (NIFI-12437) ** Remaining work not addressed in initial Jira: *** input ports (NIFI-12504) *** output ports (NIFI-12504) *** remote process groups (NIFI-12504) *** process groups (NIFI-12504) *** connections (NIFI-12504) *** System Diagnostics (NIFI-12505) *** support for cluster-specific ui elements (NIFI-12537) *** Add pagination (NIFI-12552) * Counters (NIFI-12415) * 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) * Configure Reporting Task (NIFI-12563) * Flow Analysis Rules (NIFI-12588) * Registry Clients (NIFI-12486) * Import from Registry * Parameter Providers (NIFI-12622) ** Fetch parameters from provider, map to parameter context (dialog) - (NIFI-12665) * Cluster * Flow Configuration History * Node Status History (NIFI-12553) * Status history for components from canvas context menu (NIFI-12553) * Users (NIFI-12543) * Policies (NIFI-12548) ** Overridden policy Empty or Copy * Help * About * Show Upstream/Downstream * Align * List Queue (NIFI-12589) * Empty [all] Queue (NIFI-12604) * View Content (NIFI-12589 and NIFI-12445) * View State (NIFI-12611) * Change Component Version * Consider PG permissions in Toolbox (NIFI-12683) * PG Version ** Start ** Commit ** Force Commit ** Show changes ** Revert changes ** Change Flow version ** Stop * Configure PG (NIFI-12417) * 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 * 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) ** Stop and Configure ** Open Custom UI ** Property History ** Unable to re-add any removed Property * Property Verification * More Details (Processor, Controller Service, Reporting Task) * Download Flow * Create RPG * Configure RPG * RPG Remote Ports * RPG Go To * Color * Move to Front * Copy/Paste * Add/Update Info Icons in dialogs throughout the application * Better theme support (NIFI-12655) * Run unit tests are part of standard build * Update all API calls to consider disconnect node confirmation * Update API calls to use uiOnly flag * Use polling interval from API * Routing error handling * General API response error handling ** Management CS (NIFI-12663) * Introduce header in new pages to unify with canvas and offer better navigation. (NIFI-12597) * Prompt user to save Parameter Context when Edit form is dirty * Start/Stop processors, process groups, ... (NIFI-12568) * Dialog vertical resizing on smaller screens do not allow users to access all fields (NIFI-12603) * Flow Analysis report menu [1] [https://github.com/apache/nifi/pull/8053] was: 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) * Counters (NIFI-12415) * 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) * Configure Reporting Task (NIFI-12563) * Flow Analysis Rules (NIFI-12588) * Registry Clients (NIFI-12486) * Import from Registry * Parameter Providers (NIFI-12622) ** Fetch parameters from provider, map to parameter context (dialog) - (NIFI-12665) * Cluster * Flow Configuration History * Node Status History (NIFI-12553) * Status history for components from canvas context menu (NIFI-12553)
[jira] [Created] (NIFI-12683) Consider PG permissions in Toolbox
Matt Gilman created NIFI-12683: -- Summary: Consider PG permissions in Toolbox Key: NIFI-12683 URL: https://issues.apache.org/jira/browse/NIFI-12683 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Matt Gilman Assignee: Matt Gilman Update the new canvas items in the Toolbox to consider the permissions in the current Process Group. -- 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) * Counters (NIFI-12415) * 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) * Configure Reporting Task (NIFI-12563) * Flow Analysis Rules (NIFI-12588) * Registry Clients (NIFI-12486) * Import from Registry * Parameter Providers (NIFI-12622) ** Fetch parameters from provider, map to parameter context (dialog) - (NIFI-12665) * Cluster * Flow Configuration History * Node Status History (NIFI-12553) * Status history for components from canvas context menu (NIFI-12553) * Users (NIFI-12543) * Policies (NIFI-12548) ** Overridden policy Empty or Copy * Help * About * Show Upstream/Downstream * Align * List Queue (NIFI-12589) * Empty [all] Queue (NIFI-12604) * View Content (NIFI-12589 and NIFI-12445) * View State (NIFI-12611) * Change Component Version * Consider PG permissions in Toolbox * PG Version ** Start ** Commit ** Force Commit ** Show changes ** Revert changes ** Change Flow version ** Stop * Configure PG (NIFI-12417) * 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 * 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) ** Stop and Configure ** Open Custom UI ** Property History ** Unable to re-add any removed Property * Property Verification * More Details (Processor, Controller Service, Reporting Task) * Download Flow * Create RPG * Configure RPG * RPG Remote Ports * RPG Go To * Color * Move to Front * Copy/Paste * Add/Update Info Icons in dialogs throughout the application * Better theme support (NIFI-12655) * Run unit tests are part of standard build * Update all API calls to consider disconnect node confirmation * Update API calls to use uiOnly flag * Use polling interval from API * Routing error handling * General API response error handling ** Management CS (NIFI-12663) * Introduce header in new pages to unify with canvas and offer better navigation. (NIFI-12597) * Prompt user to save Parameter Context when Edit form is dirty * Start/Stop processors, process groups, ... (NIFI-12568) * Dialog vertical resizing on smaller screens do not allow users to access all fields (NIFI-12603) * Flow Analysis report menu [1] [https://github.com/apache/nifi/pull/8053] was: 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) * Counters (NIFI-12415) * 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) * Configure Reporting Task (NIFI-12563) * Flow Analysis Rules (NIFI-12588) * Registry Clients (NIFI-12486) * Import from Registry * Parameter Providers (NIFI-12622) ** Fetch parameters from provider, map to parameter context (dialog) - (NIFI-12665) * Cluster * Flow Configuration History * Node Status History (NIFI-12553) * Status history for components from canvas context menu (NIFI-12553) * Users
Re: [PR] [NIFI-12655] theme NiFi following Material Design spec and leveraging Angular Material themes [nifi]
rfellows commented on code in PR #8294:
URL: https://github.com/apache/nifi/pull/8294#discussion_r1470330696
##
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi/src/styles.scss:
##
@@ -122,341 +169,332 @@ $appFontPath: '~roboto-fontface/fonts';
@tailwind components;
@tailwind utilities;
-$nifi-primary-palette: (
-50: #eef1f3,
-100: #d5dde1,
-200: #b9c7cd,
-300: #9cb0b9,
-400: #879faa,
-500: #728e9b,
-600: #6a8693,
-700: #5f7b89,
-800: #55717f,
-900: #425f6d,
-A100: #c7ecff,
-A200: #94daff,
-A400: #61c9ff,
-A700: #47c0ff,
-contrast: (
-50: #00,
-100: #00,
-200: #00,
-300: #00,
-400: #00,
-500: #00,
-600: #ff,
-700: #ff,
-800: #ff,
-900: #ff,
-A100: #00,
-A200: #00,
-A400: #00,
-A700: #00
-)
-);
-
-$nifi-accent-palette: (
-50: #fcfcfd,
-100: #f7f8f9,
-200: #f1f4f5,
-300: #ebeff1,
-400: #e7ebee,
-500: #e3e8eb,
-600: #e0e5e9,
-700: #dce2e5,
-800: #d8dee2,
-900: #d0d8dd,
-A100: #ff,
-A200: #ff,
-A400: #ff,
-A700: #ff,
-contrast: (
-50: #00,
-100: #00,
-200: #00,
-300: #00,
-400: #00,
-500: #00,
-600: #00,
-700: #00,
-800: #00,
-900: #00,
-A100: #00,
-A200: #00,
-A400: #00,
-A700: #00
-)
-);
-
-// Define the palettes for your theme using the Material Design palettes
available in palette.scss
-// (imported above). For each palette, you can optionally specify a default,
lighter, and darker
-// hue. Available color palettes: https://material.io/design/color/
-$nifi-primary: mat.define-palette($nifi-primary-palette);
-$nifi-accent: mat.define-palette($nifi-accent-palette);
-
-//#728e9b
-//#aabbc3
-//#e3e8eb
-
-// The warn palette is optional (defaults to red).
-$nifi-warn: mat.define-palette(mat.$red-palette);
-
-// Create the theme object. A theme consists of configurations for individual
-// theming systems such as "color" or "typography".
-$nifi-theme: mat.define-light-theme(
-(
-color: (
-primary: $nifi-primary,
-accent: $nifi-accent,
-warn: $nifi-warn
-),
-//typography: mat.define-typography-config(),
-density: -3
-)
-);
-
-// Include theme styles for core and each component used in your app.
-// Alternatively, you can import and @include the theme mixins for each
component
-// that you are using.
-@include mat.all-component-themes($nifi-theme);
-
-/* You can add global styles to this file, and also import other style files */
-
-html,
-body {
-height: 100%;
-}
-
-body {
-margin: 0;
-//font-family: Roboto, 'Helvetica Neue', sans-serif;
-}
-
-a {
-font-size: 13px;
-cursor: pointer;
-color: #004849;
-font-weight: normal;
-display: inline-block;
-font-family: Roboto;
-text-decoration: underline;
-text-decoration-color: #ccdadb;
-text-underline-offset: 3px;
-}
+//General status styles. TODO - Reconsider this... separating canvas/style
styles from html styles...
+@mixin theme($material-theme, $canvas-theme) {
+// Get the color config from the theme.
+$color-config: mat.get-color-config($material-theme);
+$canvas-color-config: mat.get-color-config($canvas-theme);
+
+// Get the color palette from the color-config.
+$primary-palette: map.get($color-config, 'primary');
+$accent-palette: map.get($color-config, 'accent');
+$warn-palette: map.get($color-config, 'warn');
+$canvas-primary-palette: map.get($canvas-color-config, 'primary');
+
+// Get hues from palette
+$primary-palette-50: mat.get-color-from-palette($primary-palette, 50);
+$primary-palette-200: mat.get-color-from-palette($primary-palette, 200);
+$primary-palette-500: mat.get-color-from-palette($primary-palette, 500);
+$primary-palette-A100: mat.get-color-from-palette($primary-palette,
'A100');
+$primary-palette-A200: mat.get-color-from-palette($primary-palette,
'A200');
+$primary-palette-A400: mat.get-color-from-palette($primary-palette,
'A400');
+$canvas-primary-palette-50:
mat.get-color-from-palette($canvas-primary-palette, 50);
+$canvas-primary-palette-200:
mat.get-color-from-palette($canvas-primary-palette, 200);
+$canvas-primary-palette-400:
mat.get-color-from-palette($canvas-primary-palette, 400);
+$canvas-primary-palette-900:
mat.get-color-from-palette($canvas-primary-palette, 900);
+$accent-palette-200: mat.get-color-from-palette($accent-palette, 200);
+$accent-palette-400: mat.get-color-from-palette($accent-palette, 400);
+$accent-palette-A200: mat.get-color-from-palette($accent-palette,
[jira] [Commented] (NIFI-12677) ExcelReader documentation gives an example of a non-existent strategy
[
https://issues.apache.org/jira/browse/NIFI-12677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17812070#comment-17812070
]
ASF subversion and git services commented on NIFI-12677:
Commit 1f7662ce0b1d88b8d33d629524ff96ddcab6010a in nifi's branch
refs/heads/support/nifi-1.x from dan-s1
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=1f7662ce0b ]
NIFI-12677 Removed documentation of non-existent strategy for ExcelReader
This closes #8310
Signed-off-by: David Handermann
(cherry picked from commit 592cc420599df8456a2e658e3653ae1403d30ed6)
> ExcelReader documentation gives an example of a non-existent strategy
> -
>
> Key: NIFI-12677
> URL: https://issues.apache.org/jira/browse/NIFI-12677
> Project: Apache NiFi
> Issue Type: Bug
>Reporter: Daniel Stieglitz
>Assignee: Daniel Stieglitz
>Priority: Minor
> Labels: backport-needed
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In the Addtional Details of Excel Reader it gives an example for a strategy
> "Use Fields From Header" which does not exist. This ticket addresses the need
> to remove the whole paragraph with the title
> {quote}
> Example 2 - Schema with Excel Header Line
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-12677) ExcelReader documentation gives an example of a non-existent strategy
[
https://issues.apache.org/jira/browse/NIFI-12677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-12677:
Fix Version/s: 2.0.0
1.26.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> ExcelReader documentation gives an example of a non-existent strategy
> -
>
> Key: NIFI-12677
> URL: https://issues.apache.org/jira/browse/NIFI-12677
> Project: Apache NiFi
> Issue Type: Bug
>Reporter: Daniel Stieglitz
>Assignee: Daniel Stieglitz
>Priority: Trivial
> Labels: backport-needed
> Fix For: 2.0.0, 1.26.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In the Addtional Details of Excel Reader it gives an example for a strategy
> "Use Fields From Header" which does not exist. This ticket addresses the need
> to remove the whole paragraph with the title
> {quote}
> Example 2 - Schema with Excel Header Line
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-12677) ExcelReader documentation gives an example of a non-existent strategy
[
https://issues.apache.org/jira/browse/NIFI-12677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-12677:
Priority: Trivial (was: Minor)
> ExcelReader documentation gives an example of a non-existent strategy
> -
>
> Key: NIFI-12677
> URL: https://issues.apache.org/jira/browse/NIFI-12677
> Project: Apache NiFi
> Issue Type: Bug
>Reporter: Daniel Stieglitz
>Assignee: Daniel Stieglitz
>Priority: Trivial
> Labels: backport-needed
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In the Addtional Details of Excel Reader it gives an example for a strategy
> "Use Fields From Header" which does not exist. This ticket addresses the need
> to remove the whole paragraph with the title
> {quote}
> Example 2 - Schema with Excel Header Line
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-12677) ExcelReader documentation gives an example of a non-existent strategy
[
https://issues.apache.org/jira/browse/NIFI-12677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17812069#comment-17812069
]
ASF subversion and git services commented on NIFI-12677:
Commit 592cc420599df8456a2e658e3653ae1403d30ed6 in nifi's branch
refs/heads/main from dan-s1
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=592cc42059 ]
NIFI-12677 Removed documentation of non-existent strategy for ExcelReader
This closes #8310
Signed-off-by: David Handermann
> ExcelReader documentation gives an example of a non-existent strategy
> -
>
> Key: NIFI-12677
> URL: https://issues.apache.org/jira/browse/NIFI-12677
> Project: Apache NiFi
> Issue Type: Bug
>Reporter: Daniel Stieglitz
>Assignee: Daniel Stieglitz
>Priority: Minor
> Labels: backport-needed
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In the Addtional Details of Excel Reader it gives an example for a strategy
> "Use Fields From Header" which does not exist. This ticket addresses the need
> to remove the whole paragraph with the title
> {quote}
> Example 2 - Schema with Excel Header Line
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] NIFI-12677 Removed documentation of example of a non-existent strategy. [nifi]
exceptionfactory closed pull request #8310: NIFI-12677 Removed documentation of example of a non-existent strategy. URL: https://github.com/apache/nifi/pull/8310 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (NIFI-12677) ExcelReader documentation gives an example of a non-existent strategy
[
https://issues.apache.org/jira/browse/NIFI-12677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Stieglitz updated NIFI-12677:
Status: Patch Available (was: In Progress)
> ExcelReader documentation gives an example of a non-existent strategy
> -
>
> Key: NIFI-12677
> URL: https://issues.apache.org/jira/browse/NIFI-12677
> Project: Apache NiFi
> Issue Type: Bug
>Reporter: Daniel Stieglitz
>Assignee: Daniel Stieglitz
>Priority: Minor
> Labels: backport-needed
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In the Addtional Details of Excel Reader it gives an example for a strategy
> "Use Fields From Header" which does not exist. This ticket addresses the need
> to remove the whole paragraph with the title
> {quote}
> Example 2 - Schema with Excel Header Line
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] NIFI-12677 Removed documentation of example of a non-existent strategy. [nifi]
dan-s1 opened a new pull request, #8310: URL: https://github.com/apache/nifi/pull/8310 # Summary [NIFI-12677](https://issues.apache.org/jira/browse/NIFI-12677) # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [ ] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [ ] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [ ] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [ ] Pull Request based on current revision of the `main` branch - [ ] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [ ] Build completed using `mvn clean install -P contrib-check` - [ ] JDK 21 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (NIFI-12679) Prompt to copy during Policy override
[ https://issues.apache.org/jira/browse/NIFI-12679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17812053#comment-17812053 ] ASF subversion and git services commented on NIFI-12679: Commit 03b925629e7b8e8771571588ba740dd738b44c75 in nifi's branch refs/heads/main from Matt Gilman [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=03b925629e ] NIFI-12679: (#8306) - When overriding a policy prompting whether the new policy should copy the users and groups or if it should be empty. > Prompt to copy during Policy override > - > > Key: NIFI-12679 > URL: https://issues.apache.org/jira/browse/NIFI-12679 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > When overriding a component, the UI should prompt whether the new policy > should be empty or a copy of the parent policy. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12679) Prompt to copy during Policy override
[ https://issues.apache.org/jira/browse/NIFI-12679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Fellows updated NIFI-12679: --- Fix Version/s: 2.0.0 Resolution: Fixed Status: Resolved (was: Patch Available) > Prompt to copy during Policy override > - > > Key: NIFI-12679 > URL: https://issues.apache.org/jira/browse/NIFI-12679 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > Fix For: 2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > When overriding a component, the UI should prompt whether the new policy > should be empty or a copy of the parent policy. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12679: Prompt to copy policy during override [nifi]
rfellows merged PR #8306: URL: https://github.com/apache/nifi/pull/8306 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (NIFI-12679) Prompt to copy during Policy override
[ https://issues.apache.org/jira/browse/NIFI-12679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17812049#comment-17812049 ] ASF subversion and git services commented on NIFI-12679: Commit 8e0c68e5cc8e39b544ed44a7885d1f04f7ae6f42 in nifi's branch refs/heads/main from Matt Gilman [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=8e0c68e5cc ] NIFI-12663: Error Handling in CS Listing (#8305) * NIFI-12663: - Handling API error responses in the Management Controller Services page. * NIFI-12679: - Renaming components based on review feedback. - Using ng-content in page-content component. - Removing the problematic route when navigating to the error page. - Fixing logic when handling service loading errors. - Handling errors in the Property Table Helper service. * NIFI-12679: - Addressing review feedback. > Prompt to copy during Policy override > - > > Key: NIFI-12679 > URL: https://issues.apache.org/jira/browse/NIFI-12679 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > When overriding a component, the UI should prompt whether the new policy > should be empty or a copy of the parent policy. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12663) Management Controller Services - General API error response handling
[ https://issues.apache.org/jira/browse/NIFI-12663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Fellows updated NIFI-12663: --- Fix Version/s: 2.0.0 Resolution: Fixed Status: Resolved (was: Patch Available) > Management Controller Services - General API error response handling > > > Key: NIFI-12663 > URL: https://issues.apache.org/jira/browse/NIFI-12663 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > Fix For: 2.0.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Update the Management Controller Services page to show API error responses. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12663) Management Controller Services - General API error response handling
[ https://issues.apache.org/jira/browse/NIFI-12663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17812048#comment-17812048 ] ASF subversion and git services commented on NIFI-12663: Commit 8e0c68e5cc8e39b544ed44a7885d1f04f7ae6f42 in nifi's branch refs/heads/main from Matt Gilman [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=8e0c68e5cc ] NIFI-12663: Error Handling in CS Listing (#8305) * NIFI-12663: - Handling API error responses in the Management Controller Services page. * NIFI-12679: - Renaming components based on review feedback. - Using ng-content in page-content component. - Removing the problematic route when navigating to the error page. - Fixing logic when handling service loading errors. - Handling errors in the Property Table Helper service. * NIFI-12679: - Addressing review feedback. > Management Controller Services - General API error response handling > > > Key: NIFI-12663 > URL: https://issues.apache.org/jira/browse/NIFI-12663 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > Time Spent: 1h 10m > Remaining Estimate: 0h > > Update the Management Controller Services page to show API error responses. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12663: Error Handling in CS Listing [nifi]
rfellows merged PR #8305: URL: https://github.com/apache/nifi/pull/8305 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (NIFI-12677) ExcelReader documentation gives an example of a non-existent strategy
[
https://issues.apache.org/jira/browse/NIFI-12677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Stieglitz updated NIFI-12677:
Summary: ExcelReader documentation gives an example of a non-existent
strategy (was: ExcelReader documentation gives an example of a non existent
strategy)
> ExcelReader documentation gives an example of a non-existent strategy
> -
>
> Key: NIFI-12677
> URL: https://issues.apache.org/jira/browse/NIFI-12677
> Project: Apache NiFi
> Issue Type: Bug
>Reporter: Daniel Stieglitz
>Assignee: Daniel Stieglitz
>Priority: Minor
> Labels: backport-needed
>
> In the Addtional Details of Excel Reader it gives an example for a strategy
> "Use Fields From Header" which does not exist. This ticket addresses the need
> to remove the whole paragraph with the title
> {quote}
> Example 2 - Schema with Excel Header Line
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [NIFI-12655] theme NiFi following Material Design spec and leveraging Angular Material themes [nifi]
scottyaslan commented on code in PR #8294:
URL: https://github.com/apache/nifi/pull/8294#discussion_r1470034592
##
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi/src/app/pages/flow-designer/service/manager/processor-manager.service.ts:
##
@@ -669,20 +669,20 @@ export class ProcessorManager {
// update the run status
updated
.select('text.run-status-icon')
-.attr('fill', function (d: any) {
-let fill: string = '#728e9b';
+.attr('class', function (d: any) {
+let clazz: string = 'primary-500';
if (d.status.aggregateSnapshot.runStatus === 'Validating') {
-fill = '#a8a8a8';
+clazz = 'warn-contrast-300';
} else if (d.status.aggregateSnapshot.runStatus === 'Invalid')
{
-fill = '#cf9f5d';
+clazz = 'accent-A200';
} else if (d.status.aggregateSnapshot.runStatus === 'Running')
{
-fill = '#7dc7a0';
+clazz = 'accent-200';
} else if (d.status.aggregateSnapshot.runStatus === 'Stopped')
{
-fill = '#d18686';
+clazz = 'warn-200';
}
-return fill;
+return clazz;
Review Comment:
Great catch! I have updated these in my latest commit. Thanks!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Resolved] (NIFI-12646) Conduct Apache NiFi 2.0.0-M2 Release
[ https://issues.apache.org/jira/browse/NIFI-12646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann resolved NIFI-12646. - Resolution: Fixed > Conduct Apache NiFi 2.0.0-M2 Release > > > Key: NIFI-12646 > URL: https://issues.apache.org/jira/browse/NIFI-12646 > Project: Apache NiFi > Issue Type: Task >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0-M2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12642) Add local file upload option in PutS3 processor
[ https://issues.apache.org/jira/browse/NIFI-12642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Turcsanyi updated NIFI-12642: --- Fix Version/s: 2.0.0 Resolution: Fixed Status: Resolved (was: Patch Available) > Add local file upload option in PutS3 processor > --- > > Key: NIFI-12642 > URL: https://issues.apache.org/jira/browse/NIFI-12642 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Balázs Gerner >Assignee: Balázs Gerner >Priority: Major > Fix For: 2.0.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Similarly to PutAzure*Storage processors, inside the *PutS3Object* processor, > add option to upload file from the local filesystem directly to AWS S3 > by-passing the content repo. > The two available file resource transfer sources are: > * FlowFile's Content (default, current behaviour) > * Local File -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12642) Add local file upload option in PutS3 processor
[ https://issues.apache.org/jira/browse/NIFI-12642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17811997#comment-17811997 ] ASF subversion and git services commented on NIFI-12642: Commit c1a21ad078d7b9c3b0422c48b9bb1f9faa3c0b6f in nifi's branch refs/heads/main from Balázs Gerner [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=c1a21ad078 ] NIFI-12642 Added support for FileResourceService in PutS3Object This closes #8295. Signed-off-by: Peter Turcsanyi > Add local file upload option in PutS3 processor > --- > > Key: NIFI-12642 > URL: https://issues.apache.org/jira/browse/NIFI-12642 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Balázs Gerner >Assignee: Balázs Gerner >Priority: Major > Time Spent: 1h > Remaining Estimate: 0h > > Similarly to PutAzure*Storage processors, inside the *PutS3Object* processor, > add option to upload file from the local filesystem directly to AWS S3 > by-passing the content repo. > The two available file resource transfer sources are: > * FlowFile's Content (default, current behaviour) > * Local File -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12642 Added support for FileResourceService in PutS3Object [nifi]
asfgit closed pull request #8295: NIFI-12642 Added support for FileResourceService in PutS3Object URL: https://github.com/apache/nifi/pull/8295 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12663: Error Handling in CS Listing [nifi]
rfellows commented on code in PR #8305:
URL: https://github.com/apache/nifi/pull/8305#discussion_r1469948325
##
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi/src/app/service/property-table-helper.service.ts:
##
@@ -153,6 +180,20 @@ export class PropertyTableHelperService {
.getPropertyDescriptor(id,
descriptor.name, false)
.pipe(
take(1),
+tap({
+error: (errorResponse:
HttpErrorResponse) => {
+// we've errored
getting the descriptor but since the service
+// was already
created, we should close the create service dialog
+// so multiple service
instances are not inadvertently created
+
createServiceDialogReference.close();
+
+this.store.dispatch(
+snackBarError({
+error:
`Service created but until to reload Property Descriptor:
${errorResponse.error}`
Review Comment:
I'm a bit confused by this wording. Can we clarify it a bit more?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Updated] (NIFI-12639) Backport JSON Schema Registry for ValidateJson
[ https://issues.apache.org/jira/browse/NIFI-12639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12639: Issue Type: New Feature (was: Improvement) > Backport JSON Schema Registry for ValidateJson > -- > > Key: NIFI-12639 > URL: https://issues.apache.org/jira/browse/NIFI-12639 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Daniel Stieglitz >Assignee: Daniel Stieglitz >Priority: Major > Fix For: 1.25.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > The changes made for NIFI-11627 were only committed on the 2.x branch and not > backported to the support/nifi-1.x branch. The purpose of this ticket is to > backport the code. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11627) Add JSON Schema Registry Service for ValidateJson Processor
[
https://issues.apache.org/jira/browse/NIFI-11627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-11627:
Issue Type: New Feature (was: Improvement)
> Add JSON Schema Registry Service for ValidateJson Processor
> ---
>
> Key: NIFI-11627
> URL: https://issues.apache.org/jira/browse/NIFI-11627
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
>Affects Versions: 1.19.1
>Reporter: Chuck Tilly
>Assignee: Daniel Stieglitz
>Priority: Major
> Fix For: 2.0.0-M2
>
> Time Spent: 9h
> Remaining Estimate: 0h
>
> For the ValidateJSON processor, add support for flowfile attribute references
> that will allow for a JSON schema located in the Parameter Contexts, to be
> referenced dynamically based on a flowfile attribute. e.g.
> {code:java}
> #{${schema.name}} {code}
>
> The benefits of adding support for attribute references are significant.
> Adding this capability will allow a single processor to be used for all JSON
> schema validation. Unfortunately, the current version of this processor
> requires a dedicated processor for every schema, i.e. 12 schemas requires 12
> ValidateJSON processors. This is very laborious to construct and maintain,
> and resource expensive.
> ValidateJSON processor (https://issues.apache.org/jira/browse/NIFI-7392)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] NIFI-12680 Fix JAR for DefaultedDynamicClassPathModificationIT on Support Branch [nifi]
exceptionfactory commented on PR #8307: URL: https://github.com/apache/nifi/pull/8307#issuecomment-1914809959 Based on GitHub Actions and local builds, there appears to be an unrelated problem with the ProvenanceRepositoryIT on Java 17. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (NIFI-12646) Conduct Apache NiFi 2.0.0-M2 Release
[ https://issues.apache.org/jira/browse/NIFI-12646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17811904#comment-17811904 ] ASF subversion and git services commented on NIFI-12646: Commit dff7ea3535abc9bf522b4dac202fe21b7da7813d in nifi's branch refs/heads/main from David Handermann [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=dff7ea3535 ] NIFI-12646 Set Python Processor versions to 2.0.0-SNAPSHOT > Conduct Apache NiFi 2.0.0-M2 Release > > > Key: NIFI-12646 > URL: https://issues.apache.org/jira/browse/NIFI-12646 > Project: Apache NiFi > Issue Type: Task >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0-M2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12646) Conduct Apache NiFi 2.0.0-M2 Release
[ https://issues.apache.org/jira/browse/NIFI-12646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17811899#comment-17811899 ] ASF subversion and git services commented on NIFI-12646: Commit 5ca7b0df81300ce1bfda901c918842eca5847eb2 in nifi's branch refs/heads/main from David Handermann [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=5ca7b0df81 ] NIFI-12646-RC4 prepare for next development iteration > Conduct Apache NiFi 2.0.0-M2 Release > > > Key: NIFI-12646 > URL: https://issues.apache.org/jira/browse/NIFI-12646 > Project: Apache NiFi > Issue Type: Task >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0-M2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12646) Conduct Apache NiFi 2.0.0-M2 Release
[ https://issues.apache.org/jira/browse/NIFI-12646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17811900#comment-17811900 ] ASF subversion and git services commented on NIFI-12646: Commit da9aa33bf1ea555211bd838db5726b1837e8b004 in nifi's branch refs/heads/main from David Handermann [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=da9aa33bf1 ] Merge branch 'NIFI-12646-RC4' > Conduct Apache NiFi 2.0.0-M2 Release > > > Key: NIFI-12646 > URL: https://issues.apache.org/jira/browse/NIFI-12646 > Project: Apache NiFi > Issue Type: Task >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0-M2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12646) Conduct Apache NiFi 2.0.0-M2 Release
[ https://issues.apache.org/jira/browse/NIFI-12646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17811898#comment-17811898 ] ASF subversion and git services commented on NIFI-12646: Commit 640b7bdfbbb8842f057a9bf49dc2b9b5d092abda in nifi's branch refs/heads/main from David Handermann [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=640b7bdfbb ] NIFI-12646-RC4 prepare release nifi-2.0.0-M2-RC4 > Conduct Apache NiFi 2.0.0-M2 Release > > > Key: NIFI-12646 > URL: https://issues.apache.org/jira/browse/NIFI-12646 > Project: Apache NiFi > Issue Type: Task >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0-M2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12646) Conduct Apache NiFi 2.0.0-M2 Release
[ https://issues.apache.org/jira/browse/NIFI-12646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17811897#comment-17811897 ] ASF subversion and git services commented on NIFI-12646: Commit 38fc0a4e8d966b6a185144e4ea6b34c948cdad1b in nifi's branch refs/heads/main from David Handermann [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=38fc0a4e8d ] NIFI-12646 Set Python Processor version to 2.0.0-M2 Signed-off-by: David Handermann > Conduct Apache NiFi 2.0.0-M2 Release > > > Key: NIFI-12646 > URL: https://issues.apache.org/jira/browse/NIFI-12646 > Project: Apache NiFi > Issue Type: Task >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0-M2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12663: Error Handling in CS Listing [nifi]
rfellows commented on code in PR #8305:
URL: https://github.com/apache/nifi/pull/8305#discussion_r1469594883
##
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi/src/app/ui/common/page-content/page-content.component.scss:
##
@@ -15,7 +15,9 @@
* limitations under the License.
*/
-.message {
+.page-content {
+//width: 500px;
Review Comment:
can this be removed?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[PR] NIFI-12682 Fix MiNiFi agent manifest hash swaps [nifi]
ferencerdei opened a new pull request, #8309: URL: https://github.com/apache/nifi/pull/8309 # Summary [NIFI-12682](https://issues.apache.org/jira/browse/NIFI-12682) # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [ ] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [ ] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [ ] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [ ] Pull Request based on current revision of the `main` branch - [ ] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [ ] Build completed using `mvn clean install -P contrib-check` - [ ] JDK 21 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (NIFI-12682) [MiNiFi] agentInfo.agentManifestHash is changing between MiNiFi restarts
Ferenc Erdei created NIFI-12682: --- Summary: [MiNiFi] agentInfo.agentManifestHash is changing between MiNiFi restarts Key: NIFI-12682 URL: https://issues.apache.org/jira/browse/NIFI-12682 Project: Apache NiFi Issue Type: Bug Components: MiNiFi Affects Versions: 1.24.0, 2.0.0-M1, 2.0.0-M2 Reporter: Ferenc Erdei Assignee: Ferenc Erdei Fix For: 1.26.0 In the C2 Heartbeat request payload the agentInfo.agentManifestHash can be used by the C2 server to determine whether agent configuration changed between heartbeats and if the C2 server needs to send a DESCRIBE_MANIFEST request. Issue: the hash is changing between restart therefore an unnecessary command might be sent to the agent. Possible root cause: Probably linkedhashmap or linkedset is missing somewhere in the flow of the supported operations. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-12648) Refactor components in elasticsearch bundle using current API methods
[
https://issues.apache.org/jira/browse/NIFI-12648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Gresock resolved NIFI-12648.
Fix Version/s: 2.0.0
Resolution: Fixed
> Refactor components in elasticsearch bundle using current API methods
> -
>
> Key: NIFI-12648
> URL: https://issues.apache.org/jira/browse/NIFI-12648
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: endzeit
>Assignee: endzeit
>Priority: Minor
> Fix For: 2.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Based on improvements to support for {{DescribedValue}} in NiFi API and other
> improvements in Java 21, the _elasticsearch_ bundle components should be
> updated to use current methods.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-12648) Refactor components in elasticsearch bundle using current API methods
[
https://issues.apache.org/jira/browse/NIFI-12648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17811802#comment-17811802
]
ASF subversion and git services commented on NIFI-12648:
Commit 5ba20b87c52acc219aad14e813b4fbddc1960c2d in nifi's branch
refs/heads/main from EndzeitBegins
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=5ba20b87c5 ]
NIFI-12648 Refactor components in elasticsearch bundle using current API methods
Signed-off-by: Joe Gresock
This closes #8303.
> Refactor components in elasticsearch bundle using current API methods
> -
>
> Key: NIFI-12648
> URL: https://issues.apache.org/jira/browse/NIFI-12648
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: endzeit
>Assignee: endzeit
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Based on improvements to support for {{DescribedValue}} in NiFi API and other
> improvements in Java 21, the _elasticsearch_ bundle components should be
> updated to use current methods.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] NIFI-12648 Refactor components in elasticsearch bundle using current API methods [nifi]
asfgit closed pull request #8303: NIFI-12648 Refactor components in elasticsearch bundle using current API methods URL: https://github.com/apache/nifi/pull/8303 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
