[jira] [Updated] (NIFI-8536) PrometheusReportingTask and PrometheusRecordSink do not support variable registry for port
[ https://issues.apache.org/jira/browse/NIFI-8536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated NIFI-8536: --- Component/s: (was: Variable Registry) > PrometheusReportingTask and PrometheusRecordSink do not support variable > registry for port > -- > > Key: NIFI-8536 > URL: https://issues.apache.org/jira/browse/NIFI-8536 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Reporter: Matthew Clarke >Assignee: Nadeem >Priority: Minor > Fix For: 1.14.0 > > Time Spent: 50m > Remaining Estimate: 0h > > The documentation for both PrometheusReportingTask [1] (reporting task) and > PrometheusRecordSink [2] (controller service) state that NiFi Variable > Registry can be used to define the port. However, configuring NiFi EL in the > port property results in: > java.lang.NumberFormatException: For input string: "${ property name>}" > Support variable registry here would allow user to set a unique port on each > host in a NiFi cluster. > [1] > http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-prometheus-nar/1.13.2/org.apache.nifi.reporting.prometheus.PrometheusReportingTask/index.html > [2] > http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-prometheus-nar/1.13.2/org.apache.nifi.reporting.prometheus.PrometheusRecordSink/index.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-8536) PrometheusReportingTask and PrometheusRecordSink do not support variable registry for port
[ https://issues.apache.org/jira/browse/NIFI-8536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated NIFI-8536: --- Fix Version/s: 1.14.0 Resolution: Fixed Status: Resolved (was: Patch Available) > PrometheusReportingTask and PrometheusRecordSink do not support variable > registry for port > -- > > Key: NIFI-8536 > URL: https://issues.apache.org/jira/browse/NIFI-8536 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions, Variable Registry >Affects Versions: 1.12.1, 1.13.2 >Reporter: Matthew Clarke >Assignee: Nadeem >Priority: Minor > Fix For: 1.14.0 > > Time Spent: 50m > Remaining Estimate: 0h > > The documentation for both PrometheusReportingTask [1] (reporting task) and > PrometheusRecordSink [2] (controller service) state that NiFi Variable > Registry can be used to define the port. However, configuring NiFi EL in the > port property results in: > java.lang.NumberFormatException: For input string: "${ property name>}" > Support variable registry here would allow user to set a unique port on each > host in a NiFi cluster. > [1] > http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-prometheus-nar/1.13.2/org.apache.nifi.reporting.prometheus.PrometheusReportingTask/index.html > [2] > http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-prometheus-nar/1.13.2/org.apache.nifi.reporting.prometheus.PrometheusRecordSink/index.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-8536) PrometheusReportingTask and PrometheusRecordSink do not support variable registry for port
[ https://issues.apache.org/jira/browse/NIFI-8536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated NIFI-8536: --- Affects Version/s: (was: 1.13.2) (was: 1.12.1) > PrometheusReportingTask and PrometheusRecordSink do not support variable > registry for port > -- > > Key: NIFI-8536 > URL: https://issues.apache.org/jira/browse/NIFI-8536 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions, Variable Registry >Reporter: Matthew Clarke >Assignee: Nadeem >Priority: Minor > Fix For: 1.14.0 > > Time Spent: 50m > Remaining Estimate: 0h > > The documentation for both PrometheusReportingTask [1] (reporting task) and > PrometheusRecordSink [2] (controller service) state that NiFi Variable > Registry can be used to define the port. However, configuring NiFi EL in the > port property results in: > java.lang.NumberFormatException: For input string: "${ property name>}" > Support variable registry here would allow user to set a unique port on each > host in a NiFi cluster. > [1] > http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-prometheus-nar/1.13.2/org.apache.nifi.reporting.prometheus.PrometheusReportingTask/index.html > [2] > http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-prometheus-nar/1.13.2/org.apache.nifi.reporting.prometheus.PrometheusRecordSink/index.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-8536) PrometheusReportingTask and PrometheusRecordSink do not support variable registry for port
[ https://issues.apache.org/jira/browse/NIFI-8536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nadeem updated NIFI-8536: - Status: Patch Available (was: Open) > PrometheusReportingTask and PrometheusRecordSink do not support variable > registry for port > -- > > Key: NIFI-8536 > URL: https://issues.apache.org/jira/browse/NIFI-8536 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions, Variable Registry >Affects Versions: 1.13.2, 1.12.1 >Reporter: Matthew Clarke >Assignee: Nadeem >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > The documentation for both PrometheusReportingTask [1] (reporting task) and > PrometheusRecordSink [2] (controller service) state that NiFi Variable > Registry can be used to define the port. However, configuring NiFi EL in the > port property results in: > java.lang.NumberFormatException: For input string: "${ property name>}" > Support variable registry here would allow user to set a unique port on each > host in a NiFi cluster. > [1] > http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-prometheus-nar/1.13.2/org.apache.nifi.reporting.prometheus.PrometheusReportingTask/index.html > [2] > http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-prometheus-nar/1.13.2/org.apache.nifi.reporting.prometheus.PrometheusRecordSink/index.html -- This message was sent by Atlassian Jira (v8.3.4#803005)