Synopsis

Description

The gpsscli history command displays the commmit history of the
job submitted to a Greenplum Stream Server (GPSS) instance with the specified
configuration file. Information displayed includes the start and end times
of the load transaction and the beginning and ending data offsets.

You can request the complete commit history or the history for the last
batch of data written to Greenplum Database. By default,
gpsscli history displays the commit history of the latest data
load transaction.

If the GPSS instance to which you want to send the request is not running on
the default host (127.0.0.1) or the default port number
(5000), you can specify the GPSS host and/or port via command
line options.

Options

config.yaml

The YAML-formatted configuration file that defines the job parameters.
If the filename provided is not an absolute path, Greenplum Database
assumes the file system location is relative to the current working
directory.

--show-commit-history {all | latest}

Specify all to display the complete commit history
of the data load operation defined in config.yaml.
latest, the default, prints the commit history of the
last batch of data written to Greenplum Database.

--gpss-host host

Specify the GPSS host. The default host address is 127.0.0.1.

--gpss-port port

Specify the GPSS port number. The default port number is 5000.

-l | --log-dir directory

Specify the directory to which GPSS writes client command log files. GPSS
must have write permission to the directory. GPSS creates the log
directory if it does not exist.

If you do not provide this option,
GPSS writes gpsscli client log files to the
$HOME/gpAdminLogs directory.

-v | --verbose

The default behaviour of the command utility is to display
information and error messages to stdout. When you
specify the --verbose option, GPSS also outputs
debug-level messages about the operation.

-h | --help

Show command utility help, and then exit.

Examples

Display the full commit history of the data load operation defined in the
configuration file named loadcfg.yaml: