[ 
https://issues.apache.org/jira/browse/NIFI-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15041844#comment-15041844
 ] 

Mark Payne commented on NIFI-1249:
----------------------------------

I started looking at this immediately, and I think it's a great idea. I have 
this just about finished up and I'd like to go ahead and get it into 0.4.0. 
Changes are pretty minimal in terms of impact. The patch will show many files 
changed, but almost all were very trivial changes (add a new override of a 
method, which just calls a different override).

> Allow ReplaceText expression language functions to access matching group 
> values
> -------------------------------------------------------------------------------
>
>                 Key: NIFI-1249
>                 URL: https://issues.apache.org/jira/browse/NIFI-1249
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Joseph Witt
>             Fix For: 0.4.0
>
>
> Chanru from the user's mailing list asked how we'd support a pretty simple 
> use case of converting 
> {quote}
> col1,col2,col3
> 2006,10-01-2004,10may2004
> 2007,15-05-2006,10jun2005
> 2009,8-8-2008,10aug2008
> {quote}
> to this
> {quote}
> col1,col2,col3
> 2006,10-01-2004,2004-05-10
> 2007,15-05-2006,2005-06-10
> 2009,8-8-2008,2008-08-10
> {quote}
> And we can do it today but it is surprising more effort than it should be.  
> The problem is that ReplaceText as-is gets us sooo close.  But what it cannot 
> do is convert the original column three into a formatted Date object which 
> can then be written out as a formatted string.  If it could then this would 
> be easy.  So for example if we extracted each column as a matching group and 
> the replacement value could be
> {code}
> ${ $3:toDate('ddMMMyyy'):format('yyyy/MM/ddd')}
> {code}
> Then we'd be all set.  But right now there is no way to take that third 
> matching group and do anything fun with expression language on it because it 
> is not a subject passed into the EL on which functions could be applied.  If 
> instead we simply added those matching groups as keys/subjects available to 
> the EL then this becomes a quite powerful tool.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to