-
Type:
Bug
-
Resolution: Works as Designed
-
Priority:
Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: None
-
Labels:None
Invoking the mongoimport tool without a filename didn't result in an immediate error. Instead, the application seems to idle (see output below). I encountered this when working through the on-demand university course with the m103 vagrant machine.
vagrant@m103:/dataset$ mongoimport --port 27000 -u m103-application-user -p m103-application-pass --authenticationDatabase admin --db applicationData --collection productsvagrant@m103:/dataset$ mongoimport --port 27000 -u m103-application-user -p m103-application-pass --authenticationDatabase admin --db applicationData --collection products
2018-05-22T20:56:41.238+0000 connected to: localhost:27000
2018-05-22T20:56:44.232+0000 applicationData.products 0B
2018-05-22T20:56:47.226+0000 applicationData.products 0B
2018-05-22T20:56:50.225+0000 applicationData.products 0B
2018-05-22T20:56:53.228+0000 applicationData.products 0B
2018-05-22T20:56:56.224+0000 applicationData.products 0B
2018-05-22T20:56:59.226+0000 applicationData.products 0B
2018-05-22T20:57:02.225+0000 applicationData.products 0B
2018-05-22T20:57:05.225+0000 applicationData.products 0B
2018-05-22T20:57:08.225+0000 applicationData.products 0B
2018-05-22T20:57:11.226+0000 applicationData.products 0B
^C2018-05-22T20:57:13.715+0000 signal 'interrupt' received; forcefully terminating
Version information:
vagrant@m103:/dataset$ mongoimport --version mongoimport version: r3.6.5-rc0 git version: a20ecd3e3a174162052ff99913bc2ca9a839d618 Go version: go1.8.5 os: linux arch: amd64 compiler: gc OpenSSL version: OpenSSL 1.0.1f 6 Jan 2014