You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Vihang Karajgaonkar (JIRA)" <ji...@apache.org> on 2017/08/08 17:40:00 UTC
[jira] [Comment Edited] (HIVE-17224) Move JDO classes to standalone
metastore
[ https://issues.apache.org/jira/browse/HIVE-17224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16118713#comment-16118713 ]
Vihang Karajgaonkar edited comment on HIVE-17224 at 8/8/17 5:39 PM:
--------------------------------------------------------------------
The change itself looks good to me. I wonder why the pre-commit didn't trigger for this patch. Can you please submit another patch so that it gets triggered? I remember there was some problem with the pre-commit few days ago.
was (Author: vihangk1):
The change itself looks good to me. I wonder by the pre-commit didn't trigger for this patch. Can you please submit another patch so that it gets triggered? I remember there was some problem with the pre-commit few days ago.
> Move JDO classes to standalone metastore
> ----------------------------------------
>
> Key: HIVE-17224
> URL: https://issues.apache.org/jira/browse/HIVE-17224
> Project: Hive
> Issue Type: Sub-task
> Components: Metastore
> Reporter: Alan Gates
> Assignee: Alan Gates
> Attachments: HIVE-17224.patch
>
>
> The JDO model classes (MDatabase, MTable, etc.) and the package.jdo file that defines the DB mapping need to be moved to the standalone metastore.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)