This content describes the most recent release of the CodeQL CLI. For more information about this release, see
https://github.com/github/codeql-cli-binaries/releases
.
To see details of the options available for this command in an earlier release, run the command with the
--help
option in your terminal.
Shell
codeql dataset import --dbscheme=<file> [--threads=<num>] <options>... -- <dataset> <trap>...
codeql dataset import --dbscheme=<file> [--threads=<num>] <options>... -- <dataset> <trap>...
[Plumbing] Import a set of TRAP files to a raw dataset.
Create a dataset by populating it with TRAP files, or add data from TRAP
files to an existing dataset. Updating a dataset is only possible if it
has the correct dbscheme
and
its ID pool has been preserved from the
initial import.
[Mandatory] Path to the raw QL dataset to create or update. The
directory will be created if it doesn't already exist.
Paths to .trap(.gz) files to import, or to directories that will be
recursively scanned for .trap(.gz) files. If no files are given, an
empty dataset will be created.
[Mandatory] The dbscheme definition that describes the TRAP files you
want to import.
Use this many threads for the import operation.
Defaults to 1. You can pass 0 to use one thread per core on the machine,
or -
N
to leave
N
cores unused (except still use at least one
thread).
[Advanced] Report errors for undefined labels.
[Advanced] Report errors for unused labels.
[Advanced] Report errors for repeated labels.
[Advanced] Report errors for redefined labels.
[Advanced] Report errors for labels used before they're defined.
[Advanced] Exit non-zero if an error occurs during trap import.
[Advanced] Construct entity IDs that encode the location in the TRAP
file they came from. Can be useful for debugging of TRAP generators, but
takes up a lot of space in the dataset.
[Advanced] Controls whether
codeql dataset import
is linkage-aware
(default)
or not. On projects where this part of database creation
consumes too much memory, disabling this option may help them progress
at the expense of database completeness.
Available since
v2.15.3
.
Show this help text.
[Advanced] Give option to the JVM running the command.
(Beware that options containing spaces will not be handled correctly.)
Incrementally increase the number of progress messages printed.
Incrementally decrease the number of progress messages printed.
[Advanced] Explicitly set the verbosity level to one of errors,
warnings, progress, progress+, progress++, progress+++. Overrides
-v
and
-q
.
[Advanced] Write detailed logs to one or more files in the given
directory, with generated names that include timestamps and the name of
the running subcommand.
(To write a log file with a name you have full control over, instead
give
--log-to-stderr
and redirect stderr as desired.)
[Advanced] Controls the location of cached data on disk that will
persist between several runs of the CLI, such as downloaded QL packs and
compiled query plans. If not set explicitly, this defaults to a
directory named
.codeql
in the user's home directory; it will be
created if it doesn't already exist.
Available since
v2.15.2
.