Oracle Property Graph Format

PGX allows the loading of property graphs from databases that support Oracle Property Graph schema. The Oracle Property Graph schema is implemented for the following database systems:

• Oracle RDBMS
• Oracle NoSQL Database
• Apache HBase

Graph Config for Oracle Property Graphs

To load Oracle Property Graphs from any database, you need to specify the following additional fields in the graph config:

Oracle RDBMS

For details on the support for the Oracle Property Graph format in the Oracle RDBMS, see Property Graph Schema Objects for Oracle Database. To load Oracle Property Graphs from the Oracle RDBMS database, you need to specify the following additional fields in the graph config:

Oracle NoSQL

To load Oracle Property Graphs from the Oracle NoSQL database, you need to specify the following additional fields in the graph config:

Apache HBase

To load Oracle Property Graphs from Apache HBase, you need to specify the following additional fields in the graph config:

Loading Vertex Properties as Labels

Since the PG format does not specify vertex labels, PGX allows to load vertex labels from a special vertex property instead. Typically a string property is used to load labels, but is not necessary.

To load a vertex property as vertex labels, you need to specify the name of the property in the use_vertex_property_value_as_label of the loading config. Notice that it is not required for the property to appear in the vertex_props section. If the property specified in use_vertex_property_value_as_label also appears in vertex_props it is both loaded as property and label.

If a vertex does not have a value for the specified property, a vertex will receive no labels as default.

The type of the property is assumed to be string. For type checking and conversion this mechanism relies on the same configuration values as for normal properties, as specified in the error_handling configuration. This means that by default the property values are converted into strings while logging a single warning.

By default the whole property is loaded as the single label of the vertex. An optional delimiter can be specified in the configuration parameter property_value_delimiter, to split the value of the property into multiple labels. For example the property value "label1, label2, label3" will be split into three distinct labels label1, label2 and label3.

Examples

For example, to load the property named label_property from a NoSQL instance, the following graph config can be used:

{
  "format": "pg",
  "db_engine": "nosql",
  "hosts": [
    "my-host1:5000",
    "my-host2:5000",
    "my-host3:5000"
  ],
  "store_name": "my-store",
  "name": "my-graph",
  "vertex_props": [{
    "name": "prop",
    "type": "float"
  }],
  "edge_props": [{
    "name": "name",
    "type": "string"
  }, {
    "name": "cost",
    "type": "double"
  }],
  "loading_options": {
    "use_vertex_property_as_label": "label_property"
  }
}

For example to load the property named label_property and delimit it by a comma, the following graph config can be used:

{
  "format": "pg",
  "db_engine": "nosql",
  "hosts": [
    "my-host1:5000",
    "my-host2:5000",
    "my-host3:5000"
  ],
  "store_name": "my-store",
  "name": "my-graph",
  "vertex_props": [{
    "name": "prop",
    "type": "float"
  }],
  "edge_props": [{
    "name": "name",
    "type": "string"
  }, {
    "name": "cost",
    "type": "double"
  }],
  "loading_options": {
    "use_vertex_property_as_label": "label_property",
    "property_value_delimiter" ","
  }
}