Using ArangoDB as your graph database?
you now have the opportunity to visualize your data graphically, using the “Graphs” tab in the admin interface.
In this post i will explain you how to do this:
Step 1) Configure the Interface
At first you have to configure the interface to display exactly the data you desire.
For the dataset you have two options:
- Select one vertex and one edge collection directly
- Select the graph by name created using the graphs api
- Manage your graphs
Then the interface offers you several advanced options:
- Decide if the graph is directed (only outbound edges are followed) or undirected (all edges are followed). By default we treat your graphs as undirected
- Define if you want to start at a random vertex in the graph. By default we will do that.
- Then you can define which of your attributes should be used as the label on the verticies. By default we will use the _key for this.
- Now lets bring in some colour. You can either use the same attribute for colouring as for labeling, but you can also use a different one
- Finally you can define a grouping of new nodes. This is useful to speed up the performance of the interface and to increase the usability. You can define a priority list of attributes here, which is elaborated from top to bottom: All vertices having the first attribute defined are grouped by its value. All other nodes are grouped by the second attribute if present etc.
Configuration of GraphViewer
In the latest version of ArangoDB (1.4) we have introduced a new tab in the Admin Interface: Graphs.
You can use this tab to view and modify your graphs stored in ArangoDB.
In this screencast you will get a short introduction on how to use the new system.
Measuring ArangoDB insert performance
ArangoDB offers a few APIs to insert documents. First, there is an HTTP API for bulk document imports. This API was already covered in another post. In general, the bulk import API should always be used when the task is to create many documents into a collection at once, as fast as possible. This works well if the documents are known in advance, e.g. when importing data from a file.
ArangoDB 1.4 provides support for multiple databases, a feature often requested by our users.
In the old days, ArangoDB provided the option to create multiple collections, but all collections were created on the same level. As there was no hierarchy of collections, there was a chance of having a collection name clash when using one ArangoDB server for multiple applications.
For example, running multiple applications inside the same ArangoDB server did not work if all applications created their own users collections. Workarounds, such as prefixing collection names, were required to make older ArangoDB versions play nicely with multiple applications.
With ArangoDB 1.4, multiple databases are supported natively. Workarounds such as prefixing collection names with application names, can go away now.
ArangoDB River Plugin for ElasticSearch
ArangoDB offers now a plugin for automated data transfer from ArangoDB into ElasticSearch.
If you want to benefit from ElasticSearch’s full text search capabilities for your ArangoDB document data, the easiest way to do so is to use this new plugin.
Implementing the push approach, otherwise, would make it necessary to write your own indexer, using your favorite programming language.
The ArangoDB river plugin software is an initial alpha version and licensed under the Apache 2 license.
ArangoDB 1.4 comes with asynchronous master-slave replication.
The new replication feature should make it much easier to create a backup from a running ArangoDB server. For example, a second ArangoDB instance can now be used as a slave by cloning all data from the master. The slave will be populated in the background while the master is running and accepting requests – not disrupting the master operations.
The bug-fix release 1.4.1 of ArangoDB is available for download. The fixed issues can be found in the changelog. It also fixes a problem with some of the build packages. The arangod daemon process was under some distributions started as root.
This is a follow to the post about ArangoDB 1.3 running on Raspberry PI. With the release of ArangoDB 1.4.0 I now tried to compile it again. As all patches required for 1.3 are part of 1.4.0 it is now much easier.
pi> sudo apt-get install libreadline6 libreadline6-dev libssl-dev
pi> git clone -b v1.4.0 https://github.com/triAGENS/ArangoDB
pi> cd ArangoDB
pi> ./configure --enable-all-in-one-icu --enable-all-in-one-v8 --enable-all-in-one-libev --disable-mruby
After a few hours, everything (including V8 & ICU) is compiled and you can start ArangoDB on a raspberry
pi> mkdir /tmp/testbase
pi> ./bin/arangod -c etc/relative/arangod.conf /tmp/testbase
and the shell in another window
pi> ./bin/arangosh -c etc/relative/arangosh.conf
or point your browser to
However, if you do not want to wait for hours, I’ve tried to build a debian package, which can be downloaded from here:
pi> wget https://www.arangodb.org/repositories/raspbian/arangodb-1.4.0-raspbian.deb
pi> sudo dpkg -i arangodb-1.4.0-raspbian.deb
This has not been tested in detail. So any feedback or improvements are welcome.
We are proud to announce that version 1.4.0 of ArangoDB has been released. The release is available for download here: https://www.arangodb.org/download
Thanks to all contributors and testers for your enormous help!
This release is a major milestone for us, because it contains two of the most wanted features:
- multi-database support
It also comes with:
The complete list of new features can be found here: https://www.arangodb.org/manuals/current/NewFeatures14.html
Packages for the bug-fix release 1.3.3 are now available from our web-site and from Homebrew. For a list of fixes checkout the CHANGELOG.