[jira] [Commented] (NIFI-13439) Add performance tracking to ProcessGroupStatus
[ https://issues.apache.org/jira/browse/NIFI-13439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17860346#comment-17860346 ] Timea Barna commented on NIFI-13439: https://github.com/apache/nifi/pull/9014 > Add performance tracking to ProcessGroupStatus > -- > > Key: NIFI-13439 > URL: https://issues.apache.org/jira/browse/NIFI-13439 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > > Introduce a new PerformanceMetrics type of class for performance tracking > values and add getter/setter to the ProcessGroupStatus. > This way QueryNiFiReportinkTask can be used to find out how much resources a > specific process group is using at a given point in time. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13439) Add performance tracking to ProcessGroupStatus
[ https://issues.apache.org/jira/browse/NIFI-13439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-13439: --- Status: Patch Available (was: In Progress) > Add performance tracking to ProcessGroupStatus > -- > > Key: NIFI-13439 > URL: https://issues.apache.org/jira/browse/NIFI-13439 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > > Introduce a new PerformanceMetrics type of class for performance tracking > values and add getter/setter to the ProcessGroupStatus. > This way QueryNiFiReportinkTask can be used to find out how much resources a > specific process group is using at a given point in time. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13439) Add performance tracking to ProcessGroupStatus
[ https://issues.apache.org/jira/browse/NIFI-13439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-13439: --- Description: Introduce a new PerformanceMetrics type of class for performance tracking values and add getter/setter to the ProcessGroupStatus. This way QueryNiFiReportinkTask can be used to find out how much resources a specific process group is using at a given point in time. was: Introduce a new PerformanceMetrics type of class that has the necessary values and just add getter/setter to the ProcessGroupStatus. This way QueryNiFiReportinkTask can be used to find out how much resources a specific process group is using at a given point in time. > Add performance tracking to ProcessGroupStatus > -- > > Key: NIFI-13439 > URL: https://issues.apache.org/jira/browse/NIFI-13439 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > > Introduce a new PerformanceMetrics type of class for performance tracking > values and add getter/setter to the ProcessGroupStatus. > This way QueryNiFiReportinkTask can be used to find out how much resources a > specific process group is using at a given point in time. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13439) Add performance tracking to ProcessGroupStatus
Timea Barna created NIFI-13439: -- Summary: Add performance tracking to ProcessGroupStatus Key: NIFI-13439 URL: https://issues.apache.org/jira/browse/NIFI-13439 Project: Apache NiFi Issue Type: New Feature Reporter: Timea Barna Assignee: Timea Barna Introduce a new PerformanceMetrics type of class that has the necessary values and just add getter/setter to the ProcessGroupStatus. This way QueryNiFiReportinkTask can be used to find out how much resources a specific process group is using at a given point in time. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12749) NiFi Toolkit export-all-flows fails when flow name contains '/'
[ https://issues.apache.org/jira/browse/NIFI-12749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-12749: --- Status: Patch Available (was: In Progress) > NiFi Toolkit export-all-flows fails when flow name contains '/' > --- > > Key: NIFI-12749 > URL: https://issues.apache.org/jira/browse/NIFI-12749 > Project: Apache NiFi > Issue Type: Bug >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The command fails if there are any flows in the registry that has a / > character because when exporting the flow, the toolkit assumes / is a path > separator as the toolkit will use the versioned flow name and version when > creating the exported files. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12749) NiFi Toolkit export-all-flows fails when flow name contains '/'
[ https://issues.apache.org/jira/browse/NIFI-12749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-12749: --- Summary: NiFi Toolkit export-all-flows fails when flow name contains '/' (was: NiFi Toolkit export-all-flows fails when flow name contains has '/') > NiFi Toolkit export-all-flows fails when flow name contains '/' > --- > > Key: NIFI-12749 > URL: https://issues.apache.org/jira/browse/NIFI-12749 > Project: Apache NiFi > Issue Type: Bug >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > > The command fails if there are any flows in the registry that has a / > character because when exporting the flow, the toolkit assumes / is a path > separator as the toolkit will use the versioned flow name and version when > creating the exported files. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12749) NiFi Toolkit export-all-flows fails when flow name contains has '/'
Timea Barna created NIFI-12749: -- Summary: NiFi Toolkit export-all-flows fails when flow name contains has '/' Key: NIFI-12749 URL: https://issues.apache.org/jira/browse/NIFI-12749 Project: Apache NiFi Issue Type: Bug Reporter: Timea Barna Assignee: Timea Barna The command fails if there are any flows in the registry that has a / character because when exporting the flow, the toolkit assumes / is a path separator as the toolkit will use the versioned flow name and version when creating the exported files. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12506) /nifi-api/flow/metrics endpoint times out if flow is big
[ https://issues.apache.org/jira/browse/NIFI-12506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-12506: --- Status: Patch Available (was: In Progress) > /nifi-api/flow/metrics endpoint times out if flow is big > > > Key: NIFI-12506 > URL: https://issues.apache.org/jira/browse/NIFI-12506 > Project: Apache NiFi > Issue Type: Bug >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > If a flow is relatively big, having more than 10K processors, > /nifi-api/flow/metrics endpoint times out if nifi.analytics.predict.enabled > set to true as gathering predictions takes long. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12506) /nifi-api/flow/metrics endpoint times out if flow is big
[ https://issues.apache.org/jira/browse/NIFI-12506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-12506: --- Description: If a flow is relatively big, having more than 10K processors, /nifi-api/flow/metrics endpoint times out if nifi.analytics.predict.enabled set to true as gathering predictions takes long. (was: If a flow is relatively big 10K processors /nifi-api/flow/metrics endpoint times out if nifi.analytics.predict.enabled set to true as gathering predictions takes long.) > /nifi-api/flow/metrics endpoint times out if flow is big > > > Key: NIFI-12506 > URL: https://issues.apache.org/jira/browse/NIFI-12506 > Project: Apache NiFi > Issue Type: Bug >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > > If a flow is relatively big, having more than 10K processors, > /nifi-api/flow/metrics endpoint times out if nifi.analytics.predict.enabled > set to true as gathering predictions takes long. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12506) /nifi-api/flow/metrics endpoint times out if flow is big
Timea Barna created NIFI-12506: -- Summary: /nifi-api/flow/metrics endpoint times out if flow is big Key: NIFI-12506 URL: https://issues.apache.org/jira/browse/NIFI-12506 Project: Apache NiFi Issue Type: Bug Reporter: Timea Barna Assignee: Timea Barna If a flow is relatively big 10K processors /nifi-api/flow/metrics endpoint times out if nifi.analytics.predict.enabled set to true as gathering predictions takes long. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12479) Add pg-export to toolkit CLI
[ https://issues.apache.org/jira/browse/NIFI-12479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-12479: --- Status: Patch Available (was: In Progress) > Add pg-export to toolkit CLI > > > Key: NIFI-12479 > URL: https://issues.apache.org/jira/browse/NIFI-12479 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Add a CLI command allowing to save a process group in NiFi as a JSON file. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12479) Add pg-export to toolkit CLI
Timea Barna created NIFI-12479: -- Summary: Add pg-export to toolkit CLI Key: NIFI-12479 URL: https://issues.apache.org/jira/browse/NIFI-12479 Project: Apache NiFi Issue Type: Improvement Reporter: Timea Barna Assignee: Timea Barna Add a CLI command allowing to save a process group in NiFi as a JSON file. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12166) Add repo usage to the monitoring endpoint
[ https://issues.apache.org/jira/browse/NIFI-12166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-12166: --- Status: Patch Available (was: In Progress) > Add repo usage to the monitoring endpoint > - > > Key: NIFI-12166 > URL: https://issues.apache.org/jira/browse/NIFI-12166 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > In the monitoring endpoint exposed by NiFi we should add some metrics around > repo usage: > flow file repo usage percent > content repo usage percent > with a label maybe as we can have multiple content repo > prov repo usage percent > with a label maybe as we can have multiple prov repo > I guess we could also add 'available' and 'used' values in GB? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-12166) Add repo usage to the monitoring endpoint
[ https://issues.apache.org/jira/browse/NIFI-12166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna reassigned NIFI-12166: -- Assignee: Timea Barna > Add repo usage to the monitoring endpoint > - > > Key: NIFI-12166 > URL: https://issues.apache.org/jira/browse/NIFI-12166 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > > In the monitoring endpoint exposed by NiFi we should add some metrics around > repo usage: > flow file repo usage percent > content repo usage percent > with a label maybe as we can have multiple content repo > prov repo usage percent > with a label maybe as we can have multiple prov repo > I guess we could also add 'available' and 'used' values in GB? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12166) Add repo usage to the monitoring endpoint
Timea Barna created NIFI-12166: -- Summary: Add repo usage to the monitoring endpoint Key: NIFI-12166 URL: https://issues.apache.org/jira/browse/NIFI-12166 Project: Apache NiFi Issue Type: Improvement Reporter: Timea Barna In the monitoring endpoint exposed by NiFi we should add some metrics around repo usage: flow file repo usage percent content repo usage percent with a label maybe as we can have multiple content repo prov repo usage percent with a label maybe as we can have multiple prov repo I guess we could also add 'available' and 'used' values in GB? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12099) Repurpose Template icon in top left bar
[ https://issues.apache.org/jira/browse/NIFI-12099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-12099: --- Component/s: (was: Core UI) > Repurpose Template icon in top left bar > --- > > Key: NIFI-12099 > URL: https://issues.apache.org/jira/browse/NIFI-12099 > Project: Apache NiFi > Issue Type: Improvement >Reporter: András Kovács >Assignee: Timea Barna >Priority: Major > > In the top left bar, we have an icon for templates that we can use to drag > and drop templates. With the removal of templates, this icon should be > replaced with a "registry icon' (TBD). > It should simulate the same behavior as when drag and dropping a process > group and click "import from a registry". > If there is no registry configured, we should print a popup explaining the > situation and redirecting the user to controller settings / registry client. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12099) Repurpose Template icon in top left bar
[ https://issues.apache.org/jira/browse/NIFI-12099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-12099: --- Component/s: Core UI > Repurpose Template icon in top left bar > --- > > Key: NIFI-12099 > URL: https://issues.apache.org/jira/browse/NIFI-12099 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: András Kovács >Priority: Major > > In the top left bar, we have an icon for templates that we can use to drag > and drop templates. With the removal of templates, this icon should be > replaced with a "registry icon' (TBD). > It should simulate the same behavior as when drag and dropping a process > group and click "import from a registry". > If there is no registry configured, we should print a popup explaining the > situation and redirecting the user to controller settings / registry client. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-12099) Repurpose Template icon in top left bar
[ https://issues.apache.org/jira/browse/NIFI-12099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna reassigned NIFI-12099: -- Assignee: (was: Timea Barna) > Repurpose Template icon in top left bar > --- > > Key: NIFI-12099 > URL: https://issues.apache.org/jira/browse/NIFI-12099 > Project: Apache NiFi > Issue Type: Improvement >Reporter: András Kovács >Priority: Major > > In the top left bar, we have an icon for templates that we can use to drag > and drop templates. With the removal of templates, this icon should be > replaced with a "registry icon' (TBD). > It should simulate the same behavior as when drag and dropping a process > group and click "import from a registry". > If there is no registry configured, we should print a popup explaining the > situation and redirecting the user to controller settings / registry client. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-12099) Repurpose Template icon in top left bar
[ https://issues.apache.org/jira/browse/NIFI-12099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna reassigned NIFI-12099: -- Assignee: Timea Barna > Repurpose Template icon in top left bar > --- > > Key: NIFI-12099 > URL: https://issues.apache.org/jira/browse/NIFI-12099 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: András Kovács >Assignee: Timea Barna >Priority: Major > > In the top left bar, we have an icon for templates that we can use to drag > and drop templates. With the removal of templates, this icon should be > replaced with a "registry icon' (TBD). > It should simulate the same behavior as when drag and dropping a process > group and click "import from a registry". > If there is no registry configured, we should print a popup explaining the > situation and redirecting the user to controller settings / registry client. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-12099) Repurpose Template icon in top left bar
[ https://issues.apache.org/jira/browse/NIFI-12099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna reassigned NIFI-12099: -- Assignee: Timea Barna > Repurpose Template icon in top left bar > --- > > Key: NIFI-12099 > URL: https://issues.apache.org/jira/browse/NIFI-12099 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: András Kovács >Assignee: Timea Barna >Priority: Major > > In the top left bar, we have an icon for templates that we can use to drag > and drop templates. With the removal of templates, this icon should be > replaced with a "registry icon' (TBD). > It should simulate the same behavior as when drag and dropping a process > group and click "import from a registry". > If there is no registry configured, we should print a popup explaining the > situation and redirecting the user to controller settings / registry client. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12006) Remove Templates from nifi 2.0
[ https://issues.apache.org/jira/browse/NIFI-12006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-12006: --- Status: Patch Available (was: In Progress) > Remove Templates from nifi 2.0 > -- > > Key: NIFI-12006 > URL: https://issues.apache.org/jira/browse/NIFI-12006 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Remove Templates from backend -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12006) Remove Templates from nifi 2.0
Timea Barna created NIFI-12006: -- Summary: Remove Templates from nifi 2.0 Key: NIFI-12006 URL: https://issues.apache.org/jira/browse/NIFI-12006 Project: Apache NiFi Issue Type: Improvement Reporter: Timea Barna Assignee: Timea Barna Remove Templates from backend -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11705) Append "Operating System / Hardware" section in NiFi diagnostic tool
[ https://issues.apache.org/jira/browse/NIFI-11705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-11705: --- Status: Patch Available (was: In Progress) > Append "Operating System / Hardware" section in NiFi diagnostic tool > > > Key: NIFI-11705 > URL: https://issues.apache.org/jira/browse/NIFI-11705 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The nifi.sh script has a diagnostic flag that provides valuable information > related to the flow, a thread dump and a lot of other information. > Append "Operating System / Hardware" section with contains number of cores, > physical ram, and disk layout. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11705) Append "Operating System / Hardware" section in NiFi diagnostic tool
[ https://issues.apache.org/jira/browse/NIFI-11705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-11705: --- Description: The nifi.sh script has a diagnostic flag that provides valuable information related to the flow, a thread dump and a lot of other information. Append "Operating System / Hardware" section with contains number of cores, physical ram, and disk layout. was: The nifi.sh script has a diagnostic flag that provides valuable information related to the flow, a thread dump and a lot of other information. Another section could be a "System" resources that contains number of cores, physical ram, and disk layout. > Append "Operating System / Hardware" section in NiFi diagnostic tool > > > Key: NIFI-11705 > URL: https://issues.apache.org/jira/browse/NIFI-11705 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > > The nifi.sh script has a diagnostic flag that provides valuable information > related to the flow, a thread dump and a lot of other information. > Append "Operating System / Hardware" section with contains number of cores, > physical ram, and disk layout. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11705) Append "Operating System / Hardware" section in NiFi diagnostic tool
Timea Barna created NIFI-11705: -- Summary: Append "Operating System / Hardware" section in NiFi diagnostic tool Key: NIFI-11705 URL: https://issues.apache.org/jira/browse/NIFI-11705 Project: Apache NiFi Issue Type: Improvement Reporter: Timea Barna Assignee: Timea Barna The nifi.sh script has a diagnostic flag that provides valuable information related to the flow, a thread dump and a lot of other information. Another section could be a "System" resources that contains number of cores, physical ram, and disk layout. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11658) Streamline using single parameter context for nested PGs
Timea Barna created NIFI-11658: -- Summary: Streamline using single parameter context for nested PGs Key: NIFI-11658 URL: https://issues.apache.org/jira/browse/NIFI-11658 Project: Apache NiFi Issue Type: Improvement Reporter: Timea Barna Assignee: Timea Barna 1. when adding a new process group to the canvas, in the create PG view where one should give the name of the process group, add a drop down menu to select the parameter context to associate with the process group. It would default to the parameter context associated to the parent process group (if there is one specified and if the user has the permissions) 2. in the configuration view of a process group, add a dedicated tab for parameter context to have dedicated handling. In addition to the dropdown menu for selecting a parameter context, add a checkbox to recursively apply the change. This checkbox would only be used when clicking "Apply", it would not be persisted. If checked, it means that the parameter context will be applied to the process group as well to all the embedded process groups (recursively) if and only if the user has the proper permissions on all process groups. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-3065) Fine-grained logging in multi-tenant context
[ https://issues.apache.org/jira/browse/NIFI-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-3065: -- Status: Patch Available (was: In Progress) > Fine-grained logging in multi-tenant context > > > Key: NIFI-3065 > URL: https://issues.apache.org/jira/browse/NIFI-3065 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Pierre Villard >Assignee: Timea Barna >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > In a multi-tenant approach, it could be interesting to offer to users a way > to have a fine-grained logging capabilities per tenant. > Let's say that root process group is used to have one process group per > "project" accessed by different teams/users, it could be really useful to > have a log file per process group containing logs for all elements inside > this process group. > A first version could be to develop a custom log appender that would log each > message in a file dedicated to its process group parent. > This improvement will ease the logging management when there are hundreds of > processors separated between different teams and this will also prevent the > access to the logs concerning one team by another team (could be a security > issue). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-3065) Fine-grained logging in multi-tenant context
[ https://issues.apache.org/jira/browse/NIFI-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna reassigned NIFI-3065: - Assignee: Timea Barna (was: Pierre Villard) > Fine-grained logging in multi-tenant context > > > Key: NIFI-3065 > URL: https://issues.apache.org/jira/browse/NIFI-3065 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Pierre Villard >Assignee: Timea Barna >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > In a multi-tenant approach, it could be interesting to offer to users a way > to have a fine-grained logging capabilities per tenant. > Let's say that root process group is used to have one process group per > "project" accessed by different teams/users, it could be really useful to > have a log file per process group containing logs for all elements inside > this process group. > A first version could be to develop a custom log appender that would log each > message in a file dedicated to its process group parent. > This improvement will ease the logging management when there are hundreds of > processors separated between different teams and this will also prevent the > access to the logs concerning one team by another team (could be a security > issue). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11473) Flow version change in NiFi should not stop a component when only position is changed
[ https://issues.apache.org/jira/browse/NIFI-11473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-11473: --- Status: Patch Available (was: In Progress) > Flow version change in NiFi should not stop a component when only position is > changed > - > > Key: NIFI-11473 > URL: https://issues.apache.org/jira/browse/NIFI-11473 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > When going from one flow version to another and the position of a component > is changing, but not its configuration, the component should not be stopped. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11473) Flow version change in NiFi should not stop a component when only position is changed
[ https://issues.apache.org/jira/browse/NIFI-11473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-11473: --- Description: When going from one flow version to another and the position of a component is changing, but not its configuration, the component should not be stopped. (was: When going from one flow version to another when the position of a component is changing, but not its configuration, the component should not be stopped.) > Flow version change in NiFi should not stop a component when only position is > changed > - > > Key: NIFI-11473 > URL: https://issues.apache.org/jira/browse/NIFI-11473 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > > When going from one flow version to another and the position of a component > is changing, but not its configuration, the component should not be stopped. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11473) Flow version change in NiFi should not stop a component when only position is changed
Timea Barna created NIFI-11473: -- Summary: Flow version change in NiFi should not stop a component when only position is changed Key: NIFI-11473 URL: https://issues.apache.org/jira/browse/NIFI-11473 Project: Apache NiFi Issue Type: Improvement Reporter: Timea Barna When going from one flow version to another when the position of a component is changing, but not its configuration, the component should not be stopped. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-11473) Flow version change in NiFi should not stop a component when only position is changed
[ https://issues.apache.org/jira/browse/NIFI-11473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna reassigned NIFI-11473: -- Assignee: Timea Barna > Flow version change in NiFi should not stop a component when only position is > changed > - > > Key: NIFI-11473 > URL: https://issues.apache.org/jira/browse/NIFI-11473 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > > When going from one flow version to another when the position of a component > is changing, but not its configuration, the component should not be stopped. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11435) NiFi CLI - add possibility to set "Maximum Timer Driven Thread Count"
[ https://issues.apache.org/jira/browse/NIFI-11435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-11435: --- Status: Patch Available (was: In Progress) > NiFi CLI - add possibility to set "Maximum Timer Driven Thread Count" > - > > Key: NIFI-11435 > URL: https://issues.apache.org/jira/browse/NIFI-11435 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > > Add a capability in the NiFi CLI to set the value for "Maximum Timer Driven > Thread Count". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11435) NiFi CLI - add possibility to set "Maximum Timer Driven Thread Count"
Timea Barna created NIFI-11435: -- Summary: NiFi CLI - add possibility to set "Maximum Timer Driven Thread Count" Key: NIFI-11435 URL: https://issues.apache.org/jira/browse/NIFI-11435 Project: Apache NiFi Issue Type: Improvement Reporter: Timea Barna Add a capability in the NiFi CLI to set the value for "Maximum Timer Driven Thread Count". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-11435) NiFi CLI - add possibility to set "Maximum Timer Driven Thread Count"
[ https://issues.apache.org/jira/browse/NIFI-11435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna reassigned NIFI-11435: -- Assignee: Timea Barna > NiFi CLI - add possibility to set "Maximum Timer Driven Thread Count" > - > > Key: NIFI-11435 > URL: https://issues.apache.org/jira/browse/NIFI-11435 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > > Add a capability in the NiFi CLI to set the value for "Maximum Timer Driven > Thread Count". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11385) Expose JMX metrics from NiFi JVM
[ https://issues.apache.org/jira/browse/NIFI-11385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-11385: --- Status: Patch Available (was: In Progress) > Expose JMX metrics from NiFi JVM > > > Key: NIFI-11385 > URL: https://issues.apache.org/jira/browse/NIFI-11385 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Most of the NiFi processors use external libraries which may register JMX > Beans like Kafka processors. Exposing such metrics can help with problem > solving. > The information available depends on the registered Beans and usually related > to performance indicators such as request/response rate, latency, request > size, request counts or tool specific ones like commit rate or sync/join time > for Kafka. > Goals > Have an REST endpoint with a list of JMX Bean attributes. > Expose data in a secure way. > Have some kind of filtering. > Non-Goals > Listing or executing supported operations of JMX Beans. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11385) Expose JMX metrics from NiFi JVM
Timea Barna created NIFI-11385: -- Summary: Expose JMX metrics from NiFi JVM Key: NIFI-11385 URL: https://issues.apache.org/jira/browse/NIFI-11385 Project: Apache NiFi Issue Type: Improvement Reporter: Timea Barna Most of the NiFi processors use external libraries which may register JMX Beans like Kafka processors. Exposing such metrics can help with problem solving. The information available depends on the registered Beans and usually related to performance indicators such as request/response rate, latency, request size, request counts or tool specific ones like commit rate or sync/join time for Kafka. Goals Have an REST endpoint with a list of JMX Bean attributes. Expose data in a secure way. Have some kind of filtering. Non-Goals Listing or executing supported operations of JMX Beans. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-11385) Expose JMX metrics from NiFi JVM
[ https://issues.apache.org/jira/browse/NIFI-11385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna reassigned NIFI-11385: -- Assignee: Timea Barna > Expose JMX metrics from NiFi JVM > > > Key: NIFI-11385 > URL: https://issues.apache.org/jira/browse/NIFI-11385 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > > Most of the NiFi processors use external libraries which may register JMX > Beans like Kafka processors. Exposing such metrics can help with problem > solving. > The information available depends on the registered Beans and usually related > to performance indicators such as request/response rate, latency, request > size, request counts or tool specific ones like commit rate or sync/join time > for Kafka. > Goals > Have an REST endpoint with a list of JMX Bean attributes. > Expose data in a secure way. > Have some kind of filtering. > Non-Goals > Listing or executing supported operations of JMX Beans. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11327) Add Export/Import All - NiFi CLI - NiFi Registry
[ https://issues.apache.org/jira/browse/NIFI-11327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-11327: --- Status: Patch Available (was: In Progress) > Add Export/Import All - NiFi CLI - NiFi Registry > > > Key: NIFI-11327 > URL: https://issues.apache.org/jira/browse/NIFI-11327 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > In NiFi Toolkit, in the CLI, we currently have the following commands > available: > registry list-buckets > registry list-flows > registry list-flow-versions > registry export-flow-version > We should have a command registry export-all-flows that does the following: > List all the buckets, for each bucket, list all flows, for each flow, list > all versions and export each version. All files should be landing in a target > directory provided as an argument of the function. > We also current have the following commands: > registry create-bucket > registry create-flow > registry import-flow-version > We should have a commend registry import-all-flows that does the following: > It takes a directory as input (the one created by the export-all-flows > command), and goes through the files to create the corresponding buckets, > flows and flows versions. > The original author, bucket id and flow id need to be kept. > Use cases: > * use case 1: NiFi 1 -> connecting to NiFi Registry 1, "re-initialising" an > existing NiFi Registry, the NiFi Registry does not change, only its > configuration. > - export everything > - change the NR flow definition repo backend from local FS to database (for > example), or from git to database, etc > - import everything > the existing NiFi instance should not see any change > * use case 2: NiFi 1 -> Registry 1, NiFi 2 -> Registry 2, Disaster Recovery > kind of thing between two different sites. > - export everything from NR1 > - import everything into NR2 > - If the import into NR2 is adding new versions, then NiFi 2 should be able > to update an existing PG to a newer version of the flow. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11327) Add Export/Import All - NiFi CLI - NiFi Registry
[ https://issues.apache.org/jira/browse/NIFI-11327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-11327: --- Description: In NiFi Toolkit, in the CLI, we currently have the following commands available: registry list-buckets registry list-flows registry list-flow-versions registry export-flow-version We should have a command registry export-all-flows that does the following: List all the buckets, for each bucket, list all flows, for each flow, list all versions and export each version. All files should be landing in a target directory provided as an argument of the function. We also current have the following commands: registry create-bucket registry create-flow registry import-flow-version We should have a commend registry import-all-flows that does the following: It takes a directory as input (the one created by the export-all-flows command), and goes through the files to create the corresponding buckets, flows and flows versions. The original author, bucket id and flow id need to be kept. Use cases: * use case 1: NiFi 1 -> connecting to NiFi Registry 1, "re-initialising" an existing NiFi Registry, the NiFi Registry does not change, only its configuration. - export everything - change the NR flow definition repo backend from local FS to database (for example), or from git to database, etc - import everything the existing NiFi instance should not see any change * use case 2: NiFi 1 -> Registry 1, NiFi 2 -> Registry 2, Disaster Recovery kind of thing between two different sites. - export everything from NR1 - import everything into NR2 - If the import into NR2 is adding new versions, then NiFi 2 should be able to update an existing PG to a newer version of the flow. was: In NiFi Toolkit, in the CLI, we currently have the following commands available: registry list-buckets registry list-flows registry list-flow-versions registry export-flow-version We should have a command registry export-all-flows that does the following: List all the buckets, for each bucket, list all flows, for each flow, list all versions and export each version. All files should be landing in a target directory provided as an argument of the function. We also current have the following commands: registry create-bucket registry create-flow registry import-flow-version We should have a commend registry import-all-flows that does the following: It takes a directory as input (the one created by the export-all-flows command), and goes through the files to create the corresponding buckets, flows and flows versions. The original author need to be kept. > Add Export/Import All - NiFi CLI - NiFi Registry > > > Key: NIFI-11327 > URL: https://issues.apache.org/jira/browse/NIFI-11327 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > > In NiFi Toolkit, in the CLI, we currently have the following commands > available: > registry list-buckets > registry list-flows > registry list-flow-versions > registry export-flow-version > We should have a command registry export-all-flows that does the following: > List all the buckets, for each bucket, list all flows, for each flow, list > all versions and export each version. All files should be landing in a target > directory provided as an argument of the function. > We also current have the following commands: > registry create-bucket > registry create-flow > registry import-flow-version > We should have a commend registry import-all-flows that does the following: > It takes a directory as input (the one created by the export-all-flows > command), and goes through the files to create the corresponding buckets, > flows and flows versions. > The original author, bucket id and flow id need to be kept. > Use cases: > * use case 1: NiFi 1 -> connecting to NiFi Registry 1, "re-initialising" an > existing NiFi Registry, the NiFi Registry does not change, only its > configuration. > - export everything > - change the NR flow definition repo backend from local FS to database (for > example), or from git to database, etc > - import everything > the existing NiFi instance should not see any change > * use case 2: NiFi 1 -> Registry 1, NiFi 2 -> Registry 2, Disaster Recovery > kind of thing between two different sites. > - export everything from NR1 > - import everything into NR2 > - If the import into NR2 is adding new versions, then NiFi 2 should be able > to update an existing PG to a newer version of the flow. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11327) Add Export/Import All - NiFi CLI - NiFi Registry
[ https://issues.apache.org/jira/browse/NIFI-11327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-11327: --- Description: In NiFi Toolkit, in the CLI, we currently have the following commands available: registry list-buckets registry list-flows registry list-flow-versions registry export-flow-version We should have a command registry export-all-flows that does the following: List all the buckets, for each bucket, list all flows, for each flow, list all versions and export each version. All files should be landing in a target directory provided as an argument of the function. We also current have the following commands: registry create-bucket registry create-flow registry import-flow-version We should have a commend registry import-all-flows that does the following: It takes a directory as input (the one created by the export-all-flows command), and goes through the files to create the corresponding buckets, flows and flows versions. The original author need to be kept. was: In NiFi Toolkit, in the CLI, we currently have the following commands available: registry list-buckets registry list-flows registry list-flow-versions registry export-flow-version We should have a command registry export-all-flows that does the following: List all the buckets, for each bucket, list all flows, for each flow, list all versions and export each version. All files should be landing in a target directory provided as an argument of the function. We also current have the following commands: registry create-bucket registry create-flow registry import-flow-version We should have a commend registry import-all-flows that does the following: It takes a directory as input (the one created by the export-all-flows command), and goes through the files to create the corresponding buckets, flows and flows versions. The original author and flow id need to be kept. > Add Export/Import All - NiFi CLI - NiFi Registry > > > Key: NIFI-11327 > URL: https://issues.apache.org/jira/browse/NIFI-11327 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > > In NiFi Toolkit, in the CLI, we currently have the following commands > available: > registry list-buckets > registry list-flows > registry list-flow-versions > registry export-flow-version > We should have a command registry export-all-flows that does the following: > List all the buckets, for each bucket, list all flows, for each flow, list > all versions and export each version. All files should be landing in a target > directory provided as an argument of the function. > We also current have the following commands: > registry create-bucket > registry create-flow > registry import-flow-version > We should have a commend registry import-all-flows that does the following: > It takes a directory as input (the one created by the export-all-flows > command), and goes through the files to create the corresponding buckets, > flows and flows versions. > The original author need to be kept. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11327) Add Export/Import All - NiFi CLI - NiFi Registry
Timea Barna created NIFI-11327: -- Summary: Add Export/Import All - NiFi CLI - NiFi Registry Key: NIFI-11327 URL: https://issues.apache.org/jira/browse/NIFI-11327 Project: Apache NiFi Issue Type: Improvement Reporter: Timea Barna Assignee: Timea Barna In NiFi Toolkit, in the CLI, we currently have the following commands available: registry list-buckets registry list-flows registry list-flow-versions registry export-flow-version We should have a command registry export-all-flows that does the following: List all the buckets, for each bucket, list all flows, for each flow, list all versions and export each version. All files should be landing in a target directory provided as an argument of the function. We also current have the following commands: registry create-bucket registry create-flow registry import-flow-version We should have a commend registry import-all-flows that does the following: It takes a directory as input (the one created by the export-all-flows command), and goes through the files to create the corresponding buckets, flows and flows versions. The original author and flow id need to be kept. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11079) Extend QueryNifiReportingTask and ProcessGroup Summary Table
[ https://issues.apache.org/jira/browse/NIFI-11079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-11079: --- Status: Patch Available (was: In Progress) > Extend QueryNifiReportingTask and ProcessGroup Summary Table > > > Key: NIFI-11079 > URL: https://issues.apache.org/jira/browse/NIFI-11079 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Add Total Task Duration and Total Active Thread Count to > QueryNiFiReportingTask and ProcessGroup Summary Table. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11079) Extend QueryNifiReportingTask and ProcessGroup Summary Table
Timea Barna created NIFI-11079: -- Summary: Extend QueryNifiReportingTask and ProcessGroup Summary Table Key: NIFI-11079 URL: https://issues.apache.org/jira/browse/NIFI-11079 Project: Apache NiFi Issue Type: Improvement Reporter: Timea Barna Assignee: Timea Barna Add Total Task Duration and Total Active Thread Count to QueryNiFiReportingTask and ProcessGroup Summary Table. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11044) Script/commands to migrate Kafka processors
[ https://issues.apache.org/jira/browse/NIFI-11044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-11044: --- Status: Patch Available (was: In Progress) > Script/commands to migrate Kafka processors > --- > > Key: NIFI-11044 > URL: https://issues.apache.org/jira/browse/NIFI-11044 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > With NiFi version 1.15.3, Kafka processor versions 0.8, 0.9, 0.10 and 0.11 > were removed. In large flows having many numbers of components it is > challenging to replace these processors manually. A tool should be be created > to help updating a flow in an automated way. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-11044) Script/commands to migrate Kafka processors
[ https://issues.apache.org/jira/browse/NIFI-11044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna reassigned NIFI-11044: -- Assignee: Timea Barna > Script/commands to migrate Kafka processors > --- > > Key: NIFI-11044 > URL: https://issues.apache.org/jira/browse/NIFI-11044 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > > With NiFi version 1.15.3, Kafka processor versions 0.8, 0.9, 0.10 and 0.11 > were removed. In large flows having many numbers of components it is > challenging to replace these processors manually. A tool should be be created > to help updating a flow in an automated way. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11044) Script/commands to migrate Kafka processors
Timea Barna created NIFI-11044: -- Summary: Script/commands to migrate Kafka processors Key: NIFI-11044 URL: https://issues.apache.org/jira/browse/NIFI-11044 Project: Apache NiFi Issue Type: Improvement Reporter: Timea Barna With NiFi version 1.15.3, Kafka processor versions 0.8, 0.9, 0.10 and 0.11 were removed. In large flows having many numbers of components it is challenging to replace these processors manually. A tool should be be created to help updating a flow in an automated way. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-9437) Flowfile Expiration does not exceed 24 days
[ https://issues.apache.org/jira/browse/NIFI-9437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-9437: -- Status: Patch Available (was: In Progress) > Flowfile Expiration does not exceed 24 days > --- > > Key: NIFI-9437 > URL: https://issues.apache.org/jira/browse/NIFI-9437 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Affects Versions: 1.15.0, 1.14.0 >Reporter: Tim Chermak >Assignee: Timea Barna >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > We discovered setting a FlowFile Expiration on a queue for anything over 24 > days is ignored and not 'aged out of the flow". So, if FlowFile Expiration is > set to anything beyond 24 days, the file does not automatically expire and > remains in the queue. > > Can this be fixed so that there is no limit? Also, perhaps the Expiration > setting can have other criteria/strategy for expiring, as indicated in an old > ticket NiFi-372 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-9437) Flowfile Expiration does not exceed 24 days
[ https://issues.apache.org/jira/browse/NIFI-9437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17620789#comment-17620789 ] Timea Barna commented on NIFI-9437: --- Handling expiration related part only, strategy related request will remain open in ticket NIFI-372. > Flowfile Expiration does not exceed 24 days > --- > > Key: NIFI-9437 > URL: https://issues.apache.org/jira/browse/NIFI-9437 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Affects Versions: 1.14.0, 1.15.0 >Reporter: Tim Chermak >Assignee: Timea Barna >Priority: Minor > > We discovered setting a FlowFile Expiration on a queue for anything over 24 > days is ignored and not 'aged out of the flow". So, if FlowFile Expiration is > set to anything beyond 24 days, the file does not automatically expire and > remains in the queue. > > Can this be fixed so that there is no limit? Also, perhaps the Expiration > setting can have other criteria/strategy for expiring, as indicated in an old > ticket NiFi-372 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-9437) Flowfile Expiration does not exceed 24 days
[ https://issues.apache.org/jira/browse/NIFI-9437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna reassigned NIFI-9437: - Assignee: Timea Barna > Flowfile Expiration does not exceed 24 days > --- > > Key: NIFI-9437 > URL: https://issues.apache.org/jira/browse/NIFI-9437 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Affects Versions: 1.14.0, 1.15.0 >Reporter: Tim Chermak >Assignee: Timea Barna >Priority: Minor > > We discovered setting a FlowFile Expiration on a queue for anything over 24 > days is ignored and not 'aged out of the flow". So, if FlowFile Expiration is > set to anything beyond 24 days, the file does not automatically expire and > remains in the queue. > > Can this be fixed so that there is no limit? Also, perhaps the Expiration > setting can have other criteria/strategy for expiring, as indicated in an old > ticket NiFi-372 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-10208) Create Resource Fetcher over HTTPS with Basic Authentication
[ https://issues.apache.org/jira/browse/NIFI-10208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna resolved NIFI-10208. Resolution: Won't Do > Create Resource Fetcher over HTTPS with Basic Authentication > > > Key: NIFI-10208 > URL: https://issues.apache.org/jira/browse/NIFI-10208 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > Create a Resource Fetcher implementation that will download NAR files over > HTTPS with Basic Authentication. > Using a filter, all matching directories/versions would download the > corresponding NARs. > Response will be HTML, no other format is expected at the moment. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-10208) Create Resource Fetcher over HTTPS with Basic Authentication
[ https://issues.apache.org/jira/browse/NIFI-10208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-10208: --- Status: Open (was: Patch Available) > Create Resource Fetcher over HTTPS with Basic Authentication > > > Key: NIFI-10208 > URL: https://issues.apache.org/jira/browse/NIFI-10208 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > Create a Resource Fetcher implementation that will download NAR files over > HTTPS with Basic Authentication. > Using a filter, all matching directories/versions would download the > corresponding NARs. > Response will be HTML, no other format is expected at the moment. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-10256) CSVRecordReader using RFC 4180 CSV format trimming starting and ending double quotes
[
https://issues.apache.org/jira/browse/NIFI-10256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timea Barna updated NIFI-10256:
---
Status: Patch Available (was: In Progress)
> CSVRecordReader using RFC 4180 CSV format trimming starting and ending double
> quotes
>
>
> Key: NIFI-10256
> URL: https://issues.apache.org/jira/browse/NIFI-10256
> Project: Apache NiFi
> Issue Type: Bug
>Reporter: Timea Barna
>Assignee: Timea Barna
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Given an input CSV file:
> scenario,name
> Honors escape beginning," ""John ""PA""RKINSON"""
> problematic,"""John ""PA""RKINSON"""
> honors escape end,"""John ""PA""RKINSON"
> Based on the RFC 4180 spec:
> https://datatracker.ietf.org/doc/html/rfc4180
> " If double-quotes are used to enclose fields, then a double-quote
> appearing inside a field must be escaped by preceding it with
> another double quote. For example:
> "aaa","b""bb","ccc"
> "
> The output should be like this:
> [
> { "scenario" : "expected_with_space", "name" : " \"John \"PA\"RKINSON\"" }
> ,
> { "scenario" : "problematic", "name" : "\"John \"PA\"RKINSON\"" }
> ,
> { "scenario" : "expected_remove_end_quote", "name" : "\"John \"PA\"RKINSON" }
> ]
> However the output is like this"
> [
> { "scenario" : "expected_with_space", "name" : " \"John \"PA\"RKINSON\"" }
> ,
> { "scenario" : "problematic", "name" : "John \"PA\"RKINSON" }
> ,
> { "scenario" : "expected_remove_end_quote", "name" : "\"John \"PA\"RKINSON" }
> ]
> Notice the "problematic" field which initially is """John ""PA""RKINSON"""
> and based on the RFC spec it should have returned this value "\"John
> \"PA\"RKINSON\"" but instead it returns "John \"PA\"RKINSON" missing the
> staring and ending double quotes.
> Notice that the other 2 fields expected_remove_end_quote and
> expected_with_space do work as expected given the RFC spec.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-10256) CSVRecordReader using RFC 4180 CSV format trimming starting and ending double quotes
[
https://issues.apache.org/jira/browse/NIFI-10256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timea Barna updated NIFI-10256:
---
Description:
Given an input CSV file:
scenario,name
Honors escape beginning," ""John ""PA""RKINSON"""
problematic,"""John ""PA""RKINSON"""
honors escape end,"""John ""PA""RKINSON"
Based on the RFC 4180 spec:
https://datatracker.ietf.org/doc/html/rfc4180
" If double-quotes are used to enclose fields, then a double-quote
appearing inside a field must be escaped by preceding it with
another double quote. For example:
"aaa","b""bb","ccc"
"
The output should be like this:
[
{ "scenario" : "expected_with_space", "name" : " \"John \"PA\"RKINSON\"" }
,
{ "scenario" : "problematic", "name" : "\"John \"PA\"RKINSON\"" }
,
{ "scenario" : "expected_remove_end_quote", "name" : "\"John \"PA\"RKINSON" }
]
However the output is like this"
[
{ "scenario" : "expected_with_space", "name" : " \"John \"PA\"RKINSON\"" }
,
{ "scenario" : "problematic", "name" : "John \"PA\"RKINSON" }
,
{ "scenario" : "expected_remove_end_quote", "name" : "\"John \"PA\"RKINSON" }
]
Notice the "problematic" field which initially is """John ""PA""RKINSON""" and
based on the RFC spec it should have returned this value "\"John
\"PA\"RKINSON\"" but instead it returns "John \"PA\"RKINSON" missing the
staring and ending double quotes.
Notice that the other 2 fields expected_remove_end_quote and
expected_with_space do work as expected given the RFC spec.
> CSVRecordReader using RFC 4180 CSV format trimming starting and ending double
> quotes
>
>
> Key: NIFI-10256
> URL: https://issues.apache.org/jira/browse/NIFI-10256
> Project: Apache NiFi
> Issue Type: Bug
>Reporter: Timea Barna
>Assignee: Timea Barna
>Priority: Major
>
> Given an input CSV file:
> scenario,name
> Honors escape beginning," ""John ""PA""RKINSON"""
> problematic,"""John ""PA""RKINSON"""
> honors escape end,"""John ""PA""RKINSON"
> Based on the RFC 4180 spec:
> https://datatracker.ietf.org/doc/html/rfc4180
> " If double-quotes are used to enclose fields, then a double-quote
> appearing inside a field must be escaped by preceding it with
> another double quote. For example:
> "aaa","b""bb","ccc"
> "
> The output should be like this:
> [
> { "scenario" : "expected_with_space", "name" : " \"John \"PA\"RKINSON\"" }
> ,
> { "scenario" : "problematic", "name" : "\"John \"PA\"RKINSON\"" }
> ,
> { "scenario" : "expected_remove_end_quote", "name" : "\"John \"PA\"RKINSON" }
> ]
> However the output is like this"
> [
> { "scenario" : "expected_with_space", "name" : " \"John \"PA\"RKINSON\"" }
> ,
> { "scenario" : "problematic", "name" : "John \"PA\"RKINSON" }
> ,
> { "scenario" : "expected_remove_end_quote", "name" : "\"John \"PA\"RKINSON" }
> ]
> Notice the "problematic" field which initially is """John ""PA""RKINSON"""
> and based on the RFC spec it should have returned this value "\"John
> \"PA\"RKINSON\"" but instead it returns "John \"PA\"RKINSON" missing the
> staring and ending double quotes.
> Notice that the other 2 fields expected_remove_end_quote and
> expected_with_space do work as expected given the RFC spec.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (NIFI-10256) CSVRecordReader using RFC 4180 CSV format trimming starting and ending double quotes
Timea Barna created NIFI-10256: -- Summary: CSVRecordReader using RFC 4180 CSV format trimming starting and ending double quotes Key: NIFI-10256 URL: https://issues.apache.org/jira/browse/NIFI-10256 Project: Apache NiFi Issue Type: Bug Reporter: Timea Barna -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-10256) CSVRecordReader using RFC 4180 CSV format trimming starting and ending double quotes
[ https://issues.apache.org/jira/browse/NIFI-10256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna reassigned NIFI-10256: -- Assignee: Timea Barna > CSVRecordReader using RFC 4180 CSV format trimming starting and ending double > quotes > > > Key: NIFI-10256 > URL: https://issues.apache.org/jira/browse/NIFI-10256 > Project: Apache NiFi > Issue Type: Bug >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-10208) Create Resource Fetcher over HTTPS with Basic Authentication
[ https://issues.apache.org/jira/browse/NIFI-10208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-10208: --- Status: Patch Available (was: In Progress) > Create Resource Fetcher over HTTPS with Basic Authentication > > > Key: NIFI-10208 > URL: https://issues.apache.org/jira/browse/NIFI-10208 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Create a Resource Fetcher implementation that will download NAR files over > HTTPS with Basic Authentication. > Using a filter, all matching directories/versions would download the > corresponding NARs. > Response will be HTML, no other format is expected at the moment. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-10208) Create Resource Fetcher over HTTPS with Basic Authentication
[ https://issues.apache.org/jira/browse/NIFI-10208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-10208: --- Description: Create a Resource Fetcher implementation that will download NAR files over HTTPS with Basic Authentication. Using a filter, all matching directories/versions would download the corresponding NARs. Response will be HTML, no other format is expected at the moment. > Create Resource Fetcher over HTTPS with Basic Authentication > > > Key: NIFI-10208 > URL: https://issues.apache.org/jira/browse/NIFI-10208 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Priority: Major > > Create a Resource Fetcher implementation that will download NAR files over > HTTPS with Basic Authentication. > Using a filter, all matching directories/versions would download the > corresponding NARs. > Response will be HTML, no other format is expected at the moment. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-10208) Create Resource Fetcher over HTTPS with Basic Authentication
[ https://issues.apache.org/jira/browse/NIFI-10208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna reassigned NIFI-10208: -- Assignee: Timea Barna > Create Resource Fetcher over HTTPS with Basic Authentication > > > Key: NIFI-10208 > URL: https://issues.apache.org/jira/browse/NIFI-10208 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > > Create a Resource Fetcher implementation that will download NAR files over > HTTPS with Basic Authentication. > Using a filter, all matching directories/versions would download the > corresponding NARs. > Response will be HTML, no other format is expected at the moment. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-10208) Create Resource Fetcher over HTTPS with Basic Authentication
Timea Barna created NIFI-10208: -- Summary: Create Resource Fetcher over HTTPS with Basic Authentication Key: NIFI-10208 URL: https://issues.apache.org/jira/browse/NIFI-10208 Project: Apache NiFi Issue Type: Improvement Reporter: Timea Barna -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-10108) Processor scheduling via parameter
[ https://issues.apache.org/jira/browse/NIFI-10108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-10108: --- Status: Patch Available (was: In Progress) > Processor scheduling via parameter > -- > > Key: NIFI-10108 > URL: https://issues.apache.org/jira/browse/NIFI-10108 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > For example a generic flow (extracting data from a table) should run for > table A every hour in environment A but for table B every day in another > environment. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (NIFI-10108) Processor scheduling via parameter
[ https://issues.apache.org/jira/browse/NIFI-10108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna reassigned NIFI-10108: -- Assignee: Timea Barna > Processor scheduling via parameter > -- > > Key: NIFI-10108 > URL: https://issues.apache.org/jira/browse/NIFI-10108 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (NIFI-10108) Processor scheduling via parameter
Timea Barna created NIFI-10108: -- Summary: Processor scheduling via parameter Key: NIFI-10108 URL: https://issues.apache.org/jira/browse/NIFI-10108 Project: Apache NiFi Issue Type: Improvement Reporter: Timea Barna -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (NIFI-10108) Processor scheduling via parameter
[ https://issues.apache.org/jira/browse/NIFI-10108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-10108: --- Description: For example a generic flow (extracting data from a table) should run for table A every hour in environment A but for table B every day in another environment. > Processor scheduling via parameter > -- > > Key: NIFI-10108 > URL: https://issues.apache.org/jira/browse/NIFI-10108 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > > For example a generic flow (extracting data from a table) should run for > table A every hour in environment A but for table B every day in another > environment. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Comment Edited] (NIFI-9475) Provide Framework-Level Retries for NiFi Relationships
[ https://issues.apache.org/jira/browse/NIFI-9475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17544245#comment-17544245 ] Timea Barna edited comment on NIFI-9475 at 5/31/22 9:03 AM: Hello [~mkapkiai], >From the NiFi framework point of view 'success' is just the name of the >relationship. The framework itself has no information about the intended use >of a relationship. So the retry framework handles every relationship equally >this is why retry can be set on a 'success' relationship. was (Author: timeabarna): Hello [~mkapkiai], >From the NiFi framework point of view 'success' is just the name of the >relationship. The framework itself has no information about the intended use >of a relationship. So the framework handles every relationship equally this is >why retry can be set on a 'success' relationship. > Provide Framework-Level Retries for NiFi Relationships > -- > > Key: NIFI-9475 > URL: https://issues.apache.org/jira/browse/NIFI-9475 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > Fix For: 1.16.0 > > Attachments: image-2022-05-17-09-27-33-222.png > > Time Spent: 2.5h > Remaining Estimate: 0h > > For a processor that routes to failure, in NiFi I have 3 options: > 1) Loop 'failure' back to the processor and retry forever > 2) Auto-terminate or route the data elsewhere without any retries > 3) Build a complex retry loop that creates or updates an attribute, routes on > that attribute to determine whether or not we've exceeded the maximum number > of retries, and if not penalizes the FlowFile (typically with a Script > processor) and then routes back to try the FlowFile again. > This provides a poor user experience and poor performance and results in very > complex flows that are difficult to understand and maintain. > As a user, when I configure a Processor, I should be able to indicate that > for Relationship ABC, I want to retry the FlowFile 5 times. Then, if the > Processor transfers a FlowFile to that relationship, it should instead > transfer the FlowFile back to its original queue and increment the transfer > count for that relationship from 0 to 1 and penalize the FlowFile. If the > Processor processes it again and transfers it to the same Relationship again, > it'll again put it back to the original queue and increment the count to 2. > Only when the data is routed to that Relationship 5 times (because that's the > configured retry count in this example) should the FlowFile actually be > transferred to that corresponding connection(s) or auto-terminated, as the > flow is configured. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (NIFI-9475) Provide Framework-Level Retries for NiFi Relationships
[ https://issues.apache.org/jira/browse/NIFI-9475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17544245#comment-17544245 ] Timea Barna commented on NIFI-9475: --- Hello [~mkapkiai], >From the NiFi framework point of view 'success' is just the name of the >relationship. The framework itself has no information about the intended use >of a relationship. So the framework handles every relationship equally this is >why retry can be set on a 'success' relationship. > Provide Framework-Level Retries for NiFi Relationships > -- > > Key: NIFI-9475 > URL: https://issues.apache.org/jira/browse/NIFI-9475 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > Fix For: 1.16.0 > > Attachments: image-2022-05-17-09-27-33-222.png > > Time Spent: 2.5h > Remaining Estimate: 0h > > For a processor that routes to failure, in NiFi I have 3 options: > 1) Loop 'failure' back to the processor and retry forever > 2) Auto-terminate or route the data elsewhere without any retries > 3) Build a complex retry loop that creates or updates an attribute, routes on > that attribute to determine whether or not we've exceeded the maximum number > of retries, and if not penalizes the FlowFile (typically with a Script > processor) and then routes back to try the FlowFile again. > This provides a poor user experience and poor performance and results in very > complex flows that are difficult to understand and maintain. > As a user, when I configure a Processor, I should be able to indicate that > for Relationship ABC, I want to retry the FlowFile 5 times. Then, if the > Processor transfers a FlowFile to that relationship, it should instead > transfer the FlowFile back to its original queue and increment the transfer > count for that relationship from 0 to 1 and penalize the FlowFile. If the > Processor processes it again and transfers it to the same Relationship again, > it'll again put it back to the original queue and increment the count to 2. > Only when the data is routed to that Relationship 5 times (because that's the > configured retry count in this example) should the FlowFile actually be > transferred to that corresponding connection(s) or auto-terminated, as the > flow is configured. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (NIFI-9879) Add min/max age and min/max size properties to ListAzure processors
[ https://issues.apache.org/jira/browse/NIFI-9879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-9879: -- Status: Patch Available (was: In Progress) > Add min/max age and min/max size properties to ListAzure processors > --- > > Key: NIFI-9879 > URL: https://issues.apache.org/jira/browse/NIFI-9879 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > > Add min/max age and min/max size properties to ListAzure processors -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9879) Add min/max age and min/max size properties to ListAzure processors
[ https://issues.apache.org/jira/browse/NIFI-9879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-9879: -- Description: Add min/max age and min/max size properties to ListAzure processors > Add min/max age and min/max size properties to ListAzure processors > --- > > Key: NIFI-9879 > URL: https://issues.apache.org/jira/browse/NIFI-9879 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Priority: Major > > Add min/max age and min/max size properties to ListAzure processors -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (NIFI-9879) Add min/max age and min/max size properties to ListAzure processors
[ https://issues.apache.org/jira/browse/NIFI-9879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna reassigned NIFI-9879: - Assignee: Timea Barna > Add min/max age and min/max size properties to ListAzure processors > --- > > Key: NIFI-9879 > URL: https://issues.apache.org/jira/browse/NIFI-9879 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > > Add min/max age and min/max size properties to ListAzure processors -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (NIFI-9879) Add min/max age and min/max size properties to ListAzure processors
Timea Barna created NIFI-9879: - Summary: Add min/max age and min/max size properties to ListAzure processors Key: NIFI-9879 URL: https://issues.apache.org/jira/browse/NIFI-9879 Project: Apache NiFi Issue Type: Improvement Reporter: Timea Barna -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9846) Implement pagination listing for Azure List processors
[ https://issues.apache.org/jira/browse/NIFI-9846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-9846: -- Status: Patch Available (was: In Progress) > Implement pagination listing for Azure List processors > -- > > Key: NIFI-9846 > URL: https://issues.apache.org/jira/browse/NIFI-9846 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > If listing a huge azure blob it could make the NiFi JVM go OOM depending on > JVM size. > To enable some kind of batching, listing requests needs to use pagination. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9846) Implement pagination listing for Azure List processors
[ https://issues.apache.org/jira/browse/NIFI-9846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-9846: -- Description: If listing a huge azure blob it could make the NiFi JVM go OOM depending on JVM size. To enable some kind of batching, listing requests needs to use pagination. was: If listing a huge azure blob it could make the NiFi JVM go OOM depending on JVM size. For instance screenshot attached ListAzureBlob is generating OOM since their blob storage is huge. To enable some kind of batching, listing requests needs to use pagination. > Implement pagination listing for Azure List processors > -- > > Key: NIFI-9846 > URL: https://issues.apache.org/jira/browse/NIFI-9846 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > > If listing a huge azure blob it could make the NiFi JVM go OOM depending on > JVM size. > To enable some kind of batching, listing requests needs to use pagination. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9846) Implement pagination listing for Azure List processors
[ https://issues.apache.org/jira/browse/NIFI-9846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-9846: -- Description: If listing a huge azure blob it could make the NiFi JVM go OOM depending on JVM size. For instance screenshot attached ListAzureBlob is generating OOM since their blob storage is huge. To enable some kind of batching, listing requests needs to use pagination. was: If listing a huge azure blob it could make the NiFi JVM go OOM depending on JVM size. For instance screenshot attached ListAzureBlob is generating OOM since their blob storage is huge. Mark suggested I make this JIRA to improve this behavior by setting a "batch size" To enable some kind of paging listing requests needs to use pagination. > Implement pagination listing for Azure List processors > -- > > Key: NIFI-9846 > URL: https://issues.apache.org/jira/browse/NIFI-9846 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > > If listing a huge azure blob it could make the NiFi JVM go OOM depending on > JVM size. > For instance screenshot attached ListAzureBlob is generating OOM since their > blob storage is huge. > To enable some kind of batching, listing requests needs to use pagination. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9846) Implement pagination listing for Azure List processors
[ https://issues.apache.org/jira/browse/NIFI-9846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-9846: -- Description: If listing a huge azure blob it could make the NiFi JVM go OOM depending on JVM size. For instance screenshot attached ListAzureBlob is generating OOM since their blob storage is huge. Mark suggested I make this JIRA to improve this behavior by setting a "batch size" To enable some kind of paging listing requests needs to use pagination. > Implement pagination listing for Azure List processors > -- > > Key: NIFI-9846 > URL: https://issues.apache.org/jira/browse/NIFI-9846 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > > If listing a huge azure blob it could make the NiFi JVM go OOM depending on > JVM size. > For instance screenshot attached ListAzureBlob is generating OOM since their > blob storage is huge. > Mark suggested I make this JIRA to improve this behavior by setting a "batch > size" > To enable some kind of paging listing requests needs to use pagination. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (NIFI-9846) Implement pagination listing for Azure List processors
Timea Barna created NIFI-9846: - Summary: Implement pagination listing for Azure List processors Key: NIFI-9846 URL: https://issues.apache.org/jira/browse/NIFI-9846 Project: Apache NiFi Issue Type: Improvement Reporter: Timea Barna Assignee: Timea Barna -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9657) Create MoveADLS processor
[ https://issues.apache.org/jira/browse/NIFI-9657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-9657: -- Status: Patch Available (was: In Progress) > Create MoveADLS processor > - > > Key: NIFI-9657 > URL: https://issues.apache.org/jira/browse/NIFI-9657 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Similarly to List/Fetch/Put ADLS processors we already have, we need to > create a MoveADLS processor (similar to MoveHDFS) so data can be moved from > one location to another. Right now data has to be fetched and then to be > pushed which is highly inefficient. > ListADLS -> MoveADLS > The ListADLS would list the files within a file system / directory > and the MoveADLS would give the option to specify the destination where the > file should be moved. Files will be no longer available on source location. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (NIFI-9657) Create MoveADLS processor
[ https://issues.apache.org/jira/browse/NIFI-9657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna reassigned NIFI-9657: - Assignee: Timea Barna > Create MoveADLS processor > - > > Key: NIFI-9657 > URL: https://issues.apache.org/jira/browse/NIFI-9657 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > > Similarly to List/Fetch/Put ADLS processors we already have, we need to > create a MoveADLS processor (similar to MoveHDFS) so data can be moved from > one location to another. Right now data has to be fetched and then to be > pushed which is highly inefficient. > ListADLS -> MoveADLS > The ListADLS would list the files within a file system / directory > and the MoveADLS would give the option to specify the destination where the > file should be moved. Files will be no longer available on source location. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (NIFI-9657) Create MoveADLS processor
Timea Barna created NIFI-9657: - Summary: Create MoveADLS processor Key: NIFI-9657 URL: https://issues.apache.org/jira/browse/NIFI-9657 Project: Apache NiFi Issue Type: Improvement Reporter: Timea Barna Similarly to List/Fetch/Put ADLS processors we already have, we need to create a MoveADLS processor (similar to MoveHDFS) so data can be moved from one location to another. Right now data has to be fetched and then to be pushed which is highly inefficient. ListADLS -> MoveADLS The ListADLS would list the files within a file system / directory and the MoveADLS would give the option to specify the destination where the file should be moved. Files will be no longer available on source location. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9455) Add aggregated predictions to Prometheus
[ https://issues.apache.org/jira/browse/NIFI-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-9455: -- Description: Add aggregated prediction metrics to Prometheus (was: Add json output format endpoint for Prometheus metrics Add a basic filtering option for the json output ) > Add aggregated predictions to Prometheus > > > Key: NIFI-9455 > URL: https://issues.apache.org/jira/browse/NIFI-9455 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > Add aggregated prediction metrics to Prometheus -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (NIFI-9587) Add json output for Prometheus metrics
[ https://issues.apache.org/jira/browse/NIFI-9587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna reassigned NIFI-9587: - Assignee: Timea Barna > Add json output for Prometheus metrics > -- > > Key: NIFI-9587 > URL: https://issues.apache.org/jira/browse/NIFI-9587 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Add json output format endpoint for Prometheus metrics > Add a basic filtering option for the json output -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9587) Add json output for Prometheus metrics
[ https://issues.apache.org/jira/browse/NIFI-9587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-9587: -- Status: Patch Available (was: In Progress) > Add json output for Prometheus metrics > -- > > Key: NIFI-9587 > URL: https://issues.apache.org/jira/browse/NIFI-9587 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Add json output format endpoint for Prometheus metrics > Add a basic filtering option for the json output -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9455) Add aggregated predictions to Prometheus
[ https://issues.apache.org/jira/browse/NIFI-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-9455: -- Summary: Add aggregated predictions to Prometheus (was: Add json output for Prometheus metrics) > Add aggregated predictions to Prometheus > > > Key: NIFI-9455 > URL: https://issues.apache.org/jira/browse/NIFI-9455 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Add json output format endpoint for Prometheus metrics > Add a basic filtering option for the json output -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9587) Add json output for Prometheus metrics
[ https://issues.apache.org/jira/browse/NIFI-9587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-9587: -- Description: Add json output format endpoint for Prometheus metrics Add a basic filtering option for the json output was:Add aggregated prediction metrics to Prometheus > Add json output for Prometheus metrics > -- > > Key: NIFI-9587 > URL: https://issues.apache.org/jira/browse/NIFI-9587 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Priority: Major > > Add json output format endpoint for Prometheus metrics > Add a basic filtering option for the json output -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9587) Add json output for Prometheus metrics
[ https://issues.apache.org/jira/browse/NIFI-9587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-9587: -- Summary: Add json output for Prometheus metrics (was: Add aggregated predictions to Prometheus) > Add json output for Prometheus metrics > -- > > Key: NIFI-9587 > URL: https://issues.apache.org/jira/browse/NIFI-9587 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Priority: Major > > Add aggregated prediction metrics to Prometheus -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9587) Add aggregated predictions to Prometheus
[ https://issues.apache.org/jira/browse/NIFI-9587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-9587: -- Description: Add aggregated prediction metrics to Prometheus > Add aggregated predictions to Prometheus > > > Key: NIFI-9587 > URL: https://issues.apache.org/jira/browse/NIFI-9587 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Priority: Major > > Add aggregated prediction metrics to Prometheus -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9455) Add json output for Prometheus metrics
[ https://issues.apache.org/jira/browse/NIFI-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-9455: -- Description: Add json output format endpoint for Prometheus metrics Add a basic filtering option for the json output was: Add json output format endpoint for Prometheus metrics Add a basic filtering option for the json output Add aggregated prediction metrics to Prometheus > Add json output for Prometheus metrics > -- > > Key: NIFI-9455 > URL: https://issues.apache.org/jira/browse/NIFI-9455 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Add json output format endpoint for Prometheus metrics > Add a basic filtering option for the json output -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9455) Add json output for Prometheus metrics
[ https://issues.apache.org/jira/browse/NIFI-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-9455: -- Summary: Add json output for Prometheus metrics (was: Add json output for Prometheus metrics and aggregated predictions) > Add json output for Prometheus metrics > -- > > Key: NIFI-9455 > URL: https://issues.apache.org/jira/browse/NIFI-9455 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Add json output format endpoint for Prometheus metrics > Add a basic filtering option for the json output > Add aggregated prediction metrics to Prometheus -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (NIFI-9587) Add aggregated predictions to Prometheus
Timea Barna created NIFI-9587: - Summary: Add aggregated predictions to Prometheus Key: NIFI-9587 URL: https://issues.apache.org/jira/browse/NIFI-9587 Project: Apache NiFi Issue Type: Improvement Reporter: Timea Barna -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9578) The Nifi User List in the UI will not populate if they are syncing a username and a group name that are the same
[ https://issues.apache.org/jira/browse/NIFI-9578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-9578: -- Description: The Nifi User List in the UI will not populate if they are syncing a username and a group name that are the same Recreation Steps: I have a user name 'kevin' I created a group named 'kevin' When I open Nifi, the user list is blank and when I check the browser console, I see the error: slick.dataview.js:191 Uncaught Error: [SlickGrid DataView] Each data element must implement a unique 'id' property Nifi uses a combined user list even though they come from different endpoints /tenant The UI only support searching for users so the 'id' (identity fields within the response json) will match which will throw the error because the code expects the id fields to be unique Reproduced in 1.13.2 was: The Nifi User List in the UI will not populate if they are syncing a username and a group name that are the same Recreation Steps: I have a user name 'kevin' I created a group named 'kevin' When I open Nifi, the user list is blank and when I check the browser console, I see the error: slick.dataview.js:191 Uncaught Error: [SlickGrid DataView] Each data element must implement a unique 'id' property Nifi uses a combined user list even though they come from different endpoints /tenant The UI only support searching for users so the 'id' (identity fields within the response json) will match which will throw the error because the code expects the id fields to be unique > The Nifi User List in the UI will not populate if they are syncing a username > and a group name that are the same > > > Key: NIFI-9578 > URL: https://issues.apache.org/jira/browse/NIFI-9578 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.13.2 >Reporter: Timea Barna >Priority: Major > > The Nifi User List in the UI will not populate if they are syncing a username > and a group name that are the same > Recreation Steps: > I have a user name 'kevin' > I created a group named 'kevin' > When I open Nifi, the user list is blank and when I check the browser > console, I see the error: > slick.dataview.js:191 Uncaught Error: [SlickGrid DataView] Each data element > must implement a unique 'id' property > Nifi uses a combined user list even though they come from different endpoints > /tenant > The UI only support searching for users so the 'id' (identity fields within > the response json) will match which will throw the error because the code > expects the id fields to be unique > Reproduced in 1.13.2 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9578) The Nifi User List in the UI will not populate if they are syncing a username and a group name that are the same
[ https://issues.apache.org/jira/browse/NIFI-9578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-9578: -- Affects Version/s: 1.13.2 > The Nifi User List in the UI will not populate if they are syncing a username > and a group name that are the same > > > Key: NIFI-9578 > URL: https://issues.apache.org/jira/browse/NIFI-9578 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.13.2 >Reporter: Timea Barna >Priority: Major > > The Nifi User List in the UI will not populate if they are syncing a username > and a group name that are the same > Recreation Steps: > I have a user name 'kevin' > I created a group named 'kevin' > When I open Nifi, the user list is blank and when I check the browser > console, I see the error: > slick.dataview.js:191 Uncaught Error: [SlickGrid DataView] Each data element > must implement a unique 'id' property > Nifi uses a combined user list even though they come from different endpoints > /tenant > The UI only support searching for users so the 'id' (identity fields within > the response json) will match which will throw the error because the code > expects the id fields to be unique -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9578) The Nifi User List in the UI will not populate if they are syncing a username and a group name that are the same
[ https://issues.apache.org/jira/browse/NIFI-9578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-9578: -- Description: The Nifi User List in the UI will not populate if they are syncing a username and a group name that are the same Recreation Steps: I have a user name 'kevin' I created a group named 'kevin' When I open Nifi, the user list is blank and when I check the browser console, I see the error: slick.dataview.js:191 Uncaught Error: [SlickGrid DataView] Each data element must implement a unique 'id' property Nifi uses a combined user list even though they come from different endpoints /tenant The UI only support searching for users so the 'id' (identity fields within the response json) will match which will throw the error because the code expects the id fields to be unique was: The Nifi User List in the UI will not populate if they are syncing a username and a group name that are the same Recreation Steps: I have a user name 'kevin' I created a group named 'kevin' When I open Nifi, the user list is blank and when I check the browser console, I see the error: slick.dataview.js:191 Uncaught Error: [SlickGrid DataView] Each data element must implement a unique 'id' property Nifi uses a combined user list even though they come from different endpoints /tenant The UI only support searching for users so the 'id' (identity fields within the response json) will match which will throw the error because the code expects the id fields to be unique Recreated in CFM 2.1.2.5-1 > The Nifi User List in the UI will not populate if they are syncing a username > and a group name that are the same > > > Key: NIFI-9578 > URL: https://issues.apache.org/jira/browse/NIFI-9578 > Project: Apache NiFi > Issue Type: Bug >Reporter: Timea Barna >Priority: Major > > The Nifi User List in the UI will not populate if they are syncing a username > and a group name that are the same > Recreation Steps: > I have a user name 'kevin' > I created a group named 'kevin' > When I open Nifi, the user list is blank and when I check the browser > console, I see the error: > slick.dataview.js:191 Uncaught Error: [SlickGrid DataView] Each data element > must implement a unique 'id' property > Nifi uses a combined user list even though they come from different endpoints > /tenant > The UI only support searching for users so the 'id' (identity fields within > the response json) will match which will throw the error because the code > expects the id fields to be unique -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9578) The Nifi User List in the UI will not populate if they are syncing a username and a group name that are the same
[ https://issues.apache.org/jira/browse/NIFI-9578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-9578: -- Description: The Nifi User List in the UI will not populate if they are syncing a username and a group name that are the same Recreation Steps: I have a user name 'kevin' I created a group named 'kevin' When I open Nifi, the user list is blank and when I check the browser console, I see the error: slick.dataview.js:191 Uncaught Error: [SlickGrid DataView] Each data element must implement a unique 'id' property Nifi uses a combined user list even though they come from different endpoints /tenant The UI only support searching for users so the 'id' (identity fields within the response json) will match which will throw the error because the code expects the id fields to be unique Recreated in CFM 2.1.2.5-1 > The Nifi User List in the UI will not populate if they are syncing a username > and a group name that are the same > > > Key: NIFI-9578 > URL: https://issues.apache.org/jira/browse/NIFI-9578 > Project: Apache NiFi > Issue Type: Bug >Reporter: Timea Barna >Priority: Major > > The Nifi User List in the UI will not populate if they are syncing a username > and a group name that are the same > Recreation Steps: > I have a user name 'kevin' > I created a group named 'kevin' > When I open Nifi, the user list is blank and when I check the browser > console, I see the error: > slick.dataview.js:191 Uncaught Error: [SlickGrid DataView] Each data element > must implement a unique 'id' property > Nifi uses a combined user list even though they come from different endpoints > /tenant > The UI only support searching for users so the 'id' (identity fields within > the response json) will match which will throw the error because the code > expects the id fields to be unique > Recreated in CFM 2.1.2.5-1 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (NIFI-9578) The Nifi User List in the UI will not populate if they are syncing a username and a group name that are the same
Timea Barna created NIFI-9578: - Summary: The Nifi User List in the UI will not populate if they are syncing a username and a group name that are the same Key: NIFI-9578 URL: https://issues.apache.org/jira/browse/NIFI-9578 Project: Apache NiFi Issue Type: Bug Reporter: Timea Barna -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9475) Provide Framework-Level Retries for NiFi Relationships
[ https://issues.apache.org/jira/browse/NIFI-9475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-9475: -- Description: For a processor that routes to failure, in NiFi I have 3 options: 1) Loop 'failure' back to the processor and retry forever 2) Auto-terminate or route the data elsewhere without any retries 3) Build a complex retry loop that creates or updates an attribute, routes on that attribute to determine whether or not we've exceeded the maximum number of retries, and if not penalizes the FlowFile (typically with a Script processor) and then routes back to try the FlowFile again. This provides a poor user experience and poor performance and results in very complex flows that are difficult to understand and maintain. As a user, when I configure a Processor, I should be able to indicate that for Relationship ABC, I want to retry the FlowFile 5 times. Then, if the Processor transfers a FlowFile to that relationship, it should instead transfer the FlowFile back to its original queue and increment the transfer count for that relationship from 0 to 1 and penalize the FlowFile. If the Processor processes it again and transfers it to the same Relationship again, it'll again put it back to the original queue and increment the count to 2. Only when the data is routed to that Relationship 5 times (because that's the configured retry count in this example) should the FlowFile actually be transferred to that corresponding connection(s) or auto-terminated, as the flow is configured. > Provide Framework-Level Retries for NiFi Relationships > -- > > Key: NIFI-9475 > URL: https://issues.apache.org/jira/browse/NIFI-9475 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > > For a processor that routes to failure, in NiFi I have 3 options: > 1) Loop 'failure' back to the processor and retry forever > 2) Auto-terminate or route the data elsewhere without any retries > 3) Build a complex retry loop that creates or updates an attribute, routes on > that attribute to determine whether or not we've exceeded the maximum number > of retries, and if not penalizes the FlowFile (typically with a Script > processor) and then routes back to try the FlowFile again. > This provides a poor user experience and poor performance and results in very > complex flows that are difficult to understand and maintain. > As a user, when I configure a Processor, I should be able to indicate that > for Relationship ABC, I want to retry the FlowFile 5 times. Then, if the > Processor transfers a FlowFile to that relationship, it should instead > transfer the FlowFile back to its original queue and increment the transfer > count for that relationship from 0 to 1 and penalize the FlowFile. If the > Processor processes it again and transfers it to the same Relationship again, > it'll again put it back to the original queue and increment the count to 2. > Only when the data is routed to that Relationship 5 times (because that's the > configured retry count in this example) should the FlowFile actually be > transferred to that corresponding connection(s) or auto-terminated, as the > flow is configured. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (NIFI-9475) Provide Framework-Level Retries for NiFi Relationships
[ https://issues.apache.org/jira/browse/NIFI-9475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna reassigned NIFI-9475: - Assignee: Timea Barna > Provide Framework-Level Retries for NiFi Relationships > -- > > Key: NIFI-9475 > URL: https://issues.apache.org/jira/browse/NIFI-9475 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (NIFI-9475) Provide Framework-Level Retries for NiFi Relationships
Timea Barna created NIFI-9475: - Summary: Provide Framework-Level Retries for NiFi Relationships Key: NIFI-9475 URL: https://issues.apache.org/jira/browse/NIFI-9475 Project: Apache NiFi Issue Type: Improvement Reporter: Timea Barna -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9455) Add json output for Prometheus metrics and aggregated predictions
[ https://issues.apache.org/jira/browse/NIFI-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-9455: -- Status: Patch Available (was: In Progress) > Add json output for Prometheus metrics and aggregated predictions > - > > Key: NIFI-9455 > URL: https://issues.apache.org/jira/browse/NIFI-9455 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Add json output format endpoint for Prometheus metrics > Add a basic filtering option for the json output > Add aggregated prediction metrics to Prometheus -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (NIFI-9455) Add json output for Prometheus metrics and aggregated predictions
[ https://issues.apache.org/jira/browse/NIFI-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna reassigned NIFI-9455: - Assignee: Timea Barna > Add json output for Prometheus metrics and aggregated predictions > - > > Key: NIFI-9455 > URL: https://issues.apache.org/jira/browse/NIFI-9455 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > > Add json output format endpoint for Prometheus metrics > Add a basic filtering option for the json output > Add aggregated prediction metrics to Prometheus -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (NIFI-9455) Add json output for Prometheus metrics and aggregated predictions
Timea Barna created NIFI-9455: - Summary: Add json output for Prometheus metrics and aggregated predictions Key: NIFI-9455 URL: https://issues.apache.org/jira/browse/NIFI-9455 Project: Apache NiFi Issue Type: Improvement Reporter: Timea Barna Add json output format endpoint for Prometheus metrics Add a basic filtering option for the json output Add aggregated prediction metrics to Prometheus -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9385) Add a metrics provider in NiFi for Cloudera Manager
[ https://issues.apache.org/jira/browse/NIFI-9385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-9385: -- Status: Patch Available (was: In Progress) > Add a metrics provider in NiFi for Cloudera Manager > --- > > Key: NIFI-9385 > URL: https://issues.apache.org/jira/browse/NIFI-9385 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > > Add a metrics provider in NiFi for Cloudera Manager -- This message was sent by Atlassian Jira (v8.20.1#820001)
