[jira] [Assigned] (NIFI-11812) Stateless hardcodes "nexus" as the only extension option - Requesting NiFi Registry and/or S3 as additional ExtensionClient options
[ https://issues.apache.org/jira/browse/NIFI-11812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Nys reassigned NIFI-11812: --- Assignee: (was: Anna Nys) > Stateless hardcodes "nexus" as the only extension option - Requesting NiFi > Registry and/or S3 as additional ExtensionClient options > --- > > Key: NIFI-11812 > URL: https://issues.apache.org/jira/browse/NIFI-11812 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Stephanie Ambrose >Priority: Major > > Right now stateless NiFi has a hard-coded check on extension type of "nexus" > on line 302 of StandardStatelessDataflowFactory. It would be nice to > configure stateless to pull nars from additional extensions such as NiFi > Registry and/or S3. "stateful" NiFi allows you to set the nar provider to > NiFi Registry, which can be configured to store to S3. It'd be nice to have > this feature for stateless as well versus being tied to only nexus. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-11077) Provide a record number in a error log message when a RecordReader fails
[
https://issues.apache.org/jira/browse/NIFI-11077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anna Nys reassigned NIFI-11077:
---
Assignee: (was: Anna Nys)
> Provide a record number in a error log message when a RecordReader fails
>
>
> Key: NIFI-11077
> URL: https://issues.apache.org/jira/browse/NIFI-11077
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: Daniel Stieglitz
>Priority: Major
>
> When a RecordReader fails for whatever reason, it would be helpful to include
> in the error log message, a record number to help easily identify which
> record failed.
> My particular use case was when using QueryRecord and ValidateRecord with
> CSVReader on a file which was mostly comma delimited except for one line
> which was pipe delimited. The error message logged did not include the line
> number where the parsing failed. There was an IlegalArgumentException thrown
> with the message
> {code:java}
> Index for header 'id' is 1 but CSVRecord only has 1 values!
> {code}
> This made it very difficult to identify which record in the CSV file was
> causing the CSVReader to fail.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-11308) Create an Expression Language function to return NiFi version
[ https://issues.apache.org/jira/browse/NIFI-11308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Nys updated NIFI-11308: Status: Patch Available (was: Open) > Create an Expression Language function to return NiFi version > - > > Key: NIFI-11308 > URL: https://issues.apache.org/jira/browse/NIFI-11308 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.19.1 >Reporter: Mark Bean >Assignee: Anna Nys >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Create a new Expression Language function which returns the version of NiFi > being run. This allows for programmatic access to version information within > the flow. Suggest the function be subjectless as it applies to the instance > making the EL call and be called "nifiVersion()" > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-11077) Provide a record number in a error log message when a RecordReader fails
[
https://issues.apache.org/jira/browse/NIFI-11077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anna Nys reassigned NIFI-11077:
---
Assignee: Anna Nys
> Provide a record number in a error log message when a RecordReader fails
>
>
> Key: NIFI-11077
> URL: https://issues.apache.org/jira/browse/NIFI-11077
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: Daniel Stieglitz
>Assignee: Anna Nys
>Priority: Major
>
> When a RecordReader fails for whatever reason, it would be helpful to include
> in the error log message, a record number to help easily identify which
> record failed.
> My particular use case was when using QueryRecord and ValidateRecord with
> CSVReader on a file which was mostly comma delimited except for one line
> which was pipe delimited. The error message logged did not include the line
> number where the parsing failed. There was an IlegalArgumentException thrown
> with the message
> {code:java}
> Index for header 'id' is 1 but CSVRecord only has 1 values!
> {code}
> This made it very difficult to identify which record in the CSV file was
> causing the CSVReader to fail.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (NIFI-12030) Make property pop-up window expandable
[ https://issues.apache.org/jira/browse/NIFI-12030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Nys closed NIFI-12030. --- > Make property pop-up window expandable > -- > > Key: NIFI-12030 > URL: https://issues.apache.org/jira/browse/NIFI-12030 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Anna Nys >Assignee: Anna Nys >Priority: Minor > Time Spent: 1h > Remaining Estimate: 0h > > When you click on a property that contains a list of values, the pop-up > selection window is a fixed width. Sometimes the property values are longer > than the window can display, and so the text is truncated. This can be a > problem, particularly with controller services, as the controller names can > be quiet long. Sometimes several instances of the controller exists, and text > is appended to the end of the controller name to differentiate the instances, > but when trying to select one, it is impossible to see the end of the text. > Would like to have this pop-up expandable in geometry at least in width, so > it can be expanded to see all of the text. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-12030) Make property pop-up window expandable
[ https://issues.apache.org/jira/browse/NIFI-12030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Nys resolved NIFI-12030. - Resolution: Won't Fix Original requester is fine with the hover-over option of seeing truncated drop-down options. > Make property pop-up window expandable > -- > > Key: NIFI-12030 > URL: https://issues.apache.org/jira/browse/NIFI-12030 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Anna Nys >Assignee: Anna Nys >Priority: Minor > Time Spent: 1h > Remaining Estimate: 0h > > When you click on a property that contains a list of values, the pop-up > selection window is a fixed width. Sometimes the property values are longer > than the window can display, and so the text is truncated. This can be a > problem, particularly with controller services, as the controller names can > be quiet long. Sometimes several instances of the controller exists, and text > is appended to the end of the controller name to differentiate the instances, > but when trying to select one, it is impossible to see the end of the text. > Would like to have this pop-up expandable in geometry at least in width, so > it can be expanded to see all of the text. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-11308) Create an Expression Language function to return NiFi version
[ https://issues.apache.org/jira/browse/NIFI-11308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Nys reassigned NIFI-11308: --- Assignee: Anna Nys > Create an Expression Language function to return NiFi version > - > > Key: NIFI-11308 > URL: https://issues.apache.org/jira/browse/NIFI-11308 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.19.1 >Reporter: Mark Bean >Assignee: Anna Nys >Priority: Major > > Create a new Expression Language function which returns the version of NiFi > being run. This allows for programmatic access to version information within > the flow. Suggest the function be subjectless as it applies to the instance > making the EL call and be called "nifiVersion()" > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12249) FetchSFTP needs failure attributes
[ https://issues.apache.org/jira/browse/NIFI-12249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Nys updated NIFI-12249: Status: Patch Available (was: In Progress) > FetchSFTP needs failure attributes > -- > > Key: NIFI-12249 > URL: https://issues.apache.org/jira/browse/NIFI-12249 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Affects Versions: 2.0.0 >Reporter: Anna Nys >Assignee: Anna Nys >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > The FetchSFTP processor has several failure relationships: > comms.failure > not.found > permission.denied > While these relationships can help route files that fail for different > reasons, it would be helpful to have the failure reason written to a flowfile > attribute, so that the reason can be automatically included in an automated > notification message. > The value of the flowfile attribute could be used in an UpdateAttribute > advanced rules to generate error-specific email notifications to the > customer. Otherwise, we need separate processors for each failure > relationship. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12249) FetchSFTP needs failure attributes
Anna Nys created NIFI-12249: --- Summary: FetchSFTP needs failure attributes Key: NIFI-12249 URL: https://issues.apache.org/jira/browse/NIFI-12249 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Affects Versions: 2.0.0 Reporter: Anna Nys The FetchSFTP processor has several failure relationships: comms.failure not.found permission.denied While these relationships can help route files that fail for different reasons, it would be helpful to have the failure reason written to a flowfile attribute, so that the reason can be automatically included in an automated notification message. The value of the flowfile attribute could be used in an UpdateAttribute advanced rules to generate error-specific email notifications to the customer. Otherwise, we need separate processors for each failure relationship. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-12249) FetchSFTP needs failure attributes
[ https://issues.apache.org/jira/browse/NIFI-12249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Nys reassigned NIFI-12249: --- Assignee: Anna Nys > FetchSFTP needs failure attributes > -- > > Key: NIFI-12249 > URL: https://issues.apache.org/jira/browse/NIFI-12249 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Affects Versions: 2.0.0 >Reporter: Anna Nys >Assignee: Anna Nys >Priority: Minor > > The FetchSFTP processor has several failure relationships: > comms.failure > not.found > permission.denied > While these relationships can help route files that fail for different > reasons, it would be helpful to have the failure reason written to a flowfile > attribute, so that the reason can be automatically included in an automated > notification message. > The value of the flowfile attribute could be used in an UpdateAttribute > advanced rules to generate error-specific email notifications to the > customer. Otherwise, we need separate processors for each failure > relationship. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-5137) Cannot clear state of a controller service
[ https://issues.apache.org/jira/browse/NIFI-5137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Nys updated NIFI-5137: --- Attachment: snip2.PNG > Cannot clear state of a controller service > -- > > Key: NIFI-5137 > URL: https://issues.apache.org/jira/browse/NIFI-5137 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.6.0 >Reporter: Joe Percivall >Assignee: Anna Nys >Priority: Minor > Attachments: snip1.PNG, snip2.PNG > > Time Spent: 10m > Remaining Estimate: 0h > > To reproduce: > # Start with a controller service that is stopped with some state stored > # Go to the state manager for that controller service > # Attempt to click on the "clear state" text but notice that it is disabled > and doesn't do anything > Workaround: > * Start at step 2 (in the state manager) > * Inspect the page using browser web tools > * Notice the "class" of the span is "link disabled" > * Remove the "disabled" class from the span > * It now behaves as expected -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-5137) Cannot clear state of a controller service
[ https://issues.apache.org/jira/browse/NIFI-5137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Nys updated NIFI-5137: --- Attachment: snip1.PNG > Cannot clear state of a controller service > -- > > Key: NIFI-5137 > URL: https://issues.apache.org/jira/browse/NIFI-5137 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.6.0 >Reporter: Joe Percivall >Assignee: Anna Nys >Priority: Minor > Attachments: snip1.PNG, snip2.PNG > > Time Spent: 10m > Remaining Estimate: 0h > > To reproduce: > # Start with a controller service that is stopped with some state stored > # Go to the state manager for that controller service > # Attempt to click on the "clear state" text but notice that it is disabled > and doesn't do anything > Workaround: > * Start at step 2 (in the state manager) > * Inspect the page using browser web tools > * Notice the "class" of the span is "link disabled" > * Remove the "disabled" class from the span > * It now behaves as expected -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-5137) Cannot clear state of a controller service
[
https://issues.apache.org/jira/browse/NIFI-5137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17775814#comment-17775814
]
Anna Nys commented on NIFI-5137:
I order to test this, I made a random controller service stateful. For
example, take CSVRecordLookupService and do the following:
1. Add class-level annotation:
@Stateful(scopes = Scope.LOCAL, description = "store some state")
2. Create some state in the onEnabled method:
StateManager sm = getStateManager();
Map stateMap = Map.of("key", "value");
sm.setState(stateMap, Scope.LOCAL);
3. Add imports:
import org.apache.nifi.annotation.behavior.Stateful;
import org.apache.nifi.components.state.Scope;
import org.apache.nifi.components.state.StateManager;
import org.apache.nifi.components.state.StateMap;
4. build the nifi-lookup-services-nar
(nifi-nar-bundles/nifi-standard-services/nifi-lookup-services-bundle/nifi-lookup-services-nar)
and drop into the installation dir/lib directory and restart nifi.
5. The manage state icon should appear in the controller service grid.
> Cannot clear state of a controller service
> --
>
> Key: NIFI-5137
> URL: https://issues.apache.org/jira/browse/NIFI-5137
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
>Affects Versions: 1.6.0
>Reporter: Joe Percivall
>Assignee: Anna Nys
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> To reproduce:
> # Start with a controller service that is stopped with some state stored
> # Go to the state manager for that controller service
> # Attempt to click on the "clear state" text but notice that it is disabled
> and doesn't do anything
> Workaround:
> * Start at step 2 (in the state manager)
> * Inspect the page using browser web tools
> * Notice the "class" of the span is "link disabled"
> * Remove the "disabled" class from the span
> * It now behaves as expected
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (NIFI-8673) Document difference between Active Threads as shown in Status bar versus as shown by Node
[ https://issues.apache.org/jira/browse/NIFI-8673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Nys reassigned NIFI-8673: -- Assignee: Anna Nys > Document difference between Active Threads as shown in Status bar versus as > shown by Node > - > > Key: NIFI-8673 > URL: https://issues.apache.org/jira/browse/NIFI-8673 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation Website >Affects Versions: 1.11.4, 1.13.2 >Reporter: Nissim Shiman >Assignee: Anna Nys >Priority: Major > > "Active Threads" on the main gui's status bar has a lower number then "Active > Thread Count" when broken down by nodes > (i.e. Global Menu -> Cluster) > > This is because "Active Threads" only captures threads by objects that are in > the graph (i.e. processors, processor groups, remote processor groups, > funnels, input and output ports). [1] > > "Active Thread Count" is more comprehensive and includes these as well as any > other threads as well (i.e. reporting tasks, controller services etc.) [2] [3] > > This difference should be documented in the Apache NiFi documentation. > > > > > [1] > [https://github.com/apache/nifi/blob/main/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/FlowController.java#L2092-2126] > [2] > [https://github.com/apache/nifi/blob/main/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-cluster/src/main/java/org/apache/nifi/cluster/coordination/heartbeat/ClusterProtocolHeartbeatMonitor.java#L157] > [3] > [https://github.com/apache/nifi/blob/main/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/FlowController.java#L2149-2153] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-5137) Cannot clear state of a controller service
[ https://issues.apache.org/jira/browse/NIFI-5137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Nys updated NIFI-5137: --- Status: Patch Available (was: Open) > Cannot clear state of a controller service > -- > > Key: NIFI-5137 > URL: https://issues.apache.org/jira/browse/NIFI-5137 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.6.0 >Reporter: Joe Percivall >Assignee: Anna Nys >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > To reproduce: > # Start with a controller service that is stopped with some state stored > # Go to the state manager for that controller service > # Attempt to click on the "clear state" text but notice that it is disabled > and doesn't do anything > Workaround: > * Start at step 2 (in the state manager) > * Inspect the page using browser web tools > * Notice the "class" of the span is "link disabled" > * Remove the "disabled" class from the span > * It now behaves as expected -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-11812) Stateless hardcodes "nexus" as the only extension option - Requesting NiFi Registry and/or S3 as additional ExtensionClient options
[ https://issues.apache.org/jira/browse/NIFI-11812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Nys reassigned NIFI-11812: --- Assignee: Anna Nys > Stateless hardcodes "nexus" as the only extension option - Requesting NiFi > Registry and/or S3 as additional ExtensionClient options > --- > > Key: NIFI-11812 > URL: https://issues.apache.org/jira/browse/NIFI-11812 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Stephanie Ambrose >Assignee: Anna Nys >Priority: Major > > Right now stateless NiFi has a hard-coded check on extension type of "nexus" > on line 302 of StandardStatelessDataflowFactory. It would be nice to > configure stateless to pull nars from additional extensions such as NiFi > Registry and/or S3. "stateful" NiFi allows you to set the nar provider to > NiFi Registry, which can be configured to store to S3. It'd be nice to have > this feature for stateless as well versus being tied to only nexus. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-6721) jms_expiration attribute problem
[ https://issues.apache.org/jira/browse/NIFI-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Nys updated NIFI-6721: --- Fix Version/s: (was: 1.latest) > jms_expiration attribute problem > > > Key: NIFI-6721 > URL: https://issues.apache.org/jira/browse/NIFI-6721 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Affects Versions: 1.8.0 > Environment: Linux CENTOS 7 >Reporter: Tim Chermak >Assignee: Anna Nys >Priority: Minor > Fix For: 2.latest > > Time Spent: 40m > Remaining Estimate: 0h > > The documentation for PublishJMS indicates the JMSExpiration is set with the > attribute jms_expiration. However, this value is really the time-to-live > (ttl) in milliseconds. The JMSExpiration is calculated by the provider > library as "expiration = timestamp + ttl" > So, this NiFi flowfile attribute should really be named jms_ttl. The current > setup works correctly when NiFi creates and publishes a message, but has > problems when you try to republish a JMS message. > GetFile -> UpdateAttibute -> PublishJMS creates a valid JMSExpiration in the > message, however, when a JMS has the expiration set, ConsumeJMS -> PublishJMS > shows an error in the nifi.--app.log file: > "o.apache.nifi.jms.processors.PublishJMS PublishJMS[id=016b1005-xx...] > Incompatible value for attribute jms_expiration [1566428032803] is not a > number. Ignoring this attribute." > Looks like ConsumeJMS set the flowfile attribute to the expiration value > rather than the time-ti-live value. Time-to-live should be jms_ttl = > expiration - current_time. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-6721) jms_expiration attribute problem
[ https://issues.apache.org/jira/browse/NIFI-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Nys resolved NIFI-6721. Fix Version/s: 2.0.0 Resolution: Fixed PR submitted: https://github.com/apache/nifi/pull/7789 > jms_expiration attribute problem > > > Key: NIFI-6721 > URL: https://issues.apache.org/jira/browse/NIFI-6721 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Affects Versions: 1.8.0 > Environment: Linux CENTOS 7 >Reporter: Tim Chermak >Assignee: Anna Nys >Priority: Minor > Fix For: 2.0.0 > > Time Spent: 40m > Remaining Estimate: 0h > > The documentation for PublishJMS indicates the JMSExpiration is set with the > attribute jms_expiration. However, this value is really the time-to-live > (ttl) in milliseconds. The JMSExpiration is calculated by the provider > library as "expiration = timestamp + ttl" > So, this NiFi flowfile attribute should really be named jms_ttl. The current > setup works correctly when NiFi creates and publishes a message, but has > problems when you try to republish a JMS message. > GetFile -> UpdateAttibute -> PublishJMS creates a valid JMSExpiration in the > message, however, when a JMS has the expiration set, ConsumeJMS -> PublishJMS > shows an error in the nifi.--app.log file: > "o.apache.nifi.jms.processors.PublishJMS PublishJMS[id=016b1005-xx...] > Incompatible value for attribute jms_expiration [1566428032803] is not a > number. Ignoring this attribute." > Looks like ConsumeJMS set the flowfile attribute to the expiration value > rather than the time-ti-live value. Time-to-live should be jms_ttl = > expiration - current_time. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-6721) jms_expiration attribute problem
[ https://issues.apache.org/jira/browse/NIFI-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Nys reassigned NIFI-6721: -- Assignee: Anna Nys (was: Seokwon Yang) > jms_expiration attribute problem > > > Key: NIFI-6721 > URL: https://issues.apache.org/jira/browse/NIFI-6721 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Affects Versions: 1.8.0 > Environment: Linux CENTOS 7 >Reporter: Tim Chermak >Assignee: Anna Nys >Priority: Minor > Time Spent: 40m > Remaining Estimate: 0h > > The documentation for PublishJMS indicates the JMSExpiration is set with the > attribute jms_expiration. However, this value is really the time-to-live > (ttl) in milliseconds. The JMSExpiration is calculated by the provider > library as "expiration = timestamp + ttl" > So, this NiFi flowfile attribute should really be named jms_ttl. The current > setup works correctly when NiFi creates and publishes a message, but has > problems when you try to republish a JMS message. > GetFile -> UpdateAttibute -> PublishJMS creates a valid JMSExpiration in the > message, however, when a JMS has the expiration set, ConsumeJMS -> PublishJMS > shows an error in the nifi.--app.log file: > "o.apache.nifi.jms.processors.PublishJMS PublishJMS[id=016b1005-xx...] > Incompatible value for attribute jms_expiration [1566428032803] is not a > number. Ignoring this attribute." > Looks like ConsumeJMS set the flowfile attribute to the expiration value > rather than the time-ti-live value. Time-to-live should be jms_ttl = > expiration - current_time. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-12030) Make property pop-up window expandable
[ https://issues.apache.org/jira/browse/NIFI-12030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Nys reassigned NIFI-12030: --- Assignee: Anna Nys > Make property pop-up window expandable > -- > > Key: NIFI-12030 > URL: https://issues.apache.org/jira/browse/NIFI-12030 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Anna Nys >Assignee: Anna Nys >Priority: Minor > > When you click on a property that contains a list of values, the pop-up > selection window is a fixed width. Sometimes the property values are longer > than the window can display, and so the text is truncated. This can be a > problem, particularly with controller services, as the controller names can > be quiet long. Sometimes several instances of the controller exists, and text > is appended to the end of the controller name to differentiate the instances, > but when trying to select one, it is impossible to see the end of the text. > Would like to have this pop-up expandable in geometry at least in width, so > it can be expanded to see all of the text. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-5137) Cannot clear state of a controller service
[ https://issues.apache.org/jira/browse/NIFI-5137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Nys reassigned NIFI-5137: -- Assignee: Anna Nys > Cannot clear state of a controller service > -- > > Key: NIFI-5137 > URL: https://issues.apache.org/jira/browse/NIFI-5137 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.6.0 >Reporter: Joe Percivall >Assignee: Anna Nys >Priority: Minor > > To reproduce: > # Start with a controller service that is stopped with some state stored > # Go to the state manager for that controller service > # Attempt to click on the "clear state" text but notice that it is disabled > and doesn't do anything > Workaround: > * Start at step 2 (in the state manager) > * Inspect the page using browser web tools > * Notice the "class" of the span is "link disabled" > * Remove the "disabled" class from the span > * It now behaves as expected -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12030) Make property pop-up window expandable
Anna Nys created NIFI-12030: --- Summary: Make property pop-up window expandable Key: NIFI-12030 URL: https://issues.apache.org/jira/browse/NIFI-12030 Project: Apache NiFi Issue Type: Improvement Components: Core UI Reporter: Anna Nys When you click on a property that contains a list of values, the pop-up selection window is a fixed width. Sometimes the property values are longer than the window can display, and so the text is truncated. This can be a problem, particularly with controller services, as the controller names can be quiet long. Sometimes several instances of the controller exists, and text is appended to the end of the controller name to differentiate the instances, but when trying to select one, it is impossible to see the end of the text. Would like to have this pop-up expandable in geometry at least in width, so it can be expanded to see all of the text. -- This message was sent by Atlassian Jira (v8.20.10#820010)
