[DOCS-12556] Deprecation status of GridFS options contentType and aliases Created: 20/Mar/19 Updated: 30/Oct/23 Resolved: 27/Mar/19 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Feedback | Priority: | Major - P3 |
| Reporter: | Daniel Aprahamian (Inactive) | Assignee: | Ravind Kumar (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 4 years, 46 weeks ago |
| Story Points: | 0.1 |
| Description |
DescriptionSee: From the driver perspective, the contentType and alias fields have been deprecated since 2015 in favor of the metadata field (GridFS Spec). These fields are not mentioned as deprecated in the docs for GridFS. Is there another mechanism for using contentType or aliases that has not deprecated these fields (like the shell or mongofiles)? If not, can we change the documentation to mark these fields as deprecated? Thanks, Scope of changes
Impact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Githook User [ 27/Mar/19 ] |
|
Author: {'email': 'ravind.kumar@mongodb.com', 'name': 'rk-mongo'}Message: Multiple small fixups: DOCSP-4943: $cond requires all arguments |
| Comment by Githook User [ 27/Mar/19 ] |
|
Author: {'email': 'ravind.kumar@mongodb.com', 'name': 'rk-mongo'}Message: Multiple small fixups:
|
| Comment by Githook User [ 27/Mar/19 ] |
|
Author: {'name': 'rk-mongo', 'email': 'ravind.kumar@mongodb.com'}Message: Multiple small fixups: DOCSP-4943: $cond requires all arguments |
| Comment by Githook User [ 27/Mar/19 ] |
|
Author: {'name': 'rk-mongo', 'email': 'ravind.kumar@mongodb.com'}Message: Multiple small fixups:
|
| Comment by David Golden [ 20/Mar/19 ] |
|
I think we should remove them from the 4.2 documentation for sure. I'm on the fence about 4.0 since we never marked them deprecated and people might not think to look back to 3.4/3.6. |