324 results found

1. Autogenerated random values in numbers based on ObjectId

   Hi,

   This is the basic suggestion from my side.we have a unique "_id" in each document while inserting the data can we make any changes in your code for example in our company we have one scenario while working on the aggregation query they need auto-generated value in numbers so it is not possible in the MongoDB.

   so I thought we can do that thing based on the _id. because we have a unique field then i converted the _id to string and separated the numbers and alphabetic separately but we don't have unique values the after separating the numbers from the objectId.

   can we do anything that generation in the objectId based on the numbers or can we have anything like alphabetic have separate numbers like using the let variable like what we did for getting the months and days.

   if you do any one of them we can do auto-generation which is unique in numbers for every document either changing in the generation in objectId or adding the alphabetic to numbers like months and days

   I am sending the query that I have used in my organization for testing purposes but the result is unexpected so can you guide me on the correct to do it or any changes can you do in the upcoming release it can be appreciated. this is the basic suggestion from my side.I am thinking why don't we do it in the MongoDB other than going to python for random values.

   mongodb: For random numbers to generate based on the _id:

   If you insert the sample of 1k documents and test this query you will duplicates in the numbers and the count will also decrease.

   1st Method: [
   {
   $addFields: {
   numbers: {
   $regexFindAll: {
   input: {
   $toString: "$id",
   },
   regex: "[0-9]+",
   },
   },
   alpha: {
   $regexFindAll: {
   input: {
   $toString: "$id",
   },
   regex: "[a-z]+",
   },
   },
   },
   },
   {
   $project: {
   numbers: {
   $reduce: {
   input: "$numbers.match",
   initialValue: "",
   in: {
   $concat: ["$$value", "$$this"],
   },
   },
   },
   },
   },
   {
   $group: {
   _id: "$numbers",
   },
   },
   {
   $count: "string",
   },
   ]

   2nd Method:

   {
   $let: {
   vars: {
   monthsInString: [
   "",
   "JAN",
   "FEB",
   "MAR",
   "APR",
   "MAY",
   "JUN",
   "JUL",
   "SEP",
   "OCT",
   "NOV",
   "DEC",
   ],
   },
   in: {
   $arrayElemAt: [
   "$$monthsInString",
   {
   $toInt: {
   $dateToString: {
   format: "%m",
   date: "$dtCollected",
   },
   },
   },
   ],
   },
   },
   },

   Like this can you do for alphabetics so that we can convert the alphabetic to numbers then we can have random values which are unique in numbers .

   Can you please check and let me know if any changes I have done wrong from my side or any other way to generate the random values in numbers in the project stage.

   why do we have to go with Python for this why don't we do it in MongoDB?

   can you suggest to me if I am wrong

   Hi,

   This is the basic suggestion from my side.we have a unique "_id" in each document while inserting the data can we make any changes in your code for example in our company we have one scenario while working on the aggregation query they need auto-generated value in numbers so it is not possible in the MongoDB.

   so I thought we can do that thing based on the _id. because we have a unique field then i converted the _id to string and separated the numbers and alphabetic separately but we don't have unique values the after separating the numbers from the objectId.

   can… more

   6 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Aggregation pipeline builder  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Screen reader support

   Hello,

   Visually impaired users rely on a screenreader to have information read by a speech synthesizer or displayed on a braille display. Popular screen readers are VoiceOver on Mac OS as well as JAWS and NVDA on Windows or Orca on Linux Desktop.
   Currently, a screen reader isn't able to work properly with MongoDB Compass.

   https://github.com/mongodb-js/compass/issues/2776

   6 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  General  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Ability to export or move database between localhost and cloud

   Exporting collections one by one, manually, is so much to do in 2020

   6 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Import/Export  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Disable the explain button while an explain is running

   The Explain Plan option does not allow ending the operation.
   When selecting the explain button, no interface animation is displayed that indicates the "running" state of the operation. Also, the tool ignores the "maxTimeMS" parameter and continues the operation even after the elapsed time.

   Steps to Reproduce

   Select the Explain Plan option > select a field to filter in the database > fill in a "maxTimeMS" value > click explain.
   Continuously clicking the explain button generates several similar operations without option to stop it.

   Expected Results

   Prevent starting multiple explain operations when there is still one in progress. Allow stop on an Explain Plan operation.
   Consider the maxTimeMS in the Explain Plan option.

   Actual Results

   Explain operations cannot be interrupted by the user and he doesn't know if something is actually being executed.

   Additional Notes
   Compass readonly version 1.35.0

   The Explain Plan option does not allow ending the operation.
   When selecting the explain button, no interface animation is displayed that indicates the "running" state of the operation. Also, the tool ignores the "maxTimeMS" parameter and continues the operation even after the elapsed time.

   Steps to Reproduce

   Select the Explain Plan option > select a field to filter in the database > fill in a "maxTimeMS" value > click explain.
   Continuously clicking the explain button generates several similar operations without option to stop it.

   Expected Results

   Prevent starting multiple explain operations when there is still one in progress. Allow stop… more

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   started  ·  AdminMassimiliano (Admin, MongoDB) responded

   We made explain plans cancellable. The new functionality is available in the most recent beta and will be rolled out in the next GA release.

5. Allow following a referenced ObjectID to the associated document

   I have documents that reference other documents in other collections using the ObjectId. It would be really helpful if I could follow these references in Compass to the associated document.

   For example, if I find a specific document by using the standard Filter/Find mechanism in Compass. From there I see that some of the fields in a given document reference another ObjectID (potentially in a different collection)

   It would be nice to have an available action (maybe an action icon?) that would take me to the related document.

   Currently I have to copy the desired object ID, switch to the other collection, and then do the second find with something like {"_id": ObjectId("62c9b444de386b2551756a56")}

   I have documents that reference other documents in other collections using the ObjectId. It would be really helpful if I could follow these references in Compass to the associated document.

   For example, if I find a specific document by using the standard Filter/Find mechanism in Compass. From there I see that some of the fields in a given document reference another ObjectID (potentially in a different collection)

   It would be nice to have an available action (maybe an action icon?) that would take me to the related document.

   Currently I have to copy the desired object ID, switch to the… more

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  General  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Display collection name and namespace on separate lines

   If you have a longish DB/namespace name, the labels on the tabs become pretty useless, as all they say is "Documents (verylongdbnamewhichiknowalready)" and there's no room for the name of the collection.

   This forces me to navigate through tabs to find the collection I was querying.
   I feel that the "Documents" or whatever main label is on the tabs can be communicated via the tab icon only.

   The name of the namespace could either be hidden entirely and shown only on the tab body, or shown on a separate line from the collection name.

   •  

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  General  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Remember collection view mode selected or add an option to save default

   Currently, after you switch to table mode in a collections tab, compass won't remember that option when you open a new collection tab. Being table mode user 99% of the time, it would be really useful to remember last mode selected when opening a new tab, or be able to define the default view mode

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  General  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Be able to save and restore the tabs complete with their existing queries, projections and sorting settings.

   The description is in the attached graphic. The gist is being able to save the Filter, Projection, Sort, Skip, Limit settings for each tab as a logically grouped set of tabs which I can give a meaningful name to and perhaps stores them on computer as a JSON file and I can reload that json file after connecting to a MongoDB and restore my tabs.

   Also, once you have this functionality, it would be nice since the application itself is written in Javascript to make a Microsoft Visual Studio Code plugin out of Compass as well so I can have it launch with my development environment where I am authoring code.

   The description is in the attached graphic. The gist is being able to save the Filter, Projection, Sort, Skip, Limit settings for each tab as a logically grouped set of tabs which I can give a meaningful name to and perhaps stores them on computer as a JSON file and I can reload that json file after connecting to a MongoDB and restore my tabs.

   Also, once you have this functionality, it would be nice since the application itself is written in Javascript to make a Microsoft Visual Studio Code plugin out of Compass as well so I can have… more

   •  

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  General  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. SQL to Aggregation framework converter

   The intent would be to run SQL queries directly on MongoDB Compass or convert them to aggregations

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Aggregation pipeline builder  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. Copy data from one collection to another

    • this should include duplicating a collection
    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. "Open in new tab" should be default behaviour

    By click on collection this should be opened in new tab. If the collection is already opened the tab will be selected. The context menu "Open in new tab" should be stay as is and opend a collection in new tab.

    The case "why" - you open a collection, put some filter, order and some other staff. Then you want check other collection and just click on it. All settings on the first collection are lost.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. Have the Export Colelction feature list all collection fields by default

    The current feature lists the fields from a sample of documents which may miss some fields. Although it is specified in a tooltip, this is quite counter-intuitive in a NoSQL database which is all about document diversity.

    When a collection has upwards to 100+ possible fields it becomes quite tedious to figure out which ones are missing from the sample data.

    I would like for MongoDB Compass to find the complete list of possible fields for a selected collection and list them all out be default.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Import/Export  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. export sorted data

    When clicking export collection button, the sort option specified should be copied to "Export query with filters"

    Examples:

    db.holidays.find (
    {Date: {eq: '2022-04-08'}
    ).sort ({System : 1})

    or even make this part editable, so we can add sort option

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Import/Export  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Support hint for explain

    Currently is not possible to force to run explain with a certain index, it would be a nice feature to have

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. mongosh should be its own tab at the top with output options

    I hate how mongosh is at the bottom. It makes it rather hard to see the results as it involves lots of scrolling, I end up having to write a js file and using mongosh in the terminal.
    It would be good if it was it's own tab at the top and give options to view the output differently.
    The best example I can give is how the robo3t does it. When the data can't be viewed as a tree or table, it just outputs it in text mode.

    Something like this is super handy for developers and makes it easier to do things like write an aggregate query that we can directly copy to/from an actual application. While the aggregate feature in compass is ok, it's not an exact match on how we would write it in code.

    I hate how mongosh is at the bottom. It makes it rather hard to see the results as it involves lots of scrolling, I end up having to write a js file and using mongosh in the terminal.
    It would be good if it was it's own tab at the top and give options to view the output differently.
    The best example I can give is how the robo3t does it. When the data can't be viewed as a tree or table, it just outputs it in text mode.

    Something like this is super handy for developers and makes it… more

    •  

    •  

    •  

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  General  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. Ability to drill-down and easily export deeply nested arrays

    Provide the ability to drill-down and export any MongoDB array from Compass to a csv file, no matter how deeply it is stored within a document. So, one should be able to drill-down to the given array (no matter how many levels deep) in Compass, and then click "export to csv" to export only that nested array's contents to a CSV file.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Import/Export  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. Schema analysis should recognize dictionaries

    In a sub-document, the keys may be common across most documents in the collection, or they may contain a set of random values. For example, using hostnames as the keys in the "hosts" sub-document.

    {
        ...
        hosts: {
            server1a: { ... }
            server2a: { ... }
            server3a: { ... }
        }
        } 
        {
        ...
        hosts: {
            server1b: { ... }
            server2b: { ... }
            server3b: { ... }
        }
    }
    

    The schema analysis should recognize the above situation to avoid creating thousands of sub-fields in the schema.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Schema Analysis  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. Support Citrix as a Compass platform

    Support Citrix as a new Compass platform

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. As a developer using extended JSON strict mode queries, I need Compass to also support queries in strict mode

    Compass should support extended JSON strict mode queries in queries on the Documents, Schema and Explain Plan tabs.

    As an example, the error message in Compass 1.14.7 for an "$oid" query is:

    unknown operator: $oid

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Queries  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. Visual rule builder for schema validation

    In Compass, it is possible to create validation rules to enforce a schema. It would be good to be able to generate these rules with a simple, visual editor, instead of having to know the MQL or JSON Schema syntax for the validation rules.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close