Application Options

Doradus Spider supports the application-level options described below.

•	StorageService: All applications can explicitly choose their storage service by defining the application-level option StorageService. The storage service name for Spider applications is SpiderService. Example:

<application name="Msgs">

<options>

<option name="StorageService" value="SpiderService"/>

</options>

...

</application>

If an application does not set the StorageService option, it is assigned the Doradus server default. Once assigned, the StorageService option cannot be changed.

•	AutoTables: Doradus Spider supports an application-level Boolean option called AutoTables, which is set to true by default. When enabled, AutoTables allows tables to be implicitly created when objects are added to them. For example, suppose the following Add Batch command is submitted:

POST /Msgs/blogs

If the blogs table does not exist and the Msgs application’s AutoTable option is true, the table is automatically created and then the Add Batch request is processed. An automatically-created table has no predefined fields, hence all field assignments are treated as dynamic Text fields. To disallow the automatic creation of tables, AutoTables must be set to false. Example:

<application name="Msgs">

<key>MsgsKey</key>

<options>

<option name="AutoTables" value="false"/>

</options>

...

</application>

•

aging-check-frequency: This option specifies a default data aging check frequency for all tables in the application that use data aging. Any table can override this option with a table-specific option. The value of the aging-check-frequency must be in the form “<number> <units>” where <number> is a positive integer and <units> is MINUTES, HOURS, or DAYS. (Singular forms of these mnemonics are also allowed.) The following example sets the default data aging check frequency to 1 day:

<application name="Msgs">

<key>MsgsKey</key>

<options>

<option name="aging-check-frequency" value="1 DAY"/>

</options>

...

</application>