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 94E95DAAC for ; Mon, 29 Oct 2012 05:21:16 +0000 (UTC) Received: (qmail 23520 invoked by uid 500); 29 Oct 2012 05:21:15 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 23104 invoked by uid 500); 29 Oct 2012 05:21: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 23018 invoked by uid 500); 29 Oct 2012 05:21:13 -0000 Delivered-To: apmail-hadoop-hive-dev@hadoop.apache.org Received: (qmail 22996 invoked by uid 99); 29 Oct 2012 05:21:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Oct 2012 05:21:12 +0000 Date: Mon, 29 Oct 2012 05:21:12 +0000 (UTC) From: "Chris Drome (JIRA)" To: hive-dev@hadoop.apache.org Message-ID: <1604980370.38023.1351488072510.JavaMail.jiratomcat@arcas> Subject: [jira] [Created] (HIVE-3630) udf_substr.q fails when using JDK7 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Chris Drome created HIVE-3630: --------------------------------- Summary: udf_substr.q fails when using JDK7 Key: HIVE-3630 URL: https://issues.apache.org/jira/browse/HIVE-3630 Project: Hive Issue Type: Bug Components: Tests Affects Versions: 0.10.0, 0.9.1 Reporter: Chris Drome Assignee: Chris Drome Internal error: Cannot find ConstantObjectInspector for BINARY This exception has two causes. JDK7 iterators do not return values in the same order as JDK6, which selects a different implementation of this UDF when the first argument is null. With JDK7 this happens to be the binary version. The binary version is not implemented properly which ultimately causes the exception when the method is called. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira