Return-Path: X-Original-To: apmail-hive-dev-archive@www.apache.org Delivered-To: apmail-hive-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2A80711211 for ; Fri, 22 Aug 2014 00:38:12 +0000 (UTC) Received: (qmail 19140 invoked by uid 500); 22 Aug 2014 00:38:11 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 19061 invoked by uid 500); 22 Aug 2014 00:38:11 -0000 Mailing-List: contact dev-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list dev@hive.apache.org Received: (qmail 19042 invoked by uid 500); 22 Aug 2014 00:38:11 -0000 Delivered-To: apmail-hadoop-hive-dev@hadoop.apache.org Received: (qmail 19039 invoked by uid 99); 22 Aug 2014 00:38:11 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Aug 2014 00:38:11 +0000 Date: Fri, 22 Aug 2014 00:38:11 +0000 (UTC) From: "Hive QA (JIRA)" To: hive-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HIVE-7680) Do not throw SQLException for HiveStatement getMoreResults and setEscapeProcessing(false) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HIVE-7680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14106247#comment-14106247 ] Hive QA commented on HIVE-7680: ------------------------------- {color:red}Overall{color}: -1 at least one tests failed Here are the results of testing the latest attachment: https://issues.apache.org/jira/secure/attachment/12663425/HIVE-7680.2.patch {color:red}ERROR:{color} -1 due to 3 failed/errored test(s), 6115 tests executed *Failed tests:* {noformat} org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_parquet_join org.apache.hadoop.hive.cli.TestMiniTezCliDriver.testCliDriver_dynpart_sort_opt_vectorization org.apache.hive.jdbc.miniHS2.TestHiveServer2.testConnection {noformat} Test results: http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/446/testReport Console output: http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/446/console Test logs: http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-446/ Messages: {noformat} 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: 3 tests failed {noformat} This message is automatically generated. ATTACHMENT ID: 12663425 > Do not throw SQLException for HiveStatement getMoreResults and setEscapeProcessing(false) > ----------------------------------------------------------------------------------------- > > Key: HIVE-7680 > URL: https://issues.apache.org/jira/browse/HIVE-7680 > Project: Hive > Issue Type: Bug > Components: JDBC > Affects Versions: 0.13.1 > Reporter: Alexander Pivovarov > Assignee: Alexander Pivovarov > Priority: Minor > Attachments: HIVE-7680.2.patch, HIVE-7680.2.patch, HIVE-7680.patch > > > 1. Some JDBC clients call method setEscapeProcessing(false) (e.g. SQL Workbench) > Looks like setEscapeProcessing(false) should do nothing.So, lets do nothing instead of throwing SQLException > 2. getMoreResults is needed in case Statements returns several ReseltSet. > Hive does not support Multiple ResultSets. So this method can safely always return false. > 3. getUpdateCount. Currently this method always returns 0. Hive cannot tell us how many rows were inserted. According to JDBC spec it should return " -1 if the current result is a ResultSet object or there are no more results" > if this method returns 0 then in case of execution insert statement JDBC client shows "0 rows were inserted" which is not true. > if this method returns -1 then JDBC client runs insert statements and shows that it was executed successfully, no result were returned. > I think the latter behaviour is more correct. > 4. Some methods in Statement class should throw SQLFeatureNotSupportedException if they are not supported. Current implementation throws SQLException instead which means database access error. -- This message was sent by Atlassian JIRA (v6.2#6252)