I set up MongoDB (DocumentDB) in Azure and could not find an option to change the MongoDB version.
db.version() // return 3.2.0
Is it possible to update it to 3.4.2?
Seems like CosmosDB supports 3.4.
https://azure.microsoft.com/en-us/blog/azure-cosmosdb-extends-support-for-mongodb-aggregation-pipeline-unique-indexes-and-more/
The list of supported MongoDB API for CosmosDB is listed here
Related
Why MongoDB is not listed in the create-strapi-app installation process?
Starting from the release of Strapi v4, MongoDB is not supported natively anymore and no connector is available. Refer to this: https://strapi.io/blog/mongo-db-support-in-strapi-past-present-and-future
I originally posted this question on ServerFault, but it didn't get any traction, so I thought that stack might be a better forum for this question. My apologies if this out of line.
We are currently running parse-server (v2.7.2) on Heroku (node.js 7.10.1), connected to an mLab mongodb database. I recently received a notification
from mLab that they have been acquired by MongoDB and will be eventually migrating all customers to MongoDB Atlas.
The migration instructions from mLab to Atlas seem fairly self explanatory. My question concerns parse-server itself:
Does our version of parse-server (2.7.2) and node.js (7.10.1) have drivers that will support Atlas MongoDB?
MongoDB feature compatibility will depend on the underlying driver version which you can find by running npm list mongodb in the directory where you installed parse-server.
You can also check the mongodb driver version requested in parse-server's package.json, but a newer driver version may be installed depending on the semver notation used.
It looks like parse-server 2.7.2 uses the mongodb 3.0.1 driver, which is fully compatible with MongoDB 3.4 and 3.6 features according to the MongoDB Driver Compatibility documentation.
The MongoDB Node 3.0.x driver won't support newer features of MongoDB 4.0 (for example, transactions), but you should otherwise be fine with an Atlas deployment using MongoDB 3.4 or newer.
I'm trying to run:
db.data.find({email: 'random#test.com'}).collation({locale:'en'})
But I keep getting a .collation is not a function. Am I using the script wrong?
Thanks.
'Collation' is introduced in MongoDB 3.4. It is now possible to use Mongo DB 3.4 with the latest beta: Robomongo 1.1 - Beta version with MongoDB 3.4 Support. Fyi.
We are using mongo client tools such as Robomongo and MongoVUE from our windows/mac machines. On the mongodb server side, we decided to try out the new MongoDB 3.0.0rc8 with wiredtiger storage. However, we find that we are not able to list any collections from our client tools and mongo shell. If we login to the server box running mongodb, and then start a mongo shell, then we are able to view the collections.
Is this a known problem - that the existing tools like Robomongo and MongoVUE which have been supporting up to 2.6.X are not yet supporting mongodb 3.0.0?
Is there any mongo client that supports version 3.0.0?
Thanks and Regards,
Archanaa Panda
We encountered the same issue today and started evaluating MongoChef http://3t.io/mongochef which looks promising, both seen to UI, features and support for WiredTiger.
Here is the answer to this question i got on google forums from Will Berkeley-
Yes, those tools need to be updated to support 3.0 on WiredTiger. Many
tools enumerate namespaces by querying system collections that do not
exist when MongoDB is running WiredTiger. The mongo shell function
db.getCollectionNames() and the show command pre-3.0 does this, too -
the reason you can list collections on the 3.0 mongod box is that you
have the 3.0 mongo shell installed there.
-Will
I use NoSQL Manager for MongoDB with Mongo 3.0/WiredTiger
This is fixed as of February 1, 2016 with Robomongo.
Using the right version that is robomongo-0.9.0-rc8 fixed my problem.
I’m using MongoDB 2.4 and I’m looking for Geospatial Query Selectors support in the MongoDB .Net driver version 1.8.2.
I see support for $geoIntersects (MongoDB.Driver.Builders.Query.GeoIntersects), $near (MongoDB.Driver.Builders.Query.Near), $nearSphere (MongoDB.Driver.Builders.Query.Near).
Does the MongoDB .Net driver version 1.8.2 support $geoWithin??????
The MongoDB C# driver still uses the (deprecated) $within as opposed to $geoWithin. Here is the relevant open JIRA ticket if you'd like to keep an eye on it. :)