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

Hive QA commented on HIVE-10378:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12889085/HIVE-10378.1.patch

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

{color:red}ERROR:{color} -1 due to 6 failed/errored test(s), 11062 tests 
executed
*Failed tests:*
{noformat}
TestAccumuloCliDriver - did not produce a TEST-*.xml file (likely timed out) 
(batchId=231)
TestDummy - did not produce a TEST-*.xml file (likely timed out) (batchId=231)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[union_fast_stats]
 (batchId=156)
org.apache.hadoop.hive.cli.TestMiniSparkOnYarnCliDriver.testCliDriver[spark_explainuser_1]
 (batchId=170)
org.apache.hadoop.hive.cli.TestMiniTezCliDriver.testCliDriver[explainanalyze_2] 
(batchId=100)
org.apache.hadoop.hive.cli.TestPerfCliDriver.testCliDriver[query14] 
(batchId=235)
{noformat}

Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/6994/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/6994/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-6994/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 6 tests failed
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12889085 - PreCommit-HIVE-Build

> Hive Update statement set keyword work with lower case only and doesn't give 
> any error if wrong column name specified in the set clause.
> ----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-10378
>                 URL: https://issues.apache.org/jira/browse/HIVE-10378
>             Project: Hive
>          Issue Type: Bug
>          Components: Transactions
>    Affects Versions: 1.0.0, 1.1.0
>         Environment: Hadoop: 2.6.0
> Hive : 1.0.0/1.1.0
> OS:Linux
>            Reporter: Vineet Kandpal
>            Assignee: Oleksiy Sayankin
>             Fix For: 2.3.1
>
>         Attachments: HIVE-10378.1.patch
>
>
> Brief: Hive Update statement set keyword work with lower case only and 
> doesn't give any error if wrong column name specified in the set clause.
> Steps to reproduce: 
> following are the steps performed for the same:
> 1. Create Table with transactional properties.
> create table customer(id int ,name string, email string) clustered by (id) 
> into 2 buckets stored as orc TBLPROPERTIES('transactional'='true')
> 2. Insert data into transactional table:
> insert into table customer values 
> (1,'user1','[email protected]'),(2,'user2','[email protected]'),(3,'user3','[email protected]')
> 3. Search result:
> 0: jdbc:hive2://localhost:10000> select * from customer;
> +--------------+----------------+------------------+--+
> | customer.id  | customer.name  |  customer.email  |
> +--------------+----------------+------------------+--+
> | 2            | user2          | [email protected]  |
> | 3            | user3          | [email protected]  |
> | 1            | user1          | [email protected]  |
> +--------------+----------------+------------------+--+
> 3 rows selected (0.299 seconds)
> 4. Update table column name with some clause In below column name is used in 
> the UPPER case (NAME) and it is not updating the column value :
> 0: jdbc:hive2://localhost:10000> update  customer     set  NAME  = 
> 'notworking'   where id = 1;
> INFO  : Table default.customer stats: [numFiles=10, numRows=3, 
> totalSize=6937, rawDataSize=0]
> No rows affected (20.343 seconds)
> 0: jdbc:hive2://localhost:10000> select * from customer;
> +--------------+----------------+------------------+--+
> | customer.id  | customer.name  |  customer.email  |
> +--------------+----------------+------------------+--+
> | 2            | user2          | [email protected]  |
> | 3            | user3          | [email protected]  |
> | 1            | user1          | [email protected]  |
> +--------------+----------------+------------------+--+
> 3 rows selected (0.321 seconds)
> 5. Update table column name with some clause In below column name is used in 
> the LOWER case (name) and it is updating the column value
> 0: jdbc:hive2://localhost:10000> update  customer     set  name  = 'working'  
>  where id = 1;
> INFO  : Table default.customer stats: [numFiles=11, numRows=3, 
> totalSize=7699, rawDataSize=0]
> No rows affected (19.74 seconds)
> 0: jdbc:hive2://localhost:10000> select * from customer;
> +--------------+----------------+------------------+--+
> | customer.id  | customer.name  |  customer.email  |
> +--------------+----------------+------------------+--+
> | 2            | user2          | [email protected]  |
> | 3            | user3          | [email protected]  |
> | 1            | working        | [email protected]  |
> +--------------+----------------+------------------+--+
> 3 rows selected (0.333 seconds)
> 0: jdbc:hive2://localhost:10000>
> 6. We have also seen that if we put the column name incorrect in set keyword 
> of the update statement it accept the query and execute job. There should 
> validation on the column name used in the set clause.
> 0: jdbc:hive2://localhost:10000> update  customer     set  name_44  = 
> 'working'   where id = 1;
>  
>  



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

Reply via email to