How do I run the stress_test_shifts commands from the shell?
Table of Contents
This file documents the stress_test_shifts resource at the shell, one section per command. Every command is a subcommand of stress_test_shifts, and every section exports its own script into projects/ores.shell/scripts/library/. Loading a script runs that one command, so a failure names the command it came from.
1. Commands
1.1. list
Reads one page of the collection. Nothing addresses it but the caller's tenant, so it is the read that shows what exists.
The command is shaped like this:
stress_test_shifts list [--offset <n>] [--limit <n>] [--order <field>] [--desc]
It is addressed at analytics.v1.stress_test_shifts.list.
stress_test_shifts list --limit 1
1.2. get
Reads the one row its key addresses. A key states every identifying column, so a partial key is refused rather than answered with an arbitrary row.
The command is shaped like this:
stress_test_shifts get <id>
It is addressed at analytics.v1.stress_test_shifts.get.
stress_test_shifts get 00000000-0000-0000-0000-000000000000
1.3. get-many
Reads several rows in one request, one key group per row.
The command is shaped like this:
stress_test_shifts get-many <id>
It is addressed at analytics.v1.stress_test_shifts.get_many.
stress_test_shifts get-many 00000000-0000-0000-0000-000000000000
1.4. add
Writes a row. The change states that the row must not exist, so a create that collides with an existing row is refused rather than replacing it. The change carries a reason and a commentary, which the server records on it so the row's history says why it moved.
The command is shaped like this:
stress_test_shifts add <stress_test_scenario_id> <family> <object_key> <shift_type> <shifts> <shift_tenors> <shift_expiries> <extras> <position> <reason> <commentary>
It is addressed at analytics.v1.stress_test_shifts.put.
stress_test_shifts add 00000000-0000-0000-0000-000000000000 __none__ __none__ - - - - - 0 system.new_record generated_script
1.5. set
Writes a row. The change states no precondition, so it replaces whatever row the key already addresses. The change carries a reason and a commentary, which the server records on it so the row's history says why it moved. Passing –version makes the write conditional on the version the caller last read.
The command is shaped like this:
stress_test_shifts set <id> <stress_test_scenario_id> <family> <object_key> <shift_type> <shifts> <shift_tenors> <shift_expiries> <extras> <position> <reason> <commentary> [--version <n>]
It is addressed at analytics.v1.stress_test_shifts.put.
stress_test_shifts set 00000000-0000-0000-0000-000000000000 00000000-0000-0000-0000-000000000000 __none__ __none__ - - - - - 0 system.new_record generated_script
1.6. put-many
Writes several rows in one request. The count states how many field groups follow. The change carries a reason and a commentary, which the server records on it so the row's history says why it moved.
The command is shaped like this:
stress_test_shifts put-many --count <n> <id> <stress_test_scenario_id> <family> <object_key> <shift_type> <shifts> <shift_tenors> <shift_expiries> <extras> <position> <reason> <commentary>
It is addressed at analytics.v1.stress_test_shifts.put_many.
stress_test_shifts put-many --count 1 00000000-0000-0000-0000-000000000000 00000000-0000-0000-0000-000000000000 __none__ __none__ - - - - - 0 system.new_record generated_script
1.7. delete
Removes a row. The change carries a reason and a commentary, which the server records on it so the row's history says why it moved. Passing –version makes the write conditional on the version the caller last read.
The command is shaped like this:
stress_test_shifts delete <id> <reason> <commentary> [--version <n>]
It is addressed at analytics.v1.stress_test_shifts.delete.
stress_test_shifts delete 00000000-0000-0000-0000-000000000000 system.new_record generated_script
1.8. delete-many
Removes several rows in one request. The change carries a reason and a commentary, which the server records on it so the row's history says why it moved.
The command is shaped like this:
stress_test_shifts delete-many <id> <reason> <commentary>
It is addressed at analytics.v1.stress_test_shifts.delete_many.
stress_test_shifts delete-many 00000000-0000-0000-0000-000000000000 system.new_record generated_script
1.9. versions
Reads the row's recorded history, newest first.
The command is shaped like this:
stress_test_shifts versions <id> [--offset <n>] [--limit <n>] [--order <field>] [--desc]
It is addressed at analytics.v1.stress_test_shifts_versions.list.
stress_test_shifts versions 00000000-0000-0000-0000-000000000000 --limit 1
1.10. version
Reads one recorded version of the row.
The command is shaped like this:
stress_test_shifts version <id> --version <n>
It is addressed at analytics.v1.stress_test_shifts_versions.get.
stress_test_shifts version 00000000-0000-0000-0000-000000000000 --version 1