Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-57636

compressor vs compressors



    • Bug
    • Status: Needs Verification
    • Minor - P4
    • Resolution: Unresolved
    • None
    • None
    • None
    • None
    • Server Development Platform
    • ALL


      Problem Description

      I needed to connect to a MongoDB Atlas cluster through zstd compression using the mongo shell. 

      I should be able to specify the compressor like we describe in our documentation:  "Starting in MongoDB 4.0.5 (and MongoDB 3.6.10), the mongo shell supports the uri connection string option compressors." 

      Link: https://docs.mongodb.com/manual/reference/connection-string/#compression-options 

      Steps to Reproduce

      mongo -version
      >>> MongoDB shell version v4.2.0


      mongo "mongodb+srv://zstd.g3mcy.mongodb.net/?compressors=zstd" --username main_user --password bryanzelle

      >>> InvalidOptions: ERROR: Cannot specify different network message compressors in connection URI and as a command-line option


      mongo "mongodb+srv://zstd.g3mcy.mongodb.net/?compressor=zstd" --username main_user --password bryanzelle

      >>> Connects Successfully 


      Does the mongo shell need to be changed to "compressors" like we have in our documentation?  Or do we need to update our documentation to state that in the shell the value is actually "compressor" and not "compressors"? 

      If we need to update the documentation, then maybe you could change this ticket to a Documentation update request or at least clarification. 


      *NOTE:  I believe the mongosh does have it correct, and they use compressors instead of compressor.  So question becomes why does mongo shell use "compressor" and mongosh use "compressors"?*

      Expected Results

      Actual Results

      Additional Notes




            backlog-server-devplatform Backlog - Server Development Platform Team (SDP)
            bryan.zelle@mongodb.com Bryan Zelle
            0 Vote for this issue
            7 Start watching this issue