Uploaded image for project: 'MongoDB for IntelliJ Plugin'
  1. MongoDB for IntelliJ Plugin
  2. INTELLIJ-159

datasources are not loaded when mongodb driver name is exposed as mongo.4 instead of mongo

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 0.0.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Environment:
      OS:
      node.js / npm versions:
      Additional info:
    • 1
    • Iteration Planetarium
    • Not Needed
    • Developer Tools

      Problem Statement/Rationale

      It seems that there are different ways of naming a MongoDB connection in IntelliJ. We assumed that the driver name is always `mongo`, but it seems that it might contain some specific version as a suffix. We've found a case where the MongoDB driver was named `mongo.4` for MongoDB 8.0 connections in a Windows environment.

      Please be sure to attach relevant logs with any sensitive data redacted.

      {"message":"LocalDataSource found in project.","pluginVersion":"0.0.1","powerSaveMode":false,"ideaUserId":"00735b5a-1d39-4d07-8940-db2c2b107fca","os":"Windows 11.0","arch":"aarch64","jvmVendor":"JetBrains s.r.o.","jvmVersion":"21.0.5","ide":"IntelliJ IDEA 2024.3","ideVersion":"2024.3","id":"6bc283d3-4dfb-46a2-a3b9-d3c22860fc66","driverId":"mongo.4","isMongoDbDataSource":false,"name":"@localhost","url":"mongodb://localhost:27017"}

      Steps to Reproduce

      We don't know how to safely reproduce it as we found only one machine that actually has this behaviour.

      Expected Results

      The connection must be shown in the toolbar as it's detected as a MongoDB query.

      Actual Results

      The connection is not shown because it's filtered out due to the anomalous driver name.

      Additional Notes

            Assignee:
            kevin.mas@mongodb.com Kevin Mas Ruiz
            Reporter:
            kevin.mas@mongodb.com Kevin Mas Ruiz
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: