[
https://issues.apache.org/jira/browse/NIFI-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372323#comment-14372323
]
ASF subversion and git services commented on NIFI-399:
------------------------------------------------------
Commit 3410197b7d88444de5c6f74622d67a1b0cc39e6a in incubator-nifi's branch
refs/heads/NIFI-353 from [~mcgilman]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=3410197 ]
Squashed commit of the following:
commit e88ed13d8d7221f5a91588f553d039d3917494be
Merge: 93b361e 3f36236
Author: Mark Payne <[email protected]>
Date: Fri Mar 20 09:11:39 2015 -0400
Merge branch 'inputstream-callback-protection' of
https://github.com/rowolabi/incubator-nifi into develop
commit 93b361e69bd046d6b2e0f561d8b2231a4505b6a9
Merge: c9eb237 a6740a6
Author: Mark Payne <[email protected]>
Date: Thu Mar 19 11:49:11 2015 -0400
Merge branch 'develop' of
http://git-wip-us.apache.org/repos/asf/incubator-nifi into develop
commit c9eb237895a94a27fc6f760b82b16ac3e2cdab95
Author: Mark Payne <[email protected]>
Date: Thu Mar 19 11:40:01 2015 -0400
NIFI-443: Removed stopFunnel from ProcessGroup because we don't want to
allow it
commit 8b911c5aab2a4b8283510a3423e3c8962a533b96
Author: Mark Payne <[email protected]>
Date: Thu Mar 19 11:04:46 2015 -0400
NIFI-443: Always start funnels when added to process group, even when
autoResumeState is false
commit a6740a6e2c87f4c994d305db55c0777dc4f99976
Author: joewitt <[email protected]>
Date: Thu Mar 19 01:21:32 2015 -0400
NIFI-399 addressed items in the ticket
commit ad18853b589d80331e2f4574bce35d79bce09c28
Author: joewitt <[email protected]>
Date: Wed Mar 18 10:59:13 2015 -0400
NIFI-399 initial port
commit 3f3623647367421cd8eb318668144aca1afb9bf4
Author: Bobby Owolabi <[email protected]>
Date: Thu Mar 19 01:43:17 2015 -0400
NIFI-396 reverting accidentially modified whitespace in
TestStandardProcessSession
commit cd183be4410bdc88de7d3a0026452ab62eb10621
Author: Bobby Owolabi <[email protected]>
Date: Thu Mar 19 01:18:22 2015 -0400
NIFI-396 updated the javadocs of ProcessSession to reflect that a
FlowFileAccessExcpetion will be thrown if an Input/Output Stream is attempted
to be accessed after the callback is executed.
commit e2760f8c980583d285137134e05c435c930fb4d2
Author: Bobby Owolabi <[email protected]>
Date: Thu Mar 19 00:54:24 2015 -0400
NIFI-396 added a DisableOnCloseInputStream class; modified
StandardProcessSession to prevent access of the Input/OutputStreams after
callbacks have been executed; updated tests
commit 7272d0df58c23d099809bf96993b55d73c617476
Author: Bobby Owolabi <[email protected]>
Date: Wed Mar 18 23:30:57 2015 -0400
NIFI-396 created tests to demonstrate the situations where the
ProcessSession throws an Exception and where it doesn't after it returns from
the callback
commit eb5ec703ba0d5c188822a37f6d7eed14af56a594
Author: Oscar de la Pena <[email protected]>
Date: Thu Mar 19 10:10:09 2015 +0800
Fixes incorrect messages count in Provenance reporter. Adds Unit test to
verify fix
> Rename EvaluateRegularExpression to ExtractText and optimize
> ------------------------------------------------------------
>
> Key: NIFI-399
> URL: https://issues.apache.org/jira/browse/NIFI-399
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Joseph Witt
> Assignee: Joseph Witt
> Labels: deprecation
> Fix For: 0.1.0
>
> Attachments: NIFI-399.patch
>
>
> The processor EvaluateRegularExpression enables some cool extraction of text
> from data. It currently limits matching results to a single matching result.
> It should be updated to allow multiple capture groups per matching term. It
> can keep the current behavior. But can also add inclusion of all matching
> groups 0..n as an index appended to the basename of the attribute.
> In addition the name of this processor (and possibly its tags) needs to be
> updated. The processor is used to extract text from a given document. The
> name should be 'ExtractText'. We can deprecate the old processor in 0.1.0
> and in 0.2.0 pull it out.
> In addition this processor should:
> - Precompile all patterns when the processor is scheduled to run.
> - Create memory buffers that do not exceed the minimum of flow file content
> or max buffer size specified
> - Support more than 1 capturing groups. The default behavior of storing
> capture group 1 at the given name is good. But there is also benefit to
> supporting multiple capture groups in a single execution.
> - Allow the user to specify the maximum length of a capturing group value
> This also prompts the need for a StandardValidator which allows for creation
> of a validator that does a bounds check on a given DataSize.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
