Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.0.0-rc0
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Query Optimization
Backwards Compatibility:
Fully Compatible
Sprint:
QO 2024-03-04
CAR Domain/s:
None

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

We currently always populate the cluster time and localNow time when constructing the ExpressionContext even if the variables are unreferenced in any expressions. This shows up in flamegraphs for fast running queries like ycsb.

causes

SERVER-114384 $$NOW can be different in sub-pipelines

Closed

is related to

SERVER-82647 Avoid getting current VectorClock in Variables::generateRuntimeConstants

Closed

Assignee:: Ben Shteinfeld
Reporter:: Ben Shteinfeld
Participants:: Ben Shteinfeld, Githook User
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Feb 27 2024 06:44:39 PM UTC
Updated:: Jan 06 2026 03:48:45 PM UTC
Resolved:: Mar 01 2024 12:42:16 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates