forked from brianfrankcooper/YCSB
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request brianfrankcooper#117 from gelin/fieldnameprefix
Conflicts: core/src/main/java/com/yahoo/ycsb/workloads/CoreWorkload.java doc/coreproperties.html hbase/src/main/java/com/yahoo/ycsb/db/HBaseClient.java
- Loading branch information
Showing
2 changed files
with
16 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -39,7 +39,8 @@ <H2>Core workload package properties</h2> | |
<LI><b>requestdistribution</b>: what distribution should be used to select the records to operate on - uniform, zipfian or latest (default: uniform) | ||
<LI><b>maxscanlength</b>: for scans, what is the maximum number of records to scan (default: 1000) | ||
<LI><b>scanlengthdistribution</b>: for scans, what distribution should be used to choose the number of records to scan, for each scan, between 1 and maxscanlength (default: uniform) | ||
<LI><b>insertorder</b>: should records be inserted in order by key ("ordered"), or in hashed order ("hashed") (default: hashed) | ||
<LI><b>insertorder</b>: should records be inserted in order by key ("ordered"), or in hashed order ("hashed") (default: hashed) | ||
<LI><b>fieldnameprefix</b>: string prefix for the field name (default: “field”) | ||
</UL> | ||
<HR> | ||
YCSB - Yahoo! Research - Contact [email protected]. | ||
|