此内容没有您所选择的语言版本。
8.5. Configuration
The OData WAR file can be configured with following properties in the
web.xml
file.
Property Name
|
Description
|
Default Value
|
---|---|---|
batch-size
|
Number of rows to send back each time, -1 returns all rows
|
256
|
skiptoken-cache-time
|
Time interval between the results being recycled/expired between $skiptoken requests
|
300000
|
local-transport-name
|
JBoss Data Virtualization's Local transport name for connection
|
odata
|
JBoss Data Virtualization OData server, implements cursoring logic when the result rows exceed the configured batch size. On every request, only batch-size number of rows are returned. Each such request is considered an active cursor, with a specified amount of idle time specified by skip-token-cache-time. After the cursor is timed out, the cursor will be closed and remaining results will be cleaned up, and will no longer be available for further queries. Since there is no session based tracking of these cursors, if the request for skiptoken comes after the expired time, the original query will be executed again and tries to reposition the cursor to relative absolute potion, however the results are not guaranteed to be same as the underlying sources may have been updated with new information meanwhile.