public final class ScanPolicy extends Policy
Modifier and Type | Field and Description |
---|---|
boolean |
concurrentNodes
Should scan requests be issued in parallel.
|
boolean |
failOnClusterChange
Terminate scan if cluster in migration state.
|
boolean |
includeBinData
Should bin data be retrieved.
|
int |
maxConcurrentNodes
Maximum number of concurrent requests to server nodes at any point in time.
|
long |
maxRecords
Approximate number of records to return to client.
|
int |
recordsPerSecond
Limit returned records per second (rps) rate for each server.
|
int |
scanPercent
Percent of data to scan.
|
compress, failOnFilteredOut, maxRetries, predExp, priority, readModeAP, readModeSC, replica, sendKey, sleepBetweenRetries, socketTimeout, timeoutDelay, totalTimeout
Constructor and Description |
---|
ScanPolicy()
Default constructor.
|
ScanPolicy(Policy other)
Copy scan policy from another policy.
|
ScanPolicy(ScanPolicy other)
Copy scan policy from another scan policy.
|
Modifier and Type | Method and Description |
---|---|
void |
validate()
Verify policies fields are within range.
|
setPredExp, setTimeout, setTimeouts
public long maxRecords
This field is supported on server versions >= 4.9.
Default: 0 (do not limit record count)
public int scanPercent
This field is supported on server versions < 4.9.
Server versions >= 4.9 might allow scanPercent, but not in conjunction with
maxRecords
. scanPercent is eventually slated for removal.
Default: 100
public int recordsPerSecond
Default: 0
public int maxConcurrentNodes
This field is only relevant when concurrentNodes is true.
Default: 0 (issue requests to all server nodes in parallel)
public boolean concurrentNodes
Default: true
public boolean includeBinData
Default: true
public boolean failOnClusterChange
Default: false
public ScanPolicy(ScanPolicy other)
public ScanPolicy(Policy other)
public ScanPolicy()
Set maxRetries for scans on server versions >= 4.9. All other scans are not retried.
The latest servers support retries on individual data partitions. This feature is useful when a cluster is migrating and partition(s) are missed or incomplete on the first scan attempt.
If the first scan attempt misses 2 of 4096 partitions, then only those 2 partitions are retried in the next scan attempt from the last key digest received for each respective partition. A higher default maxRetries is used because it's wasteful to invalidate all scan results because a single partition was missed.
Copyright © 2012–2023 Aerospike, Inc. All rights reserved.