[
https://issues.apache.org/jira/browse/IMPALA-12628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17798264#comment-17798264
]
ASF subversion and git services commented on IMPALA-12628:
----------------------------------------------------------
Commit 0aa1f3a5feb052f7c1bccb771f40fdbc28b8ed05 in impala's branch
refs/heads/master from Zoltan Borok-Nagy
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=0aa1f3a5f ]
IMPALA-12628: iceberg negative test fail in non-HDFS environments
There's a HIVE_QUERY section in iceberg-negative.test. Such sections
use Hive to execute statements. In non-HDFS environments like S3,
Ozone, etc. Hive is not configured properly, so we cannot use
it.
This patch adds the '---- IS_HDFS_ONLY' section to the relevant
test blocks (The HIVE_QUERY that creates the table, and the
Impala test that checks an error message).
Change-Id: I7987724f11d0c88d09577f52294ecc10d8ce39ce
Reviewed-on: http://gerrit.cloudera.org:8080/20812
Reviewed-by: Csaba Ringhofer <csringho...@cloudera.com>
Tested-by: Zoltan Borok-Nagy <borokna...@cloudera.com>
> iceberg negative test fail saying can't connect but there is no obvious
> server crash
> ------------------------------------------------------------------------------------
>
> Key: IMPALA-12628
> URL: https://issues.apache.org/jira/browse/IMPALA-12628
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 1.4.2
> Reporter: Andrew Sherman
> Assignee: Zoltán Borók-Nagy
> Priority: Critical
>
> This is mysterious, I'm capturing as far as I've got.
> The run of iceberg-negative.test fails in the middle.
> Did the server crash? I haven't seen that yet.
> {code}
> -- executing against localhost:21000
> update functional_parquet.iceberg_int_partitioned set input__file__name =
> 'void';
> -- executing against localhost:21000
> update functional_parquet.iceberg_int_partitioned set file__position = 42;
> -- connecting to localhost:11050 with impyla
> -- 2023-12-13 09:57:48,028 INFO MainThread: Could not connect to ('::1',
> 11050, 0, 0)
> Traceback (most recent call last):
> File
> "/data/jenkins/workspace/impala-asf-master-core-ozone/Impala-Toolchain/toolchain-packages-gcc10.4.0/thrift-0.16.0-p6/python/lib/python2.7/site-packages/thrift/transport/TSocket.py",
> line 137, in open
> handle.connect(sockaddr)
> File
> "/data/jenkins/workspace/impala-asf-master-core-ozone/Impala-Toolchain/toolchain-packages-gcc10.4.0/python-2.7.16/lib/python2.7/socket.py",
> line 228, in meth
> return getattr(self._sock,name)(*args)
> error: [Errno 111] Connection refused
> -- 2023-12-13 09:57:48,029 INFO MainThread: Could not connect to
> ('127.0.0.1', 11050)
> Traceback (most recent call last):
> File
> "/data/jenkins/workspace/impala-asf-master-core-ozone/Impala-Toolchain/toolchain-packages-gcc10.4.0/thrift-0.16.0-p6/python/lib/python2.7/site-packages/thrift/transport/TSocket.py",
> line 137, in open
> handle.connect(sockaddr)
> File
> "/data/jenkins/workspace/impala-asf-master-core-ozone/Impala-Toolchain/toolchain-packages-gcc10.4.0/python-2.7.16/lib/python2.7/socket.py",
> line 228, in meth
> return getattr(self._sock,name)(*args)
> error: [Errno 111] Connection refused
> -- 2023-12-13 09:57:48,029 ERROR MainThread: Could not connect to any of
> [('::1', 11050, 0, 0), ('127.0.0.1', 11050)]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
