Arango logo

Verify Imports and Explore Collections

Verify that an import succeeded and inspect the resulting ArangoDB collections

After an import finishes, you can confirm success and inspect the resulting knowledge graph in two ways: through the Importer / platform APIs, and directly in your ArangoDB database.

For the schema of each collection (Documents, Chunks, Entities, Communities, Relations, SemanticUnits), the relationship-type diagram, and the vector indexes that are created, see Architecture.

Verifying via the API

Project status

You can verify the state of the Importer service deployed for a project via the Arango Control Plane (ACP):

GET https://<EXTERNAL_ENDPOINT>:8529/_platform/acp/v1/project_by_name/:project_name

The status object inside importerServices looks like this when the import completes successfully:

"status": {
    "status": "service_completed",
    "progress": 100,
    "message": ""
}

For the full list of status values and what they mean, see Architecture and Error Handling.

Multi-file job status

When you submitted the import via POST /v1/import-multiple, you can poll the job directly:

GET https://<EXTERNAL_ENDPOINT>:8529/graphrag/importer/:serviceIdPostfix/v1/jobs/:job_id

See Monitoring jobs for details.

Verifying via the ArangoDB web interface

  1. Connect to your ArangoDB instance.
  2. Navigate to the database where the Importer wrote.
  3. Confirm the following collections exist (where {project_name} is your project name):
    • {project_name}_Documents - original documents.
    • {project_name}_Chunks - text chunks.
    • {project_name}_Entities - extracted entities (Full GraphRAG only).
    • {project_name}_Communities - thematic clusters (Full GraphRAG only).
    • {project_name}_Relations - edge collection.
    • {project_name}_SemanticUnits - present only if enable_semantic_units was set to true.
  4. Confirm that the graph {project_name}_kg exists and contains the vertex and edge definitions above.

Querying the knowledge graph

Once collections are populated, you can:

  • Run AQL queries directly against the collections.
  • Traverse the graph using ArangoDB’s graph functions.
  • Filter by partition_id to scope queries to a specific partition.
  • Use AutoRAG for question-answering with citations against the imported documents.

Next steps