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

Thejas M Nair commented on HIVE-8094:
-------------------------------------

Thats right lot of functions don't end up matching ".\*date.\*" . I think this 
would be a common scenario, and likely to break existing scripts.

I propose going with the 3.patch approach that retains backward compatibility. 
Also deprecate the old syntax without LIKE and print a warning asking people to 
use the new syntax. In documentation, we document the new syntax and the old 
syntax as the deprecated syntax. 

[~jdere] What do you think ?

Some of the changes to q.out with the 2.patch applied - 
{code}
--- a/ql/src/test/results/clientpositive/show_functions.q.out
+++ b/ql/src/test/results/clientpositive/show_functions.q.out
@@ -232,7 +232,6 @@ case
 coalesce
 current_database
 decode
-e
 encode
 explode
 first_value
@@ -265,18 +264,211 @@ PREHOOK: query: SHOW FUNCTIONS 'log.*'
 PREHOOK: type: SHOWFUNCTIONS
 POSTHOOK: query: SHOW FUNCTIONS 'log.*'
 POSTHOOK: type: SHOWFUNCTIONS
-log
 log10
 log2
 PREHOOK: query: SHOW FUNCTIONS '.*date.*'
 PREHOOK: type: SHOWFUNCTIONS
 POSTHOOK: query: SHOW FUNCTIONS '.*date.*'
 POSTHOOK: type: SHOWFUNCTIONS
-date_add
-date_sub
-datediff
-to_date
{code}

> add LIKE keyword support for SHOW FUNCTIONS
> -------------------------------------------
>
>                 Key: HIVE-8094
>                 URL: https://issues.apache.org/jira/browse/HIVE-8094
>             Project: Hive
>          Issue Type: Improvement
>    Affects Versions: 0.14.0, 0.13.1
>            Reporter: peter liu
>            Assignee: peter liu
>             Fix For: 0.14.0
>
>         Attachments: HIVE-8094.1.patch, HIVE-8094.2.patch, HIVE-8094.3.patch
>
>
> It would be nice to  add LIKE keyword support for SHOW FUNCTIONS as below, 
> and keep the patterns consistent to the way as SHOW DATABASES, SHOW TABLES.
> bq. SHOW FUNCTIONS LIKE 'foo*';



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

Reply via email to