Unloads a workspace, label, or task stream to the unload depot or to a flat file.
p4 [g-opts] unload [-f -L -p -z] [-c client | -l label | -s stream]
p4 [g-opts] unload [-f -L -z] [-a | -al | -ac] [-d date | -u user]
Two uses for the
|To transfer infrequently-used metadata from Helix Core Server db.* files to a set of flat files in the unload depot
|To unload a client, label, or task stream to a flat file on the client
reporting commands often retrieve a superset of
the desired data, and then users take advantage of automated or manual post-processing to
discard the irrelevant lines of output. For example, the
Unloading metadata reduces the size of the working set required by Helix Server. On large sites with many years of historical metadata, unloading can offer significant performance improvements, reduce the output of the command-line queries and the amount of information displayed in applications like P4V
metadata that has been unloaded, use the
This is useful for seeding a client into another database, or for creating a private backup of the client. The flat file uses the standard journal format. The client, label, or task stream remains fully loaded after the command is run.
Requires the -o Option.
-l options to unload a specific
client workspace or label. Users can only unload their own
workspaces or labels. Administrators can use the
to unload workspaces and labels owned by other users.
You do not need to unload a workspace in preparation for moving it from
one edge server to another because running the
p4 reload command
automatically unloads the specified workspace before reloading it into a
new edge server.
to indicate that all specified labels and/or client workspaces are to be
unloaded. You cannot use these options if you are also using the
-d date and/or
to restrict the unloading operation to labels and/or workspaces older
than a specific
date, owned by a specific
user, or both.
-L option to unload locked workspaces and/or
labels. By default, only unlocked labels or workspaces are unloaded.
The access date for a workspace is updated when:
- the workspace is used by a command that directly references the workspace. These commands include: p4 add, p4 change, p4 delete, p4 diff, p4 edit, p4 have, p4 integrate, p4 labelsync, p4 lock, p4 move, p4 opened, p4 reconcile, p4 reopen, p4 resolve, p4 revert, p4 shelve, p4 submit, p4 sync, p4 unshelve, and p4 where
- the workspace is used in a revision specifier of the
Running p4 client does NOT update the access time, only the client Update time if the client spec is edited and saved.
The access date for a label is updated when:
- the label is used by a command that directly references that label.
- the label is used in a revision specifier of the
By default, data in the unload depot is uncompressed. Use
-z to store it in compressed form. Unloaded metadata is
often highly compressible, particularly in continuous build environments
characterized by millions of build-associated workspaces labels that are
used to perform a single build and then rarely, if ever, accessed
Unload all applicable client workspaces and labels; requires
Unload client workspaces; requires
Unload labels; requires
Unload the specified client workspace’s metadata from
Unload metadata older than the specified date.
Force option; administrators can unload workspaces, labels, and task streams owned by other users.
Unload the specified label from
Promote any non-promoted shelves belonging to the specified client that is being unloaded. The shelf is promoted to the commit server where it can be accessed by other edge servers.
Unload the specified task stream. Note that the
Unload metadata owned by the specified user.
Store the unloaded workspace, label, or task stream in compressed format.
See Global options.
|Can File Arguments Use Revision Specifier?
|Can File Arguments Use Revision Range?
|Minimal Access Level Required
- To unload a workspace or label, a user must be able to scan
all the files in the workspace’s have list An internal list indicates which files and revisions the client workspace has sync'd from the depot. See 'p4 have' in Helix Core Command-Line (P4) Reference. and/or files tagged
by the label. Administrators should set
MaxResultshigh enough (in the
p4 groupform) that users do not need to ask for assistance with
To reload data from the unload depot.