Tim Armstrong created IMPALA-7363:
-------------------------------------

             Summary: Spurious error generated by sequence file scanner with 
weird scan range length
                 Key: IMPALA-7363
                 URL: https://issues.apache.org/jira/browse/IMPALA-7363
             Project: IMPALA
          Issue Type: Bug
          Components: Backend
    Affects Versions: Impala 3.1.0
            Reporter: Tim Armstrong


Repro on master
{noformat}
tarmstrong@tarmstrong-box:~/Impala/incubator-impala$ impala-shell.sh
Starting Impala Shell without Kerberos authentication
Connected to localhost:21000
Server version: impalad version 3.1.0-SNAPSHOT DEBUG (build 
cec33fa0ae75392668273d40b5a1bc4bbd7e9e2e)
***********************************************************************************
Welcome to the Impala shell.
(Impala Shell v3.1.0-SNAPSHOT (cec33fa) built on Thu Jul 26 09:50:10 PDT 2018)

To see a summary of a query's progress that updates in real-time, run 'set
LIVE_PROGRESS=1;'.
***********************************************************************************
[localhost:21000] default> use tpch_seq_snap;
Query: use tpch_seq_snap
[localhost:21000] tpch_seq_snap> SET max_scan_range_length=5377;
MAX_SCAN_RANGE_LENGTH set to 5377
[localhost:21000] tpch_seq_snap> select count(*)
                               > from lineitem;
Query: select count(*)
from lineitem
Query submitted at: 2018-07-26 14:10:18 (Coordinator: 
http://tarmstrong-box:25000)
Query progress can be monitored at: 
http://tarmstrong-box:25000/query_plan?query_id=e9428efe173ad2f4:84b66bdb00000000

+----------+
| count(*) |
+----------+
| 5993651  |
+----------+
WARNINGS: SkipText: length is negative
Problem parsing file 
hdfs://localhost:20500/test-warehouse/tpch.lineitem_seq_snap/000000_0 at 
36472193
{noformat}

Found while adding a test for IMPALA-7360



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to