[
https://issues.apache.org/jira/browse/DRILL-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15852376#comment-15852376
]
ASF GitHub Bot commented on DRILL-5196:
---------------------------------------
GitHub user chunhui-shi opened a pull request:
https://github.com/apache/drill/pull/741
DRILL-5196: init MongoDB cluster when run a single test case directly…
… through command line or IDE.
Other fixes include:
Sync mongo-java-driver versions to newer 3.2.0
update flapdoodle package to latest accordingly
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/chunhui-shi/drill DRILL-5196
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/drill/pull/741.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 #741
----
commit 6068d7a21a0cf45ba9f5f3c76ad48dbd94c6e204
Author: chunhui-shi <c...@maprtech.com>
Date: 2017-01-14T01:20:46Z
DRILL-5196: init MongoDB cluster when run a single test case directly
through command line or IDE.
Other fixes include:
Sync mongo-java-driver versions to newer 3.2.0
update flapdoodle package to latest accordingly
----
> Could not run a single MongoDB unit test case through command line or IDE
> -------------------------------------------------------------------------
>
> Key: DRILL-5196
> URL: https://issues.apache.org/jira/browse/DRILL-5196
> Project: Apache Drill
> Issue Type: Bug
> Reporter: Chunhui Shi
> Assignee: Chunhui Shi
>
> Could not run a single MongoDB's unit test through IDE or command line. The
> reason is when running a single test case, the MongoDB instance did not get
> started thus a 'table not found' error for 'mongo.employee.empinfo' would be
> raised.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
