[jira] [Created] (NIFI-12861) Provide documentation on JASN1Reader that it only supports JDK and not just JRE
Mathew Kapkiai created NIFI-12861: - Summary: Provide documentation on JASN1Reader that it only supports JDK and not just JRE Key: NIFI-12861 URL: https://issues.apache.org/jira/browse/NIFI-12861 Project: Apache NiFi Issue Type: Improvement Reporter: Mathew Kapkiai Assignee: Mathew Kapkiai -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11667) Provide default NiFi version when none is specified to DockerBuild.sh script when building NiFi container Image
[ https://issues.apache.org/jira/browse/NIFI-11667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mathew Kapkiai updated NIFI-11667: -- Summary: Provide default NiFi version when none is specified to DockerBuild.sh script when building NiFi container Image (was: Provide default NiFi version when none is specified to DockerBuild.sh script when build NiFi container Image) > Provide default NiFi version when none is specified to DockerBuild.sh script > when building NiFi container Image > --- > > Key: NIFI-11667 > URL: https://issues.apache.org/jira/browse/NIFI-11667 > Project: Apache NiFi > Issue Type: Bug > Components: Docker >Affects Versions: 1.21.0, 1.22.0 >Reporter: Mathew Kapkiai >Assignee: Mathew Kapkiai >Priority: Minor > Labels: patch > Fix For: 2.0.0, 1.23.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Use NIFI_IMAGE_VERSION as default DISTRO_VERSION when no overriding value is > provided to the DockerBuild.sh script. > When no overriding argument is passed to the DockerBuild.sh script, NiFi > version is missed as no default version is specified. The NiFi version is > required to build the url for pulling NiFi binaries. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11667) Provide default NiFi version when none is specified to DockerBuild.sh script when build NiFi container Image
[ https://issues.apache.org/jira/browse/NIFI-11667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mathew Kapkiai updated NIFI-11667: -- Summary: Provide default NiFi version when none is specified to DockerBuild.sh script when build NiFi container Image (was: Provide default NiFi version when non is specified to DockerBuild.sh script when build NiFi container Image) > Provide default NiFi version when none is specified to DockerBuild.sh script > when build NiFi container Image > > > Key: NIFI-11667 > URL: https://issues.apache.org/jira/browse/NIFI-11667 > Project: Apache NiFi > Issue Type: Bug > Components: Docker >Affects Versions: 1.21.0, 1.22.0 >Reporter: Mathew Kapkiai >Assignee: Mathew Kapkiai >Priority: Minor > Labels: patch > Fix For: 2.0.0, 1.23.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Use NIFI_IMAGE_VERSION as default DISTRO_VERSION when no overriding value is > provided to the DockerBuild.sh script. > When no overriding argument is passed to the DockerBuild.sh script, NiFi > version is missed as no default version is specified. The NiFi version is > required to build the url for pulling NiFi binaries. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11667) Provide default NiFi version when non is specified to DockerBuild.sh script when build NiFi container Image
Mathew Kapkiai created NIFI-11667: - Summary: Provide default NiFi version when non is specified to DockerBuild.sh script when build NiFi container Image Key: NIFI-11667 URL: https://issues.apache.org/jira/browse/NIFI-11667 Project: Apache NiFi Issue Type: Bug Components: Docker Affects Versions: 1.21.0, 1.22.0 Reporter: Mathew Kapkiai Assignee: Mathew Kapkiai Fix For: 2.0.0, 1.23.0 Use NIFI_IMAGE_VERSION as default DISTRO_VERSION when no overriding value is provided to the DockerBuild.sh script. When no overriding argument is passed to the DockerBuild.sh script, NiFi version is missed as no default version is specified. The NiFi version is required to build the url for pulling NiFi binaries. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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=17537971#comment-17537971 ] Mathew Kapkiai commented on NIFI-9475: -- Hi [~timeabarna] I was looking into this feature and found something weird. Why do you need to configure retry for relationship success? See image below for UpdateRecord processor. !image-2022-05-17-09-27-33-222.png! > 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-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 ] Mathew Kapkiai updated NIFI-9475: - Attachment: image-2022-05-17-09-27-33-222.png > 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-9377) NiFi QueryRecord Error: org.apache.calcite.runtime.CalciteException: Failed to encode '%Поиск%' in character set 'ISO-8859-1'
[
https://issues.apache.org/jira/browse/NIFI-9377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17507864#comment-17507864
]
Mathew Kapkiai commented on NIFI-9377:
--
Hi Pierre,
I suggest you proceed with adding documentation concerning this.
Got success too working with Arabic characters e.g. ሞልተዋል.
Used the same solution as Alexandr with success after taking time in calcite
source code.
I added in bootstrap.conf line :
java.arg.18=-Dcalcite.default.charset=utf-8
> NiFi QueryRecord Error: org.apache.calcite.runtime.CalciteException: Failed
> to encode '%Поиск%' in character set 'ISO-8859-1'
> --
>
> Key: NIFI-9377
> URL: https://issues.apache.org/jira/browse/NIFI-9377
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.12.0, 1.12.1, 1.14.0, 1.13.2, 1.15.0
>Reporter: Alexandr Mikhaylov
>Priority: Major
> Attachments: image-2021-11-13-16-07-59-879.png
>
>
> QueryrRecord Processor not working when using non-ASCII characters in a
> select phrase.
> Example use Russian Cyrillic symbols:
> JSON:
> [
> { "id":"test", "message":"Search Поиск" }
> ]
> QueryRecord Property Value:
> select * from flowfile where message like '%Поиск%'
> Error:
> NiFi org.apache.calcite.runtime.CalciteException: Failed to encode '%Поиск%'
> in character set 'ISO-8859-1'
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (NIFI-9297) Typo in AbstractListProcessor for "Tracking Entities" Listing Strategy " in Documentation
[ https://issues.apache.org/jira/browse/NIFI-9297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mathew Kapkiai updated NIFI-9297: - Description: Documentation of AbstractListProcessor Class for Listing Strategy property by "Tracking Entities" has typo in the following bolded line: "This strategy can pick entities having old timestamp that can *be missed with 'Tracing Timestamps'.* Works even when multiple subdirectories are being written at the same time while listing is running." It should have been "*be missed with 'Tracking Timestamps'".* This can be bring confusion especially to guys who are new to NiFi and they are trying to understand the referencing processors usage was: Documentation of ListSFTP processor for Listing Strategy property by "Tracking Entities" has typo in the following bolded line: "This strategy can pick entities having old timestamp that can *be missed with 'Tracing Timestamps'.* Works even when multiple subdirectories are being written at the same time while listing is running." It should have been "*be missed with 'Tracking Timestamps'".* This can be bring confusion especially to guys who are new to NiFi and they are trying to understand the processor usage > Typo in AbstractListProcessor for "Tracking Entities" Listing Strategy " in > Documentation > -- > > Key: NIFI-9297 > URL: https://issues.apache.org/jira/browse/NIFI-9297 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation Website >Affects Versions: 1.14.0 >Reporter: Mathew Kapkiai >Priority: Minor > Labels: documentation > Fix For: 1.14.0 > > > Documentation of AbstractListProcessor Class for Listing Strategy property > by "Tracking Entities" has typo in the following bolded line: > "This strategy can pick entities having old timestamp that can *be missed > with 'Tracing Timestamps'.* > Works even when multiple subdirectories are being written at the same time > while listing is running." > > It should have been "*be missed with 'Tracking Timestamps'".* > This can be bring confusion especially to guys who are new to NiFi and they > are trying to understand the referencing processors usage -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-9297) Typo in AbstractListProcessor for "Tracking Entities" Listing Strategy " in Documentation
[ https://issues.apache.org/jira/browse/NIFI-9297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mathew Kapkiai updated NIFI-9297: - Summary: Typo in AbstractListProcessor for "Tracking Entities" Listing Strategy " in Documentation (was: Typo in Documentation) > Typo in AbstractListProcessor for "Tracking Entities" Listing Strategy " in > Documentation > -- > > Key: NIFI-9297 > URL: https://issues.apache.org/jira/browse/NIFI-9297 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation Website >Affects Versions: 1.14.0 >Reporter: Mathew Kapkiai >Priority: Minor > Labels: documentation > Fix For: 1.14.0 > > > Documentation of ListSFTP processor for Listing Strategy property by > "Tracking Entities" has typo in the following bolded line: > "This strategy can pick entities having old timestamp that can *be missed > with 'Tracing Timestamps'.* > Works even when multiple subdirectories are being written at the same time > while listing is running." > > It should have been "*be missed with 'Tracking Timestamps'".* > This can be bring confusion especially to guys who are new to NiFi and they > are trying to understand the processor usage -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-9297) Typo in Documentation
[ https://issues.apache.org/jira/browse/NIFI-9297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mathew Kapkiai updated NIFI-9297: - Description: Documentation of ListSFTP processor for Listing Strategy property by "Tracking Entities" has typo in the following bolded line: "This strategy can pick entities having old timestamp that can *be missed with 'Tracing Timestamps'.* Works even when multiple subdirectories are being written at the same time while listing is running." It should have been "*be missed with 'Tracking Timestamps'".* This can be bring confusion especially to guys who are new to NiFi and they are trying to understand the processor usage was: Documentation of ListSFTP processor for Listing Strategy field by "Tracking Entities" has typo in the following bolded line: "This strategy can pick entities having old timestamp that can *be missed with 'Tracing Timestamps'.* Works even when multiple subdirectories are being written at the same time while listing is running." It should have been "*be missed with 'Tracking Timestamps'".* This can be bring confusion especially to guys who are new to NiFi and they are trying to understand the processor usage > Typo in Documentation > - > > Key: NIFI-9297 > URL: https://issues.apache.org/jira/browse/NIFI-9297 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation Website >Affects Versions: 1.14.0 >Reporter: Mathew Kapkiai >Priority: Minor > Labels: documentation > Fix For: 1.14.0 > > > Documentation of ListSFTP processor for Listing Strategy property by > "Tracking Entities" has typo in the following bolded line: > "This strategy can pick entities having old timestamp that can *be missed > with 'Tracing Timestamps'.* > Works even when multiple subdirectories are being written at the same time > while listing is running." > > It should have been "*be missed with 'Tracking Timestamps'".* > This can be bring confusion especially to guys who are new to NiFi and they > are trying to understand the processor usage -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-9297) Typo in Documentation
[ https://issues.apache.org/jira/browse/NIFI-9297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mathew Kapkiai updated NIFI-9297: - Description: Documentation of ListSFTP processor for Listing Strategy field by "Tracking Entities" has typo in the following bolded line: "This strategy can pick entities having old timestamp that can *be missed with 'Tracing Timestamps'.* Works even when multiple subdirectories are being written at the same time while listing is running." It should have been "*be missed with 'Tracking Timestamps'".* This can be bring confusion especially to guys who are new to NiFi and they are trying to understand the processor usage was: Documentation of ListSFTP processor for Listing Stategy field by "Tracking Entities" has typo in the following bolded line: "This strategy can pick entities having old timestamp that can *be missed with 'Tracing Timestamps'.* Works even when multiple subdirectories are being written at the same time while listing is running." It should have been "*be missed with 'Tracking Timestamps'".* This can be bring confusion especially to guys who are new to NiFi and they are trying to understand the processor usage > Typo in Documentation > - > > Key: NIFI-9297 > URL: https://issues.apache.org/jira/browse/NIFI-9297 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation Website >Affects Versions: 1.14.0 >Reporter: Mathew Kapkiai >Priority: Minor > Labels: documentation > Fix For: 1.14.0 > > > Documentation of ListSFTP processor for Listing Strategy field by "Tracking > Entities" has typo in the following bolded line: > "This strategy can pick entities having old timestamp that can *be missed > with 'Tracing Timestamps'.* > Works even when multiple subdirectories are being written at the same time > while listing is running." > > It should have been "*be missed with 'Tracking Timestamps'".* > This can be bring confusion especially to guys who are new to NiFi and they > are trying to understand the processor usage -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9297) Typo in Documentation
Mathew Kapkiai created NIFI-9297: Summary: Typo in Documentation Key: NIFI-9297 URL: https://issues.apache.org/jira/browse/NIFI-9297 Project: Apache NiFi Issue Type: Bug Components: Documentation Website Affects Versions: 1.14.0 Reporter: Mathew Kapkiai Fix For: 1.14.0 Documentation of ListSFTP processor for Listing Stategy field by "Tracking Entities" has typo in the following bolded line: "This strategy can pick entities having old timestamp that can *be missed with 'Tracing Timestamps'.* Works even when multiple subdirectories are being written at the same time while listing is running." It should have been "*be missed with 'Tracking Timestamps'".* This can be bring confusion especially to guys who are new to NiFi and they are trying to understand the processor usage -- This message was sent by Atlassian Jira (v8.3.4#803005)
