[jira] [Resolved] (HIVE-13875) Beeline ignore where clause when it is the last line of file and missing a EOL hence give wrong query result

["Zhihua Deng (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HIVE-13875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zhihua Deng resolved HIVE-13875.
--------------------------------
    Fix Version/s: 2.0.0
                   1.3.0
       Resolution: Fixed

> Beeline ignore where clause when it is the last line of file and missing a EOL hence give wrong query result
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-13875
>                 URL: https://issues.apache.org/jira/browse/HIVE-13875
>             Project: Hive
>          Issue Type: Bug
>          Components: Beeline
>    Affects Versions: 1.2.1
>            Reporter: Lu Ji
>            Priority: Minor
>             Fix For: 1.3.0, 2.0.0
>
>
> Steps to reproduce:
> Say we have a simple table:
> {code}
> select * from lji.lu_test;
> +---------------+------------------+--+
> | lu_test.name  | lu_test.country  |
> +---------------+------------------+--+
> | john          | us               |
> | hong          | cn               |
> +---------------+------------------+--+
> 2 rows selected (0.04 seconds)
> {code}
> We have a simple query in a file. But note this file missing the last EOL.
> {code}
> cat -A test.hql
> use lji;$
> select * from lu_test$
> where country='us';[lji@~]$
> {code}
> Then if we execute file using both hive CLI and beeline + HS2, we have different result.
> {code}
> [lji@~]$ hive -f test.hql
> WARNING: Use "yarn jar" to launch YARN applications.
> Logging initialized using configuration in file:/etc/hive/2.3.4.7-4/0/hive-log4j.properties
> OK
> Time taken: 1.624 seconds
> OK
> john    us
> Time taken: 1.482 seconds, Fetched: 1 row(s)
> [lji@~]$ beeline -u "jdbc:hive2://XXX:10000/default;principal=hive/_HOST@XXX" -f test.hql
> WARNING: Use "yarn jar" to launch YARN applications.
> Connecting to jdbc:hive2://XXXl:10000/default;principal=hive/_HOST@XXX
> Connected to: Apache Hive (version 1.2.1.2.3.4.7-4)
> Driver: Hive JDBC (version 1.2.1.2.3.4.7-4)
> Transaction isolation: TRANSACTION_REPEATABLE_READ
> 0: jdbc:hive2://XXX> use lji;
> No rows affected (0.06 seconds)
> 0: jdbc:hive2://XXX> select * from lu_test
> 0: jdbc:hive2://XXX> where country='us';+---------------+------------------+--+
> | lu_test.name  | lu_test.country  |
> +---------------+------------------+--+
> | john          | us               |
> | hong          | cn               |
> +---------------+------------------+--+
> 2 rows selected (0.073 seconds)
> 0: jdbc:hive2://XXX>
> Closing: 0: jdbc:hive2://XXX:10000/default;principal=hive/_HOST@XXX
> {code}
> Obviously, beeline gave the wrong result. It ignore the where clause in the last line.
> I know it is quit weird for a file missing the last EOL, but for whatever reason, we kind of having quit some files in this state. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)