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

ASF GitHub Bot commented on FLINK-9991:
---------------------------------------

xccui commented on issue #6450: [FLINK-9991] [table] Add regexp_replace 
supported in TableAPI and SQL
URL: https://github.com/apache/flink/pull/6450#issuecomment-420317388
 
 
   Hi @TisonKun, if there is no conflict, I usually merge a PR with the 
following steps.
   
   - fetch commits of a PR to a local branch
   - review and do some minor refactorings 
   - squash the commits into a single one and clean up the commit message 
(JIRA, tags, message, adding "This closes #XXXX")
   - pull the latest master
   - rebase to master
   - merge to local master
   - push master to my GitHub repository to trigger a Travis run
   - if tests pass: push master to apache master
   - delete the local PR branch

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Add regexp_replace supported in TableAPI and SQL
> ------------------------------------------------
>
>                 Key: FLINK-9991
>                 URL: https://issues.apache.org/jira/browse/FLINK-9991
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table API & SQL
>            Reporter: vinoyang
>            Assignee: vinoyang
>            Priority: Minor
>              Labels: pull-request-available
>
> regexp_replace is a very userful function to process String. 
>  For example :
> {code:java}
> regexp_replace("foobar", "oo|ar", "") //returns 'fb.'
> {code}
> It is supported as a UDF in Hive, more details please see[1].
> [1]: https://cwiki.apache.org/confluence/display/Hive/LanguageManual+UDF
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to