[jira] [Commented] (NIFI-2071) Support repeating capture groups in ExtractText
[ https://issues.apache.org/jira/browse/NIFI-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15520678#comment-15520678 ] ASF GitHub Bot commented on NIFI-2071: -- Github user pvillard31 commented on the issue: https://github.com/apache/nifi/pull/1050 Thanks @ijokarumawak for this review. I think I've addressed your comments, let me know if you want me to squash the commits. > Support repeating capture groups in ExtractText > --- > > Key: NIFI-2071 > URL: https://issues.apache.org/jira/browse/NIFI-2071 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joey Frazee >Assignee: Pierre Villard > Fix For: 1.1.0 > > > ExtractText doesn't currently support repeating capture groups so any > repeating patterns have to specified by hand and can only be repeated a fixed > number of times. > I think this is because it only uses find() and not findAll() in its pattern > matching [1]. > 1. > https://github.com/apache/nifi/blob/1bd2cf0d09a7111bcecffd0f473aa71c25a69845/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ExtractText.java#L324 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi issue #1050: NIFI-2071 - Support repeating capture groups in ExtractTex...
Github user pvillard31 commented on the issue: https://github.com/apache/nifi/pull/1050 Thanks @ijokarumawak for this review. I think I've addressed your comments, let me know if you want me to squash the commits. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi issue #721: Nifi 2398 - Apache Ignite Get Processor
Github user pvillard31 commented on the issue: https://github.com/apache/nifi/pull/721 @mans2singh you are using the constant defined L62 in the annotation L55 as the attribute name. I believe this is a mistake but correct me if I'm wrong. java @WritesAttribute(attribute = GetIgniteCache.IGNITE_GET_FAILED_MISSING_KEY_MESSAGE, ... --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi issue #1057: NIFI-2816 - Clean typos across the code
Github user pvillard31 commented on the issue: https://github.com/apache/nifi/pull/1057 @trixpan, to be honest, about classes/methods renaming I'll concede to our PMC authority. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-2816) The great typo cleanup
[ https://issues.apache.org/jira/browse/NIFI-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15520711#comment-15520711 ] ASF GitHub Bot commented on NIFI-2816: -- Github user pvillard31 commented on the issue: https://github.com/apache/nifi/pull/1057 @trixpan, to be honest, about classes/methods renaming I'll concede to our PMC authority. > The great typo cleanup > -- > > Key: NIFI-2816 > URL: https://issues.apache.org/jira/browse/NIFI-2816 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Andre >Assignee: Andre > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2816) The great typo cleanup
[ https://issues.apache.org/jira/browse/NIFI-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15520731#comment-15520731 ] ASF GitHub Bot commented on NIFI-2816: -- Github user trixpan commented on the issue: https://github.com/apache/nifi/pull/1057 @joewitt , @bbende suggestions? comments? > The great typo cleanup > -- > > Key: NIFI-2816 > URL: https://issues.apache.org/jira/browse/NIFI-2816 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Andre >Assignee: Andre > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi issue #1057: NIFI-2816 - Clean typos across the code
Github user trixpan commented on the issue: https://github.com/apache/nifi/pull/1057 @joewitt , @bbende suggestions? comments? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (NIFI-2819) ModifyBytes should support expression language
n h created NIFI-2819: - Summary: ModifyBytes should support expression language Key: NIFI-2819 URL: https://issues.apache.org/jira/browse/NIFI-2819 Project: Apache NiFi Issue Type: Improvement Components: Extensions Affects Versions: 1.0.0 Reporter: n h Fix For: 1.1.0 Add expression language support to "Start Offset" and "End Offset" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2819) Improve ModifyBytes (Add expression language support)
[ https://issues.apache.org/jira/browse/NIFI-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] n h updated NIFI-2819: -- Summary: Improve ModifyBytes (Add expression language support) (was: ModifyBytes should support expression language) > Improve ModifyBytes (Add expression language support) > - > > Key: NIFI-2819 > URL: https://issues.apache.org/jira/browse/NIFI-2819 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 1.0.0 >Reporter: n h > Fix For: 1.1.0 > > > Add expression language support to "Start Offset" and "End Offset" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-1971) Create a batch capable pseudo-whois ("netcat") enrichment Processor
[
https://issues.apache.org/jira/browse/NIFI-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15520845#comment-15520845
]
ASF GitHub Bot commented on NIFI-1971:
--
Github user pvillard31 commented on the issue:
https://github.com/apache/nifi/pull/858
@trixpan thanks for the changes, LGTM, full build with contrib-check,
tested the processor with various configurations. Unless someone else wants to
have a look, I'll merge it in master soon.
> Create a batch capable pseudo-whois ("netcat") enrichment Processor
> ---
>
> Key: NIFI-1971
> URL: https://issues.apache.org/jira/browse/NIFI-1971
> Project: Apache NiFi
> Issue Type: Improvement
>Affects Versions: 1.0.0, 0.7.0
>Reporter: Andre
>Assignee: Andre
> Fix For: 1.1.0
>
>
> While the QueryDNS created can be used on low to medium volume enrichment and
> to licensed DNS based lookups (e.g. commercial use of SpamHaus) many
> enrichment providers prefer the use of bulk queries using pseudo whois API
> (a.k.a. netcat interface).
> as documented
> [here|https://www.shadowserver.org/wiki/pmwiki.php/Services/IP-BGP#toc6] the
> bulk interfaces work by connecting to port 43/TCP and sending a payload like:
> {code}
> begin origin
> 4.5.4.3
> 17.112.152.32
> 208.77.188.166
> end
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] nifi issue #858: NIFI-1971 - Introduce QueryWhois processor
Github user pvillard31 commented on the issue: https://github.com/apache/nifi/pull/858 @trixpan thanks for the changes, LGTM, full build with contrib-check, tested the processor with various configurations. Unless someone else wants to have a look, I'll merge it in master soon. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (NIFI-2820) Filtering "Data Provenance search" with "Alternate Identifier URI" returns only event of type "ADDINFO"
n h created NIFI-2820: - Summary: Filtering "Data Provenance search" with "Alternate Identifier URI" returns only event of type "ADDINFO" Key: NIFI-2820 URL: https://issues.apache.org/jira/browse/NIFI-2820 Project: Apache NiFi Issue Type: Bug Components: Core Framework Reporter: n h Fix For: 1.1.0 Setting: bdfs.provenance.repository.indexed.fields=EventType, FlowFileUUID, Filename, ProcessorID, Relationship, AlternateIdentifierURI run this scenario in 2 instances of nifi (nifi_1, nifi_2): 1. generate a flowfile in nifi_1. 1. adding "alternate.identifier" attribute using UpdateAttribute. (name=alternate.identifier, value=data:xyz) 2. sending the flowfile using site-to-site to nifi_2 (another remote instance) for processing (using a remote data which only nifi_2 has access to it) 3. send back the result flowfile from nifi_2 to nifi_1 4. search for flowfile event using "alternate.identifier=data:xyz" Expected results: a list will all events that has "alternate.identifier=data:xyz" Actual result:list has only one item : "ADDINFO" event -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2820) Filtering "Data Provenance search" with "Alternate Identifier URI" returns only event of type "ADDINFO"
[ https://issues.apache.org/jira/browse/NIFI-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] n h updated NIFI-2820: -- Description: Setting: bdfs.provenance.repository.indexed.fields=EventType, FlowFileUUID, Filename, ProcessorID, Relationship, AlternateIdentifierURI run this scenario in 2 instances of nifi (nifi_1, nifi_2): 1. generate a flowfile in nifi_1. 2. adding "alternate.identifier" attribute using UpdateAttribute. (name=alternate.identifier, value=data:xyz) 3. sending the flowfile using site-to-site to nifi_2 (another remote instance) for processing (using a remote data which only nifi_2 has access to it) 4. send back the result flowfile from nifi_2 to nifi_1 5. search for flowfile event using "alternate.identifier=data:xyz" Expected results: a list will all events that has "alternate.identifier=data:xyz" Actual result:list has only one item : "ADDINFO" event was: Setting: bdfs.provenance.repository.indexed.fields=EventType, FlowFileUUID, Filename, ProcessorID, Relationship, AlternateIdentifierURI run this scenario in 2 instances of nifi (nifi_1, nifi_2): 1. generate a flowfile in nifi_1. 1. adding "alternate.identifier" attribute using UpdateAttribute. (name=alternate.identifier, value=data:xyz) 2. sending the flowfile using site-to-site to nifi_2 (another remote instance) for processing (using a remote data which only nifi_2 has access to it) 3. send back the result flowfile from nifi_2 to nifi_1 4. search for flowfile event using "alternate.identifier=data:xyz" Expected results: a list will all events that has "alternate.identifier=data:xyz" Actual result:list has only one item : "ADDINFO" event > Filtering "Data Provenance search" with "Alternate Identifier URI" returns > only event of type "ADDINFO" > --- > > Key: NIFI-2820 > URL: https://issues.apache.org/jira/browse/NIFI-2820 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: n h > Fix For: 1.1.0 > > > Setting: > bdfs.provenance.repository.indexed.fields=EventType, FlowFileUUID, Filename, > ProcessorID, Relationship, AlternateIdentifierURI > run this scenario in 2 instances of nifi (nifi_1, nifi_2): > 1. generate a flowfile in nifi_1. > 2. adding "alternate.identifier" attribute using UpdateAttribute. > (name=alternate.identifier, value=data:xyz) > 3. sending the flowfile using site-to-site to nifi_2 (another remote > instance) for processing (using a remote data which only nifi_2 has access to > it) > 4. send back the result flowfile from nifi_2 to nifi_1 > 5. search for flowfile event using "alternate.identifier=data:xyz" > Expected results: a list will all events that has > "alternate.identifier=data:xyz" > Actual result:list has only one item : "ADDINFO" event -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2820) Filtering "Data Provenance search" with "Alternate Identifier URI" returns only event of type "ADDINFO"
[ https://issues.apache.org/jira/browse/NIFI-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] n h updated NIFI-2820: -- Description: Setting: bdfs.provenance.repository.indexed.fields=EventType, FlowFileUUID, Filename, ProcessorID, Relationship, AlternateIdentifierURI run this scenario in 2 instances of nifi (nifi_1, nifi_2): 1. generate a flowfile in nifi_1. 2. adding "alternate.identifier" attribute using UpdateAttribute. (name=alternate.identifier, value=data:xyz) 3. sending the flowfile using site-to-site to nifi_2 (another remote instance) for processing (using a remote data which only nifi_2 has access to it) 4. send back the result flowfile from nifi_2 to nifi_1 5. in nifi_1, search for all events using "alternate.identifier=data:xyz" Expected results: a list will all events that has "alternate.identifier=data:xyz" Actual result:list has only one item : "ADDINFO" event was: Setting: bdfs.provenance.repository.indexed.fields=EventType, FlowFileUUID, Filename, ProcessorID, Relationship, AlternateIdentifierURI run this scenario in 2 instances of nifi (nifi_1, nifi_2): 1. generate a flowfile in nifi_1. 2. adding "alternate.identifier" attribute using UpdateAttribute. (name=alternate.identifier, value=data:xyz) 3. sending the flowfile using site-to-site to nifi_2 (another remote instance) for processing (using a remote data which only nifi_2 has access to it) 4. send back the result flowfile from nifi_2 to nifi_1 5. search for flowfile event using "alternate.identifier=data:xyz" Expected results: a list will all events that has "alternate.identifier=data:xyz" Actual result:list has only one item : "ADDINFO" event > Filtering "Data Provenance search" with "Alternate Identifier URI" returns > only event of type "ADDINFO" > --- > > Key: NIFI-2820 > URL: https://issues.apache.org/jira/browse/NIFI-2820 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: n h > Fix For: 1.1.0 > > > Setting: > bdfs.provenance.repository.indexed.fields=EventType, FlowFileUUID, Filename, > ProcessorID, Relationship, AlternateIdentifierURI > run this scenario in 2 instances of nifi (nifi_1, nifi_2): > 1. generate a flowfile in nifi_1. > 2. adding "alternate.identifier" attribute using UpdateAttribute. > (name=alternate.identifier, value=data:xyz) > 3. sending the flowfile using site-to-site to nifi_2 (another remote > instance) for processing (using a remote data which only nifi_2 has access to > it) > 4. send back the result flowfile from nifi_2 to nifi_1 > 5. in nifi_1, search for all events using "alternate.identifier=data:xyz" > Expected results: a list will all events that has > "alternate.identifier=data:xyz" > Actual result:list has only one item : "ADDINFO" event -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2820) Filtering "Data Provenance search" with "Alternate Identifier URI" returns only event of type "ADDINFO"
[ https://issues.apache.org/jira/browse/NIFI-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] n h updated NIFI-2820: -- Description: Setting: bdfs.provenance.repository.indexed.fields=EventType, FlowFileUUID, Filename, ProcessorID, Relationship, AlternateIdentifierURI run this scenario in 2 instances of nifi (nifi_1, nifi_2): 1. generate a flowfile in nifi_1. 2. adding "alternate.identifier" attribute using UpdateAttribute. (name=alternate.identifier, value=data:xyz) 3. sending the flowfile using site-to-site to nifi_2 (another remote instance) for processing (using a remote data which only nifi_2 has access to it) 4. send back the result flowfile from nifi_2 to nifi_1 5. in nifi_1, search for all events using "alternate.identifier=data:xyz" Expected results: a list of all events that satisfies the condition: "alternate.identifier=data:xyz" Actual result:list has only one item : "ADDINFO" event was: Setting: bdfs.provenance.repository.indexed.fields=EventType, FlowFileUUID, Filename, ProcessorID, Relationship, AlternateIdentifierURI run this scenario in 2 instances of nifi (nifi_1, nifi_2): 1. generate a flowfile in nifi_1. 2. adding "alternate.identifier" attribute using UpdateAttribute. (name=alternate.identifier, value=data:xyz) 3. sending the flowfile using site-to-site to nifi_2 (another remote instance) for processing (using a remote data which only nifi_2 has access to it) 4. send back the result flowfile from nifi_2 to nifi_1 5. in nifi_1, search for all events using "alternate.identifier=data:xyz" Expected results: a list will all events that has "alternate.identifier=data:xyz" Actual result:list has only one item : "ADDINFO" event > Filtering "Data Provenance search" with "Alternate Identifier URI" returns > only event of type "ADDINFO" > --- > > Key: NIFI-2820 > URL: https://issues.apache.org/jira/browse/NIFI-2820 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: n h > Fix For: 1.1.0 > > > Setting: > bdfs.provenance.repository.indexed.fields=EventType, FlowFileUUID, Filename, > ProcessorID, Relationship, AlternateIdentifierURI > run this scenario in 2 instances of nifi (nifi_1, nifi_2): > 1. generate a flowfile in nifi_1. > 2. adding "alternate.identifier" attribute using UpdateAttribute. > (name=alternate.identifier, value=data:xyz) > 3. sending the flowfile using site-to-site to nifi_2 (another remote > instance) for processing (using a remote data which only nifi_2 has access to > it) > 4. send back the result flowfile from nifi_2 to nifi_1 > 5. in nifi_1, search for all events using "alternate.identifier=data:xyz" > Expected results: a list of all events that satisfies the condition: > "alternate.identifier=data:xyz" > Actual result:list has only one item : "ADDINFO" event -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2820) Filtering "Data Provenance search" with "Alternate Identifier URI" returns only event of type "ADDINFO"
[ https://issues.apache.org/jira/browse/NIFI-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] n h updated NIFI-2820: -- Description: Setting: bdfs.provenance.repository.indexed.fields=EventType, FlowFileUUID, Filename, ProcessorID, Relationship, AlternateIdentifierURI run this scenario in 2 instances of nifi (nifi_1, nifi_2): 1. generate a flowfile in nifi_1. 2. adding "alternate.identifier" attribute using UpdateAttribute. (name=alternate.identifier, value=data:xyz) 3. sending the flowfile using site-to-site to nifi_2 (another remote instance) for processing (using a remote data which only nifi_2 has access to it) 4. send back the result flowfile from nifi_2 to nifi_1 5. in nifi_1, in data provenance window, search for all events using "alternate.identifier=data:xyz" Expected results: a list of all events that satisfies the condition: "alternate.identifier=data:xyz" Actual result:list has only one item : "ADDINFO" event was: Setting: bdfs.provenance.repository.indexed.fields=EventType, FlowFileUUID, Filename, ProcessorID, Relationship, AlternateIdentifierURI run this scenario in 2 instances of nifi (nifi_1, nifi_2): 1. generate a flowfile in nifi_1. 2. adding "alternate.identifier" attribute using UpdateAttribute. (name=alternate.identifier, value=data:xyz) 3. sending the flowfile using site-to-site to nifi_2 (another remote instance) for processing (using a remote data which only nifi_2 has access to it) 4. send back the result flowfile from nifi_2 to nifi_1 5. in nifi_1, search for all events using "alternate.identifier=data:xyz" Expected results: a list of all events that satisfies the condition: "alternate.identifier=data:xyz" Actual result:list has only one item : "ADDINFO" event > Filtering "Data Provenance search" with "Alternate Identifier URI" returns > only event of type "ADDINFO" > --- > > Key: NIFI-2820 > URL: https://issues.apache.org/jira/browse/NIFI-2820 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: n h > Fix For: 1.1.0 > > > Setting: > bdfs.provenance.repository.indexed.fields=EventType, FlowFileUUID, Filename, > ProcessorID, Relationship, AlternateIdentifierURI > run this scenario in 2 instances of nifi (nifi_1, nifi_2): > 1. generate a flowfile in nifi_1. > 2. adding "alternate.identifier" attribute using UpdateAttribute. > (name=alternate.identifier, value=data:xyz) > 3. sending the flowfile using site-to-site to nifi_2 (another remote > instance) for processing (using a remote data which only nifi_2 has access to > it) > 4. send back the result flowfile from nifi_2 to nifi_1 > 5. in nifi_1, in data provenance window, search for all events using > "alternate.identifier=data:xyz" > Expected results: a list of all events that satisfies the condition: > "alternate.identifier=data:xyz" > Actual result:list has only one item : "ADDINFO" event -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2820) Filtering "Data Provenance search" with "Alternate Identifier URI" returns only event of type "ADDINFO"
[ https://issues.apache.org/jira/browse/NIFI-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] n h updated NIFI-2820: -- Affects Version/s: 1.0.0 > Filtering "Data Provenance search" with "Alternate Identifier URI" returns > only event of type "ADDINFO" > --- > > Key: NIFI-2820 > URL: https://issues.apache.org/jira/browse/NIFI-2820 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.0.0 >Reporter: n h > Fix For: 1.1.0 > > > Setting: > bdfs.provenance.repository.indexed.fields=EventType, FlowFileUUID, Filename, > ProcessorID, Relationship, AlternateIdentifierURI > run this scenario in 2 instances of nifi (nifi_1, nifi_2): > 1. generate a flowfile in nifi_1. > 2. adding "alternate.identifier" attribute using UpdateAttribute. > (name=alternate.identifier, value=data:xyz) > 3. sending the flowfile using site-to-site to nifi_2 (another remote > instance) for processing (using a remote data which only nifi_2 has access to > it) > 4. send back the result flowfile from nifi_2 to nifi_1 > 5. in nifi_1, in data provenance window, search for all events using > "alternate.identifier=data:xyz" > Expected results: a list of all events that satisfies the condition: > "alternate.identifier=data:xyz" > Actual result:list has only one item : "ADDINFO" event -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2820) Filtering "Data Provenance search" with "Alternate Identifier URI" returns only event of type "ADDINFO"
[ https://issues.apache.org/jira/browse/NIFI-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] n h updated NIFI-2820: -- Affects Version/s: (was: 1.0.0) 0.7.0 > Filtering "Data Provenance search" with "Alternate Identifier URI" returns > only event of type "ADDINFO" > --- > > Key: NIFI-2820 > URL: https://issues.apache.org/jira/browse/NIFI-2820 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 0.7.0 >Reporter: n h > Fix For: 1.1.0 > > > Setting: > bdfs.provenance.repository.indexed.fields=EventType, FlowFileUUID, Filename, > ProcessorID, Relationship, AlternateIdentifierURI > run this scenario in 2 instances of nifi (nifi_1, nifi_2): > 1. generate a flowfile in nifi_1. > 2. adding "alternate.identifier" attribute using UpdateAttribute. > (name=alternate.identifier, value=data:xyz) > 3. sending the flowfile using site-to-site to nifi_2 (another remote > instance) for processing (using a remote data which only nifi_2 has access to > it) > 4. send back the result flowfile from nifi_2 to nifi_1 > 5. in nifi_1, in data provenance window, search for all events using > "alternate.identifier=data:xyz" > Expected results: a list of all events that satisfies the condition: > "alternate.identifier=data:xyz" > Actual result:list has only one item : "ADDINFO" event -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi issue #239: Nifi 1540 - AWS Kinesis Get and Put Processors
Github user simplesteph commented on the issue: https://github.com/apache/nifi/pull/239 +1 on separate nar for now. In the short term that's how users (like me) may benefit from it! Should be a quick win as well --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi issue #1050: NIFI-2071 - Support repeating capture groups in ExtractTex...
Github user ijokarumawak commented on the issue: https://github.com/apache/nifi/pull/1050 I confirmed that my comments are addressed. Please squash the commits then I'll merge it. Thanks @pvillard31 !! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-2071) Support repeating capture groups in ExtractText
[ https://issues.apache.org/jira/browse/NIFI-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15521801#comment-15521801 ] ASF GitHub Bot commented on NIFI-2071: -- Github user ijokarumawak commented on the issue: https://github.com/apache/nifi/pull/1050 I confirmed that my comments are addressed. Please squash the commits then I'll merge it. Thanks @pvillard31 !! > Support repeating capture groups in ExtractText > --- > > Key: NIFI-2071 > URL: https://issues.apache.org/jira/browse/NIFI-2071 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joey Frazee >Assignee: Pierre Villard > Fix For: 1.1.0 > > > ExtractText doesn't currently support repeating capture groups so any > repeating patterns have to specified by hand and can only be repeated a fixed > number of times. > I think this is because it only uses find() and not findAll() in its pattern > matching [1]. > 1. > https://github.com/apache/nifi/blob/1bd2cf0d09a7111bcecffd0f473aa71c25a69845/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ExtractText.java#L324 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
