Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] edge-cache-clear should account for vertex update #1779

Closed
1 task done
javeme opened this issue Mar 10, 2022 · 0 comments · Fixed by #1780
Closed
1 task done

[Bug] edge-cache-clear should account for vertex update #1779

javeme opened this issue Mar 10, 2022 · 0 comments · Fixed by #1780
Labels
bug Something isn't working

Comments

@javeme
Copy link
Contributor

javeme commented Mar 10, 2022

Bug Type (问题类型)

logic (逻辑设计问题)

Before submit

  • 我已经确认现有的 IssuesFAQ 中没有相同 / 重复问题

Environment (环境信息)

  • Server Version: v0.12.0

Expected & Actual behavior (期望与实际表现)

edge-cache-clear should account for vertex update operations, since adjacency vertex lookups are affected by old adjacency vertex properties.

Consider adjusting to the following logic:
boolean invalidEdgesCache = this.edgesInTxSize() + updates.size() + Deletes.size() > 0;
https://github.com/hugegraph/hugegraph/blob/72baa123b135240476718f735c085577b761a970/hugegraph-core/src/main/java/com/baidu/hugegraph/backend/cache/CachedGraphTransaction.java#L367

Vertex/Edge example (问题点 / 边数据举例)

No response

Schema [VertexLabel, EdgeLabel, IndexLabel] (元数据结构)

No response

@javeme javeme added the bug Something isn't working label Mar 10, 2022
javeme pushed a commit that referenced this issue Mar 14, 2022
…ex (#1780)

* Fix the bug when vertex updated, but the edge cache associated with that vertex
   was not updated. Here we simply clear all edge cache when  any vertex changes.
* Add two test case for the fixing

fix #1779
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant