[DOCS-16485] Investigate changes in SERVER-81523: Normalization of time-series meta field can break query Created: 08/Nov/23  Updated: 07/Feb/24  Resolved: 07/Feb/24

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: 5.0.0, 6.0.0, 7.1.0, 7.0.0
Fix Version/s: None

Type: Task Priority: Critical - P2
Reporter: Backlog - Core Eng Program Management Team Assignee: Lauren Tran
Resolution: Done Votes: 0
Labels: ca-server-80203, feature, query
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-81523 Normalization of time-series meta fie... Backlog
Participants:
Days since reply: 12 hours, 59 minutes ago
Story Points: 2

 Description   
Original Downstream Change Summary

We need to update the documentation to discourage users from running queries on the whole metaField when an the metaField is an object. They should instead rewrite the query on scalar sub-fields on the metaField.

For example, if the metaField is metadata:

{a: 1, b: 1}

, then instead of running a query like find({metadata: {a: 1, b: 2}}), users should write it as find(

{'metadata.a': 1, 'metadata.b': 2}

).

Description of Linked Ticket

null



 Comments   
Comment by Lauren Tran [ 07/Feb/24 ]

No back port to v5.0 because the time series best practice page that updates were made on does not exist for this version

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