FAQ
Dan,

    This is indeed a bug. I'll file an isssue.

    "The query doesn't return any error when run in the impala-shell, it
simply prints the query that's being run (even though --quiet was
specified) and again the command prompt."
    -- Could you copy and paste the shell output? The quiet flag works on my
end.

Thanks,

Ishaan

On Sat, Aug 3, 2013 at 6:18 AM, wrote:

Hi guys,

We've run into a problem with IN statements while migrating a system over
from MySQL and MSSQL to Hadoop (using Impala 1.1).

A legacy analysis tool uses huge IN statements instead of table joins
(which we can't do anything about at this point).

The result is IN statements with many thousands of values. While this
works in MySQL, MSSQL and HIVE, it fails in Impala. The magic number seems
to be around 2800.

E.g. select count(*) from table where id in (1,2,3, ... 2801)

The query doesn't return any error when run in the impala-shell, it simply
prints the query that's being run (even though --quiet was specified) and
again the command prompt.

When run in DB Visualizer, the error is:

13:45:18 [SELECT - 0 row(s), 0.000 secs] [Error Code: 0, SQL State:
HY000] Couldn't open transport for [server]:22000(connect() failed:
Connection refused)
... 1 statement(s) executed, 0 row(s) affected, exec/fetch time:
0.000/0.000 sec [0 successful, 0 warnings, 1 errors]


Here's the last bit of the Impala log file:

2:45:12.602 PM INFO client-cache.cc:98

CreateClient(): adding new client for [server]:22000

2:45:12.603 PMINFO thrift-util.cc:97

TSocket::open() connect() <Host: [server] Port: 22000>Connection refused

2:45:12.608 PMINFO status.cc:44

Couldn't open transport for [server]:22000(connect() failed: Connection refused)
@ 0x83af5d (unknown)
@ 0x818576 (unknown)
@ 0x7c148d (unknown)
@ 0x7c1986 (unknown)

@ 0x7d2f8a (unknown)
@ 0x7cd458 (unknown)
@ 0x7d0efc (unknown)
@ 0x7f81af (unknown)
@ 0x7f9586 (unknown)
@ 0x9a7264 (unknown)

@ 0x3f42c07851 (unknown)
@ 0x3f428e811d (unknown)

2:45:12.611 PM INFOcoordinator.cc:870

Cancel() query_id=3244fb242eb2d553:3b5f2183c2a6fea0

2:45:12.615 PMINFO plan-fragment-executor.cc:419

Cancel(): instance_id=3244fb242eb2d553:3b5f2183c2a6fea1

2:45:12.619 PMINFO data-stream-mgr.cc:302

cancelling all streams for fragment=3244fb242eb2d553:3b5f2183c2a6fea1

2:45:12.623 PMINFO data-stream-mgr.cc:170

cancelled stream: fragment_instance_id_=3244fb242eb2d553:3b5f2183c2a6fea1 node_id=2

2:45:12.627 PM INFOimpala-server.cc:951

UnregisterQuery(): query_id=3244fb242eb2d553:3b5f2183c2a6fea0

2:45:12.631 PMINFO impala-server.cc:1033

Cancel(): query_id=3244fb242eb2d553:3b5f2183c2a6fea0

2:45:12.640 PMINFO data-stream-mgr.cc:274

DeregisterRecvr(): fragment_instance_id=3244fb242eb2d553:3b5f2183c2a6fea1, node=2




Any ideas?

Thanks

Search Discussions

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupimpala-user @
categorieshadoop
postedAug 6, '13 at 4:39p
activeAug 6, '13 at 4:39p
posts1
users1
websitecloudera.com
irc#hadoop

1 user in discussion

Ishaan Joshi: 1 post

People

Translate

site design / logo © 2022 Grokbase