Post Views: 4
When we use NoSQL database, i.e. mongoDB, Cassandra, it's very tough to use command line to work on the database, today, i will introduce a very usefulUniversal SQL Client: "DBeaver", and it's FREE .
What's DBeaverDBeaver is free multi-platform database tool for developers, SQL programmers, database administrators and analysts. Supports all popular databases: mysql, PostgreSQL, SQLite, Oracle, DB2, SQL Server, Sybase, Teradata, MongoDB, Cassandra, Redis, etc.
There are two different editions, they are both free/
Community EditionCommunity Edition doesn't support too much NoSQL. You can get the source code from https://github.com/serge-rider/dbeaver
Enterprise EditionEnterprise Edition includes NoSQL databases support and additional Eclipse extensions for better project management. The source code is not open source.
Download & Install Download the edition which you want. YOu can download the zip one. Community Edition: http://dbeaver.jkiss.org/download/ Enterprise Edition: http://dbeaver.jkiss.org/download/enterprise/ Extract the package No need to install, just need to click dbeaver.exe to run it. Connect to MongoDB Open dbeaver.exe Click Menu Item: Database -> New Connection You will see a wizard for create a new connection Select a DB Driver, since we want to use MongoDB, I choose MongoDB. Click next. Then follow the wizard one by one. See screenshots as below.
Connecting to Cassandra Issue
By now, only DBeaver Enterprise Edition supports Cassandra, and by default it only supports cassandra-3.0.4. For cassandra 1.2.8, it throws exception. it's Native protocol issue: http://docs.datastax.com/en/developer/java-driver/3.1/manual/native_protocol/
The native protocol defines the format of the binary messages exchanged between the driver and Cassandra over TCP. As a driver user, you don’t need to know the fine details (although the protocol spec is in the Cassandra codebase if you’re curious); the most visible aspect is that some features are only available with specific protocol versions.
By default, the protocol version is negotiated between the driver and Cassandra when the first connection is established. Both sides are backward-compatible with older versions:
Cassandra: 1.2.x(DSE 3.2) 2.0.x
(DSE 4.0 to 4.6) 2.1.x
(DSE 4.7) 2.2.x 3.0.x Driver: 1.0.x v1 v1 v1 v1 Unsupported (1) 2.0.x to 2.1.1 v1 v2 v2 v2 Unsupported (1) 2.1.2 to 2.1.x v1 v2 v3 v3 Unsupported (2) 3.x v1 v2 v3 v4 v4
(1) Cassandra 3.0 does not support protocol versions v1 and v2
(2) There is a matching protocol version (v3), but the driver 2.1.x can’t read the new system table format of Cassandra 3.0
For example, if you use version 2.1.5 of the driver to connect to Cassandra 2.0.9, the maximum version you can use (and the one you’ll get by default) is protocol v2 (third row, second column). If you use the same version to connect to Cassandra 2.1.4, you can use protocol v3.
Related Posts DBeaver Free Universal SQL GUI Tools (Very Useful for NoSQL)