Importing and Exporting data from Dgraph Cloud

​

Importing data into Dgraph Cloud

1. Obtain dgraph binary or the latest docker image by following the installation instructions. This is required to run Dgraph CLI command dgraph live.
2. Obtain the gRPC endpoint of your Dgraph Cloud backend and a valid Client API key. An administrator gets those information with the following steps:
   • Log into the Dgraph Cloud account, select the backend
   • In the Admin section of the Dgraph Cloud console, go to Settings and copy the value of the gRPC Endpoint from the General tab.
   • Access the API Keys tab to generate an Client API Key.
     The gRPC endpoint is different from the GraphQL endpoint. The gRPC endpoint looks like <domain>:443
3. Run the Live Loader as follows:

docker run -it --rm -v <local-path-to-data>:/tmp dgraph/dgraph:latest \
dgraph live --slash_grpc_endpoint <grpc-endpoint> -f /tmp/<data-file> -s /tmp/<schema-file> -t <api-key>

docker run -it --rm -v <local-path-to-data>:/tmp dgraph/dgraph:latest \
  dgraph live --slash_grpc_endpoint <grpc-endpoint> -f /tmp -s /tmp/<schema-file> -t <api-key>

​

Exporting data from Dgraph Cloud

​

Exporting data from Dgraph Cloud using the console

1. In the Admin section of the Dgraph Cloud console, go to Settings.
2. In the Exports tab, click Create Export.
3. In the New export dialog, select the format you want to export.
4. Click Create.

​

Exporting data from Dgraph Cloud using a GraphQL client

1. Generate API Key for authentication.
2. Make a note of the GraphQL endpoint for the instance from Overview in the Dgraph Cloud console. Replace /graphql with /admin/slashin the GraphQL endpoint to get the <ADMIN_ENDPOINT>.
3. Authenticate the admin API requests by adding the <APIKEY> as the Dg-Auth header to every HTTP request.
4. To export data you need to send authenticated request to <ADMIN_ENDPOINT>.
5. Export data in JSON or RDF <FORMAT> using this mutation:
   Copy

   mutation {
     export(format: "<FORMAT>") {
       response {
         message
         code
       }
       exportId
       taskId
     }
   }
   

   A response similar to this appears:
   Copy

       "data": {
          "export":"exports/2011-12-08/0x18986fd-558223708",
          "response": {
             "code": "Success",
             "message": "Export queued with ID 0x9d2e13e8a"
          },
          "taskID": "0x9d2e13e8a"
       }
      }
   }
   

6. Make a note of the <EXPORT_ID> and the <TASK_ID>.
7. To get the status of export and the signed URLs to download the exported files, use this mutation:
   Copy

   query {
     exportStatus(exportId: "<EXPORT_ID>", taskId: "<TASK_ID>") {
       kind
       lastUpdated
       signedUrls
       status
     }
   }
   

   Depending on the format that you chose to create an export, three files are generated.

​

Exporting data from Dgraph Cloud programmatically

​

Exporting data with multi-tenancy feature enabled in Dgraph Cloud

• Cluster-wide export: this is an export of the entire backend (including all namespaces). This request can be only triggered by the Guardian of Galaxy users.
• Namespace-specific export: this is an export of a specific namespace. This request can be triggered by the Guardian of Galaxy users and by the Guardian of Namespace users.

​

Cluster-wide exports

1. Get the accessJWT token for the Guardian of Galaxy user. Send the following GraphQL mutation to the /admin endpoint:
   Copy

   mutation login($userId: String, $password: String, $namespace: Int) {
     login(userId: $userId, password: $password, namespace: $namespace) {
       response {
         accessJWT
         refreshJWT
       }
     }
   }
   

   Your variables should be referring to the Guardian of Galaxy user:
   Copy

   {
     "userId": "groot",
     "password": "password",
     "namespace": 0
   }
   

2. Once obtained the accessJWT token you need to pass it in X-Dgraph-AccessToken Header and only then you can send the following GraphQL mutation to /admin/slash endpoint:
   Copy

   mutation {
     export(namespace: -1) {
       response {
         code
         message
       }
       exportId
       taskId
     }
   }
   

3. Once done, you can now send the following GraqhQL mutation to get the signedUrls from where you can download your export files:
   Copy

   query {
     exportStatus(
       exportId: "<paste-your-exportId>"
       taskId: "<paste-your-taskId>"
     ) {
       kind
       lastUpdated
       signedUrls
       status
     }
   }
   

​

Namespace-specific exports

mutation {
  export(namespace: 123) {
    response {
      code
      message
    }
    exportId
    taskId
  }
}

mutation {
  export {
    response {
      code
      message
    }
    exportId
    taskId
  }
}