Update use-importer.md (#1876)

* Update use-importer.md * Update docs-2.0/nebula-importer/use-importer.md Co-authored-by: randomJoe211 <[email protected]>
vesoft-inc · Jan 17, 2023 · 7ae6b90 · 7ae6b90
1 parent 09bc9c4
commit 7ae6b90
Showing 1 changed file with 23 additions and 27 deletions.
diff --git a/docs-2.0/nebula-importer/use-importer.md b/docs-2.0/nebula-importer/use-importer.md
@@ -202,24 +202,23 @@ The example configuration is as follows:
 
 ```yaml
 workingDir: ./data/
- logPath: ./err/test.log
- files:
-   - path: ./student.csv
-     failDataPath: ./err/student
-     batchSize: 128
-     limit: 10
-     inOrder: false
+logPath: ./err/test.log
+files:
+  - path: ./student.csv
+    failDataPath: ./err/student.csv
+    batchSize: 128
+    limit: 10
+    inOrder: false
     type: csv
     csv:
-       withHeader: false
-       withLabel: false
-       delimiter: ","
-       lazyQuotes: false
+      withHeader: false
+      withLabel: false
+      delimiter: ","
 ```
 
 |Parameter|Default value|Required|Description|
 |:---|:---|:---|:---|
-|`workingDir`|-|No| Use this parameter to switch between multiple directories where multiple directories contain data with the same file structure. For example, the values of `path` and `failDataPath` configured below will automatically change to `./data/student` and `./data/err/student`. The parameters can be absolute or relative.|
+|`workingDir`|-|No|If you have multiple directories containing data with the same file structure, you can use this parameter to switch between them. For example, the value of `path` and `failDataPath` of the configuration below will be automatically changed to `./data/student.csv` and .`/data/err/student`. If you change `workingDir` to `./data1`, the path will be changed accordingly. The param can be either absolute or relative.|
 |`logPath`|-|No|Path for exporting log information, such as errors during import.|
 |`files.path`|-|Yes|Path for storing data files. If a relative path is used, the path is merged with the current configuration file directory. You can use an asterisk (\*) for fuzzy matching to import multiple files with similar names, but the files need to be the same structure.|
 |`files.failDataPath`|-|Yes|Insert the failed data file storage path, so that data can be written later.|
@@ -230,7 +229,6 @@ workingDir: ./data/
 |`files.csv.withHeader`|`false`|Yes|Whether there is a header.|
 |`files.csv.withLabel`|`false`|Yes|Whether there is a  label.|
 |`files.csv.delimiter`|`","`|Yes|Specifies the delimiter for the CSV file. A string delimiter that supports only one character.|
-|`files.csv.lazyQuotes`|`false`|No|If `lazyQuotes` is true, a quote may appear in an unquoted field and a non-doubled quote may appear in a quoted field.|
 
 #### Schema configuration
 
@@ -245,30 +243,29 @@ schema:
   type: vertex
   vertex:
     vid:
-      type: string
-      index: 0
+      index: 1
+      function: hash
+      prefix: abc
     tags:
       - name: student
         props:
-          - name: name
-            type: string
-            index: 1
           - name: age
             type: int
             index: 2
           - name: gender
             type: string
-            index: 3
 ```
 
 |Parameter|Default value|Required|Description|
 |:---|:---|:---|:---|
 |`files.schema.type`|-|Yes|Schema type. Possible values are `vertex` and `edge`.|
 |`files.schema.vertex.vid.type`|-|No|The data type of the vertex ID. Possible values are `int` and `string`.|
 |`files.schema.vertex.vid.index`|-|No|The vertex ID corresponds to the column number in the CSV file.|
+|`files.schema.vertex.vid.function`|-|No|Functions to generate the VIDs. Currently, we only support function `hash`.|
+|`files.schema.vertex.vid.prefix`|-|No|Add prefix to the original vid. When function is specified also, `prefix` is applied to the original vid before `function`.|
 |`files.schema.vertex.tags.name`|-|Yes|Tag name.|
 |`files.schema.vertex.tags.props.name`|-|Yes|Tag property name, which must match the Tag property in the NebulaGraph.|
-|`files.schema.vertex.tags.props.type`|-|Yes|Property data type, supporting `bool`, `int`, `float`, `double`, `timestamp`, `string`, and `geo`.|
+|`files.schema.vertex.tags.props.type`|-|Yes|Property data type, supporting `bool`,`int`,`float`,`double`,`string`,`time`,`timestamp`,`date`,`datetime`,`geography`,`geography(point)`,`geography(linestring)` and `geography(polygon)`.|
 |`files.schema.vertex.tags.props.index`|-|No|Property corresponds to the sequence number of the column in the CSV file.|
 
 !!! note
@@ -283,29 +280,28 @@ schema:
   type: edge
   edge:
     name: follow
-    withRanking: true
     srcVID:
-      type: string
       index: 0
+      function: hash
     dstVID:
-      type: string
       index: 1
+      function: 
     rank:
       index: 2
     props:
-      - name: degree
-        type: double
+      - name: grade
+        type: int
         index: 3
 ```
 
 |Parameter|Default value|Required|Description|
 |:---|:---|:---|:---|
 |`files.schema.type`|-|Yes|Schema type. Possible values are `vertex` and `edge`.|
 |`files.schema.edge.name`|-|Yes|Edge type name.|
-|`files.schema.edge.srcVID.type`|-|No|边的起始点ID的数据类型.|
 |`files.schema.edge.srcVID.index`|-|No|The data type of the starting vertex ID of the edge.|
-|`files.schema.edge.dstVID.type`|-|No|The data type of the destination vertex ID of the edge.|
+|`files.schema.edge.srcVID.function`|-|No|Functions to generate the source vertex. Currently, we only support function `hash`.|
 |`files.schema.edge.dstVID.index`|-|No|The destination vertex ID of the edge corresponds to the column number in the CSV file.|
+|`files.schema.edge.dstVID.function`|-|No|Functions to generate the destination vertex. Currently, we only support function `hash`.|
 |`files.schema.edge.rank.index`|-|No|The rank value of the edge corresponds to the column number in the CSV file.|
 |`files.schema.edge.props.name`|-|Yes|The Edge Type property name must match the Edge Type property in the NebulaGraph.|
 |`files.schema.edge.props.type`|-|Yes|Property data type, supporting `bool`, `int`, `float`, `double`, `timestamp`, `string`, and `geo`.|