[SERVER-3882] aggregation: date extraction functions should have optional target time zone Created: 16/Sep/11  Updated: 06/Dec/22  Resolved: 24/Jul/17

Status: Closed
Project: Core Server
Component/s: Aggregation Framework
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Daniel Pasette (Inactive) Assignee: Backlog - Query Team (Inactive)
Resolution: Duplicate Votes: 22
Labels: expression, usability
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-6310 Timezone support in date operators at... Closed
Assigned Teams:
Query
Backwards Compatibility: Fully Compatible
Participants:

 Description   

This will allow conversion into other time zones from UTC.



 Comments   
Comment by Asya Kamsky [ 24/Jul/17 ]

Closing at duplicate of SERVER-6310

Comment by Paul Grinchenko [ 06/Dec/12 ]

We could really use this - we actually struggled with the lack of time zone logic support

Comment by Chris Westin [ 26/Oct/11 ]

Defer from initial release of aggregation.

Recent issues with the availability of the tzdata database make this problematic: we don't have a reliable source of zone names or time differences that we can use.

However, the initial release of aggregation already supports date arithmetic, so times in different time zones can be calculated by supplying the time difference from the application.

Generated at Thu Feb 08 03:04:20 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.