You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2009/08/25 01:02:59 UTC
[jira] Updated: (HIVE-789) Add get_unique_id() call to metastore
[ https://issues.apache.org/jira/browse/HIVE-789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon updated HIVE-789:
-----------------------------
Attachment: hive-789.patch
This patch implements get_unique_id.
One concern: do I need to do any kind of migration script for metastore databases? I don't know how metastore schema migrations are done from release to release.
> Add get_unique_id() call to metastore
> -------------------------------------
>
> Key: HIVE-789
> URL: https://issues.apache.org/jira/browse/HIVE-789
> Project: Hadoop Hive
> Issue Type: Improvement
> Components: Metastore
> Reporter: Todd Lipcon
> Fix For: 0.4.0
>
> Attachments: hive-789.patch
>
>
> As noted in HIVE-718, it can be tough to avoid race conditions when multiple clients are trying to move files into the same directory. This patch adds a get_unique_id() call to the metastore that returns the current value from an incrementing JDO Sequence so that clients can avoid some races without locks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.