[SERVER-68327] Old JS engine cannot properly roundtrip NumberLong Created: 26/Jul/22  Updated: 05/Dec/22

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: 5.3.3
Fix Version/s: None

Type: Bug Priority: Trivial - P5
Reporter: Yoon Soo Kim Assignee: Backlog - Query Execution
Resolution: Unresolved Votes: 0
Labels: greenerbuild
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Query Execution
Operating System: ALL
Participants:
Linked BF Score: 6

 Description   

It seems that the old JS engine does not return correct result for the following expression.

function accumulate(state, input) {
  return input > state ? input : state;
}

Input params are state = '' (empty string) and input = NumberLong(1). The old engine returns {} and the new engine returns NumberLong(1). If input is 1.0, then both engines return 1.0



 Comments   
Comment by Ana Meza [ 08/Sep/22 ]

Based on Chris's comment I am marking this ticket as "Trivial - P5" so it does not come up on our Triage filter but this ticket remains open on the backlogĀ 

Comment by Mohammad Dashti (Inactive) [ 18/Aug/22 ]

Unassigned myself and added the query-product-triage label based on christopher.harris@mongodb.com's suggestion (over Slack).

Comment by Mohammad Dashti (Inactive) [ 09/Aug/22 ]

yoonsoo.kim@mongodb.com and max.hirschhorn@mongodb.com, thanks for the investigations on this ticket.

IMHO, it's not worth the effort to resolve the issue in all the prev. releases, as 1) the extent of work is unclear (though most probably doesn't involve the MozJS code itself, but our integration layer around it), and 2) there's a minimal impact (compared to the amount of effort involved).

christopher.harris@mongodb.com Given the status of this ticket (where there's an incorrect behavior in the previous releases and it's fixed on the master branch (after upgrading MozJS), what do you suggest?

Comment by Brenda Rodriguez [ 26/Jul/22 ]

Scheduling this as a BF day bug fix to see if there is something quick we can do in 5.0

Generated at Thu Feb 08 06:10:30 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.