324 results found

1. Avoid running queries on an ongoing condition writing. (match, lookup...)

   when performing a match, lookup or other similar ops, Don't run the query as I write the conditions but only when I'm done. this will improve speed significantly and will prevent crashes due to lack of memory on very large sets.

   when an operation that filters data occurs, you can add a small toggle btn when I'm done writing the query, and only then perform the search.
   another idea is to add a boolean field named done which on init will be set to false, and when a user is done writing the query it sets it last to true.
   the benefit of the field is it will be applicable also in text mode and not just stages.

   attached an example.

   when performing a match, lookup or other similar ops, Don't run the query as I write the conditions but only when I'm done. this will improve speed significantly and will prevent crashes due to lack of memory on very large sets.

   when an operation that filters data occurs, you can add a small toggle btn when I'm done writing the query, and only then perform the search.
   another idea is to add a boolean field named done which on init will be set to false, and when a user is done writing the query it sets it last to true.… more

   •  

   1 vote

   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  ·  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. PKCS#11 Support for Compass
   1 vote

   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  ·  Connectivity  ·  Edit…  ·  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. Sync queries across multiple computers or installations of Compass

   I work on multiple computers and I find my self missing queries that I have already created on other computers. It would be nice to have queries that are linked to a collection to be synced when using Compass on other computers. Maybe something like Github can be used as the central storage for the queries or allow users to selected popular storage options if Compass can't provide the storage natively.

   1 vote

   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  ·  Edit…  ·  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. Aggregation editor improvements

   settings for the following:
   - Turn off auto-pairs (some people really are not used to typing with it)
   - Vim keybinds (somewhat joking, but also not)
   - View full documentation within Compass.
   - Currently it seems the website manual is the only place to view documentation, being able to see it within Compass would be helpful
   - Quick reference for operators / expressions
   - Font settings (increase, boldness, change font).

   Really just turning off auto-closing brackets would be great.

   1 vote

   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  ·  Edit…  ·  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

5. Automatically pre-call `mongod --dbpath <path>` for connections to localhost.

   On Windows, whenever we connect to a localhost mongo, we need to call mongod --dbpath <db path> in a Command Prompt or Powershell prompt before clicking the "Connect" button in Compass.
   So Compass should offer the ability to automatically "pre-call" that and then perform the connection (if call was successful).

   1 vote

   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  ·  Edit…  ·  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. more aggregation pipelines are needed and most of the time if we reach above 30 pipeline its gets struck , and more hard to use

   more aggregation pipelines are needed and most of the time if we reach above 30 pipeline its gets struck , and more hard to use

   1 vote

   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  ·  Edit…  ·  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. RANDOM VALUES USING THE 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 don't we do in mongodb instead of going to python for some random number which have unique values.

   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… more

   1 vote

   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  ·  Edit…  ·  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. Changes in the objectID which is unique.1

   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 don't we do in mongodb rather than python.

   can you please add this secenrio

   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… more

   1 vote

   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  ·  Edit…  ·  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. import export database not only one data of collection

   1. able to export a database with all collection and insert it also
   2. able to export a collection from a database and insert it to database also ,not only data of a collection but also collection self with all related
   1 vote

   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  ·  Edit…  ·  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. One more dropdown option should be there for all Columns

    While Importing the files, the change of datatypes should have one more drop-down option to change all columns/field datatypes to strings/mixed/double/Int32/number, etc.

    1 vote

    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  ·  Edit…  ·  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. cross cluster lookup (kind of)

    Hi,
    This is more of an add-on request for the aggregate().

    Lets say we have two clusters , second clusters is derived from first cluster ( i-e some of the object ids in second cluster exist only in first cluster ).

    Now I want to do a lookup for the id in the first cluster from the second cluster , which is not possible.

    So , can we have another optional parameter in the aggregate function which allows us to pass the documents , over which we can apply the required stages ( i-e after using find() on cluster 2 , I will pass the result into an aggregate() call for cluster 1 ).

    example query ->
    db1 points to cluster1
    db2 point to cluster2.

    I am working on Node.js -
    let result=[];
    let response = await db2.find().forEach(item=>{
    result.push(item);
    });

    let lookupResponse = await db1.aggregate([<stages>],{},result);

    Here in the second query , the documents in which the aggregate stages should work
    is the documents present in the variable 'result'.

    I hope I was able to explain my idea.
    It would really help if this is added in the next update.

    Thanks,
    Dushyant.

    Hi,
    This is more of an add-on request for the aggregate().

    Lets say we have two clusters , second clusters is derived from first cluster ( i-e some of the object ids in second cluster exist only in first cluster ).

    Now I want to do a lookup for the id in the first cluster from the second cluster , which is not possible.

    So , can we have another optional parameter in the aggregate function which allows us to pass the documents , over which we can apply the required stages ( i-e after using find() on cluster 2… more

    1 vote

    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  ·  1 comment  ·  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

12. Tabs Name

    Hi,
    When you open a DB with Compass, all of the tabs are showing

    Documents
    DBName...

    and you should mouse over them or click them to find out which they belong to which collection
    Instead of always showing “Documents” and “DBName”, you may show which collection they are

    •  

    1 vote

    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  ·  Edit…  ·  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. When exporting a collection, make sorting the fields by alphabet optional

    At this moment, one can only select or deselect fields, but one cannot pick any field order other than alphanumerically sorted. I would at least expect 'collection order', but taking this even a step further, it would be awesome if the export fields could be reordered in any order.

    1 vote

    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  ·  Edit…  ·  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. shortcut

    For VIM user it will be more efficient when Compass Has VIM like key binding Shortcut...

    1 vote

    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  ·  Edit…  ·  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. Save export CSV configured fields in favourite query

    In case of exporting the result of a find query in a CSV file, at the moment (v. 1.36.4) we need to select which fields we are interested at the first time and in case of reuse of the favourite query we need to select these fields again.
    In fact, in the default behaviour, all fields are selected from the sampled result in the CSV exporting process.

    One way could be to save the selected fields from the CSV export configuration in the favourite query settings.

    Other ideas?

    Thanks.

    1 vote

    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  ·  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

16. Yellow triangle icon for "drop index" and other caution messages

    In MongoDB Compass, when I use the Drop Index functionality you get when clicking the "trash can" icon next to an index in the Indexes list on a collection, it shows a red "!" triangle icon in the upper left. That icon is used here to mean "Caution! You are about to do something dangerous!", as confirmed in Support case https://support.mongodb.com/case/01122132.

    I think it's more conventional to use red icons, especially "!" or triangles like this, to indicate that an error has occurred, and warnings or cautions are more conventionally indicated in yellow. (There's probably some UI/UX documents or standards out there that cover this, but I don't know UI/UX that well.) Maybe this icon should be yellow instead? And only change to red if there was an error performing a requested Drop Index action?

    Cheers,
    Andrew

    In MongoDB Compass, when I use the Drop Index functionality you get when clicking the "trash can" icon next to an index in the Indexes list on a collection, it shows a red "!" triangle icon in the upper left. That icon is used here to mean "Caution! You are about to do something dangerous!", as confirmed in Support case https://support.mongodb.com/case/01122132.

    I think it's more conventional to use red icons, especially "!" or triangles like this, to indicate that an error has occurred, and warnings or cautions are more conventionally indicated in yellow. (There's probably some UI/UX documents or… more

    •  

    1 vote

    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  ·  Edit…  ·  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. refresh

    I would like to propose new functionality to auto-refresh a collection in MongoDB Compass. For example, if I am waiting for a document to update, today I have to click refresh repetitively until the document has updated. I would like to set auto-refresh with a filter in place to be able to watch the collection as documents are updating, instead of having to click the refresh button every ~5 seconds. 

    Steps to follow:
    - Log into MongoDB
    - Open to view a collection 
    - Filter by some criteria, and click Find 
    - Click Refresh icon to reload the documents in the collection 

    I would expect auto-refresh to show some the same spinning action on the refresh icon, and continue refreshing every ~5 seconds while it is enabled/turned on. 

    I would expect to see the documents in the collection refresh every ~5 seconds with this action.

    Additional notes:
    - I have a filter with a sort that I use daily to manage incoming documents 
    - I limit my filter by 100 records, but that could be reduced to 20 if 100 is too much to auto-refresh by 

    I would like to propose new functionality to auto-refresh a collection in MongoDB Compass. For example, if I am waiting for a document to update, today I have to click refresh repetitively until the document has updated. I would like to set auto-refresh with a filter in place to be able to watch the collection as documents are updating, instead of having to click the refresh button every ~5 seconds. 

    Steps to follow:
    - Log into MongoDB
    - Open to view a collection 
    - Filter by some criteria, and click Find 
    - Click Refresh icon to reload the documents in… more

    1 vote

    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  ·  Edit…  ·  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. Chrome like controls

    I would like to be able to use chrome like controls to switch between tabs

    Cmd+opt+arrows - previous, next tab
    Cmd+t - create new tab (and select it like vs code cmd+p mode)
    Cmd+w - close tab

    1 vote

    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  ·  Edit…  ·  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. Add a DISCONNECT option to the 3 dots dropdown menu when a connection is active

    At the moment, there is no obvious way to disconnect from your connection to connect to another database, and you have to go through the top level Connect menu, which is quite cumbersome.

    •  

    1 vote

    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  ·  Connectivity  ·  Edit…  ·  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. Query console like the one in Datagrip

    We need a query console like the one in the Datagrip IDE from JetBrains so that we can make any query as well as add comments or saving all these queries in the MongoDB Compass

    •  

    1 vote

    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  ·  Edit…  ·  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