Introduction to the Graph Data Interface
This topic introduces you to the Graph Data Interface (GDI) by providing setup instructions and information about the supported data sources.
The capabilities of the Graph Data Interface are potentially endless because it enables users to freely write a multitude of SPARQL queries against virtually any Data Source or endpoint. For this reason, we have labeled the GDI as a Preview release. Features are considered "Preview" when the implementation has recently been incorporated into the product, significant development is still underway, or when Quality Assurance testing cannot cover all possible use cases of the feature. When employing a Preview feature, Cambridge Semantics recommends that you thoroughly test your specific use cases in a development environment before relying on the feature in a production environment.
Graph Data Interface Setup
AnzoGraph processes Graph Data Interface (GDI) service calls using a Java plugin that is provided by your Cambridge Semantics Customer Success Manager. The plugin, gdi-*.jar, needs to be copied to the <install_path>/lib/udx directory on the AnzoGraph leader server. For more information and setup instructions, see Deploy the Graph Data Interface Java Plugin.
Supported Data Sources
The GDI natively supports reading or ingesting data from HTTP/REST endpoints. In addition, the following file types are supported:
- CSV and TSV
- JSON
- XML
- Parquet
- SAS (SAS Transport XPT and SAS7BDAT formats)
To extend the service to access relational databases, JDBC drivers can also be added to AnzoGraph. For more information, see Deploy Optional Drivers for Accessing Database Sources.
Kubernetes-based AnzoGraph deployments are pre-configured with the GDI plugin as well as JDBC drivers for the following database types:
- Apache Derby, Hive, and Impala
- Google BigQuery
- IBM DB2
- Microsoft SQL Server
- MariaDB/MySQL
- Hyper SQL Database (HSQLDB)
- PostgreSQL
- SAP Sybase (jTDS)