Re: GridFSFileInfo.ContentType deprecation

From: Robert Stam <robert@xxxxxxxxxxx>
To: "mongodb-user@xxxxxxxxxxxxxxxx" <mongodb-user@xxxxxxxxxxxxxxxx>
Date: Thu, 14 Apr 2016 21:13:39 -0600
Why ads?
All drivers, the C#/.NET driver included, are standardizing on a new GridFS
API that is documented in this publicly available GridFS specification:

https://github.com/mongodb/specifications/blob/master/source/gridfs/gridfs-spec.rst

The specification provides the following rationale for deprecating the top
level contentType field and encouraging applications to store contentType
(along with any other application specific data) in the metadata field:

Why is contentType deprecated?Most fields in the files collection document
are directly used by the driver, with the exception of: metadata,
contentType and aliases. All information that is purely for use of the
application should be embedded in the 'metadata' document. Users of GridFS
who would like to store a contentType for use in their applications are
encouraged to add a 'contentType' field to the ‘metadata’ document instead
of using the deprecated top-level ‘contentType’ field.

On Thu, Apr 14, 2016 at 5:21 PM, Matthew Nelson-White <
mnelsonwhite@xxxxxxxxx> wrote:

Hi,

In the mongo-csharp-driver project MongoDB.Driver.GridFS v2.2.3.3 I can
see that the GridFSFileInfo.ContentType property is marked as deprecated
with the note to *"Place contentType inside metadata instead."*

Why has this been marked as deprecated?
Will new versions of the GridFS engine put this data in metadata and not
in contentType?
Is this a decision by the mongo-csharp-driver team made independent of
the GridFS team?

--
You received this message because you are subscribed to the Google Groups
"mongodb-user"
group.

For other MongoDB technical support options, see:
https://docs.mongodb.org/manual/support/
---
You received this message because you are subscribed to the Google Groups
"mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to mongodb-user+unsubscribe@xxxxxxxxxxxxxxxx.
To post to this group, send email to mongodb-user@xxxxxxxxxxxxxxxx.
Visit this group at https://groups.google.com/group/mongodb-user.
To view this discussion on the web visit
https://groups.google.com/d/msgid/mongodb-user/0edada82-8c4b-4cf2-92eb-4816cf6cbc2e%40googlegroups.com
<https://groups.google.com/d/msgid/mongodb-user/0edada82-8c4b-4cf2-92eb-4816cf6cbc2e%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.

For other MongoDB technical support options, see: https://docs.mongodb.org/manual/support/
--- 
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+unsubscribe@xxxxxxxxxxxxxxxx.
To post to this group, send email to mongodb-user@xxxxxxxxxxxxxxxx.
Visit this group at https://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/CAJCJWG1FGgGk-FvKuX46Jo50bMLPfux2fAG7ohmdNxmZqTh2cQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Why ads?