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.
Related
My MongoDB 3.2. import does not work when I try to import a dump exported from by MongoDB 3.6.
Is there a way of using "mongodump" to export to be compatible to MongoDB 3.2.
Usually MongoDB suggest to not dump/restore between clusters having more than one major version apart.
What you could do is restore your dump from MongoDB 3.6, restore it to a MongoDB 3.4 and then dump it again fom 3.4 to finally restore to to MongoDB 3.2.
See: https://stackoverflow.com/a/41844502/5945338
Usually there are incompatibilities with more than 1 major versions, please try to upgrade your MongoDB 3.2 if possible, otherwise you might need to automate the 3.4 transition part.
I recently upgrade the version of mongodb. My previous version was 3.2
When I write on console;
mongod --version
db version v3.4.2
But I cannot use operators that comes with new version of mongodb (3.4) in MongoChef.
For example this one; https://docs.mongodb.com/manual/reference/operator/aggregation/indexOfBytes/
MongoChef doesn't complete or when I try to execute the string it throws an erroras;
the selection: invalid and cannot be executed.
Should I upgrade MongoChef as well? Why I cannot use the operators in version 3.4 while my mongodb version is it.
Check your MongoChef Version as only MongoChef vertion 4.5 + are compatible with 3.4 according to the release notes.
With that, I would recommend upgrading to the latest MongoChef release 5.1 - https://studio3t.com/download/
MongoChef is now called Studio 3T now.
We are planing to migrate mongoDB from 3.2 to 3.4 but we do not want to use new features like decimal type and collation.
Is it ok to use java driver version 3.2 to work with MongoDB 3.4?
According to official JAVA driver computability table it is not OK and you should be running version 3.4 of the driver.
I have work a lot with MongoDB 2.6, then I decide to start using MongoDB 3.0.2.
1) When I create an Database using the shell command, the command return true but
the database is not created.
use NewDatabaseName
2) When i try to create some collections, sometime is created and sometime no
I'm using Debian 64Bit, latest version.
Anybody is having this issue?
MongoDB 3.0 is not compatible with all GUI.
For example today MongoVUE do not work at all.
But MongoDB Management Studio sounds like the only one that really work.
Also here some other post related.
mongodb version 3.0.0 client robomongo mongovue
Yes your problem is GUI-related. You can check out different tools on this page:
http://mongodb-tools.com/
I will most probably be using MongoChef from now on.
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.