[
https://issues.apache.org/jira/browse/HIVE-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972238#action_12972238
]
Ashutosh Chauhan commented on HIVE-1853:
----------------------------------------
That will disable the feature on metastore itself. I was hoping just undoing
the changes of HIVE-1660 will revert back Hive to old behavior where QL was
doing the pruning and thus will solve the problem you guys are seeing now. That
way we could have left partition pruning in metastore to play with and try to
fix the real bug.
> downgrade JDO version
> ---------------------
>
> Key: HIVE-1853
> URL: https://issues.apache.org/jira/browse/HIVE-1853
> Project: Hive
> Issue Type: Bug
> Affects Versions: 0.7.0
> Reporter: Namit Jain
> Assignee: Paul Yang
> Fix For: 0.7.0
>
> Attachments: HIVE-1853.1.patch, HIVE-1853.2.patch
>
>
> After HIVE-1609, we are seeing some table not found errors intermittently.
> We have a test case where 5 processes are concurrently issueing the same
> query -
> explain extended insert .. select from <T>
> and once in a while, we get a error <T> not found -
> When we revert back the JDO version, the error is gone.
> We can investigate later to find the JDO bug, but for now this is a
> show-stopper for facebook, and needs
> to be reverted back immediately.
> This also means, that the filters will not be pushed to mysql.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
