Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-6425 Update project dependencies
  3. NODE-6552

Remove type cache and use toStringTag getters from BSON helpers

XMLWordPrintableJSON

    • Type: Icon: Sub-task Sub-task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • bson-6.10.1
    • Affects Version/s: None
    • Component/s: None
    • 0
    • Not Needed
    • Not Needed
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?

      Use Case

      As a Node engineer
      I want to be able to upgrade BSON
      So that we can ship the latest features with the next version of the driver

      User Experience

      • What is the desired/expected outcome for the user once this ticket is implemented?
        • Performance tests continue working
      • If bug: What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?
        • I think the bug relates to our perf tests, not the driver or BSON

      Dependencies

      • BSON

      Risks/Unknowns

      • What could go wrong while implementing this change? (e.g., performance, inadvertent behavioral changes in adjacent functionality, existing tech debt, etc)
        • Nothing should change, performance test metrics could be impacted depending on the correctness of our usage.
      • Is there an opportunity for better cross-driver alignment or testing in this area?
        • Maybe if our performance test is implemented in a way that causes this
      • Is there an opportunity to improve existing documentation on this subject?
        • No

      Acceptance Criteria

      Implementation Requirements

      • Determine the source of the problem with the performance tests failing on the BSON upgrade

      Testing Requirements

      • Performance tests pass

      Documentation Requirements

      • None

      Follow Up Requirements

      • None

            Assignee:
            neal.beeken@mongodb.com Neal Beeken
            Reporter:
            neal.beeken@mongodb.com Neal Beeken
            Warren James
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: