-
Notifications
You must be signed in to change notification settings - Fork 446
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
Support duplicated mode in DynamicFragment #325
Conversation
maybe revise the parameter name.
|
5186c08
to
49bf390
Compare
186a880
to
5c7e275
Compare
5c7e275
to
422f6b1
Compare
b7447cf
to
83e6f65
Compare
Codecov Report
@@ Coverage Diff @@
## main #325 +/- ##
==========================================
- Coverage 77.37% 77.36% -0.02%
==========================================
Files 57 57
Lines 5300 5301 +1
==========================================
Hits 4101 4101
- Misses 1199 1200 +1
Continue to review full report at Codecov.
|
analytical_engine/core/vertex_map/dynamic_fragment_vertex_map.h
Outdated
Show resolved
Hide resolved
analytical_engine/core/vertex_map/dynamic_fragment_vertex_map.h
Outdated
Show resolved
Hide resolved
d663161
to
77a5600
Compare
according to our discussion: # by default, duplicated load
G = nx.Graph()
# or load a fragment, rather than a whole graph.
G = nx.Graph(dist=True) |
fc8b0d1
to
827a875
Compare
18afa1e
to
135244b
Compare
7f85bdf
to
ab6263a
Compare
hi, @yecol @sighingnow @pwrliang the refactoring of duplicated load of DynamicFragment is done. the pr needs you to review again. Thanks a lot. |
347661e
to
88c903a
Compare
What do these changes do?
DynamicFragment now support two type of graph storage mode.
if users want to use distributed mode to load graph, just init graph by
Related issue number
#317
TODO:
add new test case to check the add/delete/update is correct on all workers.(move to Add closeness_centrality app and test case of duplicated mode modification #336 )