Hadoop support | AllegroGraph 9.0.1
Author: Franz Incorporated

Copyright (c) 2005 - 2026 Franz, Incorporated
Last updated 27 May 2026 at 10:34

# AllegroGraph 9.0.1 support for Hadoop

- Documentation Index
  - Release Notes
  - Quick Start
  - SSL/TLS Quick Start
  - Introduction
  - Setup and Configuration
    - Download
    - Server Installation
    - Server Configuration and Control
    - WebView
    - Database Upgrading
    - Managing Users
  - Server Management
    - Performance Tuning
    - Deleting Duplicate Triples
    - Purging Deleted Triples
    - Auditing
    - Managing Users
    - Replication
    - Point-in-Time Recovery
    - Transaction Log Archiving
    - Security Overview
    - Security Implementation
  - Tools
    - agtool
    - Data Loading
    - Data Export
    - Backup and Restore
    - Querying
    - RDFS++
    - Materializer
    - Event Scheduler
    - SHACL
  - Details
    - Triple Indices
    - Freetext Indices
    - Encoded IDs
    - Connection Pooling
    - N-dimensional Geospatial Overview
    - 2-D Geospatial
    - Temporal
    - Social Network
    - JavaScript
    - Datatypes
    - Data Conversion (Rapper)
    - Stored Procedures
    - Triple Attributes
    - Lineparse Format
  - Querying
    - SPARQL documentation summary
    - SPARQL Reference
    - SPIN
    - SPARQL Magic Properties
    - Prolog
  - 3rd-party tools
    - Solr text Indices
    - MongoDB integration
    - TopBraid Composer Plugin
    - Cloudera
  - Client APIs
    - Gruff
    - GraphTalker
    - REST/HTTP interface
    - HTTP reference
    - Javadocs (Sesame and Jena)
    - Python API
    - Lisp Reference
    - JavaScript
  - Tutorials
    - N-dimensional Geospatial
    - SPARQL Tutorial
    - Java Sesame
    - Java Jena
    - Python Sesame
    - Lisp
    - Prolog
    - More...
  - Other
    - Conferences and Seminars
    - Source Code on Github
    - Amazon EC2
    - Copyrights
  - Franz, Inc.

- Integrating with Hadoop

Documentation Index

## Integrating with Hadoop

For AllegroGraph users interested in integrating Hadoop as part of their application, we suggest the following pipeline for working with Hadoop.

1. Data is stored in Hadoop or Hbase.

2. Data is retrieved via Hive or Pig or straight Map Reduce and returned to AllegroGraph as csv tables, or json files.

3. We apply a mapping to these tables or json files to produce nodes and edges or triples that go into AllegroGraph.

At the integration level we can call SQL or PIG directly from AllegroGraph from Prolog. Here is a typical simplified Prolog example:

    (hive "select id, dob, dod from person" csv "person.csv")
    (triplemap "c:/tmp/person.map" "person.csv" "person.nt")
    (load-ntriples "person.nt")

An interesting customer example that leveraged the capabilities of AllegroGraph and Hadoop Los Alamos National Labs. For more information about their process please review the white paper avalable at http://franz.com/agraph/cresources/white_papers/.

There may be additional options working with Hadoop via Intel's GraphBuilder. For additional information please see this link:

http://www.intel.com/content/dam/www/public/us/en/documents/articles/intel-dsd-graph-builder-collateral-faq.pdf