[GitHub] storm pull request: STORM-811: remove old metastor_db before runni...
Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/547 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] storm pull request: STORM-811: remove old metastor_db before runni...
Github user harshach commented on the pull request: https://github.com/apache/storm/pull/547#issuecomment-100752288 @revans2 I am +1 on the patch. Good to remove metastore_db before running tests. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] storm pull request: STORM-811: remove old metastor_db before runni...
GitHub user revans2 opened a pull request: https://github.com/apache/storm/pull/547 STORM-811: remove old metastor_db before running tests again. You can merge this pull request into a Git repository by running: $ git pull https://github.com/revans2/incubator-storm STORM-811 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/storm/pull/547.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 #547 commit e40a0fe1b7d52b5f8ad2b9b08d9884dba4829d13 Author: Robert (Bobby) Evans ev...@yahoo-inc.com Date: 2015-05-06T21:17:08Z STORM-811: remove old metastor_db before running tests again. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---