hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (Jira)" <>
Subject [jira] [Commented] (HIVE-22200) Hash collision may cause column resolution to fail
Date Sat, 14 Sep 2019 09:31:00 GMT


Hive QA commented on HIVE-22200:

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:green}SUCCESS:{color} +1 due to 16753 tests passed

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase

This message is automatically generated.

ATTACHMENT ID: 12980315 - PreCommit-HIVE-Build

> Hash collision may cause column resolution to fail
> --------------------------------------------------
>                 Key: HIVE-22200
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Jesus Camacho Rodriguez
>            Assignee: Jesus Camacho Rodriguez
>            Priority: Critical
>         Attachments: HIVE-22200.patch, HIVE-22200.patch, HIVE-22200.patch
> {{ExprNodeDescUtils.getExprNodeColumnDesc}} extracts the {{ExprNodeColumnDesc}} (column
descriptors) from an expression. In fact, it creates a map from hash to the object itself.
If same hash value is generated for two different objects, this will result in a clash in
the map and some expressions not being part of its values.

This message was sent by Atlassian Jira

View raw message