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

   ### 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.7.0
   - Backend: RocksDB x nodes
   - OS: 192 CPUs, 256 G RAM, Ubuntu 22.04
   - Data Size:  50 vertices, 100 edges
   
   ### Expected & Actual behavior (期望与实际表现)
   
   ### Expected behavior
   For the two query below, the same result should be returned:
   ```gremlin
   g.V().inE('el0').hasLabel('el0','el2').hasLabel('el1')
   
   
g.V().match(__.as('start1').repeat(__.inE('el0')).times(1).as('m1')).select('m1').hasLabel('el0','el2').hasLabel('el1')
   ```
   ### Actual behavior
   + The first query thrown a exception: ```java.lang.IllegalStateException: 
Illegal key 'LABEL' with more than one value: [1, 3]```
   + The second query returned the results normally.
   + We replaced the ```inE('el0')``` step in the first query with 
```match(__.as('start1').repeat(__.inE('el0')).times(1).as('m1')).select('m1')```,
 which should not affect the result.
   + When I executed these two queries on Janusgraph and Tinkerpop, they both 
returned the same results and were consistent with the results of the second 
query.
   + This issue was previously resolved in 
https://github.com/apache/incubator-hugegraph/pull/1737#issue-1109290490, but 
it has occurred again.
   
   ### Vertex/Edge example (问题点 / 边数据举例)
   
   ```javascript
   none
   ```
   
   ### Schema [VertexLabel, EdgeLabel, IndexLabel] (元数据结构)
   
   ```javascript
   none
   ```


-- 
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