arangoexport Examples

    This exports the collections test into the directory dump as one big json array. Every entry in this array is one document from the collection without a specific order. To export more than one collection at a time specify multiple --collection options.

    The default output directory is export.

    arangoexport will by default connect to the _system database using the default endpoint. If you want to connect to a different database or a different endpoint, or use authentication, you can use the following command-line options:

    • : name of the database to connect to
    • --server.username <string>: username
    • --server.password <string>: password to use (omit this and you’ll be prompted for the password)
    • --server.authentication <bool>: whether or not to use authentication

    Here’s an example of exporting data from a non-standard endpoint, using a dedicated database name:

    1. arangoexport --server.endpoint tcp://192.168.173.13:8531 --server.username backup --server.database mydb --collection test --output-directory "my-export"

    When finished, arangoexport will print out a summary line with some aggregate statistics about what it did, e.g.:

    1. Processed 2 collection(s), wrote 9031763 Byte(s), 78 HTTP request(s)

    This exports the collection test into the output directory export as one json array. Every array entry is one document from the collection test

    Export JSONL

    1. arangoexport --type jsonl --collection test

    This exports the collection test into the output directory export as JSONL. Every line in the export is one document from the collection test as JSON.

    This exports the collection test into the output directory export as CSV. The first line contains the header with all field names. Each line is one document represented as CSV and separated with a comma. Objects and arrays are represented as a JSON string.

    Export XML

      XGMML is an XML application based on . To view the XGMML file you can use for example Cytoscape.

      If you export all attributes (--xgmml-label-only false) note that attribute types have to be the same for all documents. It wont work if you have an attribute named rank that is in one document a string and in another document an integer.

      Bad

      1. { "rank": 1 }   // doc1
      2. { "rank": "2" } // doc2

      Good

      1. { "rank": 1 } // doc1
      2. { "rank": 2 } // doc2

      XGMML specific options

      --xgmml-label-attribute specify the name of the attribute that will become the label in the xgmml file.

      --xgmml-label-only set to true will only export the label without any attributes in edges or nodes.

      Export based on collections

      Export based on a named graph

      This exports the named graph mygraph into the xgmml file mygraph.xgmml.

      Export XGMML without attributes

      1. arangoexport --type xgmml --graph-name mygraph --xgmml-label-only true

      This exports the named graph mygraph into the xgmml file mygraph.xgmml without the <att> tag in nodes and edges.

      Export XGMML with a specific label

      1. arangoexport --type xgmml --graph-name mygraph --xgmml-label-attribute name

      This exports the named graph mygraph into the xgmml file mygraph.xgmml with a label from documents attribute name instead of the default attribute label.

      Export via AQL query

        Export via an AQL query allows you to export the returned data as the type specified with --type. The example exports all books as JSONL that are sold more than 100 times.

        1. arangoexport --type csv --fields title,category1,category2 --query "FOR book IN books RETURN { title: book.title, category1: book.categories[0], category2: book.categories[1] }"

        A fields list is required for CSV exports, but you can use an AQL query to produce these fields. For example, you can de-normalize document structures like arrays and nested objects to a tabular form as demonstrated above.