<local-path-to-data>
containing
-U, --upsertPredicate
flag or the -x, --xidmap
flag.
-U, --upsertPredicate
flag to specify the predicate name in your data
that serve as unique identifier.
For example:
xid
equal to
my.org/customer/1
and sets the predicate firstName
with the value John
.
-x, --xidmap
directory to lookup the uid
value for each
node name used in the data file or to store the mapping between the node names
and the generated uid
for every new node.
-a, --alpha
flag as follows
--alpha
default value is localhost:9080
. You can specify a comma separated
list of alphas addresses in the same cluster to distribute the load.When the path provided with -f, --files
option is a directory, then all files
ending in .rdf
, .rdf.gz
, .json
, and .json.gz
are loaded. Be sure that
your schema file has another extension (.txt or .schema for example).Environment Variable | Description |
---|---|
AWS_ACCESS_KEY_ID or AWS_ACCESS_KEY | AWS access key with permissions to write to the destination bucket. |
AWS_SECRET_ACCESS_KEY or AWS_SECRET_KEY | AWS access key with permissions to write to the destination bucket. |
s3:///
(noticed the triple-slash ///
). The long form for S3 buckets requires a
double slash (s3://
).Environment Variable | Description |
---|---|
MINIO_ACCESS_KEY | MinIO access key with permissions to write to the destination bucket. |
MINIO_SECRET_KEY | MinIO secret key with permissions to write to the destination bucket. |
--creds
flag.
By default, Live Loader loads the data into the user’s namespace.
Guardians of the Galaxy
can load the data into multiple namespaces. Using --force-namespace
, a
Guardian can load the data into the namespace specified in the data and schema
files.
namespace
from the data and schema files
exist before loading the data.123
:
namespace
from the data and schema files
exist before loading the data.--encryption key-file=value
is added to the Live Loader. This
option is required to decrypt the encrypted export data and schema files. Once
the export files are decrypted, the Live Loader streams the data to a live Alpha
instance. Alternatively, starting with v20.07.0, the vault_*
options can be
used to decrypt the encrypted export and schema files.
p
directory is
encrypted. Otherwise, the p
directory is unencrypted.--new_uids
(default: false
): assign new UIDs instead of using the existing
UIDs in data files. This is useful to avoid overriding the data in a DB already
in operation.
--format
: specify file format (rdf
or json
) instead of getting it from
filenames. This is useful if you need to define a strict format manually.
-b, --batch
(default: 1000
): number of N-Quads to send as part of a
mutation.
-c, --conc
(default: 10
): number of concurrent requests to make to Dgraph.
Don’t confuse with -C
.
-C, --use_compression
(default: false
): enable compression for connections
to and from the Alpha server.
--vault
superflag’s options specify the Vault
server address, role id, secret id, and field that contains the encryption key
required to decrypt the encrypted export.