You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "John Sichi (JIRA)" <ji...@apache.org> on 2010/12/16 20:57:02 UTC
[jira] Commented: (HIVE-1853) downgrade JDO version
[ https://issues.apache.org/jira/browse/HIVE-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972191#action_12972191 ]
John Sichi commented on HIVE-1853:
----------------------------------
This user report has similar symptoms:
http://mail-archives.apache.org/mod_mbox/hive-user/201011.mbox/%3CAANLkTik6M1juxvx0Lerre-cNN5QnFwi6_4AY0pQ6zB42@mail.gmail.com%3E
> 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
> Attachments: HIVE-1853.1.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.