[jira] [Commented] (AMBARI-22090) INCORROUT in Hive SELECT-JOIN query using Hive View 2.0

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-22090:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12889569/AMBARI-22090_branch-trunk.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:red}-1 core tests{color}.  The test build failed in [contrib/views/hive20|https://builds.apache.org/job/Ambari-trunk-test-patch/12379//artifact/patch-work/testrun_hive20.txt] 

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/12379//console

This message is automatically generated.

> INCORROUT in Hive SELECT-JOIN query using Hive View 2.0
> -------------------------------------------------------
>
>                 Key: AMBARI-22090
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22090
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-views
>            Reporter: Pallav Kulshreshtha
>            Assignee: Pallav Kulshreshtha
>            Priority: Critical
>             Fix For: 2.6.0
>
>         Attachments: AMBARI-22090_branch-trunk.patch
>
>
> TESTCASE:
> DROP TABLE IF EXISTS mydim;
> DROP TABLE IF EXISTS staging;
> CREATE TABLE mydim (
> key int,
> value string,
> status string)
> PARTITIONED BY (last_updated timestamp)
> CLUSTERED BY (key) INTO 5 BUCKETS 
> STORED AS ORC TBLPROPERTIES ('transactional'='true');
> INSERT INTO mydim PARTITION(last_updated) VALUES
> (1, 'value1', 'original value', '2017-01-01'),
> (2, 'value2', 'original value', '2017-01-01'),
> (3, 'value3', 'original value', '2017-01-01'),
> (4, 'value4', 'original value', '2017-01-01'),
> (5, 'value5', 'original value', '2017-01-01');
> CREATE TABLE staging(
> key int,
> value string)
> STORED AS ORC;
> INSERT INTO staging VALUES
> (0, 'value0'),
> (1, 'value1_new');
> – INCORROUT: 1	value1_new	original value	2017-01-01 00:00:00.0	1	value1_new
> – EXPECTED: 1	value1	original value	2017-01-01 00:00:00.0	1	value1_new 
> SELECT *
> FROM mydim,staging
> WHERE mydim.key = staging.key;



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)