[
https://issues.apache.org/jira/browse/HIVE-21896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Miklos Gergely updated HIVE-21896:
----------------------------------
Description:
According to
[https://cwiki.apache.org/confluence/display/Hive/LanguageManual+DDL#LanguageManualDDL-ShowFunctions]
the currently available functions can be listed like this:
{code:java}
SHOW FUNCTIONS <pattern>;{code}
If the user executes this command, they will get the correct list of functions,
but they will also see this on the standard output:
{code:java}
SHOW FUNCTIONS is deprecated, please use SHOW FUNCTIONS LIKE instead.{code}
If the user uses the
{code:java}
SHOW FUNCTIONS LIKE <pattern>;{code}
command then they will receive the exact same result (though through different
codes). The only difference is that one can get all the function names with
"SHOW FUNCTIONS;", while "SHOW FUNCTIONS LIKE;" returns an exception, so in
this case the pattern is mandatory.
So there should be a decision if we still accept "SHOW FUNCTIONS" without the
"LIKE". My suggestion is to accept it only if there is no pattern. so "SHOW
FUNCTIONS;" is ok, without deprecation message, but "SHOW FUNCTIONS <pattern>"
should throw an exception.
Whatever we decide, we should document it appropriately.
cc [~krishahn]
was:
According to the
[documentation|[https://cwiki.apache.org/confluence/display/Hive/LanguageManual+DDL#LanguageManualDDL-ShowFunctions]]
the currently available functions can be listed like this:
{code:java}
SHOW FUNCTIONS <pattern>;{code}
If the user executes this command, they will get the correct list of functions,
but they will also see this on the standard output:
{code:java}
SHOW FUNCTIONS is deprecated, please use SHOW FUNCTIONS LIKE instead.{code}
If the user uses the
{code:java}
SHOW FUNCTIONS LIKE <pattern>;{code}
command then they will receive the exact same result (though through different
codes). The only difference is that one can get all the function names with
"SHOW FUNCTIONS;", while "SHOW FUNCTIONS LIKE;" returns an exception, so in
this case the pattern is mandatory.
So there should be a decision if we still accept "SHOW FUNCTIONS" without the
"LIKE". My suggestion is to accept it only if there is no pattern. so "SHOW
FUNCTIONS;" is ok, without deprecation message, but "SHOW FUNCTIONS <pattern>"
should throw an exception.
Whatever we decide, we should document it appropriately.
cc [~krishahn]
> SHOW FUNCTIONS / SHOW FUNCTIONS LIKE - clarify
> ----------------------------------------------
>
> Key: HIVE-21896
> URL: https://issues.apache.org/jira/browse/HIVE-21896
> Project: Hive
> Issue Type: Bug
> Components: Hive
> Affects Versions: 3.1.1
> Reporter: Miklos Gergely
> Assignee: Ashutosh Chauhan
> Priority: Major
> Fix For: 4.0.0
>
>
> According to
> [https://cwiki.apache.org/confluence/display/Hive/LanguageManual+DDL#LanguageManualDDL-ShowFunctions]
> the currently available functions can be listed like this:
> {code:java}
> SHOW FUNCTIONS <pattern>;{code}
> If the user executes this command, they will get the correct list of
> functions, but they will also see this on the standard output:
> {code:java}
> SHOW FUNCTIONS is deprecated, please use SHOW FUNCTIONS LIKE instead.{code}
> If the user uses the
> {code:java}
> SHOW FUNCTIONS LIKE <pattern>;{code}
> command then they will receive the exact same result (though through
> different codes). The only difference is that one can get all the function
> names with "SHOW FUNCTIONS;", while "SHOW FUNCTIONS LIKE;" returns an
> exception, so in this case the pattern is mandatory.
> So there should be a decision if we still accept "SHOW FUNCTIONS" without the
> "LIKE". My suggestion is to accept it only if there is no pattern. so "SHOW
> FUNCTIONS;" is ok, without deprecation message, but "SHOW FUNCTIONS
> <pattern>" should throw an exception.
> Whatever we decide, we should document it appropriately.
> cc [~krishahn]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
