[jira] [Assigned] (NIFI-8899) Add version info to the UI
[ https://issues.apache.org/jira/browse/NIFI-8899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Smith reassigned NIFI-8899: --- Assignee: Tim Smith > Add version info to the UI > -- > > Key: NIFI-8899 > URL: https://issues.apache.org/jira/browse/NIFI-8899 > Project: Apache NiFi > Issue Type: Improvement > Components: NiFi Registry >Reporter: Mark Bean >Assignee: Tim Smith >Priority: Major > > Currently, the UI does not present the current version of NiFi Registry. This > information should be available through an "about" menu item and included on > the documentation pages. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (NIFI-9191) Add NiFi version in about tab on component UIs and documentation.
[ https://issues.apache.org/jira/browse/NIFI-9191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17409465#comment-17409465 ] Tim Smith commented on NIFI-9191: - This is a duplicate , see https://issues.apache.org/jira/browse/NIFI-8899, and needs to be closed. > Add NiFi version in about tab on component UIs and documentation. > -- > > Key: NIFI-9191 > URL: https://issues.apache.org/jira/browse/NIFI-9191 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Tim Smith >Priority: Minor > > For convenience, especially when using multiple versions of nars, the ability > to reference the current NiFi version in the component UI and usage > documentation, would be useful. A new tab on the component UI "about" to > display the running NiFi version and displaying on usage documentation would > enhance user experience. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9191) Add NiFi version in about tab on component UIs and documentation.
Tim Smith created NIFI-9191: --- Summary: Add NiFi version in about tab on component UIs and documentation. Key: NIFI-9191 URL: https://issues.apache.org/jira/browse/NIFI-9191 Project: Apache NiFi Issue Type: Improvement Reporter: Tim Smith For convenience, especially when using multiple versions of nars, the ability to reference the current NiFi version in the component UI and usage documentation, would be useful. A new tab on the component UI "about" to display the running NiFi version and displaying on usage documentation would enhance user experience. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-8960) Create ability for EvaluateJsonPath processor to match any or all defined json paths.
[ https://issues.apache.org/jira/browse/NIFI-8960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Smith updated NIFI-8960: Status: Patch Available (was: Open) Submitted pull request:https://github.com/apache/nifi/pull/5321 > Create ability for EvaluateJsonPath processor to match any or all defined > json paths. > -- > > Key: NIFI-8960 > URL: https://issues.apache.org/jira/browse/NIFI-8960 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Tim Smith >Assignee: Tim Smith >Priority: Minor > Fix For: 1.14.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Add the capability to set "Match Criteria" to "all" or "any", where all json > paths must match on json objects. Default behavior being "any". Also add the > ability to apply to either attributes matching regex or content, with > default being "match on content". -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (NIFI-8960) Create ability for EvaluateJsonPath processor to match any or all defined json paths.
[ https://issues.apache.org/jira/browse/NIFI-8960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Smith reassigned NIFI-8960: --- Assignee: Tim Smith > Create ability for EvaluateJsonPath processor to match any or all defined > json paths. > -- > > Key: NIFI-8960 > URL: https://issues.apache.org/jira/browse/NIFI-8960 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Tim Smith >Assignee: Tim Smith >Priority: Minor > Fix For: 1.14.0 > > > Add the capability to set "Match Criteria" to "all" or "any", where all json > paths must match on json objects. Default behavior being "any". Also add the > ability to apply to either attributes matching regex or content, with > default being "match on content". -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-8960) Create ability for EvaluateJsonPath processor to match any or all defined json paths.
Tim Smith created NIFI-8960: --- Summary: Create ability for EvaluateJsonPath processor to match any or all defined json paths. Key: NIFI-8960 URL: https://issues.apache.org/jira/browse/NIFI-8960 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Reporter: Tim Smith Fix For: 1.14.0 Add the capability to set "Match Criteria" to "all" or "any", where all json paths must match on json objects. Default behavior being "any". Also add the ability to apply to either attributes matching regex or content, with default being "match on content". -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-8930) Add ability for ScanAttribute processor to match on attribute values containing a delimited list of values.
[ https://issues.apache.org/jira/browse/NIFI-8930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Smith updated NIFI-8930: Assignee: Tim Smith Status: Patch Available (was: Open) > Add ability for ScanAttribute processor to match on attribute values > containing a delimited list of values. > --- > > Key: NIFI-8930 > URL: https://issues.apache.org/jira/browse/NIFI-8930 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.14.0 >Reporter: Tim Smith >Assignee: Tim Smith >Priority: Minor > > The ScanAttribute processor is limited in that an exact match is required > when applied for attribute value. There are many times an attribute contains > a delimited list of values. It would be useful to specify a delimiter and > have the match criteria applied to each delimited value in the attribute. Two > additional property descriptors need created, 'Delimiter' and 'Delimited > Match Criteria'. 'Delimiter' sets the delimiter to apply to the attribute(s). > 'Delimited Match Criteria' specifies how the delimited attributes should > match the dictionary. If 'All Must Match' is selected, all delimited values > must match a dictionary term/pattern for attribute to be matched. For 'At > Least 1 Must Match' , if any one delimited value matches,then the attribute > matches. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-8930) Add ability for ScanAttribute processor to match on attribute values containing a delimited list of values.
[ https://issues.apache.org/jira/browse/NIFI-8930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Smith updated NIFI-8930: Affects Version/s: 1.14.0 > Add ability for ScanAttribute processor to match on attribute values > containing a delimited list of values. > --- > > Key: NIFI-8930 > URL: https://issues.apache.org/jira/browse/NIFI-8930 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.14.0 >Reporter: Tim Smith >Priority: Minor > > The ScanAttribute processor is limited in that an exact match is required > when applied for attribute value. There are many times an attribute contains > a delimited list of values. It would be useful to specify a delimiter and > have the match criteria applied to each delimited value in the attribute. Two > additional property descriptors need created, 'Delimiter' and 'Delimited > Match Criteria'. 'Delimiter' sets the delimiter to apply to the attribute(s). > 'Delimited Match Criteria' specifies how the delimited attributes should > match the dictionary. If 'All Must Match' is selected, all delimited values > must match a dictionary term/pattern for attribute to be matched. For 'At > Least 1 Must Match' , if any one delimited value matches,then the attribute > matches. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-8930) Add ability for ScanAttribute processor to match on attribute values containing a delimited list of values.
[ https://issues.apache.org/jira/browse/NIFI-8930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Smith updated NIFI-8930: Affects Version/s: (was: 1.14.0) > Add ability for ScanAttribute processor to match on attribute values > containing a delimited list of values. > --- > > Key: NIFI-8930 > URL: https://issues.apache.org/jira/browse/NIFI-8930 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Tim Smith >Priority: Minor > > The ScanAttribute processor is limited in that an exact match is required > when applied for attribute value. There are many times an attribute contains > a delimited list of values. It would be useful to specify a delimiter and > have the match criteria applied to each delimited value in the attribute. Two > additional property descriptors need created, 'Delimiter' and 'Delimited > Match Criteria'. 'Delimiter' sets the delimiter to apply to the attribute(s). > 'Delimited Match Criteria' specifies how the delimited attributes should > match the dictionary. If 'All Must Match' is selected, all delimited values > must match a dictionary term/pattern for attribute to be matched. For 'At > Least 1 Must Match' , if any one delimited value matches,then the attribute > matches. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-8930) Add ability for ScanAttribute processor to match on attribute values containing a delimited list of values.
Tim Smith created NIFI-8930: --- Summary: Add ability for ScanAttribute processor to match on attribute values containing a delimited list of values. Key: NIFI-8930 URL: https://issues.apache.org/jira/browse/NIFI-8930 Project: Apache NiFi Issue Type: Improvement Affects Versions: 1.14.0 Reporter: Tim Smith The ScanAttribute processor is limited in that an exact match is required when applied for attribute value. There are many times an attribute contains a delimited list of values. It would be useful to specify a delimiter and have the match criteria applied to each delimited value in the attribute. Two additional property descriptors need created, 'Delimiter' and 'Delimited Match Criteria'. 'Delimiter' sets the delimiter to apply to the attribute(s). 'Delimited Match Criteria' specifies how the delimited attributes should match the dictionary. If 'All Must Match' is selected, all delimited values must match a dictionary term/pattern for attribute to be matched. For 'At Least 1 Must Match' , if any one delimited value matches,then the attribute matches. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-7225) FetchSFTP processor: "routing to not.found" error given when Private Key Path property is invalid
[ https://issues.apache.org/jira/browse/NIFI-7225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Smith updated NIFI-7225: Status: Patch Available (was: Open) > FetchSFTP processor: "routing to not.found" error given when Private Key Path > property is invalid > - > > Key: NIFI-7225 > URL: https://issues.apache.org/jira/browse/NIFI-7225 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.11.3, 1.10.0 >Reporter: Nissim Shiman >Assignee: Tim Smith >Priority: Major > Time Spent: 1.5h > Remaining Estimate: 0h > > In apache nifi 1.8.0, for the FetchSFTP processor, if the "Private Key Path" > property was a directory, this would be flagged immediately as a > configuration issue. > In apache 1.10 (and later) a directory is an acceptable value here, but then > on runtime, the "not.found" relationship is hit, even though the remote file > exists. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-6242) PutFileTransfer generating incorrect provenance events
[ https://issues.apache.org/jira/browse/NIFI-6242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Smith updated NIFI-6242: Status: Patch Available (was: Open) > PutFileTransfer generating incorrect provenance events > -- > > Key: NIFI-6242 > URL: https://issues.apache.org/jira/browse/NIFI-6242 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.9.2 >Reporter: Brandon Rhys DeVries >Assignee: Tim Smith >Priority: Minor > Time Spent: 1h 40m > Remaining Estimate: 0h > > PutFileTransfer transfers a (configurable size) batch of FlowFiles. However, > the provenance SEND event generated [1] uses the hostname evaluated from the > first FlowFile of the batch. If the hostname is a hardcoded string, there's > no issue... but if the hostname uses Expression Language, the generated > provenance events will be incorrect (and very confusing). > [1] > [https://github.com/apache/nifi/blob/f60585a9b6df6b3b28be1eb80a0a60deac6c0493/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/PutFileTransfer.java#L146-L147] > [2] > [https://github.com/apache/nifi/blob/f60585a9b6df6b3b28be1eb80a0a60deac6c0493/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/PutFileTransfer.java#L97] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (NIFI-6242) PutFileTransfer generating incorrect provenance events
[ https://issues.apache.org/jira/browse/NIFI-6242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Smith reassigned NIFI-6242: --- Assignee: Tim Smith > PutFileTransfer generating incorrect provenance events > -- > > Key: NIFI-6242 > URL: https://issues.apache.org/jira/browse/NIFI-6242 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.9.2 >Reporter: Brandon Rhys DeVries >Assignee: Tim Smith >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > PutFileTransfer transfers a (configurable size) batch of FlowFiles. However, > the provenance SEND event generated [1] uses the hostname evaluated from the > first FlowFile of the batch. If the hostname is a hardcoded string, there's > no issue... but if the hostname uses Expression Language, the generated > provenance events will be incorrect (and very confusing). > [1] > [https://github.com/apache/nifi/blob/f60585a9b6df6b3b28be1eb80a0a60deac6c0493/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/PutFileTransfer.java#L146-L147] > [2] > [https://github.com/apache/nifi/blob/f60585a9b6df6b3b28be1eb80a0a60deac6c0493/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/PutFileTransfer.java#L97] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (NIFI-5629) GetFile becomes slow listing vast directories
[ https://issues.apache.org/jira/browse/NIFI-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Smith reassigned NIFI-5629: --- Assignee: Tim Smith > GetFile becomes slow listing vast directories > - > > Key: NIFI-5629 > URL: https://issues.apache.org/jira/browse/NIFI-5629 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 1.6.0 >Reporter: Adam >Assignee: Tim Smith >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > GetFile repeatedly lists entire directories before applying batching, meaning > for vast directories it spends a long time listing directories. > > Pull request to follow. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (NIFI-7991) Flow Configuration History displays "annotation data not found/available" from "Advanced" changes.
[ https://issues.apache.org/jira/browse/NIFI-7991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Smith reassigned NIFI-7991: --- Assignee: Tim Smith > Flow Configuration History displays "annotation data not found/available" > from "Advanced" changes. > -- > > Key: NIFI-7991 > URL: https://issues.apache.org/jira/browse/NIFI-7991 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Tim Smith >Assignee: Tim Smith >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > On making changes through UpdateAttributes Advanced tab, discovered that > "AnnotationData" is presented in "Flow Configuration History" as "annotation > data not found/available" in both previous and new values by > ProcessorAuditor. UpdateAttribute represents the annotation data as XML. > ProcessorAuditor, at a minimum, should attempt to represent new and previous > values as the difference between the XML nodes or as String values, if not in > XML format. Default value presented is not useful. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (NIFI-7225) FetchSFTP processor: "routing to not.found" error given when Private Key Path property is invalid
[ https://issues.apache.org/jira/browse/NIFI-7225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Smith reassigned NIFI-7225: --- Assignee: Tim Smith > FetchSFTP processor: "routing to not.found" error given when Private Key Path > property is invalid > - > > Key: NIFI-7225 > URL: https://issues.apache.org/jira/browse/NIFI-7225 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.10.0, 1.11.3 >Reporter: Nissim Shiman >Assignee: Tim Smith >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > In apache nifi 1.8.0, for the FetchSFTP processor, if the "Private Key Path" > property was a directory, this would be flagged immediately as a > configuration issue. > In apache 1.10 (and later) a directory is an acceptable value here, but then > on runtime, the "not.found" relationship is hit, even though the remote file > exists. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-7991) Flow Configuration History displays "annotation data not found/available" from "Advanced" changes.
Tim Smith created NIFI-7991: --- Summary: Flow Configuration History displays "annotation data not found/available" from "Advanced" changes. Key: NIFI-7991 URL: https://issues.apache.org/jira/browse/NIFI-7991 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Reporter: Tim Smith On making changes through UpdateAttributes Advanced tab, discovered that "AnnotationData" is presented in "Flow Configuration History" as "annotation data not found/available" in both previous and new values by ProcessorAuditor. UpdateAttribute represents the annotation data as XML. ProcessorAuditor, at a minimum, should attempt to represent new and previous values as the difference between the XML nodes or as String values, if not in XML format. Default value presented is not useful. -- This message was sent by Atlassian Jira (v8.3.4#803005)
