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

fix query dirty edges of a vertex with cache #2166

Merged
merged 1 commit into from
Mar 14, 2023
Merged

Conversation

javeme
Copy link
Contributor

@javeme javeme commented Mar 13, 2023

fix #2163
Change-Id: I58b26f8a791885800e42821a3d4b2724f4e647a0

fix #2163
Change-Id: I58b26f8a791885800e42821a3d4b2724f4e647a0
@codecov
Copy link

codecov bot commented Mar 13, 2023

Codecov Report

Merging #2166 (bc70416) into master (31c6c6d) will increase coverage by 15.13%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             master    #2166       +/-   ##
=============================================
+ Coverage     53.71%   68.85%   +15.13%     
- Complexity      652      977      +325     
=============================================
  Files           488      488               
  Lines         40078    40076        -2     
  Branches       5607     5606        -1     
=============================================
+ Hits          21528    27594     +6066     
+ Misses        16284     9823     -6461     
- Partials       2266     2659      +393     
Impacted Files Coverage Δ
...ava/org/apache/hugegraph/structure/HugeVertex.java 78.16% <ø> (+0.54%) ⬆️

... and 168 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@imbajin imbajin merged commit 901da45 into master Mar 14, 2023
@imbajin imbajin deleted the edges-cache-fix branch March 14, 2023 09:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug] Turning off HugeVertexStepStrategy and LazyBarrierStrategy can return wrong query result
3 participants