[DOCS-5848] Comment on: "manual/reference/gridfs.txt" Created: 14/Jul/15  Updated: 03/Nov/17  Resolved: 01/Apr/16

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: 01112017-cleanup

Type: Bug Priority: Major - P3
Reporter: Docs Collector User (Inactive) Assignee: Kay Kim (Inactive)
Resolution: Done Votes: 0
Labels: collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Location: http://docs.mongodb.org/manual/reference/gridfs/#the-files-collection
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2453.0 Safari/537.36
Screen Resolution: 1680 x 1050
repo: docs
source: reference/gridfs


Participants:
Days since reply: 7 years, 45 weeks, 6 days ago

 Description   

I've just chased down some big challenges with Meteor File Collection which uses GridFS. Turns out that both the author and I didn't realize that arbitrary data could be added at the top level of the schema. I later spotted that fact in your earlier text, but perhaps the following change in the metadata description will help Devs spot this capability a bit better:

Recommend Changing:

files.metadata
Optional. Any additional information you want to store.

To:

files.metadata
Optional. Any additional information you want to store. Though you may also create your own arbitrary fields at the level above this.



 Comments   
Comment by Githook User [ 01/Apr/16 ]

Author:

{u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}

Message: DOCS-5848 gridfs and arbitrary fields
Branch: master
https://github.com/mongodb/docs/commit/6abc43b4314f8e75ff28d476701abd9ebd9c4f61

Generated at Thu Feb 08 07:51:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.