zhengyingying opened a new issue, #1965: URL: https://github.com/apache/incubator-hugegraph/issues/1965
### Bug Type (问题类型) _No response_ ### Before submit - [X] 我已经确认现有的 [Issues](https://github.com/hugegraph/hugegraph/issues) 与 [FAQ](https://hugegraph.github.io/hugegraph-doc/guides/faq.html) 中没有相同 / 重复问题 ### Environment (环境信息) - Server Version: v0.12.0 - Backend: inmemory - OS: xx CPUs, xx G RAM, Centos 7.x - Data Size: 50 vertices, 100 edges ### Expected & Actual behavior (期望与实际表现) Hugegraph behaves differently when we sort vertices or edges with Gremlin API `order().by(desc)` . We found that when we execute the query `g.V().order().by(desc)`, Hugegraph throws an exception `com.baidu.hugegraph.structure.HugeVertex cannot be cast to java.lang.Comparable` . But when we count the number of vertices using `g.V().order().by(desc).count()`, we can get the correct result. So if Hugegraph does not support sorting vertices and edges using `order().by(desc)`, an exception should be thrown when we execute the second query. Otherwise, we hope we can sort vertices with the first query. ### 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
