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 43E0C112A0 for ; Fri, 18 Jul 2014 20:52:17 +0000 (UTC) Received: (qmail 51070 invoked by uid 500); 18 Jul 2014 20:52:15 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 50959 invoked by uid 500); 18 Jul 2014 20:52:15 -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 50800 invoked by uid 500); 18 Jul 2014 20:52:15 -0000 Delivered-To: apmail-hadoop-hive-dev@hadoop.apache.org Received: (qmail 50779 invoked by uid 99); 18 Jul 2014 20:52:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Jul 2014 20:52:15 +0000 Date: Fri, 18 Jul 2014 20:52:15 +0000 (UTC) From: "Xingwen Zhang (JIRA)" To: hive-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HIVE-7448) --incremental=true in Beeline is not compatible with Binary columns (at least for select * from ...) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Xingwen Zhang created HIVE-7448: ----------------------------------- Summary: --incremental=true in Beeline is not compatible with Binary columns (at least for select * from ...) Key: HIVE-7448 URL: https://issues.apache.org/jira/browse/HIVE-7448 Project: Hive Issue Type: Bug Components: Clients Affects Versions: 0.12.0 Reporter: Xingwen Zhang Priority: Minor We would like to report that "--incremental=true" in Beeline is not compatible with Binary columns (at least for queries like "select * from some_table_with_a_binary_column limit 10;"). The error trace we got was: Error: Invalid column type: -2 (state=,code=0) java.sql.SQLException: Invalid column type: -2 at org.apache.hive.jdbc.JdbcColumn.columnDisplaySize(JdbcColumn.java:94) at org.apache.hive.jdbc.HiveResultSetMetaData.getColumnDisplaySize(HiveResultSetMetaData.java:60) at org.apache.hive.beeline.IncrementalRows.(IncrementalRows.java:55) at org.apache.hive.beeline.BeeLine.print(BeeLine.java:1570) at org.apache.hive.beeline.Commands.execute(Commands.java:745) at org.apache.hive.beeline.Commands.sql(Commands.java:657) at org.apache.hive.beeline.BeeLine.dispatch(BeeLine.java:794) at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:661) at org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:366) at org.apache.hive.beeline.BeeLine.main(BeeLine.java:349) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.hadoop.util.RunJar.main(RunJar.java:208) The error was gone when we reverted back to " "--incremental=false". BTW: we are using Hive 0.12. -- This message was sent by Atlassian JIRA (v6.2#6252)