Recently I worked with Oracle Support on resolving a property graph related issue. One question asked was "how do we quickly sanity check property graph functions after an upgrade?" Well, I usually run through the following steps.
- Make sure BDSG Property Graph works well with Oracle NoSQL Database using the built-in Groovy shell.
All the above steps should work without a problem.
- Now, time to move on to Apache HBase.
// Get a graph config that has graph name "connections" and
// Zookeeper host, port, and some other parameters
cfg = GraphConfigBuilder.forPropertyGraphHbase() \
.addEdgeProperty("weight", PropertyType.DOUBLE, "1000000") \
// Get an instance of OraclePropertyGraph which is a key Java
// class to manage property graph data
opg = OraclePropertyGraph.getInstance(cfg);
// OraclePropertyGraphDataLoader is a key Java class
// to bulk load property graph data into the backend databases.
opgdl.loadData(opg, vfile, efile, 2);
Note that the above HBase-related steps are shorter than those for Oracle NoSQL Database. The reason is we no longer need to retest the embedded PGX because we have already done that for Oracle NoSQL Database.
- Finally, start a PGX server which can be used for a remote PGX client.
For simplicity, I am using HTTP (instead of HTTPS or two-way SSL) and this requires setting "enable_tls":false and "enable_client_authentication": false in the following configuration file.
To kick off the PGX server,
Open a browser and connect to the following URL, you should see a very simple line of text describing the version.
If you want to tune this endpoint a bit, take a look at a previous blog I wrote.