Field Detail

PROPERTY_FILE

The property file (for a standalone bigdata instance) or the jini
configuration file (for a bigdata federation). The file must end with
either ".properties" or ".config". This parameter is ignored if the
IIndexManager is specified as an attribute of the web application
context.

READ_LOCK

The commit time against which the server will assert a read lock by
holding open a read-only transaction against that commit point
(optional). When given, queries will default to read against this
commit point. Otherwise queries will default to read against the most
recent commit point on the database. Regardless, each query will be
issued against a read-only transaction.

DESCRIBE_EACH_NAMED_GRAPH

When true and the KB instance is in the quads
mode, each named graph will also be described in in the same level of
detail as the default graph (default
false). Otherwise only the default
graph will be described.

Note: I have changed the default to false since this
operation can be long-running for messy web graphs such as the TBL six
degrees of freedom crawl. We wind up with one named graph for each
"friend", which is a lot of named graphs, plus there are a lot of
predicates that show up in web data. Together, this makes the per-named
graph response not a very good default. However, you can certainly enable
this if you only have a reasonable number of named graphs and/or only
expose the SPARQL end point to a limited audience.