DOC_1788-loading-using-eof

modules/ddl-and-loading/pages/running-a-loading-job.adoc

@@ -47,7 +47,7 @@ For more information, see xref:tigergraph-server:user-access:access-control-mode
 ----
 RUN LOADING JOB [-noprint] [-dryrun] [-n [i],j] job_name [
     USING file_var [="file_path_string"][, file_var [="file_path_string"]]*
-    [, CONCURRENCY="cnum"][,BATCH_SIZE="bnum"]
+    [, CONCURRENCY=cnum][,BATCH_SIZE=bnum][,EOF="eof_mode"]
 ]
 ----
 
@@ -110,6 +110,12 @@ The `CONCURRENCY` parameter sets the maximum number of concurrent requests that
 
 The `BATCH_SIZE` parameter sets the number of data lines included in each concurrent request sent to the GPE.  The default is 8192.
 
+==== `EOF`
+This is a boolean parameter (`"True"` or `"False"`). There are two modes for the S3 Loader: streaming mode (`"False"`) and EOF mode (`"True"`). The default mode is `"False"`): streaming mode.
+
+* In streaming mode, loading will never stop until the job is aborted.
+* In EOF mode, loading will stop after consuming the provided file objects.
+
 === Running Loading Jobs as REST Requests
 
 Another way to run a loading job is through the `+POST /ddl/{graph_name}+` endpoint of the REST{pp} server. Since the REST{pp} 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 xref:3.2@tigergraph-server:API:built-in-endpoints.adoc#_run_a_loading_job[Run a loading job].