Details
-
Type:
New Feature
-
Status: Closed
-
Priority:
Minor - P4
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.8.0-rc1
-
Component/s: mongofiles
-
Labels:None
-
Documentation Changes:Completed
Description
There's a --collection argument for mongofiles that should be removed (at least from the help) if it doesn't do anything (I suspect it doesn't,) but if it has a purpose, I can update the documentation accordingly.
Issue Links
Activity
I was tempted to open a new issue – since the title of this issue is misleading – suggesting that there is just a cosmetic problem with having this extraneous --collections argument. The actual bug is that mongofiles doesn't work with buckets, and there is no workaround. I'd put this as MAJOR.
See also SERVER-1970
Agree - title of this ticket should be changed to something like "mongofiles only works on 'fs' collection". Fix should be to add support and update the documentation to reflect this purpose.
SERVER-1970 was renamed to TOOLS-102.
See TOOLS-97 for updates on this.
Doesn't there need to be an optional --collection argument for when the files/chunks collections are prefixed with something other than "fs"?
Eg in my MongoDB:
bash# mongo file
mongos> show collections
binary_shares.chunks
binary_shares.files
system.indexes
mongos> db.binary_shares.files.count()
52
(and this all works fine via the Java driver, but...)
bash# mongofiles -d file list
connected to: 127.0.0.1
bash# mongofiles -d file -c binary_shares list
connected to: 127.0.0.1
bash# mongofiles -d file -c binary_shares.files list
connected to: 127.0.0.1
bash#
Apologies if I've missed the point!