Configuring MultipleDatabasePlacement placement strategy in the properties file

The properties file allows users to set the object placement strategy within the database.  The following shows an example entry in the properties file with regard to MultipleDatabasePlacement placement strategy:

# Placement Strategy

A GraphDatabase federation may have upto 65535 databases, each of which can have upto 65535 containers.  The MultipleDatabasePlacement placement strategy requires a configuration string (the second line in the example above).  The ConfigString is a comma separated string where each comma separated entry denotes a database, along with it’s host server (optional), filepath (optional), and number of containers (required).  The hostname and path are not required, as theThe format of the configuration string is as follows:



Example 1. Two databases in the default location with 10 containers each:


Example 2. Two databases in the default location with 10 containers each, and one database on a remote server with 30 containers:



  1. Nixon Michaelangelo
    Posted June 25, 2010 at 10:39 am | Permalink

    This post was useful. Thank you guys.

    Does InfiniteGraph support SparQL-like queries or its equivalent. Where can I find documentation about Infinite Graph’s query capabilities?

    • Posted June 25, 2010 at 12:34 pm | Permalink

      You’re welcome! Right now we don’t support SparQL, but we’re looking at this for the product roadmap. And we’ll have more information about the query capabilities under the hood of InfiniteGraph shortly. Stay tuned!

Post a Comment

Required fields are marked *

%d bloggers like this: