[jira] [Created] (HIVE-24971) Floating number parameter types with the hplsql HIVE CLI function.
Krzysztof Mierzejewski created HIVE-24971:
-
Summary: Floating number parameter types with the hplsql HIVE CLI
function.
Key: HIVE-24971
URL: https://issues.apache.org/jira/browse/HIVE-24971
Project: Hive
Issue Type: Bug
Components: hpl/sql
Affects Versions: 2.3.2
Reporter: Krzysztof Mierzejewski
I cannot get floating numbers working as user defined function parameter types
when executed from HIVE CLI with the {{hplsql}} helper function. I have tried
all the means I could think of, including casting to any type available on both
ends ({{float}}, {{double}}, {{number}}, {{numeric}}, {{decimal}}, even
_simple_ kinds and including {{RECORD}} as an argument), but only function
types that seem to support HIVE CLI -> HPL/SQL marshalling are text (string)
and integers. Every time I try to pass a float I get {{null}} on the hplsql end.
Are floating UDF parameter types supported with 2.3.2 when executing a function
from HIVE CLI?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HIVE-24970) Reject location and managed locations in DDL for REMOTE databases.
Naveen Gangam created HIVE-24970: Summary: Reject location and managed locations in DDL for REMOTE databases. Key: HIVE-24970 URL: https://issues.apache.org/jira/browse/HIVE-24970 Project: Hive Issue Type: Sub-task Components: HiveServer2 Affects Versions: 4.0.0 Reporter: Naveen Gangam Assignee: Naveen Gangam This was part of the review feedback from Yongzhi. Creating a followup jira to track this discussion. So, using DB connector for DB, will not create managed tables? @nrg4878 nrg4878 1 hour ago Author Member we don't support create/drop/alter in REMOTE databases at this point. the concepts of managed vs external is not in the picture at this point. When we do support it, it will be application to the hive connectors only (or other hive based connectors like AWS Glue) @nrg4878 nrg4878 2 minutes ago Author Member will file a separate jira for this. Basically, instead of ignoring the location and managedlocation that may be specified for remote database, the grammer needs to not accept any locations in the DDL at all. The argument is fair, why accept something we do not honor or entirely irrelevant for such databases. However, this requires some thought when we have additional connectors for remote hive instances. It might have some relevance in terms of security with Ranger etc. So will create new jira for followup discussion. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HIVE-24969) Predicates are removed by PPD when left semi join followed by lateral view
Zhihua Deng created HIVE-24969:
--
Summary: Predicates are removed by PPD when left semi join
followed by lateral view
Key: HIVE-24969
URL: https://issues.apache.org/jira/browse/HIVE-24969
Project: Hive
Issue Type: Bug
Components: Logical Optimizer
Reporter: Zhihua Deng
Assignee: Zhihua Deng
Step to reproduce：
{code:java}
select count(distinct logItem.triggerId)
from service_stat_log LATERAL VIEW explode(logItems) LogItemTable AS logItem
where logItem.dsp in ('delivery', 'ocpa')
and logItem.iswin = true
and logItem.adid in (
select distinct adId
from ad_info
where subAccountId in (16010, 14863)); {code}
For predicates _logItem.dsp in ('delivery', 'ocpa')_ and _logItem.iswin =
true_ are removed when doing ppd: JOIN -> RS -> LVJ. The JOIN has
candicates: logitem -> [logItem.dsp in ('delivery', 'ocpa'), logItem.iswin =
true]，when pushing them to the RS followed by LVJ, none of them are pushed,
the candicates of logitem are removed finally by default, which cause to the
wrong result.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
