You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hive.apache.org by "Ashutosh Chauhan (JIRA)" <ji...@apache.org> on 2013/07/26 02:03:49 UTC

[jira] [Commented] (HIVE-4935) Potential NPE in MetadataOnlyOptimizer

    [ https://issues.apache.org/jira/browse/HIVE-4935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720270#comment-13720270 ] 

Ashutosh Chauhan commented on HIVE-4935:
----------------------------------------

Which line could result in NPE? Is it 
-        LOG.info("Metadata only table scan for " + tso.getConf().getAlias()); ?
                
> 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<Node>, 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