hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yin Huai (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-4935) Potential NPE in MetadataOnlyOptimizer
Date Fri, 26 Jul 2013 00:11:48 GMT

    [ 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<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

Mime
View raw message