[
https://issues.apache.org/jira/browse/HIVE-24883?focusedWorklogId=582427&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-582427
]
ASF GitHub Bot logged work on HIVE-24883:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 14/Apr/21 12:19
Start Date: 14/Apr/21 12:19
Worklog Time Spent: 10m
Work Description: zabetak commented on pull request #2071:
URL: https://github.com/apache/hive/pull/2071#issuecomment-819474363
> > 3. What are the semantics of the comparisons? Are we following the SQL
standard?
>
> I am not aware of any SQL standards for complex type comparison. The join
ordering used follows the normal comparison, equality is check from left to
right fields.
The SQL standard covers comparisons for STRUCT and ARRAY types. LIST are not
covered but they should be identical to ARRAY. MAP type does not exist in the
standard but it is basically a specialization of MULTISET type (unordered
collection).
From what I can see in the PR most of the things so far are aligned with the
standard (speaking only for the equals operator (`=`) ) except the MAP type.
From my understanding equality between maps should not rely at all on the order
of the elements in the data structure.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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
Issue Time Tracking
-------------------
Worklog Id: (was: 582427)
Time Spent: 2h (was: 1h 50m)
> Add support for complex types columns in Hive Joins
> ---------------------------------------------------
>
> Key: HIVE-24883
> URL: https://issues.apache.org/jira/browse/HIVE-24883
> Project: Hive
> Issue Type: Bug
> Components: Hive
> Affects Versions: 4.0.0
> Reporter: mahesh kumar behera
> Assignee: mahesh kumar behera
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> Hive fails to execute joins on array type columns as the comparison functions
> are not able to handle array type columns.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
