[ https://issues.apache.org/jira/browse/HIVE-17982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16295890#comment-16295890 ]
ASF GitHub Bot commented on HIVE-17982: --------------------------------------- GitHub user alanfgates opened a pull request: https://github.com/apache/hive/pull/279 HIVE-17982 Move metastore specific itests You can merge this pull request into a Git repository by running: $ git pull https://github.com/alanfgates/hive hive17982 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/hive/pull/279.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #279 ---- commit 002233b90126469edd61658c1a32988438dfae85 Author: Alan Gates <ga...@hortonworks.com> Date: 2017-10-26T16:49:19Z HIVE-17982 Move metastore specific itests ---- > Move metastore specific itests > ------------------------------ > > Key: HIVE-17982 > URL: https://issues.apache.org/jira/browse/HIVE-17982 > Project: Hive > Issue Type: Sub-task > Components: Standalone Metastore > Reporter: Alan Gates > Assignee: Alan Gates > Labels: pull-request-available > Attachments: HIVE-17982.patch > > > There are a number of tests in itests/hive-unit/.../metastore that are > metastore specific. I suspect they were initially placed in itests only > because the metastore pulling in a few plugins from ql. > Given that we need to be able to release the metastore separately, we need to > be able to test it completely as a standalone entity. So I propose to move a > number of the itests over into standalone-metastore. I will only move tests > that are isolated to the metastore. Anything that tests wider functionality > I plan to leave in itests. -- This message was sent by Atlassian JIRA (v6.4.14#64029)