Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Done
Priority: Major - P3
Fix Version/s: 3.5.12
Affects Version/s: None
Component/s: Querying
Labels:
None

Backwards Compatibility:
Fully Compatible
Sprint:
Query 2017-08-21
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

Update expressions should always be parsed as UpdateNodes when the featureCompatibilityVersion is 3.6. When the featureCompatibilityVersion is 3.4, the old ModifierInterface implementation should be used.

depends on

SERVER-28762 Conditionally parse an update expression as an UpdateNode tree

Closed

SERVER-28763 Create UpdateArrayNode

Closed

SERVER-28764 Create AddToSetNode

Closed

SERVER-28765 Create BitNode

Closed

SERVER-28766 Create CurrentDateNode

Closed

SERVER-28767 Create IncNode/MulNode

Closed

SERVER-28768 Create MaxNode/MinNode

Closed

SERVER-28769 Create PopNode

Closed

SERVER-28770 Create PullNode

Closed

SERVER-28771 Create PullAllNode

Closed

SERVER-28772 Create PushNode/PushAllNode

Closed

SERVER-28773 Create SetOnInsertNode

Closed

SERVER-28774 Create RenameNode

Closed

SERVER-28775 Create UnsetNode

Closed

SERVER-28776 Create an alternative to ModifierObjectReplace that does not implement ModifierInterface

Closed

(10 depends on)

Assignee:: Tess Avitabile (Inactive)
Reporter:: Tess Avitabile (Inactive)
Participants:: Githook User, Matthew Russotto, Tess Avitabile
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Apr 12 2017 09:34:08 PM UTC
Updated:: Oct 12 2017 08:58:16 PM UTC
Resolved:: Aug 11 2017 06:52:20 PM UTC
Confidence Status Last Update:: 10/Aug/17 4:48 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates