You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug] The edge id is formatted by 5 instead of 4 parts #324
Hello @jiachengni! I'm here to help you with your bug and any questions you have while you wait for a human maintainer. Let’s tackle this together!
The issue you're encountering with the edge ID being formatted with five parts instead of the expected four is due to the structure of the edge ID in HugeGraph. The edge ID is typically composed of several components: srcVertexId, edgeLabel, sortKey, and tgtVertexId. However, the format can include additional parts such as sub-label-id and direction, leading to a five-part format [1][2].
The IllegalStateException during the execution of the LPA algorithm is likely caused by a mismatch between the expected edge ID format and the actual format used in the algorithm. The algorithm might be expecting a different format, possibly with four parts, which does not align with HugeGraph's edge ID structure [3][4].
To resolve this issue, you may need to adjust the algorithm's expectations or ensure that the edge ID format aligns with the expected structure. Additionally, check the configuration or logic in the WorkerInputManager and LoadService classes, as they might be contributing to the formatting issue [1].
The edge ID in Apache HugeGraph is correctly formatted with 5 parts for undirected edges and 6 parts for directed edges, not 4 parts. The IllegalStateException you're encountering is likely due to the LPA algorithm expecting an incorrect format of 4 parts. The edge ID format includes parts such as source vertex ID, direction (for directed edges), edge label ID, sort values, and target vertex ID [1]. You should adjust the LPA algorithm to handle edge IDs with 5 or 6 parts as per the EdgeId class specification.
Hey @imbajin! I'm a bot here to help with bugs, technical questions, and engineering knowledge. It looks like you're discussing server versions and edge structure changes in Apache HugeGraph. That's a bit outside my wheelhouse. If you think I should have more info on this, feel free to reach out to the Dosu Team. They'll know what to do! 😊
Activity
dosubot commentedon Apr 29, 2025
Hello @jiachengni! I'm here to help you with your bug and any questions you have while you wait for a human maintainer. Let’s tackle this together!
The issue you're encountering with the edge ID being formatted with five parts instead of the expected four is due to the structure of the edge ID in HugeGraph. The edge ID is typically composed of several components:
srcVertexId,edgeLabel,sortKey, andtgtVertexId. However, the format can include additional parts such assub-label-idanddirection, leading to a five-part format [1][2].The
IllegalStateExceptionduring the execution of the LPA algorithm is likely caused by a mismatch between the expected edge ID format and the actual format used in the algorithm. The algorithm might be expecting a different format, possibly with four parts, which does not align with HugeGraph's edge ID structure [3][4].To resolve this issue, you may need to adjust the algorithm's expectations or ensure that the edge ID format aligns with the expected structure. Additionally, check the configuration or logic in the
WorkerInputManagerandLoadServiceclasses, as they might be contributing to the formatting issue [1].To continue talking to Dosu, mention @dosu.
Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other
dosubot commentedon Apr 30, 2025
The edge ID in Apache HugeGraph is correctly formatted with 5 parts for undirected edges and 6 parts for directed edges, not 4 parts. The
IllegalStateExceptionyou're encountering is likely due to the LPA algorithm expecting an incorrect format of 4 parts. The edge ID format includes parts such as source vertex ID, direction (for directed edges), edge label ID, sort values, and target vertex ID [1]. You should adjust the LPA algorithm to handle edge IDs with 5 or 6 parts as per theEdgeIdclass specification.To reply, just mention @dosu.
Share context across your team and agents. Try Dosu.
imbajin commentedon Apr 30, 2025
@dosu @jiachengni
Please note the server version should < 1.5 due to the edge structure has been refactored in apache/hugegraph#2662 (I'll add a TODO for it)
PS: we need sync the EdgeID format to let it run well in the latest version
dosubot commentedon Apr 30, 2025
Hey @imbajin! I'm a bot here to help with bugs, technical questions, and engineering knowledge. It looks like you're discussing server versions and edge structure changes in Apache HugeGraph. That's a bit outside my wheelhouse. If you think I should have more info on this, feel free to reach out to the Dosu Team. They'll know what to do! 😊
To reply, just mention @dosu.
Share context across your team and agents. Try Dosu.