fantengfeiNana opened a new issue, #2487:
URL: https://github.com/apache/incubator-hugegraph/issues/2487

   ### Bug Type (问题类型)
   
   gremlin (结果不合预期)
   
   ### Before submit
   
   - [X] 我已经确认现有的 [Issues](https://github.com/apache/hugegraph/issues) 与 
[FAQ](https://hugegraph.apache.org/docs/guides/faq/) 中没有相同 / 重复问题 (I have 
confirmed and searched that there are no similar problems in the historical 
issue and documents)
   
   ### Environment (环境信息)
   
   - Server Version: 1.0.0 (Apache Release Version)
   - Backend: RocksDB x nodes, HDD or SSD 
   - OS: xx CPUs, xx G RAM, Ubuntu 2x.x / CentOS 7.x 
   - Data Size:  xx vertices, xx edges <!-- (like 1000W 点, 9000W 边) -->
   
   
   ### Expected & Actual behavior (期望与实际表现)
   
   我们现在使用hugegraph1.2.0版本作为底层应用,当我们 
使用一个线程池并发执行g.V().count()【获取顶点个数】和.g.E().limit(9999)【获取所有的边集合】时,发现接口返回的数据与请求的预期不一致,导致进一步解析时无法正确解析,请问/gremlin接口是异步么,还是需要控制访问方式?直接现象就是g.E().limit(9999)
 返回的结果是 g.V().count()执行的结果
   当我使用自动化测试时,并发执行时,hugegraph也是偶现异常
   
![image](https://github.com/apache/incubator-hugegraph/assets/30856919/5748ec72-b407-46e4-879d-2a171593122b)
   
   
![image](https://github.com/apache/incubator-hugegraph/assets/30856919/130b6272-4d97-4999-9069-1fc5d796b7f1)
   
   请问我该如何解决此类问题?
   
   ### 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: dev-unsubscr...@hugegraph.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to