Running a Loading Job

Search…
Clearing and Initializing the Graph Store
There are two aspects to clearing the system: flushing the data and clearing the schema definitions in the catalog. Two different commands are available.
CLEAR GRAPH STORE
Available only to superusers.
The CLEAR GRAPH STORE command flushes all the data out of the graph store (database).  By default, the system will ask the user to confirm that you really want to discard all the graph data.  To force the clear operation and bypass the confirmation question, use the -HARD option, e.g.,
1
CLEAR GRAPH STORE -HARD
Copied!
Clearing the graph store does not affect the schema.
1.Use the -HARD option with extreme caution. There is no undo option. -HARD must be in all capital letters.
2.CLEAR GRAPH STORE stops all the TigerGraph servers (GPE, GSE, RESTPP, Kafka, and Zookeeper).
3.Loading jobs and queries are aborted.
​DROP ALL clears both the data and the schema. 
Running a Loading Job
Running a loading job executes a previously installed loading job.  The job reads lines from an input source, parses each line into data tokens, and applies loading rules and conditions to create new vertex and edge instances to store in the graph data store. The input sources could be defined in the load job or could be provided when running the job. Additionally, loading jobs can also be run by submitted an HTTP request to the REST++ server.
RUN LOADING JOB
RUN LOADING JOB syntax for concurrent loading
1
RUN LOADING JOB [-noprint] [-dryrun] [-n [i],j] jobname [
2
    USING filevar [="filepath_string"][, filevar [="filepath_string"]]*
3
    [, CONCURRENCY="cnum"][,BATCH_SIZE="bnum"]
4
]
Copied!
Note that the keyword LOADING is included. This makes it more clear to users and to GSQL that the job is a loading job and not some other type of job ( such as a SCHEMA_CHANGE JOB).
When a concurrent loading job is submitted, it is assigned a job ID number, which is displayed on the GSQL console.  The user can use this job ID to refer to the job, for a status update, to abort the job, or to re-start the job.  These operations are described later in this section.
Options
-noprint
By default, the command will print several lines of status information while the loading is running. 
If the -noprint option is included, the output will omit the progress and summary details, but it will still display the job id and the location of the log file.
Example of minimal output when -noprint option is used
1
Kick off the following job:
2
  JobName: load_videoE, jobid: gsql_demo_m1.1525091090494
3
  Loading log: '/usr/local/tigergraph/logs/restpp/restpp_loader_logs/gsql_demo/gsql_demo_m1.1525091090494.log'
Copied!
-dryrun
If -dryrun is used, the system will read the data files and process the data as instructed by the job, but will NOT load any data into the graph. This option can be a useful diagnostic tool.
-n [i], j
The -n option limits the loading job to processing only a range of lines of each input data file. The -n flag accepts one or two arguments. For example, -n 50 means read lines 1 to 50. 
-n 10, 50 means read lines 10 to 50.  The special symbol $ is interpreted as "last line", so -n 10,$ means reads from line 10 to the end.
Parameters
Below are the parameters available for the RUN QUERY command introduced by the USING clause. 
filevar list
The optional USING clause may contain a list of file variables. Each file variable may optionally be assigned a filepath_string, obeying the same format as in the CREATE LOADING JOB. This list of file variables determines which parts of a loading job are run and what data files are used.
When a loading job is compiled, it generates one RESTPP endpoint for each filevar and filepath_string.  As a consequence, a loading job can be run in parts. When RUN LOADING JOB is executed, only those endpoints whose filevar or file identifier (" __GSQL_FILENAME_n__") is mentioned in the USING clause will be used. However, if the USING clause is omitted, then the entire loading job will be run.
If a filepath_string is given, it overrides the filepath_string defined in the loading job. If a particular filevar is not assigned a filepath_string either in the loading job or in the RUN LOADING JOB statement, then an error is reported and the job exits.
CONCURRENCY
The CONCURRENCY parameter sets the maximum number of concurrent requests that the loading job may send to the GPE.  The default is 256.
BATCH_SIZE
The BATCH_SIZE parameter sets the number of data lines included in each concurrent request sent to the GPE.  The default is 8192.
Running Loading Jobs as REST Requests
Another way to run a loading job is through the POST /ddl/{graph_name} endpoint of the REST++ server. Since the REST++ server has more direct access to the graph processing engine, this can execute more quickly than a RUN LOADING JOB statement in GSQL. For details on how to use the endpoint, please see Run a loading job. 
Inspecting and Managing Loading Jobs
Starting with v2.0, there are now commands to check loading job status, abort a loading job and, restart a loading job.
Job ID and Status
When a loading job starts, the GSQL server assigns it a job id and displays it for the user to see. The job id format is typically the name of the graph, followed by the machine alias, following by a code number, e.g., gsql_demo_m1.1525091090494
Example of SHOW LOADING STATUS output
1
Kick off the following job, i.e.
2
  JobName: load_test1, jobid: demo_graph_m1.1523663024967
3
  Loading log: '/home/tigergraph/tigergraph/logs/restpp/restpp_loader_logs/demo_graph/demo_graph_m1.1523663024967.log'
4
​
5
Job "demo_graph_m1.1523663024967" loading status
6
 
7
[RUNNING] m1 ( Finished: 3 / Total: 4 )
8
  [LOADING] /data/output/company.data
9
  [=============                        ]  20%, 200 kl/s
10
  [LOADED]
11
  +-------------------------------------------------------------------+
12
  |               FILENAME |   LOADED LINES |   AVG SPEED |   DURATION|
13
  | /data/output/movie.dat |            100 |     100 l/s |     1.00 s|
14
  |/data/output/person.dat |            100 |     100 l/s |     1.00 s|
15
  | /data/output/roles.dat |            200 |     200 l/s |     1.00 s|
16
  +-------------------------------------------------------------------+
17
[RUNNING] m2 ( Finished: 1 / Total: 2 )
18
  [LOADING] /data/output/company.data
19
  [==========================           ]  60%, 200 kl/s
20
  [LOADED]
21
  +-------------------------------------------------------------------+
22
  |               FILENAME |   LOADED LINES |   AVG SPEED |   DURATION|
23
  | /data/output/movie.dat |            100 |     100 l/s |     1.00 s|
24
  +-------------------------------------------------------------------+
Copied!
By default, an active loading job will display periodic updates of its progress.  There are two ways to inhibit these automatic output displays:
1.Run the loading job with the -noprint option.
2.After the loading job has started, enter CTRL+C. This will abort the output display process, but the loading job will continue.
SHOW LOADING STATUS
The command SHOW LOADING JOB shows the current status of either a specified loading job or all current jobs:
SHOW LOADING JOB syntax
1
SHOW LOADING STATUS job_id|ALL
Copied!
The display format is the same as that displayed during the periodic progress updates of the RUN LOADING JOB command. If you do not know the job id, but you know the job name and possibly the machine, then the ALL option is a handy way to see a list of active job ids.
ABORT LOADING JOB
The command ABORT LOADING JOB aborts either a specified load job or all active loading jobs:
ABORT LOADING JOB syntax
1
ABORT LOADING JOB job_id|ALL
Copied!
The output will show a summary of aborted loading jobs.
ABORT LOADING JOB example
1
gsql -g demo_graph "abort loading job all"
2
​
3
Job "demo_graph_m1.1519111662589" loading status
4
[ABORT_SUCCESS] m1
5
[SUMMARY] Finished: 0 / Total: 2
6
  +--------------------------------------------------------------------------------------+
7
  |                  FILENAME |   LOADED LINES |   AVG SPEED  |   DURATION |   PERCENTAGE|
8
  | /home/tigergraph/data.csv |       23901701 |     174 kl/s |   136.83 s |         65 %|
9
  |/home/tigergraph/data1.csv |              0 |        0 l/s |     0.00 s |          0 %|
10
  +--------------------------------------------------------------------------------------+
11
 
12
Job "demo_graph_m2.1519111662615" loading status
13
[ABORT_SUCCESS] m2
14
[SUMMARY] Finished: 0 / Total: 2
15
  +--------------------------------------------------------------------------------------+
16
  |                  FILENAME |   LOADED LINES |   AVG  SPEED |   DURATION |   PERCENTAGE|
17
  | /home/tigergraph/data.csv |       23860559 |     175 kl/s |   136.23 s |         65 %|
18
  |/home/tigergraph/data1.csv |              0 |        0 l/s |     0.00 s |          0 %|
19
  +--------------------------------------------------------------------------------------+
Copied!
RESUME LOADING JOB
The command RESUME LOADING JOB will restart a previously-run job which ended for some reason before completion.
RESUME LOADING JOB syntax
1
RESUME LOADING JOB job_id
Copied!
If the job is finished, this command will do nothing. The RESUME command should pick up where the previous run ended; that is, it should not load the same data twice.
RESUME LOADING JOB example
1
gsql -g demo_graph "RESUME LOADING JOB demo_graph_m1.1519111662589"
2
[RESUME_SUCCESS] m1
3
[MESSAGE] The current job got resummed
Copied!
Verifying and Debugging a Loading Job
Every loading job creates a log file. When the job starts, it will display the location of the log file. Typically, the file is located at
<TigerGraph.root.dir>/logs/restpp/restpp_loader_logs/<graph_name>/<job_id>.log
This file contains the following information which most users will find useful:
A list of all the parameter and option settings for the loading job
A copy of the status information that is printed
Statistics report on the number of lines successfully read and parsed
The statistics report include how many objects of each type is created, and how many lines are invalid due to different reasons. This report also shows which lines cause the errors. Here is the list of statistics shown in the report. There are two types of statistics. One is file level (the number of lines), and the other is data object level (the number of objects). If an file level error occurs, e.g., a line does not have enough columns, this line of data is skipped for all LOAD statements in this loading job. If an object level error or failed condition occurs, only the corresponding object is not created, i.e., all other objects in the same loading job are still created if no object level error or failed condition for each corresponding object.
File level statistics
Explanation
Valid lines
The number of valid lines in the source file
Reject lines
The number of lines which are rejected by reject_line_rules
Invalid Json format
The number of lines with invalid JSON format
Not enough token
The number of lines with missing column(s)
Oversize token
The number of lines with oversize token(s). Please increase "OutputTokenBufferSize" in the tigergraph/app/<VERSION_NUM>/dev/gdk/gsql/config file.
Object level statistics
Explanation
Valid Object
The number of objects which have been loaded successfully
No ID found
The number of objects in which PRIMARY_ID is empty
Invalid Attributes
The number of invalid objects caused by wrong data format for the attribute type
Invalid primary id
The number of invalid objects caused by wrong data format for the PRIMARY_ID type
incorrect fixed binary length
The number of invalid objects caused by the mismatch of the length of the data to the type defined in the schema
Note that failing a WHERE clause is not necessarily a bad result.  If the user's intent for the WHERE clause is to select only certain lines, then it is natural for some lines to pass and some lines to fail.
Below is an example.
1
CREATE VERTEX movie (PRIMARY_ID id UINT, title STRING, country STRING COMPRESS, year UINT)
2
CREATE DIRECTED EDGE sequel_of (FROM movie, TO movie)
3
CREATE GRAPH movie_graph(*)
4
CREATE LOADING JOB load_movie FOR GRAPH movie_graph{
5
  DEFINE FILENAME f
6
  LOAD f TO VERTEX movie VALUES ($0, $1, $2, $3) WHERE to_int($3) < 2000;
7
}
8
RUN LOADING JOB load_movie USING f="movie.dat"
Copied!
movie.dat
1
0,abc,USA,-1990
2
1,abc,CHN,1990
3
2,abc,CHN,1990
4
3,abc,FRA,2015
5
4,abc,FRA,2005
6
5,abc,USA,1990
7
6,abc,1990
Copied!
The above loading job and data generate the following report
load_output.log (tail)
1
--------------------Statistics------------------------------
2
Valid lines:             6
3
Reject lines:            0
4
Invalid Json format:     0
5
Not enough token:        1 [ERROR] (e.g. 7)
6
Oversize token:          0
7
​
8
Vertex:                  movie
9
Valid Object:            3
10
No ID found:             0
11
Invalid Attributes:      1 [ERROR] (e.g. 1:year)
12
Invalid primary id:      0
13
Incorrect fixed
14
binary length:           0
15
Passed condition lines:  4
16
Failed condition lines:  2 (e.g. 4,5)
Copied!
There are a total of 7 data lines. The report shows that
Six of the lines are valid data lines
One line (Line 7) does not have enough tokens.
Of the 6 valid lines,
Three of the 6 valid lines generate valid movie vertices.
One line has an invalid attribute  (Line 1: year)
Two lines (Lines 4 and 5) do not pass the WHERE clause.