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 2FA9B10E2B for ; Fri, 26 Jul 2013 00:11:49 +0000 (UTC) Received: (qmail 83888 invoked by uid 500); 26 Jul 2013 00:11:48 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 83828 invoked by uid 500); 26 Jul 2013 00:11:48 -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 83819 invoked by uid 500); 26 Jul 2013 00:11:48 -0000 Delivered-To: apmail-hadoop-hive-dev@hadoop.apache.org Received: (qmail 83816 invoked by uid 99); 26 Jul 2013 00:11:48 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Jul 2013 00:11:48 +0000 Date: Fri, 26 Jul 2013 00:11:48 +0000 (UTC) From: "Yin Huai (JIRA)" To: hive-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HIVE-4935) Potential NPE in MetadataOnlyOptimizer 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-4935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720276#comment-13720276 ] Yin Huai commented on HIVE-4935: -------------------------------- right. If that tso does not have any needed column and it does not have a conf, MetadataOnlyOptimizer will consider it as a possible TS. > Potential NPE in MetadataOnlyOptimizer > -------------------------------------- > > Key: HIVE-4935 > URL: https://issues.apache.org/jira/browse/HIVE-4935 > Project: Hive > Issue Type: Bug > Reporter: Yin Huai > Assignee: Yin Huai > Priority: Minor > Attachments: HIVE-4935.1.patch > > > In MetadataOnlyOptimizer.TableScanProcessor.process, it is possible that we consider a TableScanOperator as "MayBeMetadataOnly" when this TS does not have a conf. In MetadataOnlyOptimizer.MetadataOnlyTaskDispatcher.dispatch(Node, Stack, Object...), when we convert this TS, we want to get the alias from its conf.... -- 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