simon824 opened a new issue, #311:
URL: https://github.com/apache/incubator-hugegraph-toolchain/issues/311

   ### Bug Type (问题类型)
   
   gremlin (结果不合预期)
   
   ### Before submit
   
   - [X] I had searched in the 
[issues](https://github.com/hugegraph/hugegraph-loader/issues) and found no 
similar issues.
   
   ### Environment (环境信息)
   
   - Server Version: v0.12.x
   - Loader Version: v0.12.x
   - Data Size:  xx vertices, xx edges <!-- (like 1000W 点, 9000W 边) -->
   
   
   ### Expected & Actual behavior (期望与实际表现)
   
   
   The option `batch.max_vertices_per_batch` default value is 500, if 
spark/flink default value of `batch_size` is bigger than 500 ,will cause the 
below exception.
   
   ``` shell
   class java.lang.IllegalArgumentException: Too many vertices for one time 
post, the maximum number is '500'
     at 
com.baidu.hugegraph.exception.ServerException.fromResponse(ServerException.java:47)
     at com.baidu.hugegraph.client.RestClient.checkStatus(RestClient.java:93)
     at 
com.baidu.hugegraph.rest.AbstractRestClient.post(AbstractRestClient.java:231)
     at 
com.baidu.hugegraph.rest.AbstractRestClient.post(AbstractRestClient.java:211)
     at com.baidu.hugegraph.api.graph.VertexAPI.create(VertexAPI.java:58)
     at 
com.baidu.hugegraph.driver.GraphManager.addVertices(GraphManager.java:96)
     at 
com.baidu.hugegraph.loader.spark.HugeGraphSparkLoader.flush(HugeGraphSparkLoader.java:253)
     at 
com.baidu.hugegraph.loader.spark.HugeGraphSparkLoader.loadRow(HugeGraphSparkLoader.java:150)
     at 
com.baidu.hugegraph.loader.spark.HugeGraphSparkLoader.lambda$null$0(HugeGraphSparkLoader.java:111)
   ```
   
   ### Vertex/Edge example (问题点 / 边数据举例)
   
   _No response_
   
   ### Schema [VertexLabel, EdgeLabel, IndexLabel] (元数据结构)
   
   _No response_


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to